↓ Skip to main content
nSkillHub
Lakshay Jawa

Lakshay Jawa

Engineering Leader | Architecting AI-Driven Execution | Scaling Distributed Systems

System Design · Behavioral Interviews · Posts

About nSkillHub
#

A passion-driven space for learning — system design, Java, Spring, and software engineering best practices. As a software engineer with years of experience, this blog shares insights, deep-dives, and interview prep material. Future topics will expand into movies, photography, travel, and more. Stay tuned!

Contact Lakshay on LinkedIn

Recent

Led a Team Through a Significant Technical Change They Were Resistant To

·19 mins
Behavioral Interview Behavioral Leadership Star-Method Em Director
S1 — What the Interviewer Is Really Probing # The scoring dimension here is change leadership under resistance — not change management in the HR-training sense, but your ability to drive conviction-led transformation while preserving the trust of the people who are pushing back. Interviewers care about whether you understand why resistance exists. Is it fear of irrelevance? A legitimate technical objection? Loss of ownership over something engineers spent years building? Leaders who conflate all resistance as “people being difficult” and steamroll it create short-term compliance and long-term resentment. Leaders who can diagnose and address root cause create lasting followership.

URL Shortener (bit.ly)

·14 mins
System Design Classic Url-Shortener Base62 Distributed-Systems Caching Scalability
1. Hook # Every time you click a bit.ly or t.co link, a distributed system silently resolves a 7-character code to a full URL and redirects you — in under 10 milliseconds — before your browser even renders the loading spinner. Behind that invisible handshake sits a deceptively rich design problem: how do you build a service that creates billions of short codes, never loses a mapping, and serves hundreds of thousands of reads per second with single-digit millisecond latency, all while preventing abuse, surviving data-centre failures, and staying profitable?

Data Pipeline and Analytics: OLTP vs OLAP, Batch vs Streaming, CDC

·6 mins
As systems grow, the gap between operational data (what your application uses to run) and analytical data (what your business uses to make decisions) becomes significant. Understanding how to design data pipelines that bridge this gap is an EM-level concern.

Testing Strategy: Test Pyramid, Contract Testing, and Coverage Pragmatics

·7 mins
Testing strategy is an EM-level concern because it directly affects delivery velocity, production reliability, and onboarding speed. Too little testing = production incidents. Too much ceremony = slow CI and frustrated engineers. The goal is the right tests in the right places.