Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Code with Jason

Code with Jason artwork

279 - Mike Mroczka, Author of Beyond Cracking the Coding Interview

Dec 31, 20251 hr 1 minAudio
ShareXLinkedInFacebookWhatsAppEmail

In this episode I talk with Mike Mroczka about his book Beyond Cracking the Coding Interview. We discuss why algorithmic interviews persist, how AI has disrupted hiring, and why personal branding matters more than ever. Mike shares strategies for bypassing flooded job applications by contacting hiring managers directly. mikemroczka.com Beyond Cracking the Coding Interview on Amazon Cracking the Coding Interview by Gayle McDowell

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

SPEAKER_01Hey, it's Jason, host of the Code with Jason podcast. You're a developer. You like to listen to podcasts. You're listening to one right now. Maybe you like to read blogs and subscribe to email newsletters and stuff like that. Keep in touch. Email newsletters are a really nice way to keep on top of what's going on in the programming world. Except they're actually not. I don't know about you, but the last thing that I want to do after a long day of staring at the screen is sit there and stare at the screen some more.

SPEAKER_01That's why I started a different kind of newsletter. It's a snail mail programming newsletter. That's right, I send an actual envelope in the mail containing a paper newsletter that you can hold in your hands. You can read it on your living room couch, at your kitchen table, in your bed, or in someone else's bed. And when they say, What are you doing in my bed? You can say, I'm reading Jason's newsletter. What does it look like? You might wonder what you might find in this snail mail programming newsletter.

SPEAKER_01You can read about all kinds of programming topics like object-oriented programming, testing, DevOps, AI. Most of it's pretty technology agnostic. You can also read about other non-programming topics like philosophy, evolutionary theory, business, marketing, economics, psychology, music, cooking, history, geology, language, culture, robotics, and farming. The name of the newsletter is Nonsense Monthly.

SPEAKER_01Here's what some of my readers are saying about it. Helmut Kobler from Los Angeles says thanks much for sending the newsletter. I got it about a week ago and read it on my sofa. It was a totally different experience than reading it on my computer or iPad. It felt more relaxed, more meaningful, something special and out of the ordinary. I'm sure that's what you were going for, so just wanted to let you know that you succeeded.

SPEAKER_01Looking forward to more. Chris Sonnier from Dickinson, Texas says just finished reading my first nonsense monthly snail mail newsletter and truly enjoyed it.

SPEAKER_01Something about holding a physical piece of paper that just feels good. Thank you for this. Can't wait for the next one. Dear listener, if you would like to get letters in the mail from yours truly every month, you can go sign up at nonsense monthly dot com. That's nonsensemonthly.com. I'll say it one more time nonsense monthly dot com. And now without further ado, here is today's episode.

SPEAKER_01Hey, today I'm here with Mike Marachka. Mike, welcome.

SPEAKER_00Thanks so much for having me.

SPEAKER_01So you're the author of Beyond Cracking the Coding Interview, and many of our listeners have surely heard of Cracking the Coding Interview. As I just showed you, I have it right here in front of me, Cracking the Coding Interview. Um, but you have written kind of the sequel to this book. So tell us, tell us about that and tell us about yourself.

SPEAKER_00Absolutely. Uh the book is the sort of officially endorsed sequel to the original Cracking the Coding interview written by Gail McDowell. And uh it's sort of an expansion of everything that's sort of talked about. You don't really need the the previous book in order to benefit from the uh the sequel, but it's updated for current market conditions. It goes into a lot more depth on sort of how to actually pass these increasingly difficult coding interviews that are are part of the industry. And as far as myself, uh my name's Mike, last name's Muraczka, that's Polish.

SPEAKER_00And if you don't pronounce it correctly, that's fine. I'm not easily offended. Uh a couple things about me, I suppose. I'm a former Google engineer, I'm a senior software engineer. I've worked at a variety of companies for the last decade or so. And I also do private interview coaching and some consulting on the side for companies on just how to improve the interview processes and things like that. So um the AI industry has certainly disrupted a lot of uh how coding interviews work at this point in time. So there's a lot of sort of consulting around like how do we make sure people are actually doing the code in the coding interviews and all that kind of good stuff.

SPEAKER_00So that's uh a little bit about me.

SPEAKER_01Okay. Yeah, and there's two angles that I'd love to explore. One is um, you know, from the perspective of your target audience, people who would be interested in reading the book and stuff like that. And then just from my own selfish standpoint, I'm interested in the process of how you came to write this book and what kind of career benefits it might have brought you and stuff like that. Um I'll try to exercise some discipline and keep those questions to a minimum and focus more on the target audience.

SPEAKER_01Um and okay, so I'm gonna dive right in with um with kind of a controversial area um where as people who know me might not be surprised, I have a somewhat controversial opinion. Um maybe not controversial, uh, but at least a minority opinion. Um so kind of everybody hates these like whiteboard interviews, these like algorithmic interviews. And I myself did for a long time.

SPEAKER_01I I wasn't a fan of those. Um and one of the big gripes is that those interviews, the content of those coding challenges aren't representative of the work that you would be doing in the job, which is totally true. Um, but then I myself interviewed at Amazon. It was kind of the first time that I interviewed at a big company like that. Um, did not get the job, by the way. Um, but I but I interviewed there, and they have a ton of like preparatory material for candidates to go through.

SPEAKER_01Um and something that I read during the during my preparation was that the reason that they do these algorithmic um coding challenges is not because it's representative of the work that you would do in the job. They're not trying to get like a sample of how you would work on the job exactly. Um it's more like you can't you can't fake being able to code. Like if you just have a conversation with somebody, they can kind of like they can kind of trick you.

SPEAKER_01Um not not intentionally necessarily, but they they can trick you into thinking they're good when they're actually not. Um I've I've seen it happen a number of times firsthand. I believe it. Um and and so it's kind of like it it these coding challenges are almost like a proxy IQ test where it's like, okay, can you do this hard thing? And it's almost like the fact that it's not uh related to the work that you normally do is like part of the justification for it, or part of the benefit of it, or whatever, because it means you have to go and you have to go out of your way and deliberately study for this particular thing.

