An application made for this job — a tailored resume and cover letter that speak straight to the posting.
SuiteOp Inc. is seeking a senior individual-contributor engineer who is exceptionally good at building with AI.
You will own end-to-end features across a TypeScript monorepo—schema migrations, backend services, and typed frontends—often in a single PR. You will ship across multi-region, data-residency-sensitive products, integrate with real-world systems, and shape AI workflows and guardrails to ensure reliable AI-assisted development.
You are an engineer who happens to be exceptionally good at working with AI. Not an ML researcher, not a prompt engineer — a builder. You will spend your days in the codebase, shipping production features across the full stack: a schema migration, the backend service that reads from it, and the typed frontend that renders it, often in a single PR.
You will use AI coding tools as force multipliers — to scaffold, debug, refactor, and ship at a pace that would not otherwise be possible. The work is yours end to end. You own the features you build and their failure modes, from the database row to the screen an operator depends on during a turnover.
This is a senior individual-contributor role with no people management and no direct reports. You will influence the codebase the way the strongest senior engineers do — through the quality of what you ship, sharp code review, and architectural decisions that hold up over time — not by managing a team. The surface area is significant, and you will own a meaningful share of it.
TypeScript end to end, in a strict monorepo.
A modular backend, a modern App-Router web app, an offline-first mobile app, and an edge layer for public-facing surfaces. Managed Postgres with row-level security and an ORM that owns the schema. Background jobs on a managed queue. End-to-end type safety from database row to frontend form, validated by a single shared schema layer.
We deliberately favor managed platforms over primitives, so the team spends its time on product rather than infrastructure.
You would join mid-rebuild, the most consequential moment in the company’s lifecycle. The clean-room architecture is being laid down right now. You will not inherit a legacy system; you will help build the one that replaces it — and the product it powers already runs the daily operations of operators managing large portfolios. The patterns you set in the slices you ship — how a migration is structured, how a service is wired, how types flow from the database to the form — become the patterns the next engineer reaches for. This is foundational work, and it carries the kind of influence you earn only by building.