Tips and tricks to building a platform team and creating healthy coordination with product teams from @skamille at @twosigma.

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

Hosted by @FancyKarolina, powered by @codingsans.

#EngineeringManagement #PlatformEngineering
Here are some takeaways about communication channels:

1. Coordinate planning

You want to start coordination as early as possible. Send a platform engineer to join the planning sessions of product teams, and see if they have requests or advise them on currently available options
2. Use product managers

Using product managers in platform teams is an unconventional but useful idea. They can help with communication on every level, make it smoother and take some load off management - but definitely can’t replace them.
3. Direct communication is best

The most efficient communication happens when product teams reach out to platform teams directly. They can discuss their needs, current options and potential future options the platform team may be able to build to meet their needs.
Do you want to take a deep dive into leading platform engineering teams?

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

• • •

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

6 Oct
Why writing is important in #EngineeringManagement and how to improve it? Tips from Erica Greene at @Etsy @codeascraft to improve your team’s and your own writing skills.

Check out the interview: codingsans.com/blog/importanc…

Hosted by @FancyKarolina, powered by @codingsans.
Key takeaways about supporting your team:

1. Define the different documents

Make sure everyone in your team has a clear understanding of the different types of documents you regularly work with. This puts you all on the same page.
2. Provide templates

Provide templates for the different documents you expect your team members to write. A high level overview of the necessary contents, and a clear structure to follow can fit on just one page. Use it as a learning material and a reference point for your team.
Read 6 tweets
22 Sep
New podcast with @patkua 🔥
Some key concepts of systems thinking:

1. Emergent behavior

The main point of systems thinking is finding emergent behavior in systems; properties that no one part possesses alone. Understanding this can help you work better with complex systems.
2. Feedback loops

Feedback loops are basically the communication channels of any system. You need to be aware of the ones that are present, their speed, and that you can often adjust them or create new ones. They’re a key element when it comes to influencing a system.
3. Applying systems thinking to leadership

Teams are systems. Organizations are even bigger systems. Systems thinking can be extremely useful when it comes to figuring out leadership challenges. You can be a great leader without it, but it can be a powerful tool in your arsenal.
Read 4 tweets
8 Sep
@ProductHunt’s unbelievable journey shared by the one and only @rstankov who has been successfully scaling teams and products since the very beginning🤙🤙

Hosted by @FancyKarolina, powered by @codingsans

Check it out at: codingsans.com/blog/leadershi…

#EngineeringManagement
Here are some key takeaways:

Management is a different career

When you make the switch to management, you need to start from scratch. It’s a new career, and you need to use all your previous experiences in a new context. Rado tells some of his stories about facing this problem.
Write a journal to track your progress

You can write a manager journal to track your effectiveness as a leader. Note all your thoughts and important events. You can go through it weekly, as you plan the next week, and review it monthly, to see if there are recurring problems.
Read 5 tweets
26 Aug
We take a deep dive into creating a successful internship program for software engineers with Tom Sommer, Engineering Director @redbubble. 🤿

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

Powered by @codingsans, hosted by @FancyKarolina. 🎤
Here are some key takeaways:
Set clear goals for everyone
Including the program and the interns. Do you want to provide industry insight to your interns, or are you scouting the next Elon Musk? What do they have to do to get hired? Find these answers before moving forward.
Set the bar going in
Most companies can support interns who are fresh out of college, bootcamp, or have real coding experience. Many companies can’t support interns who have never seen code. There’s a wide range in-between, make sure to find the sweet spot for your company.
Read 5 tweets
21 Jul
We go deep into integrating remote engineers to a distributed team with @g_the_engineer from @HudlEngineering.

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

Hosted by @FancyKarolina, powered by @codingsans.

#EngineeringManagement #RemoteManagement #DistributedTeam
Here’s the problem:

Remote engineers are cut off from their team. It’s even worse when the rest of the team is in an office together. The remote person misses out on a lot of interactions, and the team isn’t motivated to include them because they have each other at hand.
Here are some takeaways from the interview:

1. Move conversations to Slack

You might think, “Sounds great, but GL pulling it off.” There is a way, but you need to be very intentional about it. Start by moving professional conversations to Slack, and go from there.
Read 6 tweets
30 Jun
We kickstart the Level-up Engineering Stories spinoff series with @rands sharing stories about his time as VPE at @SlackEng.

Check out the interview: codingsans.com/blog/leadershi…

Hosted by @FancyKarolina, powered by @codingsans.

#EngineeringManagement #LeadershipStories #leadership
Some key takeaways:

1. It takes 3 years to grow into a role

It’s not a sexy story. Once you’re a VP, you’re a VP, right? Well, it takes time to learn to be an executive. It took Rands about 3 years, so you likely won’t be able to figure out a completely new role in 3 hours.
2. Tell the truth ASAP

Always tell the truth quickly. However, handing out random facts isn’t helpful. You need to examine them, put them into context, and tell a story about what you can learn from them.

Always tell the truth asap, but don’t “YOLO the comms.”
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!

:(