Get more replies from employers
Send a job-specific resume in minutes.
You are the technical bridge between Terra's platform and our highest‑value customers. You embed directly with their engineering and product teams to architect, integrate, and optimize their use of Terra's health data infrastructure.
This is not support. This is not consulting. You are an engineer who ships — the difference is that what you ship lives inside the customer's stack, powered by ours.
These are real problems our customers bring to us. As an FDE at Terra, you'd own the technical delivery.
An AI lab wants to ingest continuous heart rate, HRV, sleep stages, and activity data from 200K+ users across multiple wearable brands through Terra's unified schema — to power real‑time personalized wellness recommendations. You architect the data pipeline: webhook ingestion, event deduplication, backfill strategy for historical data, and rate limiting to stay within their processing capacity.
A conversational health AI needs access to blood biomarkers (glucose, cortisol, cholesterol) alongside wearable data, all normalized and delivered via a single webhook. You design the integration that merges Terra's wearable and blood lab data streams into one coherent user profile.
An insurer wants to use real‑time biometric data (resting heart rate trends, VO2 max estimates, sleep consistency scores) to offer dynamic premium pricing. You scope the data sources, define the consent flow using Terra's authentication widget, and build the data delivery pipeline that feeds their actuarial models — while ensuring HIPAA and GDPR compliance.
A clinical research platform needs longitudinal wearable data from a 10,000‑participant study across Fitbit, Garmin, and Apple Health. Different devices report different metrics at different cadences. You configure Terra's integrations, build the normalization layer that maps device‑specific quirks into a unified research dataset, and handle the edge cases: what happens when a participant switches devices mid‑study, or when a data provider pushes a breaking API change.
A fitness platform with 500K users wants to migrate from maintaining 15 separate wearable integrations to Terra's single API. You plan the migration: mapping their existing data models to Terra's schema, designing the cutover strategy, and building the webhook consumer that replaces their legacy polling architecture. Zero downtime. No data loss.
A wearable company wants to become a data supplier on Terra's platform — making their data available to Terra's downstream developer and AI ecosystem. You lead the technical onboarding: validating their data format against Terra's schema requirements, configuring consent flows, setting up data quality monitoring, and scoping which downstream developers get access to what.
You are an athlete. You train, you compete, you push limits — or at the very least, you are obsessed with quantifying your own data. The discipline, ambition, and courage it takes to show up every day and get better is the same energy we run on. If you understand the data because you live it, you'll build a better product.