Ownership, not tickets
Nobody hands you a groomed backlog. You will own a surface — the exam engine, the content pipeline, the centre console — and be trusted with decisions about it.
Careers
Small team.
Small team.
Unusually large surface area.
There is no layer between the work and the outcome here. You will ship something on a Tuesday and watch a few thousand students use it on the Sunday live mock.
Why here
What working at Skelro is actually like
We would rather tell you the honest version now than have you find out in month three.
Deadlines set by an exam board
JEE and NEET happen on fixed dates. That creates real pressure at points in the year, and genuine quiet at others. We plan around it rather than pretending it is not there.
Correctness matters more than velocity
A bug in a marking scheme is not a bug, it is a student’s wrong decision about their own preparation. We review carefully and we roll back without ego.
Frontier tools, used seriously
Vision-capable LLMs sit inside our content pipeline as production infrastructure with validation and human review around them — not as a demo.
Users you can talk to
Support mail lands close to engineering. You will read what a seventeen-year-old thinks of the thing you built, in their words, the same week.
Bengaluru, with flexibility
The team is based in Bengaluru and we like being in a room together for hard problems. Day-to-day, we care that the work is good, not where the chair is.
Open roles
Where we’re hiring
We hire in small numbers and slowly. If nothing below fits but you think you should be here, the last card is not a formality — we have hired that way before.
Full-stack Engineer — Platform
Engineer — Content & ML Pipeline
Subject Matter Expert — Physics / Chemistry / Biology / Maths
Partnerships Manager — Coaching Centres
None of the above
Please include something you have built or written. We weigh that far more heavily than a CV, and we will never ask you to do unpaid work that looks like our roadmap.
Hiring process
Four conversations, about two weeks
Intro call — 30 minutes
What you have built, what you want next, and an honest description of the role from us.
Craft conversation — 60–90 minutes
A real problem from our domain, discussed the way we would discuss it internally. No whiteboard algorithm trivia.
Working session
A short paid exercise or a walkthrough of something you already own. Your choice.
Offer
We move quickly at this point, and we tell you where you stand either way.
Think you belong here?
One email. Tell us what you would work on and why.