40+ engineers · Dehradun and Bengaluru · Hybrid

Ten open roles. Published bands, published pass rates.

Redcubical Systems Private Limited is hiring across backend, frontend, platform, data, machine learning, quality, architecture and commercial roles in Dehradun and Bengaluru. Every role is hybrid, every band is published internally, and our hiring stages and pass rates are on this page so you can decide whether to spend your evening applying.

Attrition under 9 percent against an industry average of 18 to 25 percent
Paid take-home exercise, or a 90-minute live pairing session instead
You talk to clients directly. There is no account manager in between
Twelve to eighteen working days from application to offer

Email nitesh@redcubical.com Read the honest section first

Open roles: 10
Annual attrition: Under 9%
Working days to offer: 12–18
Applicants offered: 3–4%

Open roles

What we are hiring for right now

Ten requisitions, all hybrid, all anchored to Dehradun or Bengaluru. Each card lists what you would actually do, what we genuinely need, and what we do not require regardless of what other job adverts told you.

What roles are open at Redcubical Systems?

We have ten open roles: Senior Backend Engineer, Frontend Engineer, DevOps and SRE Engineer, Data Engineer, AI and ML Engineer, QA Automation Engineer, Solution Architect, Business Development Manager for international markets, Customer Success and Onboarding Manager, and Inside Sales Executive. Apply to nitesh@redcubical.com with the role in the subject line.

Dehradun, hybrid · 5–9 years

Senior Backend Engineer

Own backend services end to end: schema design, API contracts, background processing, performance under real load, and the production incidents that follow. You will work on client platforms and on HealHub, which means the schema migration you plan runs against live booking data.

What we need: deep competence in one of Node.js with TypeScript, Python or Java. Relational data modelling you can defend. Experience of a system you kept running while changing it.
What we do not require: a computer science degree, a specific institution, Kubernetes on your CV, or experience in our exact domain.

Dehradun, hybrid · 2–5 years

Frontend Engineer

Build the interfaces enterprise users spend seven hours a day inside: data tables of 50,000 rows, permission-aware navigation, reporting views and forms that survive a bad connection. React and TypeScript, with Next.js on most projects.

What we need: React and TypeScript in production, real CSS ability rather than component-library assembly, and working knowledge of WCAG 2.2 AA and keyboard navigation.
What we do not require: design skills, a portfolio site, open-source contributions, or experience with our exact state-management library.

Bengaluru, hybrid · 3–7 years

DevOps and SRE Engineer

Own infrastructure as Terraform, pipelines in GitHub Actions, and the reliability of what runs on top. You will hold the pager for our own products, run cost reviews that have removed 30 percent from live cloud bills, and lead cutover weekends on client migrations.

What we need: Terraform you wrote yourself, AWS or Azure at depth, container orchestration, and observability instincts that start with SLOs rather than dashboards.
What we do not require: certification badges, both clouds at equal depth, or Kubernetes if your container experience is ECS or Container Apps.

Bengaluru, hybrid · 3–6 years

Data Engineer

Build medallion-architecture pipelines that hold up when the source system changes without warning. Ingestion, dbt transformation, orchestration in Airflow or Dagster, data contracts, and the freshness alerting that means a stakeholder does not discover the breakage first.

What we need: strong SQL, Python, dbt or an equivalent transformation layer, one warehouse at depth among Snowflake, BigQuery, Redshift or Databricks, and dimensional modelling.
What we do not require: Spark at petabyte scale, streaming experience, or a background in statistics.

Bengaluru, hybrid · 3–7 years

AI and ML Engineer

Ship retrieval-augmented generation, extraction and agentic systems that behave predictably and do not surprise anyone with the bill. Evaluation harnesses before launch, model tiering and prompt caching from day one, guardrails and human review paths where the output matters.

What we need: Python, a production LLM system you actually operated, retrieval and chunking judgement, and evaluation discipline. Comfort saying that a problem does not need an LLM.
What we do not require: a PhD, published papers, training foundation models, or GPU cluster experience.

Dehradun, hybrid · 2–6 years

QA Automation Engineer

Own the test strategy rather than a test script backlog. Playwright suites that run in under twelve minutes, API contract tests, a defect triage process clients can see, and the judgement to argue that a flaky test is worse than no test.

What we need: Playwright or Cypress in a real pipeline, API testing, one scripting language at depth, and the confidence to block a release with evidence.
What we do not require: ISTQB certification, performance testing, security testing, or manual-only experience being held against you.

Dehradun, hybrid · 9–15 years

Solution Architect

Scope and estimate engagements for overseas clients, then stay accountable for that estimate through the build as the named delivery lead. This is deliberately uncomfortable: you cannot promise something the team then has to absorb, and you will be in the room when a client hears bad news.

