> Markdown version of [/jobs/ext/4672172-staff-software-engineer](https://www.wearedevelopers.com/jobs/ext/4672172-staff-software-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Staff Software Engineer - **Company:** Acuere Software LLC - **Location:** United States - **Contract:** Franchise - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Software as a Service, Data Governance, Data Migration, PostgreSQL, Node.Js, TypeScript, Virtual Agents - **Published:** November 11, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=c2b106eaf82db5cf ## About the Role * You've been the senior technical lead on a platform rebuild or major migration that reached production and affected real customers. * Deep experience designing multi-tenant SaaS on Postgres, including how tenancy is enforced and where it fails. * Enough TypeScript and Node depth to review and catch defects in agent-generated code, and strong opinions on typed API boundaries. * Comfortable reading legacy codebases in unfamiliar languages to establish behavior parity. * You've designed AI agent workflows or review gates that a team adopted, and you can tell us where they broke. * You write decision records people actually use, and you change your mind when the evidence says to. * You can explain a technical tradeoff to an executive in plain language. * Legally authorized to work in the US or Canada. ## Description We're rebuilding the ServiceMinder platform from scratch: a TypeScript modular monolith on Postgres, replacing the system thousands of franchise locations run their business on today. Our approach is agent-first: agents accelerate the build, while engineers set the direction, establish the guardrails, and own the result. We'll be solving problems like where module boundaries go, what the leger looks like, how tenancy is enforced and what does "correct" look like when old and new systems disagree. The pace of the whole program is set by how fast and how well these decisions are made. If you're looking to help own the technical direction of a cutting edge greenfield rebuild of a successful product: that's this job. You'll be one of the senior technical voices on the rebuild, partnering with our senior product and engineering leadership and the build team to make calls that hold up for the next decade, and to design the workflow that lets a small team build an entire platform., * Make the hard architecture calls. Module boundaries, data ownership, the ledger, tenancy enforcement, and the typed contract between services and clients. Write them down as decision records the team and the agents build against. * Design the factory's quality gates. Define the tests, evals, and automated review that decide whether agent-generated work ships, and tune them based on what gets through. * Own correctness across modules. Behavior parity with the current system, data migration and reconciliation, and a fall-forward cutover with no rollback. * Set the engineering standards. Observability, reliability targets, and definition of done for the program, set from measurement rather than guessed. * Treat AI spend as engineering. Model choice, routing, and cost are design decisions, and you'll make them that way. * Scale yourself. Most of your impact lands through others: the patterns, reviews, and decisions that make every engineer on the rebuild more effective.