Episode 31 is here!

@GergelyOrosz explains how to write a standout resume in the tech scene. Loads of details, and tips to fix your hiring process included!

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

Hosted by @FancyKarolina, powered by @codingsans.

#SoftwareEngineers #resume
Here are some key takeaways:

1. A great resume fits the job

Whatever position you’re applying for, go through the job ad, and tailor your CV. Highlight or add any relevant experience you might have.
2. Highlight achievements

Highlighting achievements, projects you’ve delivered and their impact is a great way to get attention. Very few applicants do this, but it shows a business mindset, and awareness of your work beyond the code you write.
3. Focus on hard skills

A software engineer resume is all about hard skills. There is no need to show communication training. Recruiters generally assume you’re fine in that department, and don’t even think about it before they call you for an interview.
+1 Resumes are a poor way to filter candidates

The resume process, especially at big companies isn’t working well. There is no efficient alternative, but there are methods to make it better. It may be hiring outside help, doing coding challenges, and some other options.
There is no room to get deep into the details here, so check out the full interview for a deep dive on the tech resume topic:

codingsans.com/blog/software-…

• • •

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

28 Oct
It's out!

A deep dive into making the Spotify model work with @jrasmusson, author of Competing with Unicorns @prag_notifier, formerly at @SpotifyEng.

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

Hosted by @FancyKarolina, powered by @codingsans
#EngineeringManagement
Here are a few key takeaways from the interview:

1. It's easy to copy the Spotify model

We all know about squads, tribes, guilds and so on, but that's just scratching the surface. You need the soul of the model.

#squads
2. Management is the soul

You need to change your approach to management to make the Spotify model work.

#Management #LeadershipMatters
Read 5 tweets
14 Oct
Episode 29 is out!

We discuss creating a custom software engineer career ladder for your company with returning guest, @timolsh from @Zenput!

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

Hosted by @FancyKarolina, powered by @codingsans.

#careerladder #EngineeringManagement
So how do you go about building your own software engineer career ladder?

1. Articulate your company values

It's essential for any important process or framework you want to implement. If you are clearn on your values, you'll make consistent decisions.

#companyculture #Values
2. Get backing from key stakeholders

Senior management certainly has to be on board, but it's best if your entire engineering department is clear on why creating a career ladder for them is necessary.
Read 7 tweets
30 Sep
Episode 28: @olasitarska from @Onfido talks about integrating diversity and inclusion into recruitment for tech.

Full episode: codingsans.com/blog/diversity…

Hosted by @FancyKarolina, powered by @codingsans!

#EngineeringManagement #DiversityandInclusion #womenintech #recruitment
Here are some key points she made in the interview:

1. Creating a diverse team is in your best interest. Teams with individuals coming from diverse backgrounds deliver better results.
2. Diversity and inclusion isn't just about race or gender, but it also includes different personality types or career paths.
Read 5 tweets
16 Sep
Help your developers progress from junior to senior level and beyond - tips from @fnthawar, VPE at @ShopifyEng @ShopifyDevs on episode 27!
Full interview: codingsans.com/blog/from-juni…

Hosted by @FancyKarolina, powered by @codingsans!
#EngineeringManagement #careerdevelopment
Here are some key takeaways from the interview for leveling up engineers:

1. Pair programming is the most effective way to learn. If you want developers to grow quickly, pair them up with a more senior engineer, and it's guaranteed that both people will take away a lot.
2. As an engineering manager you can hand out stretch projects to your developers.
They get an interesting piece of work, and get to see if they want to grow their skills in that direction. You get to see if they show promise for another role.
It's a win-win.
Read 5 tweets
2 Sep
Episode 26 is out with the inner workings of the feedback culture at @GitHubEng with @_ryannystrom!
Hosted by the wonderful @FancyKarolina, powered by @codingsans.
Check out the full interview: codingsans.com/blog/feedback-…

#EngineeringManagement #Feedback #feedbackculture
How do you build an open feedback culture like GitHub?

0. Before anything else, you have to know, even if you’re at a small company, you can’t start it early enough. You need to set up a feedback system with a regular cycle.
1. Have everyone do self-reviews
Wherever you are, it can’t hurt to think about what you’ve been doing over the last months. A bit of self-reflection is a great first stage for your feedback system.
Read 6 tweets
19 Aug
Get good at running one on one meetings without embracing that awkward learning curve: use the experience of @jstanier of @Brandwatch. You also get a chance to win a copy of his new book!
Full interview: codingsans.com/blog/one-on-on…
Hosted by @FancyKarolina, powered by @codingsans
Do you give #feedback at one on one meetings?

1. I use one on ones to give both positive and negative feedback. It's a frequent opportunity to do it. You want your direct reports to always know how they are perceived, rather than only learn about it at performance reviews.
2. You want to avoid giving critical feedback out of the blue. I tend to put a note about the broader topic of my critical feedback in the meeting agenda. It helps them to prepare.
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!