What we need: systems you designed and then operated, cloud cost modelling, credible estimation, and the ability to tell a client to build less without losing the engagement.
What we do not require: TOGAF, enterprise-architecture framework certifications, or experience only in the pre-sales half of the job.

Dehradun or Bengaluru, hybrid · 5–10 years

Business Development Manager (International)

Own new business in the UK, Europe, the Gulf or North America. You will bring an architect into the first call rather than presenting a deck, and you will be measured on qualified opportunities and won engagements, not on outbound activity volume across 10 markets.

What we need: IT services or software sales into one of our markets, enough technical literacy to survive a CTO conversation unaccompanied, and comfort with a three to nine month cycle.
What we do not require: a transferable client list, an MBA, or willingness to promise timelines the delivery team has not agreed.

Dehradun, hybrid · 3–7 years

Customer Success and Onboarding Manager

Take clients of our own products from signature to routine use, and keep them there. Onboarding plans, data migration coordination, training, adoption tracking, renewal risk, and the unglamorous work of chasing the one configuration nobody completed.

What we need: B2B SaaS onboarding or account management, genuine patience with non-technical users, and the discipline to log what you did so the next person is not guessing.
What we do not require: a technical degree, coding ability, or healthcare domain experience, though clinical exposure helps on HealHub.

Dehradun, hybrid · 1–4 years

Inside Sales Executive

Qualify inbound enquiries, run first-response conversations, research target accounts and book technical calls that are worth an architect’s time. This is the role most likely to become a business development or customer success role in two years, and we hire it with that in mind.

What we need: clear written English, telephone confidence with overseas buyers, CRM discipline, and curiosity about what we actually build.
What we do not require: prior sales experience, a specific degree, or a willingness to work a call-centre dialler, because that is not how this works here.

Hiring

How hiring works, with the pass rates

Most companies publish the stages and hide the odds. Both are below. The numbers are our trailing twelve months across all engineering requisitions and they are rounded, not flattering.

What is the hiring process at Redcubical Systems?

Five stages over twelve to eighteen working days: CV screen, a 45-minute technical conversation, a paid four-hour take-home or a 90-minute live pairing session, an architecture and team interview, then a conversation with a founder. About three to four applicants in a hundred receive an offer. You hear a decision at every stage, including a reason.

Stages, pass rates and timings
Stage	What happens	Typical pass rate	Time in stage
CV and note screen	A human reads it. We look for a system you owned and a decision you can explain. No keyword filter, no automated rejection.	About 25 percent	2 business days
Technical conversation	45 minutes with an engineer from the team you would join. Your work, your trade-offs, one design discussion. No trick questions and no live algorithm puzzle.	About 45 percent	Scheduled within 4 days
Paid take-home or live pairing	A four-hour scoped exercise close to real work, paid at a flat rate whether or not you progress. Or 90 minutes of pairing on our codebase if you prefer not to give up an evening.	About 60 percent	5 business days allowed
Architecture and team interview	Ninety minutes with a senior engineer and the delivery lead. You defend your exercise, then design something larger with constraints changing mid-discussion.	About 55 percent	3 business days
Founder conversation	Thirty minutes with Ashish or Nitesh. Mutual, mostly about what you want next and what we can honestly offer. Rarely a rejection stage, occasionally a redirect to a different role.	About 85 percent	2 business days
Offer	Written offer with band, band position, review date and the full benefits list. Verbal first, on the telephone, with the reasoning behind the number.	3–4 percent of all applicants	1 business day

Two honest caveats. Commercial roles replace the take-home with a written account plan and a role-play call, and run about four working days shorter. And when a client engagement is mobilising, our own scheduling is the bottleneck, not you. If we are slow, we will say why rather than leaving you refreshing an inbox.

You will not be ghosted. Every applicant gets a decision, including at CV stage. It is a person writing it.
You will get feedback on request. Ask and we will tell you specifically what was missing. We will not do this unsolicited, because not everyone wants it.
You can skip the take-home. Live pairing is an equal path, not a lesser one. Roughly a third of candidates choose it.
No unpaid trial work on real projects. If work would ship, it is employment and it is paid as such.
No aptitude tests or personality profiling. We have never found either predictive of whether someone can ship.
Reapplying is fine after six months. Several current engineers were rejected once. We keep the notes so you do not start from zero.

Money

What we pay and how we decide it

Bands are published internally, with your position inside the band and the reasoning written down. We do not pay a premium for hard bargaining, which is the only way a published band means anything.

How does pay work at Redcubical Systems?

Every role sits in a band with a floor and a ceiling. Your offer is set by band position against a written competency framework, not by your previous salary and not by how hard you negotiate. Bands are reviewed each April against market data, and individual position is reviewed twice yearly. A promotion moves your band; performance moves your position within it.

