Shri Ramdeobaba College, Nagpur
Built the foundation in engineering principles, problem-solving, and analytical thinking. Discovered programming during final year projects and realized I enjoyed debugging code more than circuits.
Freelance Journey Begins
Started freelancing while in college. Learned HTML, CSS, JavaScript by building real projects for clients. Spent more time on Stack Overflow than in lectures.
Loud Mob Media
Joined as a junior developer, working on interactive web applications. Learned React, Node.js, and that 'it works on my machine' isn't a valid deployment strategy.
Loud Mob Media
First promotion! Started mentoring junior developers and leading technical decisions. Discovered that explaining code to others is the best way to understand it yourself.
Loud Mob Media → Ei
Transitioned to leadership roles. Joined Ei as Engineering Lead, where I learned that managing people is harder than managing servers.
Ei - Learning Applications
Leading the Learning Applications team, building educational tools that actually help students learn. Turns out, the hardest part isn't the code - it's understanding what teachers really need.
The best code reviews happen over coffee, not in pull requests.— What I've learned about technical leadership
Understanding the problem is more important than writing clever code. I focus on building solutions that make sense to the people who will use and maintain them.
The fastest way to understand a system is to break it safely. I encourage experimentation, testing boundaries, and learning from failures in controlled environments.
Before writing any code, we ask: what problem are we actually solving? I prioritize features that users need over features that sound cool in meetings.
Future you will thank present you for writing things down. I insist on clear documentation, not because it's required, but because it saves everyone time later.
A working solution today beats a perfect solution next month. I prefer shipping something useful and improving it based on real feedback.
The best technical decisions come from understanding the real constraints and needs. I spend more time listening to my team than talking at them.
Built client-side and server side applications from scratch and optimized API performance by 73% while ensuring backward compatibility.
Spearheaded the migration to a modern tech stack, resulting in a 45% performance improvement and architected scalable learning platform features that support 20,000 users.
Successfully mentored 6+ developers on the Learning Applications team, resulting in improved code quality and 30% faster feature delivery through structured coaching and technical guidance.
Architected and implemented scalable learning platform features that support 20,000 users, improving system performance and reducing server costs.
Established technical standards and documentation processes for educational applications, reducing development time by 35% and improving code maintainability across learning platform projects.
Led the development of interactive learning modules and assessment tools, resulting in 25% improvement in student engagement metrics and learning outcomes.
These metrics are extracted from real projects and work experiences across my career. Each number represents actual improvements delivered - from API optimizations and system performance boosts to developers mentored and users impacted through scalable educational platforms and applications.
Building learning platforms that teachers actually want to use and students don't immediately close. Turns out, good UX matters more than fancy features.
Using AI to help with the boring parts of education so teachers can focus on actually teaching. No, we're not replacing teachers with robots.
Helping developers get unstuck, reviewing code that doesn't make me cry, and trying to create an environment where people actually want to come to work.
Building systems that can handle more users without falling over. The goal is to sleep through the night without getting paged.
I'm working on making educational software that teachers don't hate and students might actually use. This means better AI integration, simpler interfaces, and systems that work reliably. The goal is simple: build tools that solve real problems instead of creating new ones.
