Video summary

I Completed 5 Years in Tech as a Software Engineer: My Honest Journey & Learnings

Main summary

Key takeaways

Educational

Main ideas, concepts, and lessons (with key takeaways)

1) Career origin and background (non-CS entry into software)

  • The speaker completed 5 years in IT, starting from a first offer of ₹7.5 LPA and later reaching Amazon at an HD2-level.
  • Background:
    • Graduated from Electrical Engineering, NIT Kurukshetra, 2021
    • First engineer in their family; they lacked in-family CS/software mentors
    • Used YouTube/online resources, and relied on help from seniors/friends plus college support
  • Decision to start coding:
    • Began coding in the 6th semester
    • Initially struggled with problem-solving and building logic

Lesson: You don’t need a CS degree to reach high software roles, but you may need extra effort.

2) How COVID influenced development and hiring outcomes

  • COVID (2020) moved college online, giving the speaker more uninterrupted time to code/study.
  • They maintained strong academics:
    • Reported a consistently high ~9 CGPA in electrical
  • They studied some CS topics, but noted:
    • CS students often have a syllabus head start
    • Others must work twice as hard

Lesson: Environmental changes (like more time during COVID) can accelerate skill-building—use it intentionally.

3) First placement: persistence through rejections

  • During the 7th semester placement season:
    • Fewer companies visited due to post-COVID uncertainty
    • The speaker applied broadly to all eligible companies
  • Outcomes:
    • Cleared many online coding + aptitude tests and reached interviews
    • Faced repeated rejections across multiple rounds
    • Eventually received an offer of ₹7.5 LPA from a company in Noida

Lesson: Don’t treat rejections as a verdict—keep applying and improving until an offer lands.

4) Transition constraints: accepting the offer and still pursuing growth

  • Mentioned an NIT rule: once you accept one offer, you cannot sit for further campus companies.
  • They accepted the offer, despite uncertainty about future hiring, and simultaneously prepared for off-campus roles:
    • Updated LinkedIn and other portals
    • Continued interviewing while preparing

Lesson: Use the period after accepting an offer to continue building optionality (off-campus applications).

5) Growth through job changes (Societe Generale → TI → Amazon)

A) Society General (~₹16–17 LPA; ~2 years)

  • Received an offer from Societe Generale (described as a European/National bank of France).
  • Family preferred staying near home, but the speaker prioritized:
    • Faster learning via bigger projects
    • Better career trajectory
  • Why it helped:
    • Worked across front-end and back-end, and learned DevOps
    • Learned how big-company processes work (e.g., Scrum Master, Product Manager, business requirements)
    • Felt this could enable “full-fledged engineer” growth through real-world exposure
  • They emphasized they hadn’t learned many languages deeply in college (mainly DSA/C++), so this role expanded practical capability.

B) Texas Instruments (TI) as SD2/Senior Software Engineer (~2 years)

  • Left after ~2 years to pursue further growth.
  • Studied again during the job for DSA + System Design.
  • TI is described as a dream brand for electrical/ECE backgrounds, but they joined on the IT/software side.
  • Claimed benefits:
    • Ability to lead projects
    • Work across modern and legacy systems
    • Mindset shift: don’t cling to one language—be a problem solver and adapt
    • Exposure to multiple languages mentioned: Ruby, Perl, Scala, and PL/SQL (and legacy systems/types)

C) Amazon (final decision; ~7 months at time of telling)

  • Market conditions worsened after AI entry:
    • More competition
    • Layoffs from big companies increased the applicant pool
  • They kept preparing (DSA/system design) while interviewing.
  • After 8–9 months, they received multiple offers:
    • Two unicorn startups
    • Oracle
    • Microsoft
    • Amazon (final choice)
  • Negotiation and decision:
    • Chose Amazon and joined Feb 2026
    • Mentioned being offered L61 at Microsoft
    • Ultimately chose between Oracle vs Amazon

Lesson: Strategic job changes can increase both compensation and breadth of experience—but require constant upskilling and interview readiness.

Methodology / step-by-step pattern described (workflow)

