Brief
Built internal business systems and customer support platforms while growing from a beginner developer into a trusted contributor and mentor.
Experience
Justdial
First software engineering role where I grew from learning the fundamentals into a trusted contributor and mentor while building internal business systems.
Built internal business systems and customer support platforms while growing from a beginner developer into a trusted contributor and mentor.
Justdial was my first real software engineering role.
When I joined, I had cleared the interview, but the reality was that I still had a tremendous amount to learn.
The first few months were spent understanding how professional software development actually worked.
Code reviews.
Production systems.
Business requirements.
Technical trade-offs.
Working with teams.
Everything was new.
Over time, I went from learning the fundamentals to becoming a trusted contributor within the team.
I started by implementing features.
Eventually I was helping define requirements, identify better solutions, contribute across the stack, and guide junior developers.
Looking back, Justdial was where I learned how software creates measurable business value.
A significant portion of my work focused on internal systems used by customer support and operational teams.
These platforms were responsible for helping teams manage customer issues, communication workflows, escalations, and operational processes.
The goal was never simply to build screens.
The goal was to help people resolve customer problems more effectively.
Many of the challenges we encountered were not technical problems.
They were process problems.
Teams were spending time moving information between systems, coordinating manually, and following repetitive workflows.
By simplifying these processes and building the right tools, we were able to significantly improve operational efficiency.
Some workflows that previously required days of coordination could eventually be completed within minutes.
As my understanding of the business improved, my role evolved beyond implementation.
I became increasingly involved in understanding why a feature was being built, who it was helping, and whether there was a simpler way to solve the underlying problem.
This was my first exposure to thinking beyond code and into product design and user experience.
I contributed to communication-focused initiatives, including video calling and real-time interaction features.
These projects introduced challenges around reliability, performance, user experience, and real-time communication.
They also gave me exposure to problems that extended beyond traditional CRUD applications.
Although my primary strength was frontend development, I regularly worked with backend systems and APIs.
This period helped me develop a stronger understanding of how complete systems are built and how decisions on one side of the stack affect the other.
As my responsibilities expanded, I eventually helped guide two junior developers.
This was my first experience helping others navigate technical problems, reviewing approaches, and sharing lessons I had learned myself.
It reinforced the idea that engineering is not only about writing code but also about helping teams succeed.
Justdial taught me how software creates value inside large organizations.
More importantly, it taught me how to learn.
I joined without a deep understanding of professional software engineering.
Over time, I learned how to navigate large codebases, collaborate with teams, understand business requirements, and build systems that solved real operational problems.
It also taught me that technical complexity is not always the most important thing.
Some of the most impactful work comes from understanding a process deeply and removing friction from it.
This role established many habits that still influence my work today:
Understand the user.
Understand the business.
Understand the process.
Then build the solution.
Justdial represents the transition point between learning software development and practicing it professionally.
It was the place where I developed the technical foundations, business awareness, and product mindset that would later help me succeed in more complex environments.
It taught me that great software is not measured by technical sophistication alone.
Great software helps people accomplish meaningful work more effectively.