HOST_A: Welcome back to Clawd Talks. I'm Emma.
HOST_B: And I'm Ryan. Today we're doing something a little different — this is a full-length episode, and we're going deep.
HOST_A: Really deep. Because the topic deserves it. We're talking about finding a new job. Writing your CV. Surviving — and actually thriving — in interviews.
HOST_B: And before you think "oh, another career advice podcast," let me stop you right there. We're going to spend a lot of time on what actually works versus what feels like progress.
HOST_A: Because those two things are very different. And I say that as someone who went through a full job search about eighteen months ago. I did a lot of things that felt productive and were completely useless.
HOST_B: And I say it as someone who's been on the hiring side — I've reviewed hundreds of CVs, done more interviews than I can count, and made hiring decisions. So we're bringing both perspectives.
HOST_A: Alright, let's start with some numbers. Because I want to hit you with a few statistics that might genuinely change how you think about this.
HOST_B: Go ahead. Set the scene.
HOST_A: Okay. Somewhere between seventy and eighty percent of jobs are filled through networking or referrals. Not job boards. Not LinkedIn applications. Through people.
HOST_B: That number always shocks people the first time they hear it. But when you think about how hiring actually works — it makes complete sense.
HOST_A: Right. Because if you're a hiring manager and someone you trust says "hey, I know a great person for this role," you're going to talk to that person before you post anything publicly.
HOST_B: Often the job posting is almost an afterthought. The internal candidate is already half-decided before the ad goes live.
HOST_A: Which brings us to statistic number two. The average job posting receives two hundred and fifty applications.
HOST_B: Two hundred and fifty. That's a lot of competition.
HOST_A: And here's where it gets worse. Most of those CVs — and I mean most, like the majority — are never read by a human being.
HOST_B: Because of Applicant Tracking Systems. ATS. We'll talk about these a lot today.
HOST_A: Basically software that filters applications before a human ever sees them. And if your CV doesn't have the right keywords in the right format, it's gone. Silently rejected. Nobody tells you.
HOST_B: And then the ones that do make it through? An average recruiter scans a CV for six to seven seconds before deciding whether to read further or move on.
HOST_A: Six seconds. That's roughly the time it takes to say "hi, I'm a results-driven professional with a passion for excellence."
HOST_B: Which is exactly the kind of line that gets you rejected in those six seconds.
HOST_A: So we've got a situation where most jobs aren't on job boards, most applications are auto-rejected, and the ones that aren't get six seconds of attention. That's the landscape. And somehow people are surprised when their search takes months.
HOST_B: It's not a reflection of your worth. It's a reflection of a broken system that you need to understand before you can navigate it effectively.
HOST_A: Exactly. So let's talk about how to navigate it. Starting with the most important thing — the job search strategy itself.
HOST_B: And the number one thing, before we talk about any platform or tool, is networking. Genuine relationship maintenance. Not schmoozing. Not going to conferences and handing out business cards.
HOST_A: Real networking is just staying connected to the people you've worked with. And most people are terrible at this when they don't need it — and then try to activate it desperately when they do.
HOST_B: Which is exactly the wrong approach. If the first time you reach out to someone in three years is to ask for a job lead, that's awkward for everyone.
HOST_A: It's uncomfortable to receive, too. I've been on that end. Someone I hadn't spoken to since a previous company reaches out and it's immediately clear they want something.
HOST_B: Whereas genuine networking is just... staying warm. Commenting on someone's LinkedIn post. Sending a quick message saying "saw this article, thought of you." Grabbing a coffee when you're in the same city.
HOST_A: And then when you are looking, the outreach feels natural because the relationship already exists.
HOST_B: So the practical advice here is: don't wait until you need a job to maintain your network. Do it now. All the time. It's a muscle.
HOST_A: And if you're already in a search and your network has gone cold — it's not too late, it's just harder. Be honest. "Hey, I'm looking for something new, I'd love to reconnect and hear what you've been up to." People generally respect directness.
HOST_B: Now let's talk about LinkedIn specifically. Because I see a huge misuse of it. Most people treat LinkedIn like a static CV archive. They update it when they change jobs and then forget it exists.
HOST_A: Right. And then when they're job searching they suddenly go from zero activity to applying for thirty jobs at once, and recruiters see that spike and it's a red flag.
HOST_B: LinkedIn is actually a networking platform masquerading as a job board. The value isn't in the job listings — it's in the connections and the visibility.
HOST_A: If you post occasionally — even once or twice a month — about something relevant to your field, you stay visible. Recruiters who look at your profile see recent activity. Former colleagues see your name. It works.
HOST_B: And you can use LinkedIn for warm outreach in a really specific way. "I saw that your company posted a role in X — I'd love to have a fifteen minute call to learn more about the team." That message works. Submitting the form doesn't.
HOST_A: The warm outreach versus cold apply thing is so important and so underused. A personalised message to the right person almost always beats a generic application into a black hole.
HOST_B: Because you're creating a conversation instead of joining a pile.
HOST_A: Let's talk about job boards, because people will use them — and they should, they're not useless. But in priority order.
HOST_B: So LinkedIn is actually good for jobs, not just networking — because of the network effect. You can see if you have connections at the company. You can see who posted the job. You can message them.
HOST_A: Indeed is the biggest job aggregator globally. Good for breadth. Search by keyword and location and set up alerts so you're not constantly hunting.
HOST_B: If you're in the DACH region — Germany, Austria, Switzerland — Xing is still very relevant, especially in Germany and Austria. A lot of companies post there that don't bother with LinkedIn.
HOST_A: And for Switzerland specifically, jobs.ch is huge. Swiss employers take it seriously. If you're searching in Switzerland, you need to be on jobs.ch.
HOST_B: And then there's company career pages. Often underused. If you have a list of companies you'd love to work for, check their careers page directly. Sometimes roles are posted there before they hit the aggregators.
HOST_A: Which brings us to something called the hidden job market. This is real, and it's bigger than most people think.
HOST_B: The idea is that many roles — especially at the senior level — are filled before they're ever publicly posted. Someone inside the company knows someone. A recruiter reaches out proactively. A former employee comes back. The posting is a formality.
HOST_A: How do you get access to that hidden market? You become visible to the companies before the need arises.
HOST_B: Follow companies you want to work for on LinkedIn. Interact with their content — not just likes, but thoughtful comments. Follow their leaders. You start to appear in their ecosystem.
HOST_A: And then the proactive outreach piece. I'm a big fan of what I call the target list approach. You sit down and you identify twenty to thirty companies you would genuinely love to work for. Not random companies — companies you've researched and chosen.
HOST_B: And then you approach them systematically. Not all at once. Staggered over a few weeks. With personalised messages to relevant people — hiring managers, department heads, maybe even founders at smaller companies.
HOST_A: "I've been following your company for a while. I'm particularly interested in the work you're doing on X. I have a background in Y and I'd love to explore whether there might be a fit, now or in the future."
HOST_B: And then you get a conversation. Which is infinitely better than a job application form.
HOST_A: Now let's talk about recruiters. Because people either over-rely on them or completely dismiss them, and the reality is more nuanced.
HOST_B: Recruiters are most useful at the senior level, in specialised fields, and when you're making a significant career move. If you're a senior software engineer or a CFO looking for your next role, working with good specialist recruiters makes a lot of sense.
HOST_A: Because they have relationships with companies that aren't publicly hiring. They're the bridge to that hidden job market in specific sectors.
HOST_B: How to work with them well: be specific about what you want. The more clear you are — company size, industry, role type, compensation range — the easier you make their job, and the more likely they are to bring you relevant opportunities.
HOST_A: And follow up. Recruiters are juggling dozens of candidates. A polite check-in once every couple of weeks is fine. More than that and you become annoying. Less and you get forgotten.
HOST_B: One more thing on timelines. And I want to say this clearly: the average senior job search takes three to six months. That's not a failure — that's reality.
HOST_A: And one of the worst things you can do is panic at month two and accept the first offer that comes along just to make it stop. I've seen people do that and end up miserable within six months.
HOST_B: Treat the search like a project with a runway. If you can, build up savings before you leave your current role. If you're searching while employed — which is ideal — protect your energy and be patient.
HOST_A: Okay, let's move on to CVs. Because this is where so many people spend enormous effort on the wrong things.
HOST_B: The ATS problem is real and it's the first thing to address. Most companies with more than a few hundred employees use some kind of applicant tracking system. Your CV goes in, gets parsed by software, and gets scored before a human ever touches it.
HOST_A: So if you have tables, fancy graphics, columns, text boxes, unusual fonts — a lot of that is invisible to the ATS. It just sees a jumbled mess. Or nothing at all.
HOST_B: The safest CV format for ATS is single column, clean, standard fonts like Arial or Calibri, no headers and footers with critical info, no text boxes, no logos. And send it as a PDF unless the employer specifically asks for Word.
HOST_A: Even though PDFs look better, some older ATS systems still struggle with them. But most modern ones handle PDF fine, and PDF preserves your formatting. So PDF is usually the right call.
HOST_B: On length — for most roles, two pages maximum. If you're mid-career, one page might leave out too much. If you're very senior with thirty years of experience, maybe two and a half. But two is the standard.
HOST_A: Now here's the keyword piece. And I want to be really clear — this isn't about stuffing keywords. It's about mirroring the language of the job description naturally.
HOST_B: If the job description says "project management" and your CV says "managing projects" — a dumb ATS might not match those. Use their language.
HOST_A: Read the job description carefully. Pull out the key skills, tools, methodologies they mention. Make sure those appear in your CV — if you actually have them — in natural sentences.
HOST_B: Not a keyword dump at the bottom. Woven into your experience descriptions. "Led cross-functional project management for a team of twelve using Agile methodology" — that's natural and it hits keywords.
HOST_A: Let's talk about the summary section. At the top of your CV. This is prime real estate and most people waste it.
HOST_B: "Results-driven professional with a passion for excellence and a proven track record of success." That tells me absolutely nothing. I see that on a hundred CVs a day.
HOST_A: Your summary should be three to four lines. It should be tailored to the specific role. It should contain something specific. "Product manager with eight years building B2B SaaS products, most recently scaled a team from three to twenty engineers while taking a product from zero to two million ARR."
HOST_B: That's a summary. That's something memorable. That's something I'm going to keep reading.
HOST_A: And tailor it every time. Yes, every time. It takes twenty minutes. And it's the biggest unlock in the whole CV process.
HOST_B: The experience section is where most CVs fall apart. People describe their job duties — what they were supposed to do — rather than their achievements — what they actually did.
HOST_A: "Responsible for customer success operations." That tells me what your job was. "Reduced customer churn by thirty percent over twelve months by implementing a proactive health scoring system." That tells me what you're worth.
HOST_B: Quantify everything you possibly can. Revenue, cost savings, team size, percentage improvements, time saved. Numbers make achievements concrete and believable. They also differentiate you from the other two hundred and forty-nine people who had a similar job title.
HOST_A: And if you're in a role where the outputs are hard to quantify — creative fields, policy, education — think harder. How many people did your initiative reach? What was the budget you managed? How long did the project take compared to the previous one?
HOST_B: There's almost always a number somewhere. Find it.
HOST_A: Now let's talk about the Lebenslauf — the German and Swiss CV convention. Because if you're applying in DACH, there are some real differences from the UK or US norm.
HOST_B: In Switzerland and Germany, a photo is expected. Not optional — expected. It should be a professional headshot. Not a selfie, not a holiday photo cropped to show your face.
HOST_A: Date of birth is often included. Nationality, marital status — these vary but they're more accepted than in the US or UK where including them would be unusual.
HOST_B: The format is very structured. Very chronological. Swiss and German employers in particular appreciate a clean, well-organised document that's easy to scan.
HOST_A: And the Anschreiben — the cover letter. Even when companies say it's optional in DACH, it's often not really optional. German-speaking hiring managers often use the cover letter to assess your written communication skills and your motivation.
HOST_B: Treat it as required unless you have a strong signal that it genuinely isn't. And write it properly — not a rehash of your CV, but a narrative about why this company, this role, this moment.
HOST_A: Your LinkedIn profile also needs to align with your CV. I've seen hiring managers pull up LinkedIn during an interview to cross-reference. If the dates don't match, if you've inflated a title, if there's a role on your CV that's not on LinkedIn — you've got a problem.
HOST_B: And LinkedIn is its own discovery channel. Recruiters search LinkedIn independently of your applications. Having a complete, well-written profile with recommendations and skills endorsements makes you more findable.
HOST_A: Get recommendations. Actual text recommendations from former managers, clients, colleagues. They're worth a lot more than self-endorsed skills.
HOST_B: And post occasionally. Not constantly — occasionally. Even once a month. Something relevant to your field. A lesson learned, a book you found useful, a comment on an industry trend. Visibility matters.
HOST_A: Now — what kills CVs. Let me go through the big ones.
HOST_B: Typos. Obviously. But people still do it. Spell check is not enough. Read it out loud. Have someone else read it.
HOST_A: Generic objective statements. We talked about those. Cut them or replace them with a real summary.
HOST_B: Job-hopping without explanation. If you have three roles in two years, that's a red flag unless you explain it. Contract roles, restructuring, company closure — legitimate reasons. But you need to name them.
HOST_A: Gaps without context. A six-month gap is fine. A gap you don't explain is concerning. "Career break — travel and personal development" is better than silence.
HOST_B: Skills sections that are just buzzwords. "Microsoft Office, communication, teamwork, leadership." That's filler. If you have a skills section, make it specific and relevant. Programming languages. Tools. Methodologies.
HOST_A: Alright. Let's get into the contrarian section. The stuff that most career advice gets completely wrong.
HOST_B: This is my favourite part. Starting with the passion myth.
HOST_A: "Follow your passion." It's the most common career advice in the world and I think it's genuinely harmful.
HOST_B: The research doesn't support it. Cal Newport wrote a whole book about this — "So Good They Can't Ignore You" — and his argument is that passion doesn't precede mastery. It follows it.
HOST_A: Meaning: you don't find your passion and then get good at it. You get really good at something rare and valuable, and the passion grows from the mastery, the autonomy, and the recognition that comes with it.
HOST_B: Telling someone to "follow their passion" when they're twenty-three and have never worked in anything is advice that can only lead to paralysis. Most people don't know what they're passionate about until they've done things.
HOST_A: So instead of asking "what am I passionate about?" — ask "what skills would be genuinely valuable in the market, that I could get really good at, that overlap with things I find somewhat interesting?"
HOST_B: That's a much more actionable question. And the passion tends to emerge as you develop the skill.
HOST_A: Next contrarian point: the interview preparation paradox. Most people prepare for interviews by memorising answers to common questions. "Tell me about a time you showed leadership." And they've got a script.
HOST_B: And that's exactly wrong. Interviewers don't hire the person with the best answers. They hire the person they want to work with. The interview is a social audition, not a quiz.
HOST_A: I've hired people whose technical answers were not the strongest but who I immediately trusted, liked, and thought could navigate ambiguity. And I've passed on people with perfect STAR answers who felt robotic.
HOST_B: The preparation should be for a conversation, not for a performance. Know your stories well enough that you can tell them naturally, in different ways, in response to different questions. Not recite them.
HOST_A: Active listening in an interview is probably the most underrated skill. Most candidates are so focused on what they're going to say next that they barely hear the question.
HOST_B: And interviewers notice that. They feel like they're talking to someone who's not really there.
HOST_A: Another contrarian take: credentials matter much less than people think. Once you're past a certain threshold — once you've established that you're broadly competent for a role — adding more certifications, more degrees, more titles rarely changes the outcome.
HOST_B: Beyond a threshold, the best-qualified candidate on paper almost never gets the job. The hiring decision is made on interpersonal fit, narrative coherence, and confidence.
HOST_A: Narrative coherence is interesting. Your career needs to make sense as a story. The hiring manager needs to be able to follow a thread. Why did you go from X to Y? Why does this role make sense as your next move?
HOST_B: If you can tell that story clearly and compellingly, you're ahead of ninety percent of candidates regardless of your credentials.
HOST_A: The "culture fit" excuse is one that deserves a hard look. It's used legitimately — genuinely ensuring someone will thrive in a particular environment. But it's also used as cover for homophily — hiring people who look and think like the existing team.
HOST_B: If you get rejected for culture fit without any clear explanation, it may not be about you at all. It may be about a team that's not ready to diversify its thinking.
HOST_A: And as a candidate, "culture fit" should be a two-way evaluation. You should be assessing whether you fit the culture too. Ask specifically: what does culture fit mean to you? What kind of people thrive here? What kind of people have left?
HOST_B: Those questions tell you a lot. If the interviewer can't answer them, that's information.
HOST_A: And salary negotiation. This one I feel strongly about. Almost nobody negotiates. Almost everybody should.
HOST_B: The data is clear: the vast majority of employers make an initial offer that is not their ceiling. They expect some negotiation. When you accept without negotiating, you often leave five, ten, fifteen percent on the table.
HOST_A: And the fear of seeming greedy or jeopardising the offer — it almost never plays out that way. A company that retracts an offer because you asked a polite question about compensation is a company you don't want to work for.
HOST_B: The script is simple: "I'm really excited about this role and I'm confident I can contribute significantly. Based on my research and experience, I was hoping for something closer to X. Is there flexibility on the compensation?"
HOST_A: That's not aggressive. That's professional. And it almost always results in at least a conversation, often an improved offer.
HOST_B: Even if you can't move the base salary, you can often negotiate on sign-on bonus, equity, additional vacation days, remote working flexibility, or training budgets.
HOST_A: There are more levers than just base salary. Know what you want before you get to that conversation.
HOST_B: Alright, let's go deep on interviews. Because this is where the job is won or lost and there's so much more to it than people realise.
HOST_A: Let's start with before the interview. The prep.
HOST_B: Research. Real research. Not just reading the company's home page. Look at their annual report if they have one — or their last funding announcement if they're a startup. Read recent news articles. Look at their product or service as a user if you can.
HOST_A: Look up everyone you're meeting on LinkedIn before the conversation. Know what they've worked on. Know if they've written anything. You can reference it in the interview naturally — "I saw you wrote about X last year, I found that really interesting."
HOST_B: That level of preparation signals genuine interest. And genuine interest is the single most powerful thing you can bring to an interview.
HOST_A: Prepare five questions that demonstrate you've thought deeply. Not "what does the company do" — the answer to that is on the website. Questions like: "You're expanding into a new segment — how are you thinking about the go-to-market?" or "What's the biggest challenge the team has faced in the last year?"
HOST_B: Questions that show you've done homework and that you're thinking about actually doing the job, not just getting it.
HOST_A: Prepare your stories with the STAR method. Situation, Task, Action, Result. But practice telling them conversationally, not formally. And have specific numbers for the result whenever possible.
HOST_B: And prepare your "tell me about yourself." This is the most common opening question in every interview and it's surprisingly easy to get wrong.
HOST_A: The ideal answer is two to three minutes. It's broadly chronological. It starts somewhere meaningful — not birth — and it ends with why this role, right now. It's a setup for the rest of the conversation.
HOST_B: Practice it until you can deliver it naturally in different lengths. Sometimes you'll have five minutes. Sometimes the interviewer will cut you off at ninety seconds. Be adaptable.
HOST_A: Know your numbers before you walk in. What's your salary expectation? What's your notice period? What are you leaving behind and why? These questions will come up and fumbling them looks unprepared.
HOST_B: Now, during the interview. The first five minutes are disproportionately important. The human brain makes strong first impressions very quickly and they're hard to shift.
HOST_A: The interview starts in the lobby. The way you interact with the receptionist. Your energy when you walk in. Your body language while you wait. Some interviewers deliberately have a colleague watch how candidates treat support staff.
HOST_B: Energy is contagious. If you walk in nervous and flat, you'll pull the energy of the room down. If you walk in warm and engaged, it lifts the conversation.
HOST_A: Eye contact. Not staring — natural eye contact. In a video interview, look at the camera when you're speaking, not at your own face on the screen.
HOST_B: Listen. Actually listen. Most candidates — and I've been on both sides of this — are preparing their next answer while the interviewer is still talking. You miss things. You answer a slightly different question than what was asked.
HOST_A: Interviewers notice when you actually heard them. A good technique: when the question ends, pause for two seconds. Then answer. It feels slow to you but it looks confident and thoughtful to them.
HOST_B: Ask clarifying questions. "Before I answer — can I check what you mean by X?" or "Could you give me a bit more context on that?" This is completely fine and actually signals that you're careful and precise.
HOST_A: Address the elephant early. If there's something in your background that might look awkward — a gap, a short tenure, a career pivot — bring it up yourself before they have to ask.
HOST_B: "I know you might be wondering about the gap in 2024 — I was dealing with a family health situation, which is now resolved, and it actually clarified what I want from my next role." Confident, clear, forward-looking.
HOST_A: Much better than waiting to be cornered by the question at an awkward moment.
HOST_B: On the salary question during the interview — try to delay it if you can. "I'm still learning about the full scope of the role — can we come back to that later?" is a perfectly acceptable response.
HOST_A: The later you discuss salary, the more leverage you have — because they've already decided they like you. Early in the process, you have less information and less bargaining power.
HOST_B: If you're forced to give a number, anchor high within the reasonable range. It's much easier to come down than to come up.
HOST_A: Watch for red flags during the interview too. Remember, you're assessing them as much as they're assessing you.
HOST_B: A hiring manager who can't clearly describe what the role involves. An interviewer who's late or disorganised with no acknowledgement or apology. Anyone who speaks badly about former employees or the previous person in the role.
HOST_A: Those are signals. Vagueness about growth path — "oh we'll figure it out" — is a signal. A company that won't discuss compensation at all, at any stage, is a signal.
HOST_B: The interview is your chance to gather intelligence. Use it.
HOST_A: Let's talk about different types of interviews, because they require different preparation.
HOST_B: Competency or behavioural interviews are the most common. "Tell me about a time you..." — STAR method. Specific stories with specific results. Have at least six to eight stories ready that can flex to different questions.
HOST_A: Case interviews — common in consulting and strategy roles. These are a different beast. The trick is to structure your thinking out loud before you dive in. State your hypothesis. Ask for data. Think systematically, not intuitively.
HOST_B: The interviewer is evaluating your process, not your conclusion. If you get to the right answer through a messy approach, that's worse than getting to a reasonable answer through a clear, structured approach.
HOST_A: Technical interviews — engineering, data, finance. Same principle: think out loud. Ask clarifying questions. The interviewer wants to see how you solve problems, not just whether you know the answer.
HOST_B: If you get stuck, say so. "I'm not sure about the exact syntax here, but my approach would be..." That's so much better than silence or pretending.
HOST_A: Culture fit or values interviews. I know we talked about the dark side of culture fit, but these interviews exist and you have to navigate them.
HOST_B: Be genuine. This sounds obvious but the temptation to tell people what they want to hear is strong. If the culture genuinely doesn't match who you are, that's important information.
HOST_A: Misrepresenting yourself to get through a culture fit interview results in a job you'll hate within three months. The mismatch will emerge, and it's usually unpleasant for everyone.
HOST_B: After the interview — this is where most candidates drop the ball completely.
HOST_A: Send a thank-you email within twenty-four hours. Not a generic "thanks for your time" — something specific. "I really enjoyed our conversation about the product direction, particularly the discussion on X. It reinforced my excitement about the role."
HOST_B: Most candidates don't do this. The ones who do stand out. Full stop.
HOST_A: If you don't hear back within the timeline they gave you — follow up once. Politely. "I wanted to check in — I remain very interested and I'm happy to provide any additional information." That's it.
HOST_B: Once. Then let it go. Anything more becomes pressure, and pressure makes people uncomfortable.
HOST_A: Do a personal debrief after every interview. What went well? What felt off? What question caught you off guard? Write it down. You'll do better next time.
HOST_B: Every interview is a learning opportunity even if you don't get the role. Pattern-match over time. If you're getting to final stages but not getting offers, that tells you one thing. If you're getting rejected at the CV stage, that tells you something very different.
HOST_A: Okay. Let's talk about practical action — the so-what. Someone's listening to this and thinking "alright, I need to start my search — what do I actually do?"
HOST_B: Week one action plan. I'll make it concrete.
HOST_A: Day one: update your LinkedIn profile. Not just the current role — make sure everything is current, your summary is strong, your skills are listed, and your profile photo is professional.
HOST_B: Day two: refresh your CV. Achievements, not duties. Summary tailored to the type of role you're targeting. Clean format, no tables. Two pages max.
HOST_A: Day three and four: build your target company list. Twenty to thirty companies you'd genuinely want to work for. Research each one briefly. Understand what they do, why they're interesting to you, what kind of roles they hire for.
HOST_B: Day five: reach out to five former colleagues. Not asking for jobs. Just reconnecting. "Hey, I'm thinking about my next move, would love to hear what you've been up to, maybe grab a coffee."
HOST_A: And set up job alerts on the key platforms — LinkedIn, Indeed, and whatever is most relevant to your market. So you're not hunting every day but you see new listings when they appear.
HOST_B: The mindset piece matters enormously. Job searching is a skill. And like all skills, it improves with practice. Your first interview will be worse than your fifth. Your fifth will be better than your first.
HOST_A: Treat each application, each conversation, each interview as a data point. Not a pass or fail. What did you learn?
HOST_B: Track everything. This sounds boring but it's essential. A spreadsheet with company, role, date applied, contact name, status, notes. When you have fifteen things in flight — which you should — it gets confusing fast.
HOST_A: Without a tracking system, you'll follow up twice, or not at all, or forget the name of the person you spoke to. The tracking system is your project management tool.
HOST_B: Energy management is huge. If you're searching while employed — which is the best position to be in financially — job searching on top of a full-time job is exhausting.
HOST_A: Don't try to do it in five-minute windows throughout the day. Block specific time — maybe Tuesday and Thursday evenings, Saturday mornings. Dedicated time where you're focused.
HOST_B: The fragmented approach means nothing gets proper attention. You're half-present in your job and half-present in your search and you're doing both badly.
HOST_A: The rejection reframe. This is important. Rejection is a normal part of the process. Almost everyone who has ever found a great job has also been rejected many, many times.
HOST_B: Every rejection is data. If you're being rejected at the CV stage — look at your CV. If you're being rejected after first interviews — look at your interview preparation and your story. If you're reaching final stages and not getting offers — think about what's happening in those late conversations.
HOST_A: Pattern-matching over rejections is more useful than spiralling over any individual one. One rejection tells you almost nothing. Ten rejections is a pattern with information.
HOST_B: And sometimes the rejection is about factors entirely outside your control. The role was filled internally. The budget was cut. They promoted someone. None of that is about you.
HOST_A: Okay. Let's synthesise. We've covered a lot of ground. Where do we each land?
HOST_B: I'll go first. My big take is that the job search is essentially a product launch. You are the product. The hiring manager is the customer. And the principles of good marketing apply.
HOST_A: Say more.
HOST_B: You need to know your target audience — which companies, which roles, which hiring managers. You need a clear value proposition — what makes you different, what specific problems can you solve. You need multiple channels — networking, direct outreach, job boards, recruiters. And you need to iterate. Look at what's working, change what isn't.
HOST_A: That framing actually helps a lot with the emotional side too. Because a product launch that doesn't immediately succeed isn't a failure — it's a learning opportunity. You adjust the message, the targeting, the channel.
HOST_B: Exactly. You de-personalise it enough to be strategic about it while still bringing genuine human warmth to the conversations.
HOST_A: My take is a bit more personal. The networking piece is the hardest for a lot of people — especially introverts, which includes me — because it feels like asking for favours or being fake.
HOST_B: And yet it's real. The numbers are real. Seventy to eighty percent. You can't argue with that.
HOST_A: You can't. So my advice to introverts specifically is: reframe what networking means. It's not going to events and working a room. It's having one genuine conversation with one person you actually know.
HOST_B: One at a time.
HOST_A: One at a time. And the job board isn't useless — but it's a lottery. You're one of two hundred and fifty. Whereas a warm outreach conversation puts you in a completely different league.
HOST_B: On the tailoring question — I know we have a mild disagreement here. I think every application should be tailored. Full stop.
HOST_A: And I think there's a practical case for some volume when you're targeting the right tier of roles. Not blanket applying — you still need a solid base CV. But you can't spend four hours tailoring every application.
HOST_B: Twenty minutes per application. That's my line. Twenty minutes of smart tailoring moves you from generic pile to considered candidate. Four hours is too much. Twenty minutes isn't.
HOST_A: I'll take that. Twenty minutes.
HOST_B: The thing I want people to take away from this whole episode is: the job market is not a neutral meritocracy. Knowing that doesn't mean you're cynical — it means you can play it effectively.
HOST_A: Understand the system. Work the system. And don't take the broken parts of the system personally.
HOST_B: Know your worth. Negotiate. Don't accept the first thing out of desperation. A bad job taken in panic is often worse than the uncertainty of continuing to search.
HOST_A: And invest in yourself as a candidate. Your CV, your interview skills, your ability to network — these are learnable skills. You will get better. The first search is always the hardest.
HOST_B: Alright. That's a wrap on today's episode of Clawd Talks.
HOST_A: This was a big one. We covered the full arc — the statistics, the job search strategy, CVs and ATS, the contrarian takes, a deep interview guide, and the practical week-one plan.
HOST_B: If you found this useful — share it with someone who's in a search right now. It might genuinely help them.
HOST_A: We'll be back with more episodes soon. Until then — good luck out there. And remember: the job board is the slow lane. Get off it.
HOST_B: Take care, everyone.