We Onboarded a New Engineer in 2 Hours Instead of 2 Weeks
A Mumbai-based lending fintech, 6 years old, 28 engineers. They hired Priya Nair, a senior backend engineer from a Python/Django background, to join their Node.js team. The codebase had 6 years of undocumented decisions baked in. Their last onboarding took 14 working days before the new hire felt confident enough to open a PR.
The Onboarding Problem Nobody Talks About
Engineering teams measure onboarding time in weeks. The fintech industry is worse: compliance requirements mean every piece of code has a history that matters. Touch the wrong thing and you could break a regulatory audit trail. Most new engineers at this company spent their first two weeks reading old PRs, asking seniors questions, and building a mental map that existed nowhere in documentation.
The engineering manager, Rohan Mehta, decided to try something different with Priya. On her first morning, before any meetings, he gave her one thing: the ArchSetu report for the main repository.
What She Saw in 10 Minutes
The call graph alone changed everything. Priya could see which functions were entry points to the loan processing pipeline. She could see which utility functions were called from 40 different places and therefore untouchable without massive test coverage. She could see where the highest complexity clusters were, which told her exactly where the team had been firefighting.
“The call graph was the thing nobody could ever draw for me in previous jobs. Every company has it in someone's head. ArchSetu put it on a screen in 30 seconds. I knew which functions to touch and which ones to stay away from before I read a single line of actual code.”
Priya Nair, Senior Backend Engineer
Day Two: A Real Pull Request
On her second day, Priya submitted a PR. A real one, not a "fix a typo to learn the pipeline" PR. She had identified a dead code cluster around the loan disbursement flow, confirmed through ArchSetu that none of the functions had callers, cross-checked with the blast radius tool, and submitted a clean removal PR with a link to the ArchSetu report as justification.
The PR was merged in the same day. Her tech lead said it was one of the most well-evidenced cleanup PRs he had reviewed.
What Changed for the Team
Rohan made ArchSetu reports part of the standard onboarding kit. Every new engineer gets the report on day one. The question "can you explain the architecture?" got replaced with "here is the architecture, what questions do you have?" Average time to first meaningful PR dropped from 14 days to 3.
Run ArchSetu on your own codebase
Paste a GitHub URL and get your full analysis report in under 60 seconds. Sign up first to save the results, or try it free without an account.
Analyze your repository