Keka HR | Senior Software Engineer | India

Summary

I went through four interview rounds at Keka HR for a Senior Software Engineer role in India and received an offer.

A recruiter reached out on LinkedIn. After I shared my profile and followed up once, I got a callback in about 15 days.

First half: overview of the role and basic background questions.
Second half: a ~2-page code snippet to review by adding comments in the document.
You don't need to catch every issue, but you should find a good share of the critical ones.
Typical issues: hardcoded credentials, SQL injection, N+1 queries, missing input validation, logical bugs.
The snippet is offered in a language of your choice (Java, TypeScript, C#, etc.).

Verdict: Selected (heard back the next day)

Build a few working APIs and demo them on Postman.
Problem (paraphrased): a mini alerting service with REST APIs to ingest and list alerts. Depending on severity, it triggers a notification, skips it, or only logs the incident. It also handles deduplication and failures of the external call.
The expectation is working APIs that meet all functional requirements, structured the way you'd write production code.
Any language or framework is allowed (Node.js, Spring Boot, .NET, etc.). Have your environment set up before the interview.

Verdict: Selected (heard back the next day)

Covers LLD (API and DB schema design), HLD, and code snippets for critical flows.
Problem (paraphrased): a trip management service with trips, drivers and admins. Admins can view trips and assign drivers. Strong focus on concurrency control.
The expectation is a clean schema and API design, plus solid knowledge of concurrency control mechanisms.
Excalidraw or Draw.io is fine for diagrams.

Verdict: Selected (heard back the next day)

A deep dive into my current project: the full architecture on Excalidraw, how it handles scale, what could be improved, and the business context.
A few standard HM questions at the end (e.g. why I'm looking to switch).

Verdict: Selected (heard back after 2 days)

✅ Selected. Final confirmation came about a week after the last round, and the offer letter arrived about 2 weeks later.

01
Mini Alerting Service API
Data Structures & Algorithms
Build a mini alerting service with REST APIs to ingest alerts and list them. Based on the severity of each alert, the service should either trigger a notification, skip the alert, or only log the incident. The service must also handle deduplication of alerts and gracefully manage failures of external calls.
02
Trip Management Service Design
System Design
Design a trip management service that manages trips, drivers, and admins. Admins can view trips and assign drivers. The design should emphasize concurrency control mechanisms, providing both a low‑level API/DB schema (LLD) and a high‑level architecture (HLD). Include code snippets for critical flows and diagram the solution using tools like Excalidraw or Draw.io.