AI-Native Engineer

What You’ll Build

• AI Agents: The agents that plan, write, animate, narrate and check a video, and the tools and APIs they call.
• The Player: A timeline engine where every frame is a function of the clock and every viewer action is captured.
• The Video Pipeline: Rendering, 4K export, audio sync, and playback on every browser and phone.
• The Platform: APIs, data models, background jobs and integrations on PostgreSQL and AWS, used by paying customers every day.
• How We Build: Better ways to build with AI, which you prove and then make the team’s defaults.

Stack: TypeScript, Node.js, React, PostgreSQL, AWS and the Claude API.

What AI-Native Means Here

AI agents write most of our code. They’re fast, and often confidently wrong, so the safeguards are the craft. You’ll get very good at them here.

• Tests First: A failing test before the fix, against real services where we can.
• You Own Every Line You Merge: Even when an agent wrote it.
• Check It Like a User: Open the real page on a phone and in Safari. A green check isn’t proof; ask what it could miss.
• Agents Have Guardrails: They can’t merge, deploy or touch production. Every change goes pull request → CI → review → beta → production.
• Secrets Stay Out of Prompts: Keys, tokens and passwords never go into an agent’s prompt.
• Mistakes Become Rules: When an agent gets something wrong, you add the test, lint rule or guide edit that stops it happening again.

Who You Are

• AI-Native: You already write a lot of your code with AI agents (Claude Code, Cursor or similar), and you can show us how you keep it correct. You can tell when an agent is confidently wrong, and you catch it before it ships. You like trying new tools and workflows, and you measure whether they worked.
• A Production Engineer: About 2 years building and running production software. What you shipped matters more than the count. You understand how production systems are built: API and data-model design, relational databases and migrations, background jobs and queues, caching, and failure handling (retries, timeouts, idempotency). You’ve debugged a live issue from logs and metrics, and you think about monitoring, rollbacks and safe deploys before something breaks. You write tests that catch real bugs, and you’re comfortable with CI/CD, cloud basics (AWS or similar) and security hygiene. You’re strong in TypeScript or JavaScript and at home across React, Node.js and SQL, with a degree in computer science or a related field, or equivalent experience.
• A Teammate: A go-getter. You see a problem and start on it. Fast and careful. You ship quickly, then check it really works. A clear writer in English, because much of our work happens in writing.
• Bonus: Graphics or animation (WebGL, GSAP, Canvas), video or audio (ffmpeg, codecs), ML coursework or research.