SPEAKER_01And it's like, are you the kind of person who would do that and and succeed with it or not? Anyway, that's how I look at all that stuff. I'm I'm curious your take.

SPEAKER_00I actually think I agree with you. There's there's maybe a handful of arguments people come up with as to why coding interviews are bad. And when we talk about coding interviews, we're not talking about the practical ones, build tic-tac-toe, you know, in React or or you know, make a crud express endpoint and node or something like that. But we're talking about the algorithmic data structures and algorithms using leech code and and other sites like that to sort of practice. I I think there's uh a handful of people that are are kind of you know believe like we do that there's there's benefit to this.

SPEAKER_00And then there's the vast majority of people that just hate the whole process. But I think there's maybe kind of two arguments for it. That the first one is if we did kind of go and specifically try to test what's in the interview, you'd actually find that there's about 20 different interview types because you might be a senior software engineer and I might be a senior software engineer, but we will both be doing very different things, even if we've been in the industry for a decade. You might know back end, I might know front end, you might be good at security, I might be good at HTML and CSS. And there's not a whole lot of overlap there.

SPEAKER_00So there's actually like 20 different types: there's cloud, there's infra, there's mobile, there's um like there's just there's tons of different things that you'd actually have to do. So it makes everything a lot more complicated. The other kind of thing to mention, I think, is that this this idea that it's not at all representative of your your day-to-day job. I'm gonna actually, there's a a post I really like that uh one of my co-authors wrote, actually, his name's Nil, and he wrote a post that's uh in defense of coding interviews, is what it's called. And it's actually just sort of like an argument as to why coding interviews are not as bad as people make them out to be.

SPEAKER_00And there's a handful of good points in there, but the one that really resonates with me is that I actually don't think uh if if you were to look at your day-to-day job as a software engineer, that the number of data structures and algorithms that you actually use on a day-to-day basis is quite astonishing. Now, sometimes you don't realize that. So, again, if you're a front-end engineer and you're traversing the DOM, like that's a tree, you're probably doing a depth-verse search, especially if you're doing anything complicated. I've used binary search in uh you know my own day-to-day job before.

SPEAKER_00Even if you're using things like Redis, like distributed caches, all those sorts of things are really important to know how they work under the hood. A database is a very simple thing.

SPEAKER_01If I can interrupt you for a second here, um what is a data structure and what is an algorithm?

SPEAKER_00Yeah, yeah, good question. So an algorithm is just a series of steps that we use to accomplish a specific task. So if you're you know in a I have a morning routine algorithm where I wake up, I you know, take some uh supplements, I you know, uh go about my day, I make my coffee, and there's an algorithm for me waking up. It's the same thing if we wanted to find the shortest distance between two points or um quickly and efficiently determine um you know two numbers that sum to zero.

SPEAKER_00Like there's some tons of different algorithms that sort of exist. And there's certainly popular ones that software engineers would be uh familiar with binary search, depth for search, things of that nature. Algorithms algorithms are pretty easy to understand. Data structures um I think are also fairly easy to understand.

SPEAKER_01Sorry, before we before we move on to data structures, let me let me interrupt again. I'm glad you use the example of like your morning routine as an algorithm, because algorithms don't have to be code. Um there are there are problems that can be solved algorithmically and problems that can't. Um if it's like more of an open-ended problem where you have to like bring to bear your like human judgment and stuff like that. That's not algorithmic, but but something more cut and dry, like um finding the length of the hypotenuse of a triangle, for example, you can use the Pythagorean theorem to find the answer algorithmically.

SPEAKER_01You're not using any code, um, but you are using an algorithm. Um, and the reason I wanted to like pause and dwell on these things is because oftentimes the my personal experience is like there exists a word like algorithm, and I only have like kind of a vague idea of it, and and it has all these connotations, maybe emotional connotations, where it's like, oh no, algorithm. Uh and I think of all those like uh CS classes that I didn't do very well at and stuff like that, and I'm like, oh no.

SPEAKER_01Um but then I say like hang on a second, what is an algorithm? And if you like if if you if you blow away all of your um baggage um around that idea and just start from scratch again, you're like, hang on, an algorithm is just a series of steps, and that's literally all it doesn't even have to be code, it's just a series of steps. That's it. Um that makes the whole thing a lot easier to grasp.

SPEAKER_00You're you're spot on. And I think, like you said, there's with every word that maybe we throw out even in this podcast, I think there's it invokes a certain amount of, like you said, baggage. If I you know mention dynamic programming, like there's gonna be software engineers that are like, oh, I I don't know about that one. Or like so everyone sort of has this preconceived notion of what things are. So yeah, algorithms, like we said, are just a series of steps. And data structures are just a way to structure data. And again, a simpler example that doesn't really use code for a sample, for example, is just like if you think of your phone book.

SPEAKER_00So the phone book has data in it, right? It's just people's names and their phone numbers. And I know this is 2025, so we have to hopefully most of the audience knows what a phone book is. But at this point, it's just people's names and then their phone numbers, maybe a description of and could you say that even a phone number is a data structure? Yeah, sure, absolutely. Uh a structured series of of numbers. So absolutely. And I think that uh a phone book, you know, you could structure a phone book in lots of different ways.

SPEAKER_00You could have names not next to phone numbers. You could have uh you know all of the names randomly sort of put in there, or you could have them sorted alphabetically. And the way that we choose to structure the data is going to matter if we care about finding things quickly. So again, if we sort of order everything by let's say last name, and then we specifically uh sort of put last name, then first name, and then the the phone number associated with it. If I want to find uh, let's say Jason Sweat, for instance, in the phone book, I'd go to Sweat.

SPEAKER_00And it's very easy for me to immediately know where in the book I am just based on where I open it up. If I open it up and I say, oh, I'm at B, okay, I need to go right in the book. I need to go down towards S, for instance. If I'm at the Z or the X or the Y, I can go back left. And it's a very easy way to sort of navigate because we have the data in a structured manner. That's the same thing we do, except in code as well. So data structures are just ways to more efficiently access the types of data that we care about.

