You build applications. Real ones, with users, that have to keep running long after the first version shipped. Most of our data and AI work eventually needs software around it before anyone can use it, and that software has to be built properly, by someone who has done it before.
What you'll work on
Web applications, internal tools, integrations into the systems clients already run on (ERPs, CRMs, the rest), and the products that turn an AI prototype into something a client can actually put in front of their teams. Front end where people meet the work, back end where the logic and the data live, infrastructure when it touches the cloud.
You'll also look after what we've already built: keeping it current, refactoring when it's earned, paying down debt before it turns into the expensive kind. Different client, different domain, often in the same week.
What you bring
Real experience building software, and not just your first or second project. You know how an application fits together end to end: how a request travels from the front end through the API to the database and back, where state lives, where things buckle under load. Front end (a modern framework like React or Next), back end (APIs and data models), and the architecture that holds the two together. At least one language you know deeply: TypeScript, Python, C#, whichever you reach for first.
The whole lifecycle is second nature, not just the writing-code part: requirements, design, build, test, deploy, and the long tail of keeping it alive. You can look at a system and point to where next year's problem is hiding. You write code other people can read and maintain, you think about tests, and you care about the parts nobody demos (logging, error handling, observability) because they are what keep software standing in production.
How we work
We're spec-led. Before we build, we write a proper functional analysis: what it does, for whom, and how we'll know it works. We follow a disciplined lifecycle with testing built in from the start, and we build alongside the client's own developers, so the people who'll maintain it have been writing it from day one.
We also code as agentically as we can. Claude Code, Cursor, Copilot, whichever tool fits. It makes a good engineer faster. It does not make someone an engineer. The judgment about what to build, how to structure it, and what "done" actually means still comes from you. If you already work this way, great. If you don't yet, you'll pick it up here.
What you'll get
A team that takes craft seriously and respects experience. Real ownership, a personal growth plan with your name on it. Competitive pay.
Read the Plainsight playbook for the longer version of how we work.