In one paragraph
Darwinbox is an enterprise HR platform. I joined as an intern in January 2025, moved into the Core Engineering team when I converted to SDE-1 in July 2025, and left in August 2026. The work was the layer underneath an HR product that nobody sees when it works: who is allowed to see what, what changed and when, how locations and employees get provisioned, and how the product reads in languages other than English. Everything below is at the level of detail on my resume.
Audit trail migration
The audit trail recorded changes across more than 65 entity models inside the main application. I drove its migration into a dedicated microservice in phases across three releases.
What made it hard was the shape of the data rather than the volume. Each entity model has its own field types and its own web of linked collections, and an audit record is only useful if the lookups that make it readable (who changed which record, under which tenant) resolve exactly as they did before. So the work started with an inventory of every model and relation, and of each field that needed special handling, mapped out before the service was written.
The constraint was that production audit coverage could not have a gap at any point. Entities moved in slices. For each slice the new service was verified against the existing trail before it became the source of truth, with the old path still writing until the comparison held, so a problem meant a rollback rather than a missing record. Three releases later the main application no longer owned auditing at all.
Event-driven location provisioning
Location provisioning ran as a scheduled CRON job, so a new location only existed after the next batch. I refactored it into event-driven creation, and a bottleneck that implementation teams hit on every rollout went away.
Effective Date History
I contributed to the design and delivery of Effective Date History, which gives the platform point-in-time snapshots of employee data: what a record looked like on a given date, as well as what it looks like now.
Template Permission Roles
I designed and delivered an automated Template Permission Role system for tenant-level access control, so permission configuration follows organisational hierarchies instead of being assembled by hand for each tenant.
Reliability and localisation
I diagnosed and resolved defects across the bulk data import modules that ingest employee and organisational records, and implemented Multi-Language Framework support to close gaps in i18n coverage for multilingual enterprise deployments.
Internship
Before converting to SDE-1, I built a simulation framework in Next.js for custom automation workflows. It let teams preview how a workflow would behave against production-equivalent configuration before deploying it live.