How We Hire Engineers in Kerala

We hire for thinking, not trivia

Kerala produces a remarkable amount of engineering talent, and the conventional way to filter it is with algorithm puzzles and pedigree checks. At BSH Technologies we have found that approach selects for the wrong thing. We do not need people who can reverse a binary tree under a stopwatch; we need people who can sit with an ambiguous problem, ask good questions, and make sound decisions when the requirements are still forming. Those are different skills, and our hiring is built to find the second kind.

This is partly self-interest. Most real work is ambiguous, so the ability to reason clearly under uncertainty predicts on-the-job success far better than memorised tricks do. A candidate who has drilled a thousand puzzles may still freeze the first time a problem arrives without a clean statement attached.

What we actually look for

When we evaluate someone, a few qualities matter more than a polished CV:

• How they handle not knowing. We deliberately pose under-specified problems and watch whether they ask, assume, or freeze.
• How they explain their reasoning. An engineer who can articulate why they chose an approach will be a far better teammate than one who just produces an answer.
• Whether they care about the user. The best engineers connect their code to the person who will use it, not just to the ticket.
• How they respond to feedback. We give a small critique during the process and see whether it is met with curiosity or defensiveness.

A candidate who says I am not sure, here is how I would find out tells us more than one who confidently recites the right keyword. We are hiring colleagues for years, not contestants for an afternoon.

Beyond the obvious pipelines

Pedigree filtering also misses people. Some of the strongest engineers we have hired did not come from the most famous colleges or the expected backgrounds — they were self-taught, came from adjacent fields, or simply did not test well under artificial pressure. By focusing on demonstrated reasoning rather than credentials, we widen the pool and find talent that a narrower filter would have discarded.

The interview that only rewards confidence quietly filters out the thoughtful people you most want to hire.

That breadth matters in Kerala specifically, where capable people take many different routes into software. We would rather meet someone where they are and assess how they think than disqualify them for a path we did not expect.

What the process looks like for a candidate

We try to make our hiring feel like a day at work rather than an interrogation, because the goal is to see how someone actually operates. Instead of whiteboard puzzles under a stopwatch, we work through a realistic problem together, talk openly about trade-offs, and let the candidate use the tools and references they would use on the job — because nobody builds real software from memory with no internet. We are honest that we want to see their thinking, not catch them out, and that framing changes how people show up: they relax, ask the questions they would actually ask, and reveal the judgement we are hiring for. We also treat the conversation as two-directional. A candidate is evaluating us as much as we are evaluating them, and a respectful, transparent process is the first thing it tells a good engineer about what working here is like. The people we most want to hire have options, and how they are treated in an interview is a signal they read closely.

Why this fits how we work

Our hiring philosophy is inseparable from our delivery philosophy. Because we run a software-factory model with shared process and review, a new engineer does not need to arrive knowing every tool — they need to arrive able to learn, reason, and collaborate. The scaffolding teaches the specifics; the person brings the judgement. Growing the team from Thrissur on these terms has given us engineers who are genuinely good to work with, not just technically adequate.

It also shapes our culture. A team selected for curiosity and honesty about what they do not know is a team that asks for help early, reviews each other's work generously, and keeps learning — which is exactly the environment good software comes from.

Hiring is the most important thing we do

It is worth stating plainly why we invest so much care here rather than treating hiring as an administrative chore to get through quickly. Every person we bring on shapes the team for years — the standard they hold, the way they treat colleagues, the questions they think to ask. A single bad hire does not just underperform; it lowers the bar for everyone around them and quietly teaches the team that the bar is lower than it was. A great hire does the opposite, raising what everyone considers normal. Given that leverage, a slow and thoughtful process that occasionally lets a good candidate walk is far cheaper than a fast one that lets the wrong person in. We would always rather wait for the right colleague than rush to fill a seat, because the team we are building is the single biggest factor in whether the software we ship is any good.

Work with BSH

If you want your software built by engineers chosen for how they think rather than how they test, that is the team BSH Technologies has deliberately assembled in Kerala. Bring us your project and you will feel the difference in the questions we ask.