Skip to content
Tech News
← Back to articles

Bloomy (YC S26) is hiring a founding engineer

read original more articles
Why This Matters

Bloomy is an innovative AI-driven educational platform that personalizes learning for K-12 students, significantly accelerating their progress. Its rapid growth and unique AI-native approach position it as a transformative force in EdTech, offering opportunities for engineers to shape the future of education technology. Joining Bloomy means contributing to a product that directly impacts millions of students and educators.

Key Takeaways

Bloomy is an AI tutor and curriculum for K-12 students. Our student users are learning approximately 2x faster in early pilots, and students and teachers alike love our product.

How it works: We diagnose students’ skill gaps, map out a personalized learning path for them, and then have an AI tutor teach them. The AI learns about how they learn, so it can increase the efficiency of its teaching and, consequently, their learning.

How you can help: You will be joining as the founding engineer. Right now, engineering is one founder (me) orchestrating fleets of coding agents that produce a large share of our code and curriculum against specs, verification harnesses, and QA gates. I’m a solo founder with domain expertise as a former teacher and sales leader, but I’m not an engineer by training, and I need someone with true technical expertise to actualize the vision of improving education for millions of students.

Why we’re different: Bloomy is AI-native. I built the entire product from February to April of this year, got it into the hands of 500 students across 6 schools from April to June, started YC in June, and have roughly doubled ARR every 2 weeks since then. Thousands of students will soon use our product this fall. Bloomy is also the first EdTech company to go through YC for the past 5 batches, so it represents an opportunity to be on the ground floor of one of relatively few startups trying to transform education with AI.

Your first 90 days

First week

Ship a feature or a fix to production and watch real students in real classrooms hit it the next school day. Our loop from “merged” to “a 6th grader used it” is as short as it gets.

First month

Get acquainted with the React/TypeScript app, the Supabase backend, the content pipeline, and the agent fleets that feed it. Take ownership of your first fleet — write the spec, build the harness, set the QA gate — and start shipping through it.

Three months later

... continue reading