All Episodes
May 3, 2024 - Freedomain Radio - Stefan Molyneux
21:14
Nailing Job Interviews
| Copy link to current segment

Time Text
Yo, it's Steph.
Hope you're doing well.
Just wanted to let you know there's a new feature or benefit or perk or bonus that's coming out for donors to supporters and you can join of course at freedomain.locals.com or you can join at subscribestar.com slash freedomain.
And what we're doing is live call-in chat shows, maybe once or twice a week, just for donors.
So this is something that I did just for donors.
I'm just throwing it out here so you can get a sense of the kind of goodies that are up there if you support the show in this way, which I hope that you do.
And I hope to see you at the next one, freedomain.locals.com or subscribestar.com slash freedomain.
Here we go.
So I'm going to start with something that I think is interesting, hopefully valuable.
Job interviews.
Now, it's actually one of my first semi-viral videos was about job interviews.
And the reason that you should listen to me about job interviews is obviously I have been interviewed a whole bunch of times, but I've probably interviewed well over a thousand people and hired a hundred people or more over the course of my career.
Which is pretty good.
That's pretty rare.
Pretty good.
But this is in particular, of course, I mean, a bunch of people have worked for free domain until I burn them out like matches, Lucifer matches.
But I software, when I was chief technical officer in a software company, I co-founded a lot of interviews and all of that.
So I wanted to, you know, give you some tips and thoughts, keep this relatively brief if there's things that you want to talk about elsewise.
So we'll just do this, but Okay, so these are the things that I was sort of looking for.
Because people have a big challenge when it comes to, what are you, why are you there?
Like, what are you saying about your old job, right?
So, if you say bad things about your old job, that's a challenge.
I was always kind of on the lookout for that.
And the thing is though, if you, because if you want to explain why something went wrong in your old job, You're going to have to provide so much context and the person is going to have to trust you that you are, you know, not at fault, that you just had a bad boss.
And then, you know, well, why did you not know that you had a bad boss before you worked there?
You say, oh, well, you know, the bad boss was just moved in over me and so on.
Okay, but it's kind of tough because I'll just tell you this from my standpoint, I think this is probably true as a whole, but from my standpoint, when I hear someone say, I was a victim, it wasn't my fault, in some relationship thing, I don't believe them.
Now, I don't disbelieve them, but I don't believe them.
Now, there are a few treasured people in my life, Who, you know, some in fact are on the call.
The few treasured people in my life, if they say it was somebody else's fault, I'm like, yep, okay, I'm down for that, right?
I believe that, I accept that.
But for most people, they're selling you a narrative about how things went wrong, and it's just not their fault.
They're innocent victims, they tried their very best, but just bad people had control and ruined their lives, or made their lives difficult, or messed up with their career.
So, what you're doing, unfortunately, if you bring this kind of stuff to a job interview, what you're doing is you are making the assumption That the relationship with the job interviewer is something other than what it is.
In other words, you're asking for credibility when you've just met someone.
So again, if you've known someone for a long time, they're legit, they're honest, they tell the truth, and they do their best, and they have credibility with you, then if they say, you know, someone just had a bad relationship with someone, or my boss was a difficult Then, in general, you probably believe them, because you've known them for a long time, you have that credibility.
But in a job interview, just remember, you have no credibility, because they just met you.
So, if you start talking about things which would require the interviewer to trust them, in other words, I had a bad boss, or it was a bad company, or a bad environment, or bad clients, and it wasn't my fault at all, then you're asking for the job interviewer to trust you, when he doesn't even know you.
And that shows poor judgment.
And if you're trying to say, like you're demonstrating poor judgment by asking some boss to take sides, oh, the company was corrupt or they treated their employees really badly or whatever it is, it's like, well, maybe you were just a bad employee, right?
So don't assume trust.
In a new relationship.
Don't assume you have any credibility in a new relationship.
Maybe it's a little different if somebody's listened to my show for 10 years and they do a call-in, maybe I have some credibility there.
But never assume trust in a new relationship.
And this is a funny thing too, this isn't just in job interviews of course.
You see this happening all the time where, you know, some woman on a date will spill the beans about her last boyfriend or, you know, how many antidepressants she's on.
I mean, I remember being on a date, I said this sort of some time ago, I remember being on a date with a woman and she told me that her boyfriend had left her with $17,000 in debt.
And she was sort of railing about her boyfriend and it's like, but we just met.
So we don't, you don't have any credibility with me.
And of course, if you blame other people for voluntary relationships, your judgment looks suspect.
So when you're in a job interview, you know, how is, you know, what was going on at your last job or what's going on at the job?
Why are you looking and so on?
I say, well, I'm looking to get to the next step in my career, and I think I can do that.
Well, that's a tough thing, because if you say, I'm looking for the next step in my career, but I'm going to do it laterally, then people will be concerned that you use that, right?
Because, I mean, everybody knows you're not too satisfied with the job if you're looking for a new one, and so trying to explain that, why, is a challenge, right?
So I'm looking for a new challenge, I'm looking to move on, I'm looking to move, I want more
responsibility, whatever it is, right?
And then of course, but then the question is, you know, why are you being given more
responsibility in your current job, that kind of stuff, right?
So I think there is a general understanding just based upon being in a job interview that
you're looking for a new job because you're dissatisfied with something in your current
job and just try and keep whatever dissatisfactions you have, do your very best to try and keep
them to a minimum and just say, I'm looking to move on, I'm looking to acquire a different
different set of skills and whatever it is, right?
And all of that.
So I think that's... Because whenever you're going for a job interview, one thing that the interviewer knows for sure is that you can't get what you want in your current position.
Right, so if you're looking, like if you're a really valuable employee and you wanted to get more into sales and marketing from tech, they'd know that your current employer won't accommodate that.
So then the question is why?
Because like really good, really good employees, bosses, like smart bosses will try to accommodate whatever really good employees want to do.
So if you're a really good programmer and you want to get into sales and marketing, and you're really, you know, a great employee and so on, then your boss will try and facilitate that as much as possible.
Yeah, looking for something different, looking to move up, looking to move on.
Just keep it to a minimum as much as possible and that way also discreet.
Knowing that you can be discreet is really, really important.
Now the other thing that I would recommend in job interviews is come prepared with your value add.
So a lot of people, this is particularly true in the tech world, will say, I know this code, I know that code, I've experience with this and that and so on.
And you know, that's all fine, but that's kind of why you're in the, that's why you're in the room to begin with.
That's kind of already known.
What you want to do, if you, I think to have your best chance at a successful job interview.
Now a successful job interview is not where you get the job.
That's sort of important to recognize.
A successful job interview is where you get a job at a place you want to work.
And you want to have a business competent manager.
So a manager who understands profit and loss, a manager who understands that you need to get two to three X productivity out of your employees in order to justify hiring them because like more than their salary.
Cause a variety of, you know, obviously overhead and taxes and computers and maybe some travel budget and expenses and office space.
There's a lot, a lot that you need to spend and just the risk.
Cause there's going to be some turnover, right?
So, to get a job at the place you want to work, your manager has to be business competent.
In other words, he has to understand the profit and loss and all of that.
Because if he's not business competent, then his decisions won't be driven by profit, they will be driven by politics.
And if you've ever had a boss who's into politics, it's a really crazy-making situation that you really don't want to be in as a whole.
If you're talking about your value, your value isn't the bag full of acronyms of things that you know.
I know SQL, I know Java, and that's all good, right?
But what you want to do is you want to say, here's the money I made for the last place, right?
So, you know, I came up with this automated process that saved X amount of hours per week, of some guy who was, you know, a hundred bucks an hour,
right?
So, say five hours a week from some guy who was a hundred bucks an hour,
so it's 500 bucks a week that I saved, you know, that's a lot, right? I mean, that's some good
stuff, right? That's some good stuff. That's, what, 24,000 a month or 25,000 a month? A year, sorry, a year.
$25,000 a year.
So, you know, so just with that one thing, I covered a third of my salary.
Let's say you make $75k, so I spent a certain amount of time, and I saved a third of my salary, and then I did this other thing, which covered even more of my salary, and I automated this process, and I was faster than this guy.
So you want to show the business value that you provide, and that's in order to filter out Managers who work on politics not profit because you don't want to work for those guys in my opinion.
That's that's pretty Pretty wretched.
So make sure you come in.
It doesn't have to be a pure spreadsheet, but you got to come in with With the value-add, right?
The business value-add, the monetary value-add, here's how I made money for my last employer.
Now, you get the question about weaknesses, and you know, of course, this is all, you know, I'm too much of a perfectionist.
I tend to get over-involved in my projects, like all stuff that obviously managers know that's just basic suck-up stuff.
So, weaknesses.
I generally, I would be pretty honest with my weaknesses.
Oh, you know, I would go sometimes on for 10 minutes about the things that I know that I'm not great at.
And when you give your weaknesses, you want to give your weaknesses and your workarounds, right?
You want to give your weaknesses and your workarounds, right?
So, you can say that, you know, I tend to be not quite as detail-oriented as I need to be, and so I create a spreadsheet of all the details I need to remember.
Or, I cross-checked my work with someone who couldn't see the big picture, so I bring the big picture to my worker, my work companion who wasn't into the big picture, he'd bring the details to me, and we'd both end up stronger.
You know, one of the twins' powers activated, or something like that.
So, whenever you talk about your weaknesses, I think it's important to be honest about that stuff, but when you know a weakness, it's incumbent upon you to solve it, or to have some way to solve it.
And I think that's really important as well.
Now, when it comes to salary, right?
I mean, you've seen that meme, I'm sure.
It's like two gunslingers in the Wild West.
And, you know, one guy is saying, well, what does the job pay?
And the other guy is saying, well, what are you currently making, right?
They just don't want to Right?
So, in my opinion, and I went through this whole process at one of the companies I worked with where my tech lead came to me and said that, you know, they'd all been sitting down and talking with their friends and they felt underpaid as a whole, right?
They felt underpaid relative to what their colleagues were making in similar fields with similar amounts of experience and so on.
So I ordered a salary review and ended up interviewing a bunch of people outside the company to get a sense of salaries, talk to my friends who are also managers, how much you're paying people for this, that and the other.
And I did end up making the case.
I got about a million dollars extra per year for my tech team in terms of payroll.
So, when people are like, you gotta help the underprivileged, so to speak, or you help the people poorer than yourself, well, you know, I've actually done that kind of stuff.
And of course, the nice thing was that if they moved on, they had that salary as a base to start working with.
So, I think if you want to talk about, if the salary comes up in a job interview, again, my sort of personal opinion, what I would most respect is somebody who had industry knowledge.
Rather than, here's my salary, what does the job make, right?
So say, well, you know, my research and what I've talked about with colleagues and so on, that the industry average for this job with this amount of experience with these kinds of responsibilities tends to be in this range, right?
And of course, it depends exactly where you live and the different postal zip codes are more expensive, more costly than others.
Talking about industry standards and industry ranges is the way to go.
And then of course, you know, you want to be honest.
And of course, if you've made the case, you know, at the last place they made me, they paid me $80,000 a year, but I saved them over $300,000 because of X, Y, and Z. And you want to keep track of this in your job, right?
You want to keep track of the value add that you have brought to Like when you're doing projects, right?
You keep some notes, you know?
Here's how much time I spent.
It cost the company this much.
Here's how much I saved.
And here's the, you know, I'm not saying you necessarily keep all the source files and data, right?
But you'd want to have, confidently be able to say, here's what I made.
So you want to keep track of the value that you're adding in your current job.
And that's two benefits, right?
Well, three, I guess.
One is just confidence.
The second is when you go for a raise, you can say to your boss, look, I saved the company X amount of bucks, so I deserve a raise, right?
And here's my documentation for it.
And then, of course, if you are going for other jobs, having that kind of data available is really good.
And then you can confidently say, okay, here's the industry averages, you know, between 60 and 90,000 for my kind of job.
But I also I really do keep track of what makes the company money.
Like if you show a boss that you have a business mindset, he's going to be way more comfortable in hiring you, right?
So the very fact that you've kept track of the value that you've added to the last company makes you a lot more valuable to the new company.
And a lot of people just get down into the weeds and do their job and do their work and they just do what they're told and kind of reactive and they're not thinking about the business as a whole.
So, I would definitely keep track of that.
So, you can say, you know, here's the range for this kind of position.
I think I should be at the upper end of the range or maybe even above it because X, Y and Z, right?
Like I've done all of this value and so on, right?
So, now what about if you get called into a job and you don't have the experience they're looking for?
So to me, there was only one ever good answer for that, which is, if you hire someone who can really learn, they will never, ever be short of experience.
If you hire someone who can really learn, because things in tech are always changing, right?
So if you get someone who matches exactly what you want right now, but they don't have much of a flexible ability to learn, then when the technology changes, they'll be left adrift.
They'll get stuck, right?
I don't know this, but I also, when I first started, other things I didn't know, and keep track of the things you're learning on your job.
Again, if you keep track of the progress and value that you add, and the things you learn in your current job, it'll be easier to make the case.
You say, look, I didn't know PHP, and then I learned it and produced this, and I didn't know MySQL, and I learned it and produced this, and I didn't know JavaScript, and I learned it and produced this.
So, you can, and this is a choice that managers have to make, right?
Do you choose someone who's got the right skills for now and hope that they can learn more in the future, or do you choose someone who's good at learning?
And therefore we'll continue to progress no matter, as the technology inevitably changes, no matter what.
Are you nimble, right?
Are you nimble?
Are you a ninja?
Can you, right?
So, when it comes to experience, I think as long as you have, and don't just say stuff, like, I'd say show it.
And showing it means that you simply have it documented.
You don't have to hand over the documentation, of course.
But you can wave it around and read from it or say, here's how I know this.
Like, I'm not just making this up.
I actually know this, right?
Like how many lines of code are you able to get done in a week?
You should document that and you should keep track of that so that you know that.
And then you can know that it has improved.
Well, you know, when I first started, I did, I got a hundred lines of code done a week and then it went up to 500 and then it went up to a thousand.
So at this rate, I'll be able to code Windows NT in a long weekend.
So, or whatever, right?
So I would think.
It's fine.
Just focus on your ability to learn and have everything documented.
Again, you don't have to hand over the documentation, but you need to know it for yourself, because that's going to be a real confident builder.
I think you want a boss who's got some thought of an entrepreneurial mindset, because otherwise he's going to put you in a little cubicle and in a little intellectual box that you won't be able to leave, which I would imagine for this audience is kind of painful. So in all of my jobs I tried really to think as an
entrepreneur and this is obviously before I was an entrepreneur. So even when I was a waiter I
viewed myself in an entrepreneurial light even as a waiter.
Because as a waiter, you are kind of an entrepreneur because you're working for tips.
And so, the more value add that you can bring, the better, right?
So, obviously, if there was a guy coming in who was obviously on a date with a girl, I would defer to the guy and all of that, and that way he would seem higher status, and that would be a value add.
That I could provide as a waiter.
I, of course, wanted the bill to be higher, so I learned how to describe... One of the places I worked, the dessert was a profiterole, which is like this amazing pastry and ice cream and chocolate sauce, and it's just an amazing, like a vertical tower of diabetes.
But I learned how to describe that in a way that almost everyone would order it.
And so, yeah, learning how to upsell, because the more I can sell, the better it is for the restaurant, and then the better it is for my tip.
And so on, right?
And there's a certain kind of authoritarian deferment, which is where you are an authority and then you defer to, in particular, the man on the date.
Because they don't care if you defer to them and you don't have any authority.
So, to be an authority about the restaurant and the food and so on, it was a high-end seafood restaurant.
To know everything and then to defer, to be high status and then to defer is really great.
Of course, I had a newspaper route when I was 12 or so, and I was entrepreneurial in that way, in that I could always go and try and get more people to subscribe to the newspaper, which upped my income and so on.
So, in every job, imagine that you're a contractor who could be fired at any time and has to prove his value.
And if you take that approach and you document the value that you are providing, you are going to be ahead of like literally 97, 98% of the employees out there who tend to be kind of reactive to that kind of environment.
So.
But entrepreneurial, you can just claim to making claims without evidence.
is not particularly reassuring to bosses.
But if you make a claim, oh, I made money, oh, I learned this, and I advanced that, and I learned how to, I didn't enter my last job with this skill, but I then became an expert at it, and I'm willing to work weekends, and I love to learn, and like, I'm willing to study weekends, and I love to learn, and all of that.
And being a hobbyist also, I mean, I know this more in the tech realm, if you are a hobbyist, in other words, if you loved computers from the very beginning, and you did it all for free, I would always hire hobbyists over Even very well-educated people, because I found that the hobbyists... I remember I hired one guy, he had a PhD in computer science, he was terrible!
Terrible!
I hired another guy who'd never taken any education in computers who was fantastic because he was just a hobbyist who loved it.
So, but again, everything should be documented and if you take every job and every job interview as if you're an entrepreneur rather than an employee, you'll get the right kind of boss and I think you'll get the right kind of environment and that I think is going to be the most satisfying.
And of course, as you As you practice and hone your entrepreneurial skills within an employee environment, then when it comes to be an entrepreneur, if you want to do that, and I'm sure you at least want to give it a try if you get the opportunity, you'll be ready.
Export Selection