C++ Weekly - Ep 409 - How To 2x or 3x Your Developer Salary in 2024 (Plus Some Interviewing Tips!)

[@aliveli8650]

The video is good but title is 100% clickbait

[@jbond5834]

ahhah

[@gustafbstrom]

Yet another bullet to put under "Getting your name out there". As a youtuber-as-a-job, one has to look at empirical facts about what makes a video much more likely to be watched and I suppose clickbaiting is one of them. Jason is at least professional enough to have his avatar doing the "shocked face thumbnail" instead of himself. :)

[@cppweekly]

I even explicitly show in the episode guide that it's click-bait! It's right on the tin!

[@mriegger]

FWIW I relentlessly did mock interviews for 6 months prepping for interviews. Ended up with multiple FAANG offers. The multiple offers was key. One of the FAANGs increased their offer by ~50% from their already excellent initial offer. Also a bunch of guys I mock-interviewed with also got offers. Ended up saying "hello" to them on the internal company chat. Pretty awesome

[@victotronics]

Not sure that I agree with that Dunning-Kruger summary. 1. Incompetent people don't know their limitations so tend to overestimate their skills, so "If you think you're an 8, you're probably a 4" 2. Competent people know their limitations so tend to underestimate themselves, eh "If you think you're a 5 you might be a 8".

[@DonReba]

The actual result observed by Dunning and Kruger showed only the first part, not the second. Competent people tend have accurate estimates of their ability.

[@victotronics]

@@DonReba True, but follow-up research has shown the second part to the extent that in common parlance it's now part of the DK effect.

[@rdwells]

My understanding of D-K syndrome is that no one with it thinks they're a 4 but are actually a 2; they think they're a 10 and are actually a 2.

[@pixelsupreme6824]

the irony of Dunning-Krüger is that most overestimate their understanding of it kzbin.info/www/bejne/oZTJg5hnaq5nbas

[@mriegger]

Generally good to check your ego and be humble in interviews. Just factually state what difficult things you did, and the accolades you won, without bragging.

[@AxWarhawk]

If you are watching this channel, and are looking to increase your salary, probably get into some webdev job. Looking around here, in central Europe, a senior C++ developer often gets payed less than a mediocre fullstack developer. Apart from this: when you apply for a job, always state your salary expectations in your first interview. If the company cannot match that, further interviews will be mostly a waste of your time. Next, while being employed, continue applying for jobs. And if you have the opportunity to switch to a job with a higher salary, either switch or go to your current employer and ask them to match the offer. Finally, when you are given new responsibilities in your job, always demand a raise in salary for taking them on -- do not accept one-time bonus payments or a share in stocks, or anything like that as a compromise.

[@tauicsicsics]

not sure if we should reject share in stocks, this is 70% of the entire package, at least at most FAANGS.

[@honey_sukesan]

As always, "to the point" video. Thanks, Jason for sharing these tips.

[@coding_with_thomas]

Thats a great and honest talk. One of the best advices I ever got was "learn in public" and one very good start to step out in public is create a website/blog. And that is a good reference for one self as well a good training for communicating and practicing. At least it worked out well for me.

[@spudgossie]

Being passionate is what it's all about. My favourite question to ask when I was interviewing someone was "Tell me something you've read or some code you've seen recently that you thought was interesting/cool?" If they start to gabble, they've got the job

[@rdwells]

On the subject of avoiding the words "guru" and "expert": some time around 1986 or '87 I interviewed someone whose cover letter said they were a C guru. So, in the interview, I asked for his opinion of the upcoming ANSI C standard. Him: The what? My (thinking): Okay, this is over.

[@sirhenrystalwart8303]

According to the consensus on teamblind, the best way to increase your salary is to just grind leetcode and system design questions. That seems to be what everybody up to about 600k in TC says to do. Maybe Jason's suggestions work beyond that for the principle and higher roles? Or maybe it's just a different strategy entirely? Hmm.

[@jaybee9054]

If Jason cannot be considered a C++ 'expert' and 'guru,' then I don't know who is

[@oschonrock]

very different episode, but very useful especially for younger audience.

[@gustafbstrom]

