012018 — 2022
FOUNDATION
Electrical & Electronics Engineering
Engineering gave me a systems mindset: break a complex problem into parts, reason about dependencies, and build from a technical foundation rather than from surface-level familiarity.
← JOURNEY CAREER TRANSITION / ENGINEERING
UPSC → SOFTWARE ENGINEERING
From civil-services preparation to systems that ship.
A deliberate shift from disciplined preparation to practical engineering — rebuilding technical depth from the ground up and proving it through work that can be used, deployed, debugged, and explained.
I graduated in Electrical & Electronics Engineering in 2022, spent the next phase preparing seriously for UPSC Civil Services, and then chose to move into software.
ENGINEERING FOUNDATION→UPSC PREPARATION→TECHNICAL TRANSITION→PRODUCTION WORK
01 / THE PATH
Not a straight line. A useful one.
The important part of the transition is not pretending every phase was software experience. It is being clear about what each phase built — and what had to be learned from scratch.
022022 — 2025
DEPTH
UPSC Civil Services Preparation
I spent this period in focused preparation. It strengthened research, consistency, communication, decision-making, and the ability to learn large bodies of material from first principles.
032025 — 2026
TRANSITION
Software, Data & Cloud
I moved deliberately into software through hands-on web development, backend APIs, SQL and relational data, AWS, deployment, debugging, and production-oriented project work.
042026 — NOW
SHIP
Building Real Systems
The goal shifted from finishing tutorials to understanding complete product flows — interface to API, API to data, deployment to monitoring, and iteration after real usage exposes what needs improvement.
02 / WHAT CARRIED OVER
Different domain. Transferable operating system.
UPSC preparation did not make me a software engineer. But it did strengthen habits that became useful once I started doing the technical work.
01RESEARCH
Learn large systems without getting lost in them.
UPSC preparation forced me to work across broad subjects, separate signal from noise, connect ideas, and keep revising until the underlying structure made sense.
02DISCIPLINE
Consistency became a system, not a mood.
Long preparation cycles taught me to keep showing up, work through slow progress, and stay with difficult material long enough for it to become usable knowledge.
03FIRST PRINCIPLES
Understand why before memorising how.
That habit now shapes how I learn software: trace the request, understand the data flow, reproduce the failure, and then fix the underlying reason instead of copying a patch.
04COMMUNICATION
Complex ideas should become explainable.
Structured writing and repeated synthesis improved how I break problems down, document decisions, explain trade-offs, and communicate what a system is doing.
03 / THE REBUILD
I did not try to convert preparation into experience. I built new evidence.
Once I decided to move into technology, the priority was simple: stop treating software as another syllabus and start treating it as a craft.
That meant writing code, breaking it, debugging it, understanding browser and server behaviour, learning relational data, deploying applications, reading logs, and repeatedly connecting concepts that courses often teach in isolation.
WEB FUNDAMENTALS
HTML, CSS, JavaScript, browser behaviour, responsive interfaces, DOM and user interaction.
BACKEND
Node.js, Express, REST APIs, authentication, validation, application structure and request lifecycles.
DATA
SQL, MySQL, relational modelling, querying, persistence, and thinking about data as part of product behaviour.
CLOUD / DELIVERY
AWS, containers, CI/CD, deployment, monitoring, reliability, and the work required after code leaves a laptop.
04 / PROOF OF TRANSITION
The answer to a career gap is evidence.
I cannot change the chronology of my path. What I can control is the quality of evidence that comes after it.
PRODUCTION PRODUCT / 01
LeadKavach
Full-stack CRM/SaaS work across interfaces, APIs, authentication, relational data, messaging workflows, mobile delivery, and production operations.
VIEW CASE STUDY ↗FULL-STACK SYSTEM / 02PYQPath
An exam-intelligence platform connecting search, paper generation, user/admin workflows, MySQL-backed data, hosting, and analytics.
VIEW CASE STUDY ↗CLOUD VALIDATION / 03AWS Certified Solutions Architect – Associate
Supporting evidence for cloud architecture fundamentals alongside the deployment and infrastructure work demonstrated across projects.
VIEW CREDENTIAL ↗05 / IF YOU ARE MAKING A SIMILAR MOVE
Do not hide the gap. Reduce the uncertainty around what you can do now.
01
Be precise about the past. Preparation is preparation; engineering experience should come from engineering work.
02
Choose depth over endless courses. Learn enough of one stack to follow a feature from UI to API to database to deployment.
03
Build proof that can be inspected. Case studies, working products, architecture decisions, debugging stories, and production trade-offs are more useful than a long tools list.
04
Expect fundamentals to matter. JavaScript, HTTP, databases, browser behaviour, APIs, Git, debugging, and basic systems thinking compound across frameworks.
05
Let the transition become part of your story, not your apology. The goal is not to sound conventional; it is to make the present capability credible.
06 / NOW
The direction is software. The standard is production.
I am now focused on strengthening full-stack fundamentals, backend and API engineering, relational data, AWS and cloud delivery, and the engineering judgement that comes from shipping and debugging real systems.