Software Engineer

About DevGrid

We connect every system an engineering organization runs on (source control, cloud infrastructure, ticketing, asset ownership, vulnerability scanners, on-call) into one queryable model. Then we let AI agents and humans ask questions nobody can answer today: what's running where, what's about to go end-of-life, who owns the fix when a vulnerability lands, which apps share a dependency chain.

We're early-stage, with paying F500 customers, and we're chasing the context layer that AI engineering agents need to do useful work inside enterprise engineering organizations.

The Role

We're hiring an early-career software engineer to join our small team in Charlotte. The stack is Node/TypeScript, Python, and Go. On a typical week you'd be:

• Writing ingestion adapters that pull data from customers' engineering systems (source control, cloud infrastructure, ticketing, asset ownership, and more)
• Building APIs that AI agents query through MCP
• Building features in the web app (dashboards, search, configuration screens) where customers explore the graph and act on what they find
• Pairing with senior engineers on the normalization layer that turns 20+ data sources into one coherent graph
• Shipping code that runs against enterprise production systems, not toy datasets
• Owning small features start-to-finish in your first weeks, bigger ones as you ramp

Senior engineers pair with you on hard problems and review your code. Expect to be in the deep end early. You won't get ticketed to death or PR-reviewed into oblivion, and you'll see your work land in customers' hands within days.

Who we're looking for

This is an early-career role. More than anything else, we're hiring for high agency: the kind of person who looks at what needs doing, starts, and figures things out instead of waiting to be told. The right candidate has shipped something (a school project, a bootcamp capstone, a side project, or 0–2 years of professional work). We love bootcampers and self-taught engineers who can prove they ship.

You're a fit if you:

• Default to action: when something needs doing, you start it and flag what you can't figure out
• Have built something in Node and TypeScript and want to build a lot more
• Pick up new languages and stacks without too much fuss (Python and Go are part of the work)
• Think clearly about systems, data, and APIs
• Talk about technical problems out loud and can explain what you're doing and why
• Like being part of a tight team where pairing, code reviews, and real conversations happen often, virtually and in-person

How we work with AI

Shipping matters, token maxxing doesn't.

We use AI coding tools heavily (Claude Code, Cursor, whatever else gets the work done), and you will too, starting day one. You own the code that goes out under your name. You can defend the decisions inside it. Whether you or an AI wrote the first draft doesn't change that. If you've been holding off on AI tools because you wanted to learn "the right way" first, that hesitation isn't a fit. If you've been using them and have opinions about what works and what doesn't, even better.

Location Model

We're in Charlotte, NC and we co-locate frequently. Being in the same room makes us faster while we're early. If you're already in Charlotte, this works. If you're committed to fully remote, we're probably not a fit yet, and that's okay.

Compensation

$65,000 base salary, plus health benefits, and flexible time off.

How our hiring process works

1. You apply.
   Send a résumé to hello@devgrid.io or apply through this listing.
2. We review.
   We read every application and reply within a week. If we want to talk, we'll say so. If not, we'll say that too.
3. First call (30 min).
   Meet one of the co-founders. We tell you about the role; you tell us about your work and what you're looking for.
4. Technical conversation (1 hour).
   No LeetCode. We dig into how you think through problems out loud. Bring one you've actually worked on; we'd rather hear about that than do whiteboard puzzles.
5. Take-home exercise.
   A small build in a clean environment. Not a real-world problem, just a way to see how you work.
6. References and offer.
   We talk to your references, you talk to ours, and we make an offer with comp, equity, and a start date.

How to apply

Send a résumé to hello@devgrid.io. A few sentences about what you've been working on and why DevGrid clicked for you helps more than a cover letter.