Thanks Jason, helpful tips.

[@TrippLilley]

How did you leave off the most important advice?! You HAVE to start your career with a paid internship at a wacky startup consultancy based on a stellar response to an off-the-cuff email interview problem. When will you be offering Rust training? I'd like to sign up for that, please.

[@cppweekly]

Ha! I had no idea you watched these videos. You know Sophia (previously Jon Turner) does Rust training right?

[@blaisofotso3439]

Dear Jason Turner, I hope this message finds you well. i am student in Mechatronics in germany, I've been following your videos on KZbin and have found them incredibly insightful. Your expertise in C++ is truly admirable, and I appreciate the effort you put into sharing your knowledge. However, I often find it challenging to fully grasp the concepts you present due to the advanced nature of the topics. As a beginner in C++, I would love to delve into the language from the ground up and eventually comprehend the intricacies you discuss. Could you kindly recommend a comprehensive learning path for someone starting with C++? I'm particularly interested in the tools, books, and resources you would suggest for a beginner. Additionally, if you have any videos or book recommendations focused on understanding compilers, I would greatly appreciate it. Thank you for your time and for being an inspiration to the C++ community.

[@cppweekly]

I tried to put together a playlist for learners: kzbin.info/aero/PLs3KjaCtOwSY34fFKyhOFovFlB7LikDwe&si=yu2FWEB_OC6rr8du Hopefully you find this helpful.

[@blaisofotso3439]

Thank you so much Much appreciated

[@alikin]

"I hope this message finds you well." So familiar.

[@kinershah464]

Very very informative video. Especially the last part where recruiters ask how much do you earn. I always get annoyed by that question. My usual approach is to ask a counter question to deviate from the topic, like what is your budget? 😅 doesn't work always though.

[@katanasteel]

Well if the company don't have testing and/or CI... maybe that something to work on for them.

[@cppweekly]

Yes, that is fair. But the point I wanted to get across is that you should be aware of the fact that you are not only being interviewed - you are also interviewing the company you might be working for. You should know what you're getting into.

[@nextlifeonearth]

To the imposters: fake it 'till you make it.

[@abyesilyurt]

Thanks! This was a very valuable video.

[@cppweekly]

Glad you enjoyed it!

[@revealingfacts4all]

no, no, no, you never give out a salary requirement. It's akin to asking someone to show you their poker hand before making your bet. The best response to the salary question when they ask is, "I would be honored to year your most competitive offer." What you make at your last job is completely irrelevant because once I start my new job, I will have nothing to do with that other company. I can right a book on this topic but that's the most succinct take away I can offer anyone stumbling through these comments. I have been both an individual contributor at big and small companies and several manager roles (director and VP level). It's also worth mentioning that it works in your favor to re-say some of the things you heard about in the interview that you would be excited to work on - it shows you paid attention and are engaged then follow up with the most competitive offer type statement. BUT NEVER GIVE OUT A NUMBER! NEVER!

[@TheBusttheboss]

I only give out a range I want, never my current salary.

[@001HK0]

How would I get on a podcast? Is it considered bad form to ask relevant podcasters?

[@cppweekly]

It is definitely *not* bad form to ask. When I ran CppCast we would sometime struggle to have a guest every week, and it was great when people reached out to us.

[@SillySussySally]

I just got years of experience under my belt and a lot of dumb luck. I feel like this video is full of survivorship bias. Plus, most people I know that are based are actually looking to maximize pay per effort ratio. Most programming jobs pay well enough to not starve.

[@akidas101]

Lol yes soon programmer's will not be able to afford rent in these costly places.

[@cppweekly]

This is based on my observations around my meetup and conferences. It's not based on my own experience directly.

[@ultimatesoup]

I already make 300k. Can I double that?

[@friedkeenan]

Well, I know you could halve it by cutting me in

[@prashantsrivastava6621]

I am afraid that some of those lines even compiles

[@stephenhowe4107]

Another way of publishing yourself is by publishing useful open source code that does a respectable task, is robust, uses good techniques, is fast that other programmers can incorporate in their codebases. And be prepared to answer questions, fix any discovered bugs.