SPEAKER_01Okay. Um, so that's what data structures and algorithms are. I forget where we were before before we went down that rabbit hole.

SPEAKER_00Yeah, I think the the higher level um point is about kind of interviewing and uh how hard these interviews have been. Like you mentioned, you'd you'd gone through an Amazon one, and these sorts of uh data structures and algorithms, questions exist and they're asked at companies like big tech companies, Amazon, Netflix, Google, and they're asked in in some ways as part of an IQ test. And we're talking about sort of uh the defense of coding interviews in general. And I do think that the the the general defense here is that most people maybe don't realize they're using a data structure or an algorithm, but I think it's because of that preconceived baggage, as you've you sort of said.

SPEAKER_00I think when you take a step back and you look at it, when you're using um, let's say Python, you know, if you use a dictionary in Python, that's a hash table under the hood. You know, and if you choose to use a set versus a list or uh a dictionary, like those are going to impact how fast your code can run. And especially at a big tech company, it actually kind of matters how fast your code runs because we're doing things potentially for you know uh billions of people.

SPEAKER_01Yeah, yeah, I got a taste of that for one of my consulting clients I worked with like a year ago. Um, they were at a bigger scale than most of the places I'd worked with before. And like it got to a point where like it mattered uh how our loops were structured because memory usage came into the picture. And it's like, wow, like usually that would be premature optimization, but not here. It's like we have to think about it right from the beginning before it even goes to production for the first time.

SPEAKER_00Yes, and it's I think it's actually kind of a meme you can find online where people maybe get into they they understand data structures and algorithms, they learn it to be able to pass the interviews, they then get into let's say Google or Meta or something like that, and then they start trying to write highly optimized code for something that doesn't need optimization. So I'm glad that you mentioned this idea of like premature optimization. Certainly we the interviews are centered around how do we optimize things, but it's important to realize that the best form of optimization is the one that you choose not to do when it's not necessary.

SPEAKER_01Yeah, you have to apply your optimization optimally.

SPEAKER_00Absolutely.

SPEAKER_01Um yeah, okay. And and there's another whole aspect of this. It's really interesting how like all this is tied into like ideology and psychology and even politics and stuff like that. Um a lot of people reject the idea of doing any kind of live coding in an interview. Um, you know, it doesn't have to be um this crazy like uh traverse a tree or something like that.

SPEAKER_01Um it can be something as simple as when when I was interviewing people when I was um when I was hiring people some years ago, I gave them an intentionally really simple coding challenge. Um they they had to code a certain version of the game Hangman. Um and it was it was meant to filter out people who it sounds this sounds mean, and I hope nobody who failed the interview is listening.

SPEAKER_01But it it it was meant to fail it was meant to filter out people who couldn't do easy things. Yep. Um and so I intentionally set the bar very low, and most people failed. Um it was it was really crazy, including people with 10 or 20 years of experience. Um and so you can't just go by again a a conversation, you can't take people's words for it. You can't take people's word for it. Um I I saw this chat in a Slack recently, and and people were like frustrated that they didn't pass the coding interview at a certain uh company.

SPEAKER_01Um and they're like, what, like all the companies that have hired me over the last 20 years, like I I can just get all these jobs without uh knowing what I'm doing. It's like, well, maybe like there's tons of people like that. Maybe um it it's not because you have ever had a job in your life, it does not logically follow that you're qualified for every job. Um so they need to like evaluate you somehow, they need something to go off of.

SPEAKER_01Um Yeah.

SPEAKER_00Yeah, if I can just uh interject there for a second. I I think you would I think the average listener would be astounded at the number of people with master's degrees, PhDs in computer science that you ask them to write a for loop with a couple of conditional statements, and they can't do it. Um there's a classic algorithm or a classic question that people may or may not know that's called fizz buzz. Um, and it's basically can you write a for loop and three conditional statements? You can even do it in in less code than that, but can you do this, this basic task?

SPEAKER_00And the number of people that that can't is problematic. Now, now to be clear, I do want to be fair to folks. I do think that is unnatural to be watched while coding. And I I want to be kind of sympathetic to that. Because if you're you're you know actively being like somebody's actively watching you type on the keyboard as you try and do even a simple task, it can be somewhat stressful. But that again goes back to the idea of practicing and the importance of practice and and the whole point of interview prep spaces is is that we can get significantly better if we just spend a little bit of time on these sorts of things.

SPEAKER_00So yeah, it's it's definitely something that is uh amazing to me, though. The number of people that uh just just cannot answer very simple questions with 10 years of experience in the space.

SPEAKER_01It truly is incredible. Um I I'm familiar with that phenomenon, and it's like, okay, wait, A is true and B is true, but it really, really doesn't seem like A and B can both be true at the same time, yet they are. How how does this work? Um Yeah, and I've like um I've encountered people who like spend four years at college majoring in a specific language, and then they get out and they can't speak the language.

SPEAKER_01And it's like, how how does that work? Um and I'm not trying to just like uh be mean to people by saying that, it's just like I I find it interesting. It's a really interesting phenomenon how people can can propose that this is like their main thing, this is their thing, but then they can't do the thing. I I I don't get it.

SPEAKER_00Yeah, and I there's a number of people I think that are are convinced that they know it because they can intellectually describe it. So if if I ask you how to do again, like some sort of question or puzzle or coding exercise, and you can describe how you would do it, it's also very different than being able to translate your thoughts into code. And some people like there's so many different parts of the interview sort of process that could be debugged. Is it like, can you not actually come up with the thoughts to begin with? Um, can you not translate it into code well?

SPEAKER_00Are you able to translate it into code, but just like buckle under the stress of the interview when somebody's watching you? Because again, that can be nervous. But there's so many different sort of failure points, I think, for this. And and certainly not everything is is uh just because people are um you know like not prepared, but there there are a number of things that can, I think, go wrong. And again, practice is is is why practice is so important.

