Engineering Career Roadmap: From Problem Solving to System Design

The Honest Advice Nobody Gives You in University

Srejon Khan presents a technical progression framework for engineering students and graduates. He asserts that mastering problem-solving fundamentals is the primary job for early-career developers to avoid freezing during technical rounds.

Why This Matters

University curricula often emphasize theoretical models, but the technical reality of software engineering requires deep knowledge of system trade-offs, such as primary-secondary-secondary replica sets in MongoDB. Understanding how architecture behaves under 10x traffic or service failure is more critical than memorizing frameworks, as these represent the high-stakes decisions senior engineers face weekly.

Key Insights

• Hash map O(1) complexity and binary search tree logic are foundational vocabularies for engineering careers (Khan, 2026).
• High Level Design (HLD) focuses on fault tolerance and node failure scenarios rather than simple implementation (Khan, 2026).
• Low Level Design (LLD) and SOLID principles should be applied after experiencing code breakage to understand their necessity.
• Daily problem-solving rituals, such as one LeetCode exercise every morning, outperform short-term interview cramming.
• Distributed systems knowledge, including concurrent database write handling, offers higher market value than knowing multiple frameworks.

Practical Applications

• Use case: Configuring a MongoDB p-s-s replica set to manage primary node failures and read/write behavior. Pitfall: Following basic instructions without analyzing architectural trade-offs leads to brittle systems.
• Use case: Building original projects to solve specific problems for personal portfolios. Pitfall: Cloning tutorial repositories fails to demonstrate the independent problem-solving skills recruiters prioritize.
• Use case: Participating in open-source code reviews to develop technical taste and understand complex structuring. Pitfall: Relying on a ‘framework-first’ approach prevents deep understanding of underlying software principles.

References:

• https://dev.to/srejon_khan/the-honest-advice-nobody-gives-you-in-university-41cd