This role exists because the platform needs a dedicated owner. Someone who thinks end-to-end-from a Garmin syncing at 3am to a webhook landing 400ms later. You're not building features. You're building the foundation.
What you'll own
- Ingestion Pipeline- How provider data enters Terra from cloud APIs (Garmin, Fitbit, Oura) and mobile SDKs (Apple Health, Health Connect). Raw data in, queued for normalization.
- Normalization Engine- Transforms heterogeneous provider payloads into Terra's standardized models: Activity, Sleep, Daily, Body, Menstruation, Nutrition. The core IP that makes 500+ sources feel like one.
- Provider Framework- How new sources get onboarded. Web-based (OAuth, polling, rate limiting) and mobile-only (on-device SDK, background sync). Adding provider should be as fast as .
- Auth & Connections- Connect widget, custom UI flows, OAuth sessions, Terra User lifecycle, Reference ID mapping.
- Upstream Supplier Connector- New ingestion surface. Data suppliers push into Terra instead of us pulling. Ground-up build.
- API Versioning- Backwards compatibility and deprecation across the /v2 surface.
- Observability- Monitoring and alerting across the full pipeline. You know when a provider degrades before our developers do.
What you'll build
- Scale event delivery to 10x- AI lab consumption is growing exponentially. Redesign the hot path without proportional cost increase.
- Ship the upstream supplier connector- Schema contracts, auth, validation, rate limiting. The interface for suppliers to push directly into Terra.
- Redesign normalization for schema evolution- Providers change APIs. Our models evolve. Downstream consumers can't break.
- Multi-destination fan-out- One event, reliably delivered to webhooks, SQL, S3, and queues simultaneously. Independent retry logic per destination.
- Provider health dashboards- Real-time visibility into every source's freshness, latency, error rates, and schema drift.
- Harden mobile SDK data path- Apple Health and Health Connect are fundamentally different from cloud APIs. On-device processing, background sync constraints, OS-level limits. Make it scale.
Who you are
- A systems thinker - you see data flow and failure modes before you see features.
- Battle-tested at scale - you've operated platforms processing billions of events. You've fixed production at 2am.
- Observability-first- monitoring and tracing are part of your design, not bolted on after.
- Opinionated where it matters- event delivery guarantees, schema evolution, idempotency, API versioning. Opinions earned by shipping.
- Fast- architecture whiteboard Monday, production deploy Friday.
- Default yes- hard problems make you lean in.
- Accountable- you own production, you respond to incidents, you care about uptime. Skin in the game.