Video summary

Senior Software Engineer at Microsoft | Madhav Bahl | College, Hackathons, Tech & AI

Main summary

Key takeaways

Technology

High-level overview

The video is an interview-style discussion hosted by Kartik, featuring Madhav Bahl (Microsoft Senior Software Engineer). The conversation focuses on career growth for software engineers—especially for college students transitioning into industry—and includes practical guidance on mindset, hackathons, learning paths, and what “software engineering” actually involves beyond just coding.

Key advice & themes (technological/career concepts)

1) Mindset for junior developers: ask “why” (not just “do it”)

Madhav emphasizes that freshers often execute tasks exactly as instructed by seniors/PMs. Instead, he recommends building a habit of asking “why” you’re doing a task:

  • What is the feature goal?
  • Who benefits (users)?
  • What impact will it have on the business?
  • Is it aligned with the product direction?

This deeper understanding helps prevent becoming overly dependent on commands.

He also frames this as relevant in the age of AI agents: if you only follow instructions, you risk becoming “replaceable” by automation/agents that can execute tasks.

2) Software engineering is more than coding (system thinking)

Madhav argues that coding is only one part of software engineering and uses a “house building” analogy:

  • Coding = laying bricks
  • Software engineering also includes:
    • Design & architecture
    • Testability (unit, functional, end-to-end, smoke testing)
    • Durability/robustness (avoid breaks/leaks—analogous to engineering failures)
    • Monitoring & operational readiness
    • CI/CD and release processes
    • Collaboration and enforcing architecture via code patterns rather than documentation alone

He stresses that in industry you must care about the full product lifecycle, not just implementation.

3) How seniors differ from SDE-2: impact and influence

As you grow from SDE-2 to Senior, the scope shifts:

  • Senior engineers work on problems that influence other people and shape architecture/standards.
  • They may:
    • Review PRs
    • Guide architecture decisions
    • Mentor others
    • Consider broader business impact

He notes there isn’t one universal job description, but the general growth direction is to think beyond your immediate feature/team.

4) Learning & career growth through hackathons

A significant portion covers hackathons as a practical training ground:

  • Hackathons force focused learning because you must build under constraints (little time, high urgency).
  • You quickly learn basics of new technologies—even if the final idea isn’t “winner-grade.”
  • They build the habit: learn + build + iterate, often using documentation/videos while constantly shipping.
  • They improve networking because industry mentors/judges are present, and you can stay in touch.

Benefits mentioned include:

  • Cash prizes (early motivation)
  • Learning cycles like 36 hours / 12 hours / fixed hackathon timelines
  • Exposure to real-world expectations around scalable production readiness, beyond typical college projects

5) System design / architecture / CI-CD should start early (even before you “need” it)

Madhav suggests DSA is necessary, but it becomes insufficient later.

Recommendation:

  • Start learning System Design, Architecture, and CI/CD
  • Knowing only coding can make you fall behind once interviews and real systems become more complex

He also mentions that industry interviews reward system design knowledge as a “green flag.”

6) Enforcing architecture through code, not documents

He provides practical enforcement ideas:

  • Use patterns/interfaces (conceptually referenced example: a state pattern, where each state implements a state interface).
  • Avoid brittle structures like heavy if-else / switch that make maintenance hard.
  • Use CI so tests run on every PR (quality gates prevent merging broken changes).

He emphasizes that:

  • Automation pipelines keep code reliable
  • Deployment/ring strategies and staged rollouts are real parts of engineering—not just “release day” logistics

7) Luck + effort + resilience (career outcome framing)

While not purely technical, this shapes how you plan your career:

  • He acknowledges luck plays a role in internships/offers.
  • Effort still matters: prepare, reflect, and keep iterating.
  • For rejection, he advises asking:
    • What could you do differently?
    • What wasn’t working (skills/process)?

8) Personal learning path: from C++ → teaching/mentoring → software engineering

Madhav describes early motivation around programming (e.g., C++ / “hello world”). He also discusses switching streams (electronics/communication to CS) and how persistence helped.

He credits mentoring and talking to people as a form of “reverse mentoring” and as an accelerator for learning.

Sources / main speakers

  • Madhav Bahl — Senior Software Engineer at Microsoft (guest)
  • Kartik — Interview host / mentor / podcast creator (main speaker, interviewer)

Original video