Share this page!

Level-up Engineering Podcast 🎙️ Profile picture
Twitter logo
26 Aug, 5 tweets, 3 min read
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.
Embed interns into teams
Dedicated intern projects didn’t work out for Redbubble. Integrating them into existing teams yielded better results. Just make sure to put them on a team that can support them as necessary.
That’s just the tip of the iceberg when setting up an internship program. 🗻 Do you want to learn more?

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

#internship #leadership #management #softwareengineering

• • •

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

Level-up Engineering Podcast 🎙️ Profile picture
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
Level-up Engineering Podcast 🎙️ Profile picture
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
Level-up Engineering Podcast 🎙️ Profile picture
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
Level-up Engineering Podcast 🎙️ Profile picture
16 Jun
New episode!

Mark Kinsella, VPE at @Opendoor talks about why you need entrepreneurial engineers and how to lead them.

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

Hosted by @FancyKarolina, powered by @codingsans.

#EngineeringManagement #EntrepreneurialEngineer
Here are a few key takeaways ->

1. Entrepreneurial engineering is built on tech expertise

Business-minded engineers need strong technical skills to be able to find and build the right solutions. Mid- to senior level is a must. Let junior engineers focus on the technical side.
2. Creativity and collaboration are must-haves

They need creative and critical thinking to come up with technical solutions to complex customer and business problems. Collaboration is equally important, as they need to work with people focusing on different areas of the problem.
Read 5 tweets
Level-up Engineering Podcast 🎙️ Profile picture
2 Jun
New episode!

@jyhsu, VPE at @RangeDotCo shares what she's learned about managing remote meetings as a leader.

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

Interviewed by @FancyKarolina, powered by @codingsans.

#EngineeringManagement #leadership #RemoteMeetings
Here are some key takeaways:

1. Set up some ground rules

Company-wide core hours are the best tool you can have to organize remote meetings across time zones. You also need to make sure people understand to be reasonably accommodating to each other’s schedules.
2. Move announcements out of meetings

Most people have more meetings in the remote world. Not calling meetings for announcements and status updates is a good start to counterbalance that. You can use asynchronous platforms to replace these meetings.
Read 6 tweets
Level-up Engineering Podcast 🎙️ Profile picture
19 May
Episode 42 is here, the answer to life, the universe and everything: @mseavers, ex-CTO at @riotgames @RiotCareers discusses building self-managing teams.

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

Hosted by @FancyKarolina, powered by @codingsans

#EngineeringManagement
Here are some key takeaways:

1. What does the manager do in a self-managing team?

The leader’s job is to coach. You don’t do the frontline work, so you shouldn’t make all the frontline decisions. Teach your direct reports to solve problems and think for themselves.
2. There are reasons not to build an autonomous team

Leaders often have a desire to get more involved in the frontline work. Making decisions for your team can be quicker than taking time to have them think it through. But you come out ahead in the long run by letting these go.
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

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!

Like this author's thread?

Get emails when @lvlupeng has new unrolls!

Check out other threads from @lvlupeng!

Read all threads by @lvlupeng

:(