We do not ask for your current salary or a payslip until an offer is agreed, and we do not use your last number to anchor our first one. If you were underpaid before, that is not information we want in the decision.

The uncomfortable half of transparency: if you negotiate hard, we will not move much, usually a single band step at most and only where we can justify it against the framework. Someone joining next quarter would see that gap and it would be indefensible. Sales roles carry a variable component of 20 to 30 percent of total, paid quarterly against collected revenue rather than signed contracts, because we have watched too many firms pay commission on invoices that never cleared.

Two reviews a year, in April and October. April is the band and market review; October is position and promotion only. There is no bonus pool at the end of the year that depends on the company having had a good one. If we owe you a rise, you get it on the review date.

Indicative annual fixed pay by role family
Role family	Band range, INR lakh
Engineer, 1–3 years	6 – 12
Engineer, 3–6 years	12 – 22
Senior engineer, 5–9 years	20 – 34
Lead or staff engineer	30 – 46
Solution architect	38 – 60
QA automation, 2–6 years	8 – 20
Customer success manager	9 – 20
Inside sales executive	5 – 11 plus variable
Business development manager	18 – 36 plus variable

Indicative fixed cost to company for the current cycle, excluding variable pay. Bengaluru bands run roughly 12 to 18 percent above Dehradun for the same role to reflect local cost of living. Exact band and your position within it are given in writing with the offer, before you are asked to decide.

Learning, and why people stay

The budget, the conferences and the attrition claim

We claim attrition under 9 percent. That is a strong claim in Indian IT services, so here is the number, the reasoning, and the parts of it we cannot fully prove.

Why is attrition so low, and should we believe it?

Annual voluntary attrition across the trailing twelve months is under 9 percent, against a published Indian IT services average of 18 to 25 percent. Average engineer tenure on a client account is about 2.5 years. We believe four things drive it: location, published bands, direct client contact, and the fact that a founder is reachable.

Location. In Dehradun an engineer is not fielding three competing offers a quarter. That is the largest single factor and we did not earn it through culture work. It is a structural advantage of not being in a city where every firm poaches from every other firm.

Published bands. The most common reason a good engineer leaves is discovering a peer earns 30 percent more for the same work. Publishing bands removes that discovery. It also removes our ability to quietly underpay someone who does not ask.

Direct client contact. Engineers here present their own work to the client who commissioned it. It is exposing, and it is also the thing people say they cannot get back at a larger firm.

A reachable founder. At 40+ engineers this is genuinely true and it is one of the things that will stop being true if we grow carelessly. We would rather say that now than pretend otherwise later.

What we cannot prove. Nine percent of a headcount our size is a small absolute number, so the figure is statistically noisy year to year. It is unaudited, it is our own HR data, and it counts voluntary departures only. A single bad quarter would move it several points. Treat it as directional and ask us about it in the founder conversation.

Learning and development

Learning budget: INR 60,000 per engineer per year, no approval needed under INR 15,000
What it covers: Courses, books, certifications, subscriptions, hardware for learning
Conferences: One domestic conference a year fully funded, including travel and time
International conferences: Funded where you are speaking or presenting. Two engineers a year, chosen by proposal
Certification exams: Paid on first attempt and on one retake, including AWS, Azure and Kubernetes
Internal time: Four hours a week protected for learning, held on the same day across a team
Mentoring: Every engineer under three years has a named senior engineer with time allocated
Talks: A fortnightly internal engineering talk. Presenting is voluntary and counts as work

The honest part

What working here is actually like

Read this section before the benefits list. If any of it sounds wrong for where you are in your career, that is useful information and we would rather you had it now.

Less specialisation support than a large firm

At 40+ engineers there is no dedicated performance-engineering team to escalate a slow query to, no internal platform team maintaining a golden path, and no design-system group handing you components. When the database is slow at 40 million rows, you are the person who reads the query plan. Some engineers find that the fastest growth of their career. Others find it exhausting, and both reactions are legitimate.

You carry on-call

Engineers on product teams and on supported client platforms take a one-week rotation roughly every six to eight weeks. Nights are genuinely quiet most weeks, and when they are not, you are compensated for the callout and you take the following day off. What we will not pretend is that the pager does not exist. It does, and it is attached to real users of HealHub who cannot book a patient if we are down.

You talk to clients directly

You will demo your own work to a CTO in London or Dubai, explain your own slippage, and occasionally hear that a decision you made was wrong. There is no account manager translating for you. This is the single biggest difference from a large services firm, and it is the reason some people join and the reason a few leave.

