10 Brutal Truths That Engineers Must Accept in 2025 | Before It’s Too Late…

Summary

In this brutally honest video, Savendra Puri shares valuable career insights from his 20+ years of experience in software engineering and DevOps. He highlights common mistakes like chasing too many things at once, focusing on certifications without purpose, and failing to articulate one’s work. Puri stresses the importance of deep expertise, practical experience, effective communication, and the need for career self-assessment. He urges viewers to focus on making a real impact, stop comparing timelines with others, and to shift from tactical thinking to a strategic, leadership-oriented mindset.

Takeaways

• 😀 Focus on one core area rather than spreading yourself too thin with multiple interests or certifications.
• 😀 DSA (Data Structures and Algorithms) is important for job entry, but it won't make you a great software developer. Focus on system design and real-world problem solving.
• 😀 Side projects are often ineffective unless they provide unique value or deep research. Build impactful projects that showcase your understanding.
• 😀 Master the ability to explain your work clearly and concisely in different formats, as communication is key to showcasing your contributions.
• 😀 Everyone’s career timeline is different. Stop comparing yourself to others and focus on your own growth and progress.
• 😀 Be aware of career plateauing. If you've been in the same role for too long without learning or growing, it's time to make a change.
• 😀 As you progress, shift your focus from just solving problems to making a bigger impact with your decisions and leadership.
• 😀 Don't expect promotions or salary hikes simply by doing your job well. Learn how to market your work and ensure people know about your contributions.
• 😀 Avoid becoming a busy leader who spends all day in meetings. Focus on impact, delegate tasks, and prioritize your time effectively.
• 😀 Don’t become a career bureaucrat. Stay hands-on in your field, whether it’s coding or another skill, to maintain relevance and leadership credibility.

Q & A

What is the main takeaway from the speaker’s first brutal truth?

The first brutal truth emphasizes that many people are either chasing the wrong goals or trying to pursue too many different things at once, which dilutes their focus and progress. Instead, it is suggested that you should focus deeply on one core domain and build expertise in that area.

Why does the speaker say DSA (Data Structures and Algorithms) is not equivalent to career growth?

The speaker clarifies that while mastering DSA can help you pass technical interviews, it doesn't make you a well-rounded developer or engineer. DSA focuses on problem-solving but doesn't equip you with the skills needed to write quality, maintainable code, or to handle real-world challenges like system design and project delivery.

What is the issue with side projects according to the speaker?

The problem with side projects is that many people build projects that are too common or don't add unique value. The speaker warns that if you aren't deeply involved in creating something meaningful and distinct, it won't impress in interviews or truly demonstrate your technical capabilities.

How does the speaker suggest you should explain your work or projects?

The speaker recommends that you should be able to explain your project in different levels of detail—quickly, in a summary, and with more depth. Practicing these explanations helps ensure you fully understand your work and can communicate it clearly, which is crucial in interviews or team settings.

What is the danger of comparing your career progress to others, according to the speaker?

The speaker warns against comparing your journey to others, especially based on superficial information like LinkedIn posts or YouTube thumbnails. He emphasizes that everyone’s career path is different, and that it’s more productive to focus on your own growth, inspired by others, but not intimidated by them.

What should you do if you feel you've plateaued in your career?

If you feel stagnant in your career, the speaker advises conducting a self-audit of the past 6-12 months. Reflect on what you’ve learned, the impact you’ve made, and whether you’ve met new people or explored new opportunities. If you haven't, it might be time to shake things up to avoid becoming complacent.

What does the speaker mean by 'thinking beyond the code' as you progress in your career?

As you advance in your career, your value shifts from simply solving individual problems to a more strategic role that includes system design, architecture, decision-making, and mentoring. The speaker stresses that you need to focus on the broader impact of your work, not just writing code.

How does the speaker suggest you should approach salary raises or promotions?

The speaker points out that doing good work isn't enough on its own to get a promotion or salary increase. You also need to market your work effectively by speaking up in meetings, sharing your accomplishments, and ensuring the right people know your contributions. Consistency is key.

What does the speaker mean by 'managing your work' versus 'multiplying impact'?

The speaker warns against becoming caught up in a cycle of constant meetings and tasks that don’t lead to real impact. Instead, you should delegate tasks, stop micromanaging, and focus on creating value by ensuring that meetings and work are purposeful and contribute to larger goals.

Why is it important to avoid becoming a 'career bureaucrat' as per the speaker?

The speaker criticizes individuals who focus too much on corporate jargon and frameworks without staying hands-on with the technical work or real-world challenges. He emphasizes the importance of remaining connected to execution and technology to truly lead and make an impact, rather than just managing from a distance.