Senior Full Stack Engineer (Remote)

The Role

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.

What You'll Do

• Ship full vertical slices across a TypeScript monorepo — schema migration, backend service, frontend component — in a single PR, with end-to-end types holding the slice together
• Drive the rebuild through its remaining phases, including the web dashboard, admin surface, mobile app, and a public API
• Integrate with the messy real world: property management systems, smart locks, payments, and a high-frequency telemetry pipeline
• Raise the quality bar by example — through the code you ship, the reviews you give, and the patterns you leave behind for the next engineer
• Shape how we work with AI: the workflows, guardrails, and standards that make AI-assisted development reliable and repeatable, not lottery-ticket development

Our Stack

• TypeScript end to end, in a strict monorepo
• A modular backend
• A modern App-Router web app
• An offline-first mobile app
• An edge layer for public-facing surfaces
• A managed Postgres with row-level security and an ORM that owns the schema
• A background jobs on a managed queue

How We Work

• Small team, high ownership
• You own features end to end, including their failure modes
• AI-first development, structurally
• The codebase is deliberately built for AI comprehension: narrow module boundaries, strict types, schema-first data flow
• AI tooling is part of the dev loop, not a side project
• Types over tests, but tests where it counts. End-to-end type safety catches most bugs at compile time
• Real engineering hygiene. No `any`, no silenced warnings, no logic in controllers, no auto-save forms
• Async-first. Decisions happen in writing so they outlast the meeting, and so strong engineers can do their best work on their own schedule