Senior Software Engineer

Join our team as a Senior Software Engineer, where you'll play a crucial role in shaping our product and engineering practices. You'll work closely with the founders, early customers, and a small senior team to deliver major features to production every week. Your responsibilities will include prototyping new workflows, designing core systems, and optimizing performance and stability. You'll have the opportunity to work on a variety of tasks, from AI agent development to data ingestion pipelines and CI/CD foundations. This is a hands-on role for builders who want to own features end-to-end.

• Ownership of large surfaces of the product, including schemas, services, agent loops, and UI, alongside the founders and a small senior team.
• Prototyping new workflows against live customer feedback and designing core systems that must remain correct, performant, and maintainable.
• Contributing to the development of AI agents that explore a project's design space, ingestion pipelines for public utility data, and performance optimization in the simulation engine.
• If you have (1) and (2) but are still ramping on (3), we'll teach you. The reverse isn't true
• Engineering fundamentals. (1) ~5-7 years shipping production software, with meaningful time at a startup that grew through a real scaling phase. You learned to engineer before LLM coding tools existed. You read code, debug live systems, and reason about performance, scalability, and maintainability without leaning on autocomplete. This is the bar
• AI-native workflow. (3) You use Claude Code, Cursor, or similar agentic tooling every day, not because we told you to, but because you've internalized that these tools are a force multiplier when paired with strong fundamentals (and a foot-gun without them). You know what to delegate, what to review carefully, and where the tools fall down
• End-to-end product instinct. (2) You can hold a Pydantic schema, a React component, and a customer's planning constraint in your head at the same time, and ship the right tradeoff between them. You write clearly enough that a teammate in a different timezone can pick up where you left off without a meeting
• Domain background in a science or engineering field (bio, chem, physics, ME, ChemE)
• Production experience shipping LLM-powered features