SPEAKER_01Yeah, I just had a thought actually. Um so the people who study a language for four years and then can't speak it, um I think most of those people can like read and write in the language. Um but I've I've learned that reading and writing in a language and speaking and listening in the language are two totally different things. Totally different. Like yeah, like I can read and write Spanish decently, um, but I can hardly speak Spanish.

SPEAKER_01And I really have a hard time hearing Spanish. Like if I watch a YouTube in Spanish, uh forget about it. Like I I don't understand anything other than a word here and there. Um so those are two totally different things. Um in Chinese, I can speak uh better than I can in Spanish, um, but I can't read or write at all. Um to be fair, learning to read and write Chinese as an English speaker is way harder than learning Spanish.

SPEAKER_01Um but it it's just a totally different um skill, and it's like in a way the speaking and listening is like the application of it, and reading and writing is um is is not an application of the learning in quite the same way. You know, when you're writing, you can kind of take your time and and it doesn't matter how long it takes you to come up with the next word, but with speaking, it's real time. If if it takes you five seconds to remember a certain word, the other person is sitting there and waiting.

SPEAKER_01Um so it's it's a different the stakes are a little higher, the pressure is a little higher, all that stuff. It's a little harder. And so maybe maybe the case with these CS majors who can't code, um maybe they're doing the equivalent of they can read and write in the language, but they can't speak and listen.

SPEAKER_00Absolutely. I yeah, like I said, yeah, it's it's a great analogy. I do think that if we if we ignore cheating in an interview for a second, we sort of set aside the potential for people to cheat. Um and if we look back to how I've seen interviews done, let's say about six years ago. There was a really cool process I really liked that uh Salesforce did, and I don't mind kind of saying them by by name because I really uh think they did a wonderful job. And and what they did is they they would ask a question and they'd ask you to before asking the question, they'd they'd log into Google Meets and they'd talk, make sure that you were just kind of comfortable, and then they'd ask you to share your screen.

SPEAKER_00Um, and then they'd say you can use any tool you like. Uh this is the question. It's an algorithmic style question. It's a little harder than the typical one, but we're gonna give you a full hour. On top of that, I'm gonna actually turn off my camera, mute my mic, and I'm gonna go away. So I'm not even gonna be watching you. Quite frankly, I'm gonna let you hit the record button, and we're just gonna see what you do. I'm gonna look at the recording afterwards, and at the end of the hour mark, um, you're you're welcome to kind of leave and we'll we'll go about the business. So no pressure to sort of perform in front of people. You didn't have to like, you know, be constantly talking or worrying if you were communicating enough in the interview process.

SPEAKER_00You could just sit down and you could focus. And it was uh again geared towards the idea of, hey, look, you know, maybe you're not a senior engineer yet, maybe you're nervous in front of uh people, but take all the time you need, but can you get it done? That's the question. Now with AI, when we start entering that into the mix, this becomes a little bit less feasible, of course, because we can kind of just you know get AI to do a lot of these uh puzzles for us. But uh at that time it was a really, really good, great process. And I think it's screened for competency, but not necessarily um, you know, like again, you if you have the five-second pause equivalent of to what the method is that you're looking for in JavaScript or something, it just isn't a big deal.

SPEAKER_01Yeah. Yeah, I I like that. Um I used to do my um my screenings live, and I would ask the person to narrate everything as they were doing it. Um, because a big part of it was I wanted to see how they approached uh the the problem and how they thought and stuff like that. I started with 30 minute sessions, but then I I found that that was way too much time actually. Um because it was usually abundantly clear within like five minutes if the they would either like do okay or they would crash and burn immediately.

SPEAKER_01And again, most people crashed and burned. Um I want to ask a totally different question, if I may. Um I myself was on the job hunt between January and late March of this year, 2025. Um I had a really hard time. Um and people are often surprised. I I've been on a couple job searches in the last five years or so. Um, people are surprised when I tell them that I don't tend to have an easy time finding a job because they're like, Well, I would hire you in a second.

SPEAKER_01Uh and it's like, okay, well, do you have a job for me? No. Um so um um, but even like with my podcast and being like uh famous in this tiny way that I am, it only helps so much. Um so I had a really hard time in this job search. Um I relied a lot on personal connections. Um and and that when it worked, it worked great. And that's indeed how I how I ended up getting a job, which I started a few weeks ago.

SPEAKER_01Um thank you. Um but when I applied to jobs, like I almost never heard anything back, which isn't shocking because I hear these days people get hundreds of applicants. Um, and I'm curious, just like if we take a really like macro take on the whole thing, do you have a feel for what has gone on over the last let's say five or ten years in hiring? I I find this um I find this trajectory or whatever of the job market really interesting.

SPEAKER_01We had COVID, uh, which was this like big spike in hiring and stuff like that. And then we had like a hangover and all that stuff, but I'm not super clear on what's really happening and why and all that stuff. So I'm I'm curious if you have. Kind of a macro take on the whole thing. Um and then I don't know if if you could characterize the job market now, um how would you characterize it? And obviously, like I don't know how much you know and all that stuff, so feel free to take that question any way you want.

SPEAKER_00Sure. Uh let me see. There are a couple pieces to it. So let me see if I can uh tease some of that apart. So for one, I I think you alluded to the idea that things change, you know, in the last five, six years. There there have been a couple of big changes. One of the pushes was that uh pandemic issue where sort of everything was sort of forced to go remote. And so companies had to learn to do remote interviews. And now it's actually very common to do remote interviews, whereas uh beforehand it was common to do like a phone screen interview where maybe you had one remote interview, and then most interviews were actually done in person.

SPEAKER_00They'd fly you out and you'd sort of go there, especially at big tech companies like Google or Amazon or Meta or places like that. So what I'd say is that's been a huge shift, and now it's it was very common within the last sort of four to five years for everything to be remote. And it's only been in the last year and a half, again, with the introduction of uh AI sort of tools that sort of help you cheat, where that sort of uh is is becoming not a viable option. And some companies are now sort of being forced to revert their processes and go back into starting to bring people in person again.

