Learn about engineering leadership in #hypergrowth from @akoskapui, VPE at @Shapr3D. Recruitment strategies, decision making and planning.

Full interview here: bit.ly/3m8H3e0

Interview by @FancyKarolina, powered by @codingsans.

#EngineeringManagement #hypergrowth100
Some key takeaways:

1. Create hiring requirements

Don't lower the bar in hiring, look for people as good or better than your existing employees. Create explicit requirements for each position so applicants are measured to the same standard whoever conducts their interviews.
2. Hire engineering managers with deep technical knowledge

This is essential for tech companies in hypergrowth. You need managers to mentor and support your junior employees and new hires. You can’t rely only on senior engineers for this, they’re busy coding and interviewing.
3. Scale decision making

As your organization grows you stop being able to make all the decisions yourself. Rely on your team and managers to help you shape the environment. The leader’s job isn’t micromanagement, but empowering employees to make decisions and stick to them.
4. Planning in hypergrowth

It’s impossible to plan for everything in hypergrowth. You need to rely on high-level estimates when making decisions, and count on finding a lot of unforeseen complexity when implementing them. Take each step to make the next step forward more clear.
Do you want to learn more?

Check out the full interview: codingsans.com/blog/hypergrow…

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Level-up Engineering Podcast 🎙️

Level-up Engineering Podcast 🎙️ Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @lvlupeng

17 Mar
Learn how to go from engineer to CEO and what you need to master for such a career change from @rehemagi co-founder and CEO at @thedashbird.

Check out the full interview: bit.ly/2OKrsFj

Hosted by @FancyKarolina, powered by @codingsans.

#CEOmindset #startuplife
Here are some key takeaways:

1. Nothing can prepare you

Whether you come from software engineering, sales, marketing or any other field, nothing can prepare you for being a CEO. Running a company requires experience in every discipline. You must learn on the fly.
2. The engineering background can help

A background in engineering helps you when you need to iterate your strategy in any field. Come up with potential solutions, set expectations for them, use data, and make rational decision. Software engineers are good at this.
Read 5 tweets
17 Feb
@felhobacsi VPE @bitrise talks about how he became aware of his shortcomings in leadership soft skills and how he keeps improving them every day.

Full interview: codingsans.com/blog/leadershi…

Hosted by @FancyKarolina, powered by @codingsans.

#LeadershipSkills #EngineeringManagement
Here are some key takeaways from the interview:

1. Take feedback

This is the best way to know you’re doing something wrong. Take all the feedback you can get, and consider it carefully. Some may be way off, but you can find some of your weaknesses by paying attention.
2. Work on your self-awareness

Your biggest enemy is your autopilot. Your defense mechanisms tend to kick in way too early, and they get in the way of cooperation. Becoming more self-aware helps you master your instincts and salvage situations that may spiral out of control.
Read 6 tweets
3 Feb
How do you onboard engineers remotely?

Jerie Shaw explains @ShopifyEng's process, and how they made it more effective than in-person onboarding.

Check out the interview: codingsans.com/blog/remote-on…

Hosted by @FancyKarolina, powered by @codingsans.

#RemoteOnboarding #remotework
Here are some key takeaways:

1. Social isolation

People are sitting at home all day working, so you can’t bet on their forming bonds getting them past the early days in the company. You need to manage energy levels, create opportunities for bonding, and make onboarding useful.
2. Make it flexible

Make your onboarding process modular, so you can keep iterating in small increments. Just like microservices.

Different time zones also require flexibility. Make sure to provide opportunities for facilitated and individual learning whenever possible.
Read 5 tweets
20 Jan
How do you turn around underachieving teams?

In this episode, John Ford @ford739564, VPE at @LogMeIn shares his framework you can use right away.

Full interview: codingsans.com/blog/improve-t…

Hosted by @FancyKarolina, powered by @codingsans.

#EngineeringManagement #Leadership
Here are a few key takeaways from the interview:

1. Assess the team performance

You may be told that an engineering team underperforms, but in reality the expectations may be set too high. Keep an open mind as you examine the people, process and technology aspects of the team.
2. Set realistic velocity goals

You need to set up proper goals for the team. In software engineering, the correct way is to set up time distribution among different aspects of the work, like feature development, maintenance, security and support.
Read 6 tweets
6 Jan
It’s out!

Tips and tricks to facilitate knowledge sharing with @balazsbalazs formerly from @fb_engineering.

Check out the full interview: codingsans.com/blog/knowledge…

Interview by @FancyKarolina, powered by @codingsans.

#EngineeringManagement #KnowledgeSharing
Here are some key takeaways from the interview:

1. Choose your methods carefully

It’s usually best to prioritize active ways for sharing knowledge, and be pragmatic about how much effort you put into each method. Make sure you get the most benefit with a reasonable investment.
2. Documentation is overrated

You can’t ignore documentation, and there are key things you always need to document. However in many situations you can get away with less documentation than you’d expect, so look for opportunities to save some time and effort.
Read 6 tweets
9 Dec 20
Learn everything you ever wanted to know about skip level meetings from @SarahM and @b_tanishab from @Mailchimp!

Check out the full interview here: codingsans.com/blog/skip-leve…

Key takeaways in the thread 👇

Hosted by @FancyKarolina, powered by @codingsans.

#SkipLevelMeeting
1. Use skips to build relationships and share insight

This is the very idea behind skip level meetings. You need them the most, when you’re not involved closely with the team’s work on a daily basis.
2. You get feedback about the in-between manager

Management doesn’t have hard metrics. You can only tell how well a manager is doing by getting feedback from their team. It’s not spying. Everyone should know about it, and you can either reward them or help them improve.
Read 5 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!