High Growth Engineer

High Growth Engineer is a Substack focusing on enhancing the careers of software engineers through practical advice on productivity, leadership, communication, and mentorship. It combines actionable strategies with personal growth insights to navigate career progression, from junior roles to senior leadership, emphasizing the importance of mentorship, effective planning, and continuous learning.

Career Development Productivity Leadership and Management Communication Skills Technical Skills Mentorship Negotiation and Compensation Work-Life Balance

The hottest Substack posts of High Growth Engineer

And their main takeaways

5 crucial ways to improve your Slack communication as an engineer

130 implied HN points • 23 Apr 23
  1. Improving Slack communication is crucial for software engineers' career growth.
  2. Mastering asynchronous communication tools like Slack can lead to quick seniority advancements.
  3. Using Slack effectively on a daily basis can significantly impact one's career trajectory.

How to get estimates right 95% of the time ✅

102 implied HN points • 30 Apr 23
  1. Estimating can be stressful and difficult, but with practice, you can improve.
  2. Mistakes in estimating are a part of the learning process.
  3. Getting estimates right most of the time is achievable with time and experience.

9 key lessons learned on my path from Engineer to VP 🔑

2 HN points • 21 Jan 24
  1. Become an expert in your domain to gain visibility and transition to leadership roles.
  2. Learn to handle stress and manage it effectively as you climb the career ladder.
  3. Avoid complacency, seek out challenging projects, and continuously strive for growth to advance in your career journey.
Get a weekly roundup of the best Substack posts, by hacker news affinity:

A Guide to Public Speaking for Software Engineers

2 HN points • 05 Nov 23
  1. Feedback on improving communication skills is crucial for software engineers.
  2. Don't rely solely on technical skills, enhance communication skills for growth.
  3. Public speaking is important for software engineers to reach their full potential.

Why, how much, and when you should be taking time off as an engineer

1 HN point • 14 Jan 24
  1. Taking time off helps you grow as an engineer by providing fresh perspectives and avoiding burnout.
  2. It's recommended to take at least 5 days off per quarter and communicate with your team about your time off.
  3. Taking time off also gives you the opportunity to learn outside of work, improving your skills and contributing back to your team.

The Journey to Staff Engineer: Main takeaways

1 HN point • 10 Sep 23
  1. The post discusses key takeaways from a live session with 5 Staff Engineers.
  2. It mentions that a Staff Engineer is one level above a Senior Engineer at Big Tech companies.
  3. The post offers a link to subscribe for a 7-day free trial to access the full archives.