Working in developer tools as an engineer

Developer tools is one of the few corners of the industry where the person building the product is also the person who uses it. That single fact explains most of what makes devtools a magnet for strong engineers: tight feedback loops, technically deep work, and coworkers who hold the bar high because they would notice a bad API immediately. The comp sits close to general software roles in San Francisco and New York, the culture skews craft-first, and the main risk is narrow rather than large. This post covers who is hiring, what the work and pay actually look like, and the one trap to check before you take the offer.

What counts as developer tools?

Devtools is software whose customer is another engineer. The category is wider than it first looks. It runs from languages and runtimes through the whole path code takes to production and back.

• Build, test, and CI/CD. Compilers, bundlers, test runners, build systems, pipeline tooling.
• Cloud and infrastructure. Databases, queues, container platforms, infra-as-code, internal developer platforms.
• Observability. Logging, metrics, tracing, error tracking, incident tooling.
• Developer experience. IDEs, editors, code review, version control hosting, package registries.
• API and data infrastructure. API gateways, data pipelines, vector stores, the plumbing under AI and LLM products.

If you have used Postgres, Datadog, GitHub, Vercel, Stripe, or a CI runner this week, you have used devtools. The point of the category is that the buyer reads documentation, files issues, and judges you on whether the abstraction holds.

Why does devtools attract strong engineers?

Three reasons keep showing up, and none of them are about the mission slides.

1. 01You are your own user. You feel the bug before a customer reports it. The gap between writing code and knowing whether it is good is hours, not quarters. That loop is rare outside devtools and it is the thing senior engineers miss most when they leave.
2. 02The problems are genuinely hard. A query planner, a distributed scheduler, a language server that stays fast on a million-line repo. These are the problems people who like platform and infrastructure work want to spend years on.
3. 03Your peers are the bar. When your customer is an engineer, you cannot ship a sloppy API and hide it behind a marketing page. The product is the interface, so the team that builds it tends to care about interfaces.

In devtools the gap between writing code and knowing whether it is good is hours, not quarters.

The flip side is that bottom-up devtools companies are often slower to monetize. Engineers love the product, adopt it for free, and the revenue conversation happens later and higher up. That changes how you should read a company's funding and runway, which we get to below.

What does devtools pay?

Cash comp for devtools engineers tracks the broader market closely. There is no devtools discount and no obvious premium either. What moves the number is level, city, and whether the company is venture-backed and recently funded or already at scale. The ranges below are illustrative for SF and NYC base plus typical cash bonus, not advice, and equity sits on top.

The split that actually matters is not devtools versus other sectors. It is scaled devtools versus early devtools. A platform company past its Series C pays cash like big tech and gives you a small grant. A founding engineer at a seed-stage devtools company takes a haircut on cash for a percentage point of the company. Both are devtools. They are different jobs. Decide which trade you are making before you compare offers, and read startup versus big tech if you are weighing the cash side honestly.

Who is hiring in devtools right now?

Hiring in the category clusters around two engines in 2026. The first is AI infrastructure: vector databases, model-serving platforms, evaluation and observability for LLM apps, and the agent tooling layer. The second is the steady demand for the boring, load-bearing stuff: databases, CI, observability, and internal developer platforms that every other company depends on.

The most useful way to spot who is actually staffing up is to watch funding. A devtools company that just closed a round has approved headcount and an urgent plan, which is exactly why the roles.cc board sorts every role by how recently the company raised. You can scan recent raises directly, and for the mechanics of why a fresh close is the cleanest hiring signal, see why funding recency is the best signal.

What is the one risk specific to devtools?

The niche risk is concentration, and it has two faces. First, technical: deep devtools expertise is portable across companies but only within the category. Years spent on a compiler or a query engine make you very hireable at the next infra company and less obviously so at a consumer product shop, where the day-to-day is different. That is fine if you love the work. It is a cost if you might want to switch.

Second, market: bottom-up devtools companies often have love long before they have revenue. A product engineers adore can still struggle to convert that into a paid contract, and the gap between adoption and dollars is where devtools startups stall. So when you evaluate a devtools offer, ask harder than usual about who pays, how much, and how often. Free users are not a business. The standard offer-evaluation work in how to evaluate a startup job offer applies, with extra weight on the revenue question.

• Ask about paying customers, not signups. How many companies pay, and what is the average contract? Adoption without revenue is a warning, not a moat.
• Ask how the free tier converts. If the answer is vague, the monetization plan probably is too.
• Check the runway against the burn. A devtools company that monetizes late needs more runway to get there. Map the funding stage to a realistic timeline.
• Confirm the work is the work you want to stay portable in. Infra depth is a great bet if infra is where you want to be for the next decade.

None of this should scare you off. The risk is specific and checkable, which is the best kind. A strong devtools company with real revenue and a fresh raise is one of the better places an infrastructure-minded engineer can work, full stop.