Stories
Stories from engineering leaders in the Philippines
We asked the people in the room. These are their words, from interviews recorded at our meetups and the feedback forms attendees fill in after each edition.
Attendee stories
Why engineering leaders join eHeads
Every technical person really passionate about creating projects or maybe just a startup should go here, because you'll be surrounded by other builders, by other engineering heads.
After attending several eHeads meetups, it was very helpful for me to hear perspectives from those in the actual leadership positions.
Interviews and takes
Engineering leadership advice
Mentoring and feedback
How the leaders we interviewed coach their people, run one-on-ones and deliver feedback that leads somewhere.
5 answers
Underperformance and hard calls
Managing underperformers, resolving conflict, and the decisions that never get easier.
4 answers
Stakeholders, scope and alignment
Aligning engineering with product and the business, explaining technical work to non-technical people, and protecting scope.
9 answers
Building and inheriting teams
Starting a team from scratch, taking over someone else's team or codebase, and building a culture that keeps improving.
9 answers
From engineer to leader
Whether to move from IC to management, and what the leaders we asked think makes a great software engineering leader.
5 answers
Keeping teams current
Adopting new tools without chasing every shiny one, and keeping a team learning.
5 answers
Feedback forms
Straight from the feedback forms
What's your biggest takeaway from all the talks we had?
There are practical use cases of AI in software engineering. It's there to supplement, not replace.
What's your biggest takeaway from all the talks we had?
Mostly about connecting to such excellent devs, engineers, and founders.
Your turn
Come to the next eHeads.
Open to every technology leader, especially new ones. It's free.