A brief but impactful conversation with Google project manager, Pavel, on how to make a great CV that lands you the interview at Google (and other tips!). Chat with Pavel here —> https://app.carrus.io/s/pavel-latif

Pavel started his career as embedded software developer where he grew into the role of a software architect. Later he transitioned to product owner role which led to engineering program management. He's worked with both software and hardware products and interviewed 100s of candidates for roles in software development and project management and mentored professionals in their early career development. Currently he works as a Technical program manager at Google.

Shownotes:

[2:30] The job interview at Ericsson and Google and how project management differs
[6:30] Big, top down company interview process vs. bottom-up culture like Google
[9:30] How Google rates culture fit during technical interviews and the "How" you're responding
[11:00] The difference between the interview vs. the actual job role

[12:00] What Google is looking for in a TPM Role / the importance of problem-solving skills vs. actual solutions
[15:00] How the Google has changed since the pandemic
[18:20] The #1 tip Pavel has to make your CV for Google
[20:15] What Pavel wrote on his CV for the Google application and an example of what to do vs. what not to do

[23:15] Why focusing on keywords and crawling on your resume/CV is the wrong approach
[23:40] How Pavel got the job at Google with a cold-email that led to a referral and job
[26:30] Tips on how to get referrals on LinkedIn
[28:10] The number 1 interview tip - why your answers need to relate to the level's expectations (up-leveling and down-leveling)

Questions, comments, feedback?

Drop me an email at misha@carrus.io!