Start with the system boundary
Clarify data ownership, API contracts, permissions, and failure paths before implementation grows expensive.

Software Engineer
Full-Stack Developer (Backend Focused)
A passionate software engineer focused on building scalable, reliable, and user-centric digital products. I enjoy solving complex problems, learning new technologies, and turning ideas into production-ready systems.
Currently, I'm a Computer Science student with hands-on experience in building modern web applications using React, Next.js, Node.js, and TypeScript.
I've worked on projects involving authentication systems, REST APIs, databases, and performance-optimized frontends. I'm particularly interested in system design, backend architecture, and cloud-native development.
@codes-stories
Problem Solving
@gaurav_krrr
@gauravkrrr
The landing page now behaves like a small product: it records real visits, captures recruiter context, and makes system ownership visible before an interviewer even opens a project.
Skill proficiency across technologies
My journey as a developer
Tech Startup
Building scalable microservices, REST APIs, and real-time systems using Node.js, React, and MongoDB. Led migration from monolith to microservices architecture.
University
CGPA: 8.5+ | Coursework: Data Structures, Algorithms, OS, DBMS, System Design, Computer Networks
Amazon Web Services
Foundational understanding of AWS Cloud services, security, architecture, pricing, and support.
GitHub Community
Contributed to 10+ open source projects. Active in MERN stack and DevOps communities. 80+ repositories with 25+ followers.
Meta (Coursera)
Professional certificate covering React, Figma, version control, and testing with 95% completion rate.
Real-time activity & interactive code playground
function* fibonacci() {
let [a, b] = [0, 1];
while (true) {
yield a;
[a, b] = [b, a + b];
}
}
const fib = fibonacci();
for (let i = 0; i < 10; i++) {
console.log(fib.next().value);
}
// Output: 0, 1, 1, 2, 3, 5, 8, 13, 21, 34Developer profile
My focus is practical engineering: clean UI, useful backend features, and enough system thinking to explain tradeoffs clearly in an interview. The site now highlights the work, the architecture, and the proof points without making visitors hunt for them.
Next.js frontends, API routes, authentication, dashboards, and database-backed workflows.
REST APIs, MongoDB models, validation paths, and production-minded service boundaries.
Responsive UI, readable flows, analytics signals, and features recruiters can actually test.
Admin tooling, protected routes, content publishing, and operational visibility.
System design case study
A concise look at the implementation today and the trade-offs I would make before increasing campus-scale traffic.
A focused MERN implementation for QR-based campus entry and exit records.
QR scan
Validation + workflow
Auth + API rules
Entry/exit records
Design decisions
Library
Programming Language

Programming Language

Version Control
Concept
Library
Framework
CSS Framework

Container

Server
Language
Automation
Database
Database
Database
Language
Testing Tool
Editor

Editor
Engineering approach
The work I enjoy sits between product requirements and dependable systems: clear boundaries, thoughtful implementation, and ownership after launch.
Clarify data ownership, API contracts, permissions, and failure paths before implementation grows expensive.
Treat authentication, validation, admin workflows, and useful signals as part of the feature—not follow-up work.
Choose the simplest solution that meets the product need, then document the constraints and next sensible improvement.
What colleagues say about working with me
“Gaurav's system design thinking is impressive for his experience level. His QR-based attendance system showed real architectural maturity.”












