JOB DESCRIPTION
Build like a founder. Ship like Spartan.
Our clients are startups in a race: an MVP in 30 days, and billions of data points the year after. We're looking for a Data Engineer to build the platform that carries it.
We don't act like vendors. We embed. Our teams sit inside startups backed by YC, Pear VC, BlingCap, a16z, and Techstars, working beside founders and engineers from Stanford, MIT, Yale, Google, Amazon, and Uber. Together we ship those MVPs and scale the systems behind them to millions of users and billions of requests.
This isn't a batch-and-dashboards seat three layers from the client. You'll be in the founder's Slack. Your pipelines run in production. You'll own the data platform behind real-time operations, analytics, and AI, from ingestion all the way to serving.
Data is the core of the job. Backend and infra come with it, because owning the path to production means you deploy your own work and build the services that hand data to the product. You don't need to arrive as an expert in all three. You do need to be willing to learn the other two.
70% of our portfolio is LLM-powered, and every one of those features runs on data someone had to make trustworthy first. That's your work. Cursor, Claude, and Codex are default tools here, not experiments. You'll use AI every day, and you'll be expected to use it well.
Not every environment fits everyone, so here's an honest picture of the teammate we're looking for.
You'll thrive here if:
Some weeks will stretch you. That's the job. But you'll never carry it alone. A critical client release or a tricky production issue? Someone always has your back. We push each other hard because we care how far each of us can go. We win together. We lose together. Nobody gets left behind.
One last thing. We're not filling seats. We're looking for teammates for the battles ahead. If you read all this and something in you said yes, trust that feeling and apply. We respect people who back themselves. Every Spartan here started with that same yes.
Every project brings a different stack, so in a year here you'll touch more of this list than most engineers do in five. What we adopt is decided by our engineers through an internal Tech Radar, not handed down from a slide deck.