Senior Engineer
The short version
You're a senior engineer who never stopped loving the build. You've spent years shipping real software for real companies, and somewhere along the way you got fast, and then you got good, which is the harder one. You reach for AI tools the way you'd reach for any power tool: constantly, and with a healthy suspicion. You know the thing that compiles isn't the same as the thing that's done.
You don't need to run the client. You don't want to spend your week in steering committees. You want hard problems, room to solve them, and a high bar for what ships. We built a role for that.
What this actually is
The Senior Engineer is the building core of an engagement. Not a junior taking tickets. Not a contractor on a separate track, handed scraps and kept away from the client. A senior engineer who works alongside a Conductor and a set of AI agents, owns a real slice of the work, and ships production software.
Here's the division of labor. The Conductor owns the architecture, the client relationship, and the outcome. You own the craft of the implementation: the code, the tests, the edge cases, and the judgment call about whether a thing is actually ready. On the pure engineering, your day can look a lot like a Conductor's. The difference is the scope of what you carry, not the depth of what you know.
That's the honest version. Some of our senior engineers are on the path to becoming Conductors and want the client and ownership scope eventually. Others are exceptional builders who'd rather go deep than go wide, and have no interest in running a steering call ever again. Both are first-class here.
What you'll do
Build production software
Take features and systems from spec to shipped. Own the implementation, including the high-complexity parts: the integration that touches four systems, the migration with thirty years of legacy quirks, the performance path that has to hold under real load. AI handles the boilerplate. You handle the parts that need a person.
Exercise judgment, constantly
The defining skill of this job is knowing when AI-generated output is production-ready and when it's quietly wrong. AI made it faster to write good code and just as fast to write bad code. The bar for craft didn't drop when the tools got good. It rose. You're the reason a fast engagement is also a safe one.
Build against the architecture, and push on it
A Conductor sets the technical direction in ADRs and specs. You build against it without needing someone over your shoulder, and when you see a better path or a flaw in the plan, you say so. Good architecture survives contact with the engineer implementing it.
Communicate like a consultant
You give clear updates, flag risks and blockers before they turn into fires, and represent MiT well when you're in a room with the client's team. You won't own the client relationship, but every interaction you have with a client is the client's view of all of us.
Make the team better
Review pull requests with care. Share what you know. Help us vet the next engineer. The people doing the work are the best judges of who else can do it.
You're probably a fit if...
You've been building production software for years and you still like it. You're fluent with AI-assisted development and use it every day, but you treat the output as a draft, not a verdict. Hand you a spec and an architecture, and you'll turn it into working software without needing to be watched. You reason about edge cases, failure modes, and the difference between "passes the test" and "actually correct." You write code other people can read. You take ownership of your slice and flag the thing nobody else noticed.
And you're at peace with letting someone else own the client and the architecture, because it frees you to do the part you're best at. Whether you want to grow into a Conductor someday or stay a builder for your whole career, there's a seat here.
You're probably not a fit if...
You need a fully specified ticket before you can move, and you stall without one. You think AI output is done the moment it runs. You want to own the architecture and the client relationship right now, today, in which case we'd rather talk to you about the Conductor role. You see tests and code review as red tape. Or your sense of yourself needs the "lead" badge on every project.
Those are all reasonable ways to be. This particular seat just isn't built for them.
We care far more about how you build and how you judge than about a specific stack or a specific number of years.
Most of our senior engineers have at least five years of professional experience, and plenty have a decade or more. That said, here's what we look for.
Core (non-negotiable)
Years of professional experience shipping and maintaining production software, not just prototypes
Fluency with AI-assisted development workflows, and the judgment to know when to trust the output and when not to
Strong command of at least one language and framework, with the range to pick up others quickly
Solid engineering fundamentals: meaningful test coverage, real error handling, sound data modeling, and an awareness of security basics like the OWASP Top Ten
The autonomy to build against a spec and an architecture without constant supervision
Clear written and verbal communication, with technical and non-technical audiences alike
Preferred (genuinely preferred, not secretly required)
Experience in consulting, professional services, or other client-embedded engineering roles
Depth in one or more of our core areas: application development, data engineering, cloud infrastructure, or AI/ML systems
Background in any of our target verticals: manufacturing, insurance, energy/utilities, healthcare, and logistics
A track record of mentoring other engineers and raising the bar on a team
An interest in eventually growing into a Conductor role (genuinely optional, not the expected path)
What we explicitly don't require
A computer science degree, or any particular degree. Mastery of our exact stack. The title "lead" on your resume. A LinkedIn profile full of consulting buzzwords. We'll teach you our patterns. We can't teach judgment, and you already have it.
We don't believe in a single ladder everyone has to climb.
Some senior engineers grow into Conductors when they want to own the client relationship and the architecture, and we sponsor that growth deliberately.
Others get deeper and more valuable as builders year over year, and that's a real career here, not a holding pattern. We meet you where you want to go.
Interested? Tell us about yourself.
No cover-letter template, no trick questions. Tell us who you are, what you've built, and why this role caught your eye. A real person reads every application, and a real person will respond.