Practical approach used across the career (implied “method”)

  • Start early and grind fundamentals
    • Begin coding in 6th semester (or as early as possible)
    • Practice problem-solving consistently (e.g., “Leetcode”/similar platforms)
  • Leverage available time
    • During COVID/online period: code/study heavily most of the day, then revise for exams
  • Use a broad placement application strategy
    • Apply to all companies you can
    • Clear online coding/aptitude tests first, then push toward interviews
  • Accept offers when needed, but keep preparing
    • If campus placements restrict re-entry after acceptance, pivot to off-campus:
      • Update LinkedIn and job portals
      • Interview in parallel with preparation
  • After switching companies, rebuild value
    • Expect to start “from zero” each time
    • Re-earn credibility through strong performance and challenging projects
  • While working, prepare for the next jump
    • Ongoing loop:
      • Work + update resume/portfolio
      • Study DSA + System Design
      • Do interviews regularly (sometimes across weekends/startup/interview rounds)
  • Adapt your skill identity
    • Don’t become “a Java developer”
    • Learn what the project needs; focus on solving problems end-to-end
  • Decision-making during multiple offers
    • Compare offers by:
      • Role level/scope
      • Learning opportunities
      • Compensation structure (including stocks)
    • Negotiate and choose based on long-term fit, not only money

What to avoid / warnings the speaker emphasizes

1) Avoid “company hopping” without skills

  • Explicit warnings against:
    • Switching too frequently (e.g., “every 6 months”)
    • Chasing only salary while failing to gain real capabilities
  • Consequences described:
    • Little/no meaningful growth or respect
    • Imposter-type feelings

2) Don’t run away from discomfort

  • Don’t instantly switch companies just because something feels uncomfortable.
  • Discomfort may include:
    • Hard work
    • Weekends
    • Toxic managers
    • Micro-management
    • Gatekeeping in approvals (e.g., delayed PR approvals)
  • Instead:
    • Stay and learn when you’re building skills and experience

3) Don’t believe the “glorified remote-life” myth

  • Pushes back against social media narratives like:
    • International trips
    • Constant fun/office perks
    • Games and free food only
  • Notes the real picture can include:
    • Overnight work sometimes
    • Weekend work sometimes
    • Toxic colleagues/managers sometimes
    • Gatekeeping and friction

Reality check on work-life balance and company dynamics

  • Compares pre-AI vs post-AI market/company posture:
    • During 2021–22 (when the Society General period started), engineers felt they had more leverage
    • With AI and layoffs, competition increased and companies became more demanding
  • Claims:
    • Work-life balance may decline slightly post-AI
    • At Amazon (high scale), it isn’t as “chill” as some smaller/European companies
    • More is required due to scale

Personal mindset lessons: imposter syndrome and “start from scratch”

  • Describes recurring imposter syndrome after every switch:
    • At Society General: felt less qualified vs peers with more CS/internship exposure
    • At TI: again had to prove themselves at a new company level
    • At Amazon: again needed to build an image from zero
  • Resolution:
    • Treat it as normal; it takes time to build credibility again

Lesson: Imposter feelings are expected during transitions—don’t let them stop you.

Communication and teamwork as a core skill (not just coding)

  • Being a good engineer includes:
    • Writing documents
    • Participating in meetings
    • Communicating with team and leadership
    • Estimating tasks and delivering reliably
  • Example:
    • If a deadline becomes risky (e.g., realizing on day 3 that work won’t finish by day 4), communicate early about the risk.

Lesson: Communication up the chain and honest risk-sharing are essential professional skills.

Closing purpose of the video

  • The goal is to provide real guidance without hype—“no BS”.
  • Encourages viewers to look beyond curated success stories and understand tradeoffs.

Speakers / sources featured (as stated or implied)

  1. Primary speaker: The YouTube creator (name not explicitly stated in subtitles; referred to as “brother” throughout; father reacted to the offer letter video).
  2. Family source mentioned: Father (reacted to the offer letter; the video went viral).
  3. Referenced external sources (not speakers):
    • YouTube / online platforms (for guidance/learning)
    • Seniors and friends (peer guidance)
    • Company names: Amazon, Societe Generale, Texas Instruments (TI), Oracle, Microsoft, plus two unicorn startups (not individually named)

Original video