---

💫 About Me

name: Utkarsh Pawade
role: Full-Stack Developer | Aspiring Backend & Distributed Systems Engineer
education: B.Tech CSE, Final Year @ IIIT Sonepat
focus:
  - Backend Engineering
  - Distributed Systems & Large-Scale System Design
  - DevOps & Cloud Infrastructure
  - Capacity Estimation & Requirements Analysis
currently_learning:
  - High-Throughput Backend Optimization
  - Container Orchestration (Kubernetes deep-dive)
  - Event-Driven Architectures (Kafka, Redis Streams)
  - Agentic AI Workflows
problem_solving: 500+ DSA problems across LeetCode / CodeChef / Codeforces
portfolio: https://portfolio-eight-jet-16.vercel.app/
ask_me_about: ["System Design", "Scalable Backends", "DevOps", "MERN", "Cloud"]

• 🔭 Currently architecting distributed, fault-tolerant systems with a focus on rigorous requirements analysis and capacity estimation before writing a single line of code.
• 🌱 Diving deep into Backend Engineering, DevOps, and Cloud-Native patterns — caching, queues, sharding, observability.
• 💬 Ask me about system design trade-offs, API design, CI/CD pipelines, or competitive programming.
• ⚡ Fun fact: I treat every project like a mini production system — load tests, monitoring, and a runbook included.

---

🌐 Connect With Me

---

🛠️ Tech Stack

👨‍💻 Languages

🎨 Frontend

⚙️ Backend

🗄️ Databases & Caching

☁️ Cloud & DevOps

🤖 AI / ML

---

🏆 Competitive Programming

800+ DSA problems solved across the major judges. I treat CP as a daily gym session for algorithmic thinking.

LeetCode Stats	CodeChef Stats	Codeforces Stats

---

📊 GitHub Analytics

📈 Contribution Graph

---

---

🏅 GitHub Trophies

---

🧠 What I'm Building Toward

• Backend Engineering — designing APIs that don't fall over at 10× traffic.
• Distributed Systems — consistency models, leader election, replication, sharding.
• System Design — every project starts with a one-pager: requirements → bottlenecks → capacity estimates → component diagram → trade-offs.
• DevOps Mindset — containerize early, monitor everything, automate the boring parts.
• Cloud-Native — AWS / GCP / Azure primitives, IaC, and serverless patterns.

_{Thanks for stopping by — let's build something that scales. 🚀}