Role: Senior iOS Engineer
Location: Remote (US) or Austin, TX
Our client is building the operating substrate for household labor.
They are not a cleaning company, not a marketplace, and not a robotics lab. They are an integrated three-layer stack that sits beneath whoever performs work inside the home — human today, humanoid tomorrow — owning the data, the access, and the policies that make household execution deterministic for the first time.
Layer 1 is the proprietary execution graph: per-job structured records of every household task they run. Layer 2 is sovereign access — the direct contractual relationship they hold with each household, the channel any future labor unit (human or humanoid) must traffic through to reach the consumer. Layer 3 is the ML/policy stack that converts Layer 1 data into deployed task execution.
Cleaning is the wedge — the right training task for Layer 1 — not the market.
Everyone operates inside an AI-native operating system. AI handles briefings, task management, and synthesis. You bring judgment, product intuition, execution, and speed.
They move fast and work hard. Expect long hours, nights, and weekends. If you are looking for work-life balance, this isn't the place for you.
They are looking for ambitious builders who want to build a category-defining company.
Position Overview:
As Senior iOS Engineer, you own the consumer surface of Layer 2 — Sovereign Household Access.
Layer 2 is the load-bearing relationship: households assign the platform as the operating substrate for the labor inside their home, and every future human or humanoid labor unit traffics through that relationship to reach the consumer. The iOS app is how that relationship becomes tangible. Booking, repeat scheduling, real-time status, automated restitution, trust signals — these are not "features." They are the mechanism through which a household stops "hiring a cleaner" and starts subscribing to the platform.
You own this end-to-end: architecture, performance, release process, and ongoing iteration. Your work determines whether the product feels like utility infrastructure or a service provider — and that distinction is the core thesis.
This is a long-term ownership role. Not a pixel-perfect implementer, not someone who waits for Figma specs, not a junior learning role.
Key Responsibilities:
What "High Agency" Means in This Role:
You can take an ambiguous goal like "increase repeat-booking rate" or "make restitution feel automatic" and propose UX changes, implement them, instrument them, measure impact, and iterate independently — without waiting for a PM to define every detail.
Outcomes in First 6 Months:
Qualifications:
✅ You likely fit if you:
❌ This might not be for you if you:
What they offer:
Interested?
If you’re reading this thinking “this is exactly me”, please DM me on LinkedIn!🔗