Founding Engineer

About us
Engineering teams now run many coding agents at once, and all of that parallel work eventually has to come together. We're building a merge queue for that world. Instead of looking at where text overlaps, we model how changes across pull requests actually interact, resolve independent conflicts in parallel, and prepare each pull request against the code that main is about to become, so work lands cleanly. Teams keep their agents, their existing Git workflow, and their required checks and reviews. The core of this is a code graph engine we're building in-house in Rust. We're early, in stealth, and working with our first design partners. We'll share more

about the company
once we're in conversation. The role You'll work on the hardest part of the product: generating accurate code graphs across languages, and making the system that uses them fast and reliable in production. That means reading language specs and compiler internals, deciding what a useful graph representation is for a given language, and getting it to work on real repositories that don't build cleanly. This is a small team, so you'll also own what you ship: the services around the engine, the cloud infrastructure they run on, the monitoring that tells us when something is wrong before a customer does, and the dashboard our users actually look at.

What you'll do
• Design and build code graph extraction for languages that existing tooling doesn't cover, including the intermediate representation, the resolution of symbols and references, and incremental updates as repositories change.
• Work on the graph engine itself: performance, memory behavior, correctness on large and messy codebases, and the analysis that determines how changes interact.
• Build and operate the services around it, including the Git and CI integrations, the APIs, and the orchestration that resolves conflicts in parallel.
• Own deployment and reliability end to end: infrastructure as code, deployment pipelines, and observability that surfaces real problems rather than noise.
• Build the frontend our users work in, including the dashboard. You don't need to be a design specialist, but you should be able to take a feature from the engine all the way to a usable interface.
• Carry production on-call with the rest of the team, and respond to customer issues quickly during pilots.
• Work directly with design partners. You'll hear what's broken firsthand and decide, with the team, what's worth building. What we're looking for
• Strong systems engineering experience, with production work in Rust and Go, or deep experience in comparable systems languages and the ability to be productive in both quickly.
• A real understanding of code graphs on a systems level: ASTs, control and data flow, call graphs, symbol resolution, and the tradeoffs in representing them at scale.
• Familiarity with code intelligence and program analysis tooling such as Joern and code property graphs, SCIP, Graphify, tree-sitter, LSIF, or compiler frontends and language servers. We care that you understand how these systems work and could build one, not that you've used these specific tools.
• Experience shipping and running software in production: cloud architecture, containers and orchestration, CI/CD, infrastructure as code, and observability through metrics, tracing, logging, and alerting that actually catches failures.
• Product judgment. You can look at a customer request and reason about whether it's worth building, what it costs, and what it means for everyone else using the product.
• Comfort with ambiguity and early-stage pace. Specs will be thin, priorities will shift, and you'll often be the person who decides how something should work.
• Comfort working across the stack. You can build and maintain production frontend code, typically TypeScript and Svelte, and you're willing to own a feature end to end rather than handing the UI to someone else.
• Fluency with agentic coding tools such as Claude Code, Cursor, or Codex. We use them heavily, and we're building for teams that do too. We want someone who runs several agents in parallel as a matter of course, has opinions about where they help and where they don't, and knows what it's like to clean up after them. Nice to have
• Experience with Git internals, merge algorithms, CI systems, merge queues, or developer productivity tooling.
• Compiler, static analysis, or program analysis background.
• Experience building language frontends, parsers, or language servers.
• Work on large monorepos or at the scale where incremental analysis becomes necessary.
• Open source contributions in any of the above. If you're strong in most of this but not all of it, we'd still like to hear from you. What the pace is actually like We want to be straight with you about this, because it's the kind of thing people should opt into knowingly rather than discover later. We're pre-launch with design partners depending on us, so this is an intense environment. Priorities move quickly, scope changes, and there are stretches around launches and partner onboarding where the work gets heavy. Everyone on the team shares a production on-call rotation, which means being reachable outside normal hours when something breaks. We aim to respond to customers faster than they expect, and that expectation applies to all of us, founders included. What we're looking for is ownership: when something is broken or a customer is blocked, you deal with it rather than waiting for someone to assign it. If you'd rather work somewhere with clearly bounded scope and predictable hours, this isn't the right fit right now, and that's a reasonable thing to want. Compensation and benefits The base salary range for this role is $150,000 – $300,000 per year + equity. This is our good-faith estimate of what we expect to pay at the time of posting. Where an offer falls in the range depends on job-related factors such as the depth and relevance of your experience and the scope you take on. Equal opportunity We are an equal opportunity employer. We do not discriminate on the basis of any status protected by federal, New York State, or New York City law. That includes actual or perceived race, color, religion or creed, national origin, sex, gender (including gender identity and expression), sexual orientation, age, disability, pregnancy, sexual and reproductive health decisions, marital or partnership status, familial status, caregiver status, immigration or citizenship status, military or veteran status, genetic information or predisposing genetic characteristics, height, weight, arrest or conviction record, credit history, salary history, unemployment status, or status as a victim of domestic violence, sex offenses, or stalking. We will consider qualified applicants with arrest and conviction records in accordance with the New York City Fair Chance Act and New York State law.