Careers
Noopenrolestoday.Thedoorisnotlocked.
Apoliums is a small engineering team in Indore, and we hire when a project genuinely needs another person rather than to fill a headcount plan. Nothing is open right now — but the work below describes what it is like here, and we do read speculative applications.
- Open roles
- None currently
- Location
- Indore, India
- Hours
- IST, office-based
- Speculative
- info@apoliums.com
Current openings
We are not advertising a role at the moment.
Rather than list roles we are not actively hiring for, this page says so plainly. When something opens it will be posted here with the level, the salary range and the team it sits in.
If you want to be in the conversation when that happens, send us your work now. A short note about what you have built, a link to code we can read, and what kind of problem you want next is more useful to us than a formatted CV. We keep good applications on file and get in touch when the shape of the work matches.
We reply to every application that includes something we can actually look at, whether or not there is a role.
Life at Apoliums
What the engineering culture actually is.
You own what you ship
An engineer here takes a piece of work from the conversation with the client to the deploy and the week after it. Nobody hands you a ticket stripped of its context, and nobody takes your work over the wall.
Review is normal, not a verdict
Every change is read by someone else before it merges. The point is to find the failure mode nobody thought about, and to spread knowledge of the codebase past one person.
Small team, wide surface
You will work across the stack more than a large company would let you — schema one week, a React interface the next, a deploy pipeline after that. That is the trade for not having a specialist queue to wait behind.
Estimates you set
The person doing the work gives the estimate. If it is going to slip, saying so early is the expected behaviour and never the punished one.
Written over spoken
Decisions, trade-offs and the reason a thing is built the way it is get written down. It makes handover survivable and means a good idea is not lost because the person who had it was on leave.
IST hours, no heroics
Work happens in normal hours from the Indore office. Late nights before a launch are a planning failure, not a badge.
Hiring process
Four steps, about two weeks, paid where it should be.
- 01
Your work, not your CV format
Send code we can read — a repository, a project you shipped, a contribution to something open. A CV is fine, but the code is what gets read first.
- 02
A conversation about it
Forty-five minutes on something you built: why it is shaped that way, what you would change now, what broke in production. No whiteboard puzzles.
- 03
A paid, realistic exercise
A small piece of work close to what the job actually is, done in your own time within a few days. Paid at a fair rate, because unpaid take-homes are a tax on people who cannot afford one.
- 04
Meet the people you would work with
A session with the engineers on the team, then a straight conversation about money, level and start date. You get a decision within a week either way, with a reason attached.
Learning
Getting better is part of the job, not homework.
- Time inside the week
- Learning is scheduled work, not something you fit around delivery. Reading, a course, or rebuilding something badly to find out how it works.
- Rotation across projects
- Engineers move between problems on purpose so nobody becomes the single point of failure for one client's system.
- Design and review exposure
- You sit in the architecture and estimate conversations early. Judgement about what to build is learned by watching it get decided, not after a promotion.
Settled before an offer, not after
- Salary band and level for the role
- Working hours and office expectations
- Equipment and workspace set-up
- Leave policy and notice period
- Who you report to and who reviews your work
- What the first three months are meant to produce
All six are covered in the first conversation. Nothing about pay or expectations is held back until the end.
Interns and early career
No formal programme, and we will not pretend otherwise.
We do not run a scheduled internship intake. When the team has capacity to teach properly, we take one or two people and pay them — an unpaid intern doing real client work is not something we are willing to do. If you are early in your career, send the same thing everyone else sends: something you built, and what you learned building it.
info@apoliums.com