SPEAKER_00Exactly. Yeah, so there's some early signs of both Meta and Amazon doing that, and I uh suspect that this year there will be an announcement. And once one major tech company chooses to do so, I anticipate it won't be long before the others follow. Um, even companies like Zoom, for instance, which is sort of a very much a remote first company, uh recently has said that actually we don't do remote work anymore. We we're now going to be an in-person company, which is a little ironic um given sort of what that they they do. But it's interesting to see just how much this impacts everything from certainly the hiring process.

SPEAKER_00But if you then hire people that can't do the job because they've somehow gotten in through through not a uh uh uh skill on their own, you then have culture problems and that sort of trickles down from there. A lot of people don't realize just the amount of money that goes into hiring a single candidate can be upwards of, I think it's I think Google quotes$700,000 per person that they end up actually hiring. And that doesn't include the salary, it's just like the effort that goes into recruiters and then interviewer time and all that kind of stuff. And I think that number is only going up.

SPEAKER_00So so I guess yeah, the first question is sort of like how are things different? Well, those are some of the things that have changed. Uh, and this remote interviewing is different because well, because it is, quite frankly. Um, there's lots of different reasons for that. But then as far as like the difficulty in getting a job right now, because again, AI is a thing. You used to be able to click on a job on LinkedIn or indeed.com or someplace like this and apply, you'd spend time filling out the form. And hopefully you'd hear back if you did 20, 30, 50 of them.

SPEAKER_00Nowadays, there are AI tools that'll go click those buttons for you, auto-enter your information, and then flood companies with uh your your resume. And lots of people are familiar with them. If you were to do just any amount of Googling, you could find tools like this, which means every every job that exists, you can get AI to sort of apply for you on your behalf. So recruiters who were already overwhelmed now face the task of needing to sort through not you know a X amount of people, but 10x the number of candidates.

SPEAKER_01And I want to add something else. Um we're no longer geographically constrained, and so the market got like flattened in a big way. Um now jobs are available to a much broader pool of applicants, and um applicants are available to a much broader pool of employers.

SPEAKER_00Absolutely. And there's been even more shifts, like take uh Netflix, for instance. Um they used to be well known for hiring only senior engineers, and they actually changed their process. Now they hire junior and intermediate engineers as well. And companies have have found that actually just more heads is tends to be a pretty good thing. And then getting into the habit of just uh um letting go people, I suppose, that um aren't performing to the standard that they hope for is better. So rather than having a select number of people, it's like let's actually hire more than we need and anticipate needing to let go some people.

SPEAKER_00So that's a little bit more of a cutthroat decision that places have made. And there's lots of different reasons for that change. Some of it was again um culture problems with people getting in that shouldn't have gotten in. And then I think even more so than that, there have been you know sort of policy changes within um the United States at the very least, that I can say that have kind of made big impacts and um certain other things that they care about. I don't know if you've seen it all in the news, but there's uh been a lot of uh concern with North Korea specifically, because we there was a recent um sort of news scandal where they found North Koreans specifically that had basically um taken a US person's identity.

SPEAKER_00The person had no experience at all with coding or anything like that, but pretended to, and would go into the interviews and have sort of things pop up on their screen to say exactly what you know, what exactly they should say to pass the interview, exactly what they needed to type to pass the interview. And then um these people would give half the salary to the person in order to sort of be like spies within um uh different industries. So it's kind of a big deal, and it's uh we're we're finding more and more instances of that as things occur over time. So I think that was a little bit uh rambly, a little all over the place.

SPEAKER_00But yeah, it just kind of shows the involved in that.

SPEAKER_01That is fascinating. Um going back to before, um, the reason I said the thing about the flattening of the markets is because it opens up every job uh posting to be applied to by way more people. And so um, you know, people overuse the word spam these days. Um like my kids say, like, oh, I spammed the controller button on the video game, and it's like, well, that's not what spam means.

SPEAKER_01Um but it truly is spam uh when when a job application is getting like a thousand applications and ninety percent of them are junk, and sadly ninety percent is maybe even a conservative estimate, maybe it's ninety-five or ninety-nine percent that that aren't worth even talking to. Um and so I was aware of this phenomenon when I started my job search, and my thought was like, well, the traditional path to just getting interviews is kind of ruined uh for for the foreseeable future.

SPEAKER_01Um and so I'm like, all right, well, I can't really do that anymore, so what do I do? And ironically, you know, it's it's ironic that um technology allowed us to do remote interviews, and then in an additional advance in technologies forced us to go back to in-person interviews because of the AI trickery. Um and so technology allowed us to have remote job applications, you don't have to walk into a place and fill out a peop piece of paper anymore.

SPEAKER_01Um but now technology makes it so job applications don't really work anymore. And so in in another instance of this, I had to go back to the old-fashioned way and just talk with people I knew and try to get referrals and stuff like that. And almost all of my um not almost all, but probably probably half of my interviews came from that.

SPEAKER_00Yeah, that that's and you're you're spot on about it, it it sort of enabling and then disabling the ability to have people interview. I think that even with with further advances in technology, we might find that again, it it's now possible, again, maybe some way to verify identities and sort of monitor a person's um activities and things like that, where it could be m safer, let's say, uh to sort of interview folks. But I do think that the the higher level point that's really important, I think, for for listeners is to realize that right that that existing path is now broken.

SPEAKER_00If you apply to a job, it's very, very likely that over 500 other people have applied to that same tech job. That's a that's an actual stat. And I think that the concern there is if you're only ever using this one path to try and get uh interviews, you're you're gonna be at a loss. Like you said, I think you you ended up leveraging connections, and that's definitely something we recommend. There's other strategies in the book though. There's um not rather than focusing on the tools specifically, I'll just say what the high-level idea is. And the high-level idea is that there's always a hiring manager at a big tech company looking for uh heads, like looking for qualified candidates.

