Careers at AppAxis
We're looking for the unreasonably good.
Not “good for a startup.” Not “good with potential.” Actually, demonstrably, unreasonably good at building software for industries where getting it wrong has real consequences.
We're a small team. Every person we add changes the company. So we're careful. Probably annoyingly careful. But the people who make it through tend to like it here — because they're surrounded by people who are just as obsessive about their craft as they are.
A note about our hiring bar.
We built AppAxis on a simple premise: the best software for specialized industries comes from people who are both elite engineers and genuine industry experts. Not one or the other. Both.
That's a narrow intersection of humans. We know. It means we hire slowly, sometimes painfully slowly. We'd rather have an open role for six months than fill it with someone who's merely excellent at half of what we need.
Our clients trust us because every person on our team has done real work in their industry — not just read about it. When you join AppAxis, you're joining a team where nobody is faking it and everyone can hold a conversation three levels deeper than the person in the room expects.
If that sounds exhausting, it's probably not for you. If it sounds like the team you've been looking for your entire career, keep reading.
Open Roles
Two roles. Two very different skill sets. One shared requirement: you have to be someone our clients would want in the room.
Product Engineer
Remote (US) · Full-time
The person who ships the thing and decides what the thing should be.
Most companies split product management and engineering into separate roles. We think that's a mistake — at least for the kind of work we do. Our Product Engineers own the entire lifecycle: talking to clients, understanding the domain problem, designing the architecture, writing the code, and shipping it to production. You're not handing a spec to someone else. You are the spec. And the implementation. And the person who answers the phone when something breaks at 2 AM (though our systems rarely break at 2 AM, because you built them well).
This might be you if…
- You've shipped production systems in at least one of our industries — not just written code for them, but understood why the code mattered to the business
- You can stand up a Supabase or PostgreSQL schema, a Next.js frontend, and a deployment pipeline, and you don't need someone to tell you which order to do them in
- You've run a product discovery call with a client and come back with a plan that engineering, design, and business all agree on — because you are all three
- Your GitHub profile looks like a person who actually builds things, not a person who stars repos
- You've read an RFP, a regulatory framework, or an industry spec sheet and thought "I could build something better than what they're asking for"
Probably not for you if…
- You need a product manager to tell you what to build
- You think "full-stack" means you've used both React and Node
- You haven't shipped anything to production in the last 12 months
- You're primarily interested in title progression rather than craft progression
Industry Strategist
Remote (US) · Full-time
The person who's already lived the problem our clients are trying to solve.
We don't hire consultants who've read about industries. We hire people who've operated inside them. Our Industry Strategists have run operations, managed P&Ls, led teams, or built products in the industries we serve. You've sat in the meetings where the real decisions happen. You know why the ERP migration failed. You know which compliance requirement actually matters and which one is theater. You translate between "what the client says they want" and "what will actually move the needle." This isn't a coding role — but you need to be technical enough to earn the respect of the engineers in the room and dangerous enough to know when a proposed architecture won't survive contact with reality.
This might be you if…
- You've held an operational or leadership role in healthcare, manufacturing, financial services, construction, field services, law, IoT, or government
- You can explain a complex industry workflow to an engineer and a complex technical tradeoff to a CEO — in the same meeting
- You've been the person who said "that's not how this industry actually works" and saved a project from expensive failure
- You have opinions about why most industry software is terrible, and those opinions are informed by years of being forced to use it
- You can look at a system architecture diagram, an API spec, or a data model and have an informed opinion — you don't write the code, but you can tell when the code is solving the wrong problem
Probably not for you if…
- Your industry experience is limited to reading analyst reports
- You think strategy means making slide decks
- You've never been accountable for a P&L, an operational outcome, or a shipped product
- You describe yourself as a "thought leader" without irony