Senior Backend Engineer (Full) [33068] Full Time NEW

About us

The company is building the execution engine for home services, starting with cleaning.

We make work inside the home deterministic by defining duration and execution—replacing arrival windows, variable scope, and “it depends” with certainty.

Our advantage compounds: the reliability system is learned through real in-home execution and encoded into software. The result is a service customers trust, and a data advantage competitors can’t shortcut.

How We Work

Everyone at the company operates inside a custom AI-native operating system. AI handles briefings, task management, and synthesis. You bring judgment, systems thinking, execution, and speed.

We move fast and we work hard. Expect long hours, nights, and weekends. If you’re optimizing for work-life balance, this isn’t the place for you. If you want to build a category-defining company, you’ll love it here.

We are looking for ambitious builders who want to build a category defining company.

The Role

As Senior Backend Engineer, you own the spine — the core backend systems that power execution reliability, scheduling, and logistics.

Company’s competitive advantage is deterministic execution. The execution engine that makes this possible is your domain. You ensure these systems scale cleanly as revenue and job volume double, and you protect the invariants that make our execution layer trustworthy.

This is a senior, system-level ownership role. Not a ticket executor, not a pure API builder, not a feature-only engineer.

What You’ll Own

→ Scheduling, assignment, and logistics systems

→ Provider performance and capacity modeling

→ Model integration (pre-ML and ML stages)

→ State transitions and idempotency guarantees

→ API architecture across mobile, web, and ops

→ Event emission and data integrity

→ Background processing, retries, and queues

→ Infrastructure reliability and observability

What “High Agency” Means in This Role

You can take an ambiguous problem like “reduce schedule breakage” and turn it into system design, implementation, instrumentation, metrics, and an iteration plan — without being told how.

• Proactively identifies architectural weaknesses before they break at scale
• Writes design docs without being asked
• Thinks in invariants, not just features
• Comfortable owning production systems with real-world consequences

Outcomes in First 6 Months

→ Establish clear ownership of the execution engine

→ Improve system observability and monitoring coverage

→ Reduce scheduling breakage or operational incidents

→ Document and enforce core system invariants

→ Deliver an architecture that supports multi-city expansion without rewrites

What Success Looks Like After 12 Months

• Backend supports multi-city expansion without architectural rewrites.
• Execution error rates are materially reduced.
• The system can absorb 2x volume without structural stress.

What We’re Looking For

We value demonstrated ownership and shipped systems over logos or credentials.

Must-Haves (non-negotiable)

• Strong experience in Python backend systems (Django, FastAPI, or similar frameworks)
• Experience designing and maintaining event-driven or asynchronous systems
• Deep understanding of: transaction management, idempotency, concurrency, and data modeling in relational databases (Postgres preferred)
• Experience with background workers / queues (Celery, SQS, etc.)
• Comfort with AWS infrastructure and production observability
• Experience instrumenting systems for analytics and ML pipelines
• Strong testing discipline (unit + integration + scenario testing)
• AI-native builder: You use AI as a force multiplier — accelerating exploration, testing, and refactoring — but you deeply understand the systems you ship.

What Makes Someone Exceptional Here

• Has built or maintained logistics, scheduling, or operational systems
• Has seen production systems fail and knows how to design for resilience
• Thinks about performance and scaling early
• Understands tradeoffs between elegance and reliability
• Can reason about how backend decisions impact real-world operations

What This Is (and Isn’t)

This is not a role for someone optimizing for strict boundaries. It is a role for someone who wants:

• System-level ownership of the engine that powers a category-defining company
• Hard problems with real-world consequences

The company is an equal opportunity employer. We evaluate candidates based on capability and mindset, not pedigree.