Engineering
Intern
REMOTE (US) · FLEXIBLE TIMING
We don't hire interns to do intern work. We hire emerging builders and treat them as engineers.
We explicitly do not use years of experience as a hard qualifier. A 19-year-old dropout who's been building and shipping real systems for two years may have deeper evidence of obsession, ownership, and taste than a 10-year veteran in a narrow swim lane.
The intern is someone who could be our AI engineer, backend engineer, or FDE in 18 months — you just don't have the resume yet. You have side projects with real users, evidence of going deeper than anyone asked, and learning velocity that's off the charts.
WHAT YOU'LL DO
You'll work with a mentor to scope a project in week 1, then own it end-to-end. You're a real engineer on the team — standups, production ships, code review, real deliverables. The track emerges based on your strengths and where the team needs help most.
AI track
mentor: AliceCasey evaluation infrastructure, prompt engineering, ranking improvements, simulation tooling.
Data platform track
mentor: GregOutcome data pipelines, reconciliation tooling, analytics infrastructure, integration improvements.
Product track
mentor: GauravSelf-serve features, deployment tooling, customer-facing dashboards, internal tools.
WHAT WE LOOK FOR
- –Obsession. Have you built something because you couldn't stop thinking about it? Side projects with real users. Open-source contributions where you went deeper than the issue asked. Evidence of staying up until 3 AM because the problem was interesting, not because someone assigned it.
- –Technical fundamentals. Strong CS fundamentals. Comfortable in TypeScript. You use Claude Code as a force multiplier, not a crutch — you catch when the AI gives bad output and fix it.
- –Learning velocity. When you encounter something you don't know, how fast do you figure it out? The take-home tests this directly — you're dropped into a real EMR integration or a real AI scheduling dataset and need to make sense of it.
- –Communication. The Loom walkthrough in the take-home tests whether you can explain your thinking clearly. An engineer who can build but can't communicate what they built and why is only half useful.
THE PROCESS
Intro Chat
30 min, remoteDaniel. The decisive question: "Show us something you built. Not for a class — something you built because you wanted to."
Take-Home
48–72 hr window, asyncPick one of three tracks (AI, data platform, or FDE/integration). Real data, real problems — the same exercises our full-time candidates get. Record a 10-minute Loom walking us through your solution.
Review + Live Extension
60 minDaniel plus the mentor whose track you picked. First 20 min: we ask questions about specific technical choices. Next 30 min: you extend your take-home live, using Claude Code on your laptop.
Offer
APPLY
Send a short note to daniel+intern@zingage.com — show us something you built because you wanted to. Link, screen recording, or a paragraph describing the hardest technical problem you ran into and how you solved it.