Ep 69 is out!

Somer Esat shares advice on coaching engineers on their career path as an engineering manager.

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

Hosted by @FancyKarolina, powered by @codingsans

#EngineeringManagement #leadership #careerdevelopment
Here are a few takeaways:

1. Manage information wisely

As an EM, you talk to ICs, leads and the technical director regularly. Make sure you share helpful information with them while also creating a reporting structure where people can talk about their problems confidentially.
2. Coach engineers in their career development

Encourage engineers to evaluate their growth, to pinpoint areas to improve and to ask for help from their lead or seniors on the team. Have career development discussions with them, and discuss the expectations of the next level.
3. Help engineers choose tracks

Engineers can choose the principal or the leadership track. Provide guidance if they're unsure: describe the options, observe their traits, and understand their motives. You can also expose them to some aspects of each track to help them decide.
Want to learn more about coaching engineers in their career development?

Check out the full interview through the link below!
codingsans.com/blog/engineer-…

• • •

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

Aug 10
Ep 68 is out!

@beznahej talks about implementing an OKR performance management system to set&track goals in a meaningful way.

Check out the full interview:
codingsans.com/blog/okr-perfo…

Hosted by @FancyKarolina, powered by @codingsans

#EngineeringManagement #leadership #OKRs
Here are a few takeaways:

1. Focus on the bigger picture

When engineers work on a piece of code, they don't see how it contributes to North Star goals. OKRs help them see the bigger picture, so they'll value their own contribution more.
2. Customize OKRs

An OKR performance management system works best if you tailor it to your team's needs. Be patient when you introduce OKRs, have discussions to see what works and what needs to be changed, and welcome questions and suggestions from everyone.
Read 6 tweets
Jul 27
Ep 67 is out!

@ritendra from @fb_engineering gives advice on improving cross-functional collaboration in software engineering.

Check out the full interview:
codingsans.com/blog/cross-fun…

Hosted by @FancyKarolina, powered by @codingsans

#EngineeringManagement #leadership
Here are a few takeaways:

1. Don't overemphasize roles

Cross-functional collaboration works best if you hire well-rounded people who can think outside of their assigned roles. Product managers may have engineering ideas, just like engineers can come up with great product ideas.
2. Encourage empathy sessions

Cross-functional collaboration can cause frustration when people don't see the value of other functions. Hold empathy sessions where cross-functional partners explain what's challenging about their role. They'll appreciate each other's work more.
Read 5 tweets
Jul 14
Ep 66 is out!

@tylerhartley talks about the philosophies, habits and challenges of building truly agile organizations.

Check out the full interview:
codingsans.com/blog/agile-org…

Hosted by @FancyKarolina, powered by @codingsans

#EngineeringManagement #agile #leadership
Here are a few takeaways:

1. Become an entirely agile organization

Do not limit agile to engineering. When your entire organization adapts to the agile philosophies, you can react to changes easier and faster.
2. Strive for "pretty good"

As an agile organization, you’re constantly iterating your product. This means you always leave room for improvement. So, don't try to make everything perfect the first try - strive for "pretty good" and keep iterating!
Read 5 tweets
Jun 29
Ep 65 is out!

@SteveTauber talks about productive IT audit sessions from preparation through execution to follow-up actions.

Check out the full interview:
codingsans.com/blog/it-audit

Hosted by @FancyKarolina, powered by @codingsans

#EngineeringManagement #audit #leadership
Here are a few takeaways:

1. Provide psychological safety

The number one trait of high-performance teams is psychological safety. If you can establish that within your company, it's easier for everyone to work together and build a high quality engineering product.
2. Evaluate objectively

It's hard to pinpoint what's going wrong in your company. Reflecting on how your teams operate, why they follow certain rituals and how they interact with each other is a good way to start.
Read 6 tweets
May 20
Ep 62 is out now!

We talk to @Davidmeirsiegel, CEO @Meetup about motivating and retaining talent during the Great Resignation.

Check out the full interview:
codingsans.com/blog/how-to-im…

Hosted by @FancyKarolina, powered by @codingsans

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

1. Build a community

The biggest takeaway from the pandemic is that people stick around at a company for the community. Your best bet to improve retention is to work on building a community.
2. Utilize hybrid teams

Take advantage of the time you spend in the office by prioritizing collaborative work. This makes collaboration more efficient and supports everyone in building relationships, strengthening your community. You can maximize focus time in the home office.
Read 5 tweets
Mar 16
Do we need ethics in software engineering? If so, what would it look like?

This is what we discuss with @unclebobmartin in the latest episode.

Check it out: codingsans.com/blog/software-…

Hosted by @FancyKarolina, powered by @codingsans

#SoftwareEthics
Key takeaways from the interview:

1. Software is essential

Everything we do goes through software. Lives constantly depend on software and by extension, engineers. This is plenty of reason to start thinking about a universal set of ethics and quality standards.
2. Own your responsibility

Machines can’t take responsibility for their malfunctions. It always has to be the people programming and supervising them. There is no place to deflect responsibility for the consequences of our work to our managers or our companies.
Read 6 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

Don't want to be a Premium member but still want to support us?

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

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(