Founding Engineer - Full Stack

Founding Engineer — Full-StackSan Francisco, CA · On-site 5 days/week · Full-time$200K–$300K base + 0.2%–1.0% equityThe companyThe company is building the unified AI operations platform for the physical economy: field services, transportation, retail, and manufacturing.The product is designed for enterprises that will run hundreds of AI agents across real operational workflows, not demo environments or single-step copilots.Those workflows are messy by default: email threads, spreadsheets, phone calls, ERP updates, proof-of-delivery checks, exception handling, and manager approvals.A broken workflow is not just a UX problem; it can mean missed ETAs, unverified proof of delivery, or stale system-of-record updates.The company launched in November 2025 and already has 6 active customers in production, with multiple multi-million-dollar deals and late-stage conversations with $1B+ and $2B+ enterprise accounts.It is backed by a $15M seed round from Base10, with a team of 10 people and 4 engineers today scaling toward roughly 10.The CEO previously co-founded Motive and scaled it from $0 to $500M ARR and a $5B valuation.The CTO built products and teams at Facebook Messenger, Airbnb, and Discord, including core messaging, voice, video, and gaming systems.The company exists to replace a heavy services-led deployment model with software that non-technical teams can actually operate themselves.The roleThis is a founding full-stack role for an engineer who wants to own the systems behind enterprise AI agents end to end: agent orchestration, browser automation, voice, enterprise integrations, and the frontend surfaces that make all of it usable.The expected split is roughly 70% backend, 30% frontend, but the real requirement is ownership: take a customer problem, turn it into a product decision, ship the system, and harden it in production.You will report to the CTO and work directly with a small founding team. There is no heavy PM layer between you and the customer problem.This is a role for someone who wants scope, not tickets.The technical problemThe hard part is not building an AI wrapper around a workflow.The hard part is making agents reliable enough to do real work across fragmented enterprise systems, long-running tasks, and partially structured human processes.That means dealing with stateful orchestration, retries, recovery, partial failure, idempotency, system boundaries, access constraints, and interfaces that stay understandable for non-technical operations teams.The product has to hide system complexity without hiding control.What you'll own• Core agent platform capabilities: build and harden the primitives behind voice, browser automation, and multi-agent orchestration for enterprise workflows that can span days.• Workflow execution: design the state management, retries, recovery paths, and failure handling required for long-running production tasks.• Enterprise integrations: reverse-engineer customer systems and connect the platform to tools such as Salesforce, Outlook, TMS, and ERP systems.• End-to-end feature ownership: take a problem from customer conversation to shipped production code, including requirements, implementation, validation, and iteration after launch.• Customer-facing product development: spend 5–20% of your time with customers, understanding how their operators work and turning that into better platform decisions.• Frontend experiences: ship React interfaces that make complex agent workflows inspectable, controllable, and usable by enterprise operations teams.• Architecture and technical direction: help decide how the platform should evolve as usage, integrations, and customer requirements expand.Who this is forYou are likely a strong fit if you have:• Already shipped meaningful systems end to end, not just contributed to components owned by other people.• Comfort working across backend and frontend, with enough React depth to ship production-quality operator workflows.• Experience with orchestration, integrations, async systems, automation, or other products where reliability matters more than a clean demo path.• Strong judgment around state, failure modes, data consistency, and what should be abstracted versus exposed.• The ability to talk to customers, identify the real workflow, and turn that into a technical plan without waiting for a spec.• Comfort working in a small team where architecture, implementation, and product thinking happen in the same conversation.• High standards for shipping quality, especially when the product touches enterprise operations and external systems.• The ability to move quickly without losing rigor.• Already operated at senior/staff scope and want direct ownership over product, architecture, and customer outcomes rather than a ladder-driven role.This role is open to engineers with 3+ years of experience, or 2+ years at VC-backed startups, if they have already shown unusually strong ownership.Tech focus and environment• Frontend: React• Product surface: enterprise operator workflows and agent control interfaces• Integration surface: Salesforce, Outlook, TMS, ERP, and adjacent enterprise systems• Working model: in-office, 5 days per week, at 10th & Market in San FranciscoThe technical surface is still being shaped by the founding team. The bar is not familiarity with one framework or one service. The bar is making good technical decisions in a system that has to work for real customers.Why this role exists nowThe product is already in production with real customers, which means the next constraint is no longer whether the idea works.The constraint is whether the platform can scale from early customer success into a repeatable enterprise system that supports more agents, more workflows, and more integrations without becoming brittle.The company is also explicitly trying to avoid the heavy forward-deployed engineering model that most AI companies use to compensate for product gaps.The founding engineer in this seat will shape the architecture while it is still small enough to get right.This role is not for you if• You want a narrow feature backlog and clearly specified tickets.• You do not want to work directly with customers.• You prefer a pure frontend or pure backend role.• You are uncomfortable making architecture decisions in ambiguous environments.• You do not want an in-office role in San Francisco.• You are not interested in enterprise systems, operational workflows, or integrations.Compensation and logistics• Base salary: $200K–$300K• Equity: 0.2%–1.0%• Location: San Francisco, CA• Work model: on-site, 5 days per week• Visa sponsorship: not available• Employment: full-timeAbout AuroraAurora helps exceptional engineers find the right role at some of the most ambitious startups worldwide.We work with teams that value high ownership, strong technical standards, and clear scope.