SPEAKER_00So if you think you are like you know a good software engineer and you think that you you want to be able to kind of interview someplace, one of the best things that you can do is find the hiring managers, not the recruiters, but the actual hiring manager. And sometimes they post very publicly on LinkedIn. Hey, I'm at DoorDash, I'm hiring three people for backend development. And you can find these through various tools. Again, it's not really about the tools, but there are tools that allow you to do this. Um, and then once you find them, you send emails to them, and there are tools that kind of help you guess what the email is of the person.

SPEAKER_00And you can actually send an email directly to a hiring manager and say, Hey, I saw it from this post, you're looking for folks. This is why I'm a good fit. Here's my resume. Give them all of that work up front. You bypass the recruiter altogether. And there are very few people currently doing that. So right now, in 2025, this is what we find one of the best ways to kind of get in to companies. And I say big tech, but it works well for startups and things like that too. If you personally write a note that's thoughtful to the founder and say, hey, I'm really interesting, I'm really interested in this technology.

SPEAKER_00I'd really like to work here. I saw that you were hiring. Here's my resume. What can I do to get in the door? Like that's a lot more powerful than just, you know, you've you've applied to the same position that a thousand other people did in the last you know 30 days that there's been uh advertised for. Does that make sense?

SPEAKER_01It totally does. Um, and the job that I ended up getting, um, I work now at a place called Cisco Maraki. Um I I got hired by somebody I I knew already. Um he had been on the podcast before, like, and he's active in the Ruby community. I was aware of him, he was aware of me. Um and and so that really helped to kind of um he he like I I was a known entity before I entered the interview process.

SPEAKER_01Um and I I wasn't able to like you know, there's some situations where you kind of bypass the normal vetting system because it's just like, oh, you're looking for oh, just like come work here. You don't need to interview, like just come have a job. Um, it wasn't that. I still went through the full interview process and all that stuff. Um, but like I had actually applied to the same job and got rejected. Um same exact same exact job opening. Um sad.

SPEAKER_01Yeah. Um, but then like it was like I applied, some days later got rejected. Some days later, a friend of mine uh gave me a referral. Um, and then I got in the interview process and and here I am. Um so that was really a a stark demonstration of the power of a personal referral, and I think there's another lesson there too. Um it wasn't just dumb luck that I had already known the um hiring manager for this position.

SPEAKER_01Um I've been doing this podcast for some number of years, and it is uh very consciously I I started this podcast very consciously to boost my career. Yes. Um and that meant maybe different things when I when I first started, I had different things in mind. Um and I don't think I was working a job at the time. I was doing freelancing and consulting, but I had in my mind, like if I ever need to use this for that, if I ever need to get a job, um I I think this podcast will help me tremendously.

SPEAKER_01That's what I thought. I don't know if it helped me tremendously. Again, it's it's hard to characterize it because like it when it worked, it really worked, you know? Yes. Um, but it's it's not like I had dozens of people falling over themselves to want to interview me and hiring me. That was not the case. It was like three places uh were interested in interviewing me, and then one hired me, but you know, you only need it to work once, and for that once that it worked, it worked out totally great.

SPEAKER_01Um, so the the the advice that I want to share is is to make yourself into um a person I I'll I'll put it in kind of a vague way, make yourself into somebody. Um so like you know, ten years ago I was like anonymous. Um but then once I put out this podcast and I spoke at conferences and all that, I like you know, frankly, I raised my status.

SPEAKER_01I became a higher status person and a more well-known person. And that kind of thing. If you become a high status person, it affords you relationships with other high status people. And if you have relationships with high status people, they can you you have good opportunities open to you which wouldn't be open to you otherwise.

SPEAKER_00I I completely agree with that. I I would amend what you said instead of make yourself into somebody, like ask how you are already somebody. And I think you'll find a lot of people with 10 years of experience, uh, you know, especially the the sort of folks that already have some career capital uh under their belt, it's a matter of sort of showcasing that. So imagine um, you know, maybe maybe you didn't start a podcast, maybe you know, did open source work and you did commits to, I don't know, Apache servers or something like that.

SPEAKER_00Like that, that actually is is high value. And a lot of people would value that sort of thing. So it doesn't have to be starting a podcast. It could be technical contributions, um, it could be social contributions, it could be you started a charity. There's there's like lots of things you can do. You could have your own business um doing things. You could, for instance, write a book. Um, there's lots of different things you can do to sort of become more well known, but making yourself into somebody is important, or at least asking yourself, is there any way that I can leverage the stuff that I've already done for the last several years of my career? Um what is the better way of showing that?

SPEAKER_01Yeah, similar to how we explored the questions of like what is a data structure and what is an algorithm. Um, this job search process is an exercise in sales and marketing. Um, and for me, like when I do my podcast, that is marketing. Um, because it's a way of letting people know that I exist. Um a lot a lot more people know who I am because of my podcast than would know who I am if I didn't have my podcast.

SPEAKER_01So that's marketing. Um and like the stuff, the actual content of the podcast, that's marketing too. Um, because I'm like allowing people to get to know me over time and they're forming a certain opinion of who I am and stuff like that. Um then in a um job interview uh that's that's a sales process. Um and a lot of developers have what I call a pathological aversion to sales and marketing.

SPEAKER_01Um but I think the thing that they don't like isn't sales and marketing. What they don't like is bad sales and marketing. Um so a lot of people think of sales as like coercion. Um but it's not that. My definition of sales is helping people buy what they want to buy. Um and in an interview, it's um, you know, the the buyer, they're they they need, you know, when I need to buy a set of tires for my car, um, that's the thing I need to buy. When somebody's hiring somebody, they have a job that they need to fill and they need a candidate.

SPEAKER_01So it's like you can't just go to the candidate store and buy a candidate, but it's still a sales transaction that's happening. Um, and the idea isn't to coerce the buyer in into or like even really overtly persuade the buyer, um, but to help the buyer ask answer the question, um, is this the thing that I should buy? And if it is the thing that they should buy, uh, then you should help them understand um why.