Health cover for you, a spouse and two children, plus parents at a subsidised premium.
Term life and accident cover at a multiple of fixed pay, at no cost to you.
Provident fund and gratuity per Indian statute, correctly and on time.
Twenty-four days of paid leave plus twelve public holidays, plus casual and sick leave.
Twenty-six weeks maternity leave per statute, and four weeks paid paternity leave, which is not statutory.
Two weeks fully paid bereavement leave for an immediate family member, without a form.
Mental health support through a confidential external counselling service, six sessions a year.
Referral bonus paid in two parts, on joining and at six months.

Applying

How to apply, and what to put in the email

How do I apply?

Email nitesh@redcubical.com with the exact role name in the subject line, a CV of two pages or fewer, and three or four sentences about one system you built, what constraint shaped it, and what you would change now. That short paragraph is the part we read first. Every application gets a human reply within two business days.

Send the email

To nitesh@redcubical.com, subject line "Application: Senior Backend Engineer" or whichever role. Attach the CV as a PDF. Include links to code, writing, a shipped app or a talk if you have them. No covering letter template, please. The four sentences are worth more.

Reply within two business days
Tell us the constraint, not the stack

The strongest applications describe a limit they worked inside: a legacy schema they could not change, a 300-millisecond budget, a regulator, a two-person team. Listing eleven technologies tells us nothing about judgement. One paragraph about a hard trade-off tells us most of what we need for the screen.

This is the part of your application that matters most
Say what you want next

Deeper in one area, broader across the stack, closer to clients, further from them, or towards leading people. We will tell you honestly whether this role offers it. A mismatch found now is much cheaper than one found in month seven.

Also useful if you are applying speculatively
Tell us about access needs early

Interview format, timing, assistive technology, a quiet room, extra time on the exercise, or anything else. Ask at any point and it is arranged without discussion or documentation. It does not form part of any assessment.

No justification required
If nothing fits, write anyway

Roughly one hire in six comes from a speculative approach that arrived before we advertised. Tell us what you would build here. We hold a small number of unadvertised requisitions, particularly at senior engineer and architect level, and we keep good speculative notes for six months with your consent.

Same address, same two-day reply

Answers

Careers questions

How do I apply for a job at Redcubical Systems?

Email nitesh@redcubical.com with the role name in the subject line, a CV of no more than two pages, and three or four sentences on a system you built and what you would change about it now. Links to code, writing or shipped products help more than a covering letter. We reply to every application within two business days.

Are roles at Redcubical Systems remote, hybrid or in office?

All roles are hybrid and anchored to either Dehradun or Bengaluru, typically three days a week in the office. We are not a fully remote company. Long-running client engagements need engineers who can pull an architect to a whiteboard, and our newer engineers learn measurably faster sitting next to senior ones.

What is the hiring process and how long does it take?

Five stages: CV screen, a 45-minute technical conversation, a paid take-home or live pairing session, an architecture and team interview, then a conversation with a founder. Twelve to eighteen working days from application to offer. Roughly three to four applicants in a hundred receive an offer, and we tell you at every stage where you stand.

Do you pay for take-home exercises?

Yes. The take-home is scoped to four hours and paid at a flat rate whether or not you progress, invoiced by you or paid as a gift voucher if invoicing is awkward. We ask for four hours of your unpaid time only if you choose the live pairing option instead, which takes ninety minutes.

What is attrition like at Redcubical Systems?

Under 9 percent annually across the trailing twelve months, against a published Indian IT services average of 18 to 25 percent. Average tenure on a client account is about 2.5 years. We think the reasons are location, band transparency and the fact that engineers here talk to clients directly rather than through three layers.

Do you hire freshers and people without a computer science degree?

Yes to both, though fresher intake is limited to roughly six places a year because mentoring capacity is the binding constraint rather than budget. We do not filter on degree, institution tier or a minimum academic percentage. We do filter hard on whether you can explain a technical decision you made and its trade-offs.

Will I get to work on your own products or only client projects?

Both, over time. Around a fifth of engineering capacity sits on our 4 own products, and rotations between product and client work happen at natural engagement boundaries. Product work carries production on-call for real users. Client work carries direct exposure to overseas stakeholders. Most engineers want a period of each.

What happens if the role I want is not listed?

Write anyway, to nitesh@redcubical.com, and tell us what you would do here. We hold a small number of open requisitions that never get advertised, and roughly one hire in six arrives this way. What does not work is a generic CV with no indication of what you want to build.

One email. A human reads it in two days.

Role name in the subject, two-page CV, and four sentences on something you built. Send it to nitesh@redcubical.com and judge us on the quality of the reply.

Email nitesh@redcubical.com Read about the company first

Continue exploring

About RedcubicalHow the company is built and funded Our productsFour systems you might work on Technology stackWhat we actually build with Delivery processHow an engagement runs day to day FAQQuestions about the company ContactFor anything that is not an application