Senior Platform Engineer · Java
Event-driven systems for banking and logistics clients. You'd own architecture decisions on one platform and be the named engineer on it.
Tip: press Ctrl + K from anywhere.
Three years of data from replacing whiteboard rounds with paid work samples: offer acceptance up, first-year attrition down by more than half, and a noticeably less uniform set of people. The process below is what we actually run, in the order you'll experience it.
We'll tell you where you stand within two working days of every stage, including when it's a no. Being left in silence is the single most common complaint about technical hiring and it's entirely avoidable.
With an engineer from the practice you'd join, not a recruiter reading a script. You get to ask what the work is actually like, and we'd rather you asked hard questions.
We walk through something you've built and something you've broken. No live coding under observation, no puzzles with a trick. If you can't discuss past work for confidentiality reasons, we'll use one of our own systems instead.
A scoped problem shaped like our real work, done in your own time within a week. We pay ₹12,000 for it whether or not we make an offer, because your time has value and unpaid take-homes quietly filter out anyone with caring responsibilities.
Meet the people you'd work with daily and a practice lead. Salary band is stated in the job listing, so this conversation is about the role rather than a negotiation you're set up to lose.
Bands are annual, in INR, and are what we'll actually pay within. If none of these fit but you think we should talk, the last card is for you.
Event-driven systems for banking and logistics clients. You'd own architecture decisions on one platform and be the named engineer on it.
The unglamorous half of AI work: eval sets, regression suites, cost budgets. If you think demos are the easy part, we'll get on well.
Landing zones, migration waves and the FinOps conversation nobody enjoys. Six delivery centres, one platform standard to hold together.
Product surfaces for Atlas and Relay. Accessibility and Core Web Vitals are requirements here, not stretch goals.
Own the test strategy across three client programmes. We want someone who'll argue against a coverage target when it's the wrong metric.
Kafka and Snowflake pipelines for energy and logistics clients, where late, duplicate and impossible data is the normal case.
Interfaces used eight hours a day by people under time pressure. Research with actual operators is part of the job, not a phase.
You'd be paired with engineers who screen alongside you. Reading a codebase isn't required on day one, but wanting to learn is.
Twelve places. Six months of structured mentoring on a live project with a named senior, then a permanent team. No prior experience expected.
If you're good and we're wrong not to have a role for you, make the case. We've created four positions in the last two years from exactly this.
₹10 L family floater including parents, plus outpatient and mental health cover that doesn't require a diagnosis to claim.
40% of us are fully remote. Core overlap is four hours; the rest is yours to arrange. No badge-in metrics, ever.
₹1.2 L a year and eight working days. Our internal cohorts are taught by engineers who are still shipping.
For any parent, regardless of gender or how the child arrived. Phased return over six weeks at full pay.
Internal bands are visible to everyone. Reviewed twice a year against market, and adjusted without needing to be asked.
Compensated, rotated, and capped at one week in six. If a rota is firing often, we treat that as an engineering defect.
Write to careers@climentos.com and an engineer from the relevant practice will reply — not a mailbox, and not a template.
We reply to every application within three working days, including the ones that are a no.
Tell us the shape of the problem. We'll come back with a build plan, a team shape and a number — no obligation, no deck.