SPEAKER_01So to me, that's all that is.

SPEAKER_00I I completely agree. I I think that there's there's maybe a little bit too much emphasis on wanting the technological achievements to speak for themselves. Like, well, I I I worked in this technology for the past 10 years, or I have years of experience dictate whether or not you should get jobs, just like the the person that you said at the beginning. It's like what everyone else is just uh wrong about having hired me. Well, maybe, but like you you probably are good at a very specific set of things.

SPEAKER_00And does this company need that very specific set of things? Maybe. I don't know. You have to kind of show what you're good at and highlight that in sort of uh the best way possible. Right now, um there's sort of this, you know, in in economics at large, there's sort of this shift in the marketplace where there's a lot more gig workers and people, you know, it's the gig economy that people talk about. And I think that this era of doing work is gonna revolve a lot more on selling your own personal attributes and what makes you special as an individual.

SPEAKER_00And to a certain extent, I realize engineers are gonna hate that, but it it is gonna be one of the key factors to getting jobs. And I think that anything um that you do to sort of promote your brand is is definitely gonna be a net positive. Some people just I I met a uh I say I want to say kid, but that's that's not fair to them. But a younger individual who's just starting his career and he decided he was gonna post for a hundred days on LinkedIn. He said publicly he was gonna post for a hundred days, um, just different learnings about the job search.

SPEAKER_00And so he started doing that. And by day 100, he got a job. And the reason he got a job is because he was very publicly saying he was gonna do something, he was following through on that commitment and he was developing interesting content. Oh, oh, that actually, if I had a similar type of situation that you did in an interview, and if that similar thing happened to me, I would have also panicked or freaked out about it. So he was sharing useful information to people, and eventually people just after a hundred days started reaching out. He got notice. So it's it's again, it doesn't have to be something huge that you do, and you don't have to have any sort of prior notoriety, but just doing kind of something a little bit more public makes a big difference.

SPEAKER_01Yeah, I totally agree. Um, I'm hesitant to give a lot of advice on a lot of topics because I've gotten a lot of bad advice over the years, and I really I think that's no good. Um, but I'm very confident in giving the advice that it's a good idea to like um raise your profile and do these things publicly and stuff like that, uh, because only good things are gonna come out of that. Like even if it doesn't help you get a job, like it's um you'll never like regret well probably you'll never regret like um building a good reputation online and that kind of thing.

SPEAKER_00Absolutely. I I I think we're in agreement.

SPEAKER_01Yeah. Um okay. So I I want to go back to like the the big picture of the job market and stuff like that, because frankly, it's something that like worries me a little bit. Um because I'm like in the industry. Um maybe the job I'm at now is the job that I'll have for the rest of my career, but I don't want to bet the farm on that. Um and I've seen people who have like atrophied and they kind of take their job for granted, and then one day there's a layoff and it's like a little red hen situation or something.

SPEAKER_01They they haven't been putting in the work and suddenly they you know it's too late. You you can't go back and like you can't go back and have been marketing yourself for the last 10 years starting today, it's too late. Um so I'm I I really want to avoid that, and I want to always have the mentality of like if I got laid off today, uh how good of a position am I in to get my next thing? But again, things are different now.

SPEAKER_01Um and I've you know there's that saying predictions are hard, especially about the future, and so I'm I'm not gonna try to predict I'm not I'm not gonna like kill myself over predicting the future, but I want to at least give it some thought. Um so it seems like what has happened, I used to think that software engineers were like basically in infinite demand and always would be. Now I think I was mistaken. Um it seems to me that maybe what has happened over the last couple of years is companies have realized, like, oh wait, we can get by with like not as many engineers.

SPEAKER_01Like maybe people saw what Elon Musk did with Twitter and he he got rid of the vast majority of the programmers and the world didn't end. Um Twitter is still up despite everybody's predictions, not everybody's despite a lot of predictions that it would crash and burn. Um and um so now it seems like the demand is no longer bottomless and it's gone from being a seller's market to a buyer's market.

SPEAKER_01And I'm not sure it's like is is this a temporary uh swing or is this like a permanent state of things? What's going on? Um again, I'm I'm concerned and I'm trying to imagine like how do I position myself, what's gonna happen, that kind of thing. Any thoughts on that?

SPEAKER_00Uh a handful. Uh if I can if you can indulge me just to go down a rabbit hole for a second, because you brought up Twitter as the example. Um there are there exists, I don't remember what the term is for it, but there's I think it's a psychology term, but it's it's basically around the idea of like if you uh a popular thing on Facebook a while ago was a picture of a dress, and people asked, is it blue or is it green? And you'd find half the people would say it's a blue dress, and then the other half would say it's a green dress. And people would be like, no, it's very clearly one or the other. And and the I find the Twitter situation to be exactly that as well.

SPEAKER_00So people are like, look, Twitter, um uh like there was this big um you know, you know, sort of change that Elon Musk kind of came in and come up with. And I don't want to get into politics on it, but the the the high level still was Twitter's still up and running. But I find about half the people will say, look, it worked, Twitter's still running. And then I think the other half I find, and it's very, very, very distinct. Software engineers will say very different things about it. The other half will say Twitter is now not good. And there's lots of kind of different things they'll point to. They'll point to like, you know, it crashing when Donald Trump went on, and like the kind of examples of like Twitter going down at like a significantly higher rate um fairly regularly now, and and things like that.

SPEAKER_00Um, attrition from the app in general. So so there's lots of things that was it, like it did it work? Yeah, I mean, it kind of, sure. I guess it depends on the maybe what we're calling uh working there. So it's interesting just to kind of dwell on that for a second. Is did it did it work or did it not?

SPEAKER_01Yeah. By the way, my personal definition uh is did it go down permanently? Yeah. And obviously that didn't happen.

SPEAKER_00Sure. I think uh there there are enough things where I think most Google engineers could stop working for the next decade and Google search and some some semblance of it would probably stay up, but there would be a lot of things that would go wrong. So like if it if it stops working the way users intend for it to, I think maybe would be how I would I would view the better definition. So like if I want to post a tweet, can I?

SPEAKER_01Yeah, that's that's interesting. Um, yeah, and I think my angle is not um, was that a uh like sound move to lay off all those people? Um but did the predictions of the naysayers come true or not true? Yeah um and obviously the the predictions uh the predictions that it would go down permanently were were not true.

SPEAKER_00This this I agree with. Yeah, it's it's still a fun thing to talk about. But as far as uh going back out of the rabbit hole for a second, um, yeah, I think we've sort of established the idea that interviews are changing, processes are changing. Again, I don't want to exactly say what I think the process will look like in the future, but I'm confident of a couple of things. So the the first thing I'd say is some people think, again, with the advent of AI, that coding interviews are going away. And for reasons that Jason, you've already brought up, that that's not happening because there are too many people that actually cannot code.

SPEAKER_00Uh so we need some sort of uh process in place. Uh I would also go a step farther and say that I think a democratized way to measure people outside of specific expertise is important because it doesn't scale to ask custom questions uh that could easily get leaked and then need to be sort of re-come up with every single time, which is why the lead code data structures and algorithms work so well, because you can like if if one question gets leaked, you can go grab another one. There's a site that has 3,000 of them.

SPEAKER_00So it's it's very easy to just kind of keep asking them. So I don't think they're going away anytime in the near future, despite what a lot of people say. And then I think in-person interviews are also likely to kind of come back. And I'd say that if you get to that in-person piece, I found that at least in the current market, it's a lot easier to pass the in-person interviews than it is to get through everything else. And I'm not going to say that in-person interviews are easy, but if you already kind of know what you're doing and you can get to that point, then you have that ability to interact with other people and just sort of have a certain amount of likability kind of displayed.

SPEAKER_00So I think that's kind of maybe a couple of the high-level things. As far as like specific feed advice to give here, I think we've covered one of the pieces, which is make yourself hireable and publicly hireable is important. Do things in public. The other thing I'd say is realize that you need a bit more of a buffer. And whether we talk about that from a financial buffer, like make sure that you have a you know a savings of, you know, like I think that's a little bit outside the scope to talk about, but it's it's it's interesting to like there are some people that are living paycheck to paycheck, and that's going to be significantly harder and realize that.

SPEAKER_00Um more in line with tech though, realize that you need to give yourself as much of a buffer as you can. So if you are suspecting layoffs, like maybe we start doing the prep before we get fired rather than waiting for it to happen. And that's it's not an easy thing to say, and I wish that there was a better answer to that. But that that is transparently what I find to be the best thing. If you already are hitting the ground running, you're better off. I'm not saying you should have the foot out the door, but also you can't uh undo years and years of not doing like any sort of prep of any kind.

SPEAKER_00It's kind of like if you're maybe overweight and uh you you're trying to like then change all of your habits and stuff like that. Well, you didn't get in this position by you know overnight. So you're not gonna get out of it overnight either.

SPEAKER_01Yeah. So you're trapped somewhere and you need to get through the small opening, and it's like, oh, I need to fit through the opening, but you you can't lose a hundred pounds and yeah, yeah.

SPEAKER_00Can't rush it.

SPEAKER_01Yeah. Um, okay. Yeah, wow. This has been um a really fun conversation, uh, dear listener. I hope this has been enjoyable and informative. Um and Mike, do you want to tell people about where they can find your book and anything else you want to send them to?

SPEAKER_00Absolutely. Yeah, so uh my name's Mike Marachka, so mikemarochka.com, and I think maybe we can leave a link in the show notes if you're interested in uh any sort of coaching or uh consulting work uh for me. But if you're interested in the book, that's actually available on Amazon that's beyond cracking the coding interview, and maybe we can leave a link for that as well. Also, if you're interested and you're not sure you want to commit to it, uh there's uh nine free chapters that I give away that I'm also happy to give a link to in the chapter as well. So if you want to get information, both technical information that's in the book and then non technical information and just get a sense as to what the style is.

SPEAKER_00I understand. That not everybody likes a book. You want to get a sample, you can do that for free from the URL as well.

SPEAKER_01Awesome. Well, Mike, thanks so much for coming on the show.

SPEAKER_00Jason, thanks for having me.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. 338 - Code Review, Testing, and Staying Sharp in the AI Era with Joel Hawksley

    Nov 18, 20261 hr 5 minAudio

    In this episode I talk with Joel Hawksley, Staff Software Engineer at GitHub and creator of ViewComponent, about whether AI is making us dumber, why blocking code reviews struggle under a flood of AI-generated code, and...

    Credit the people on this episode

  2. 337 - User Testing, Paper Prototypes, and Escaping Hourly Billing with John Athayde

    Nov 17, 20261 hr 18 minAudio

    In this episode I talk with John Athayde, designer-developer and co-author of The Rails View, about what architecture school taught him about software design. John tells the story of a user test at LivingSocial that...

    Credit the people on this episode

  3. 336 - Riccardo Carlesso, Co-Organizer of Rubycon Italy

    Nov 13, 202646 minAudio

    In this episode I talk with Riccardo Carlesso, Google developer advocate and co-founder of Rubycon, a Ruby conference held in Rimini, Italy in May 2026. Riccardo explains how a joke about PyCon became the conference's...

    Credit the people on this episode

  4. 335 - Blastoff Rails: Starting a Ruby Conference from Scratch with Travis Dockter

    Nov 11, 202654 minAudio

    In this episode I talk with Travis Dockter, organizer of Blastoff Rails in Albuquerque. When Sin City Ruby and RailsConf both ended, Travis decided to start his own conference. We discuss how cheaply you can run a...

    Credit the people on this episode

  5. 334 - Merge Queues and Building Mergify with Julien Danjou

    Nov 10, 202655 minAudio

    In this episode I talk with Julien Danjou, CEO of Mergify, about merge queues: why PRs that pass CI separately can still break main together, and how testing changes in a queue keeps main green. We discuss how Mergify...

    Credit the people on this episode