Picture yourself pressing Submit on an application for a role you really want. In your head, the CV now lands on one desk, one person reads it from top to bottom, and that person says yes or no. If the answer is silence, the verdict must have been no.
That picture is understandable, but it’s also wrong in a way that matters. If you believe one person makes one decision, you’ll write one document for one imagined reader. In reality, several people read your application, and each makes a small decision with limited time.
Several Readers, Several Decisions
Hiring processes vary a lot across companies, countries, and roles. A forty-person startup might have the founder read every application, while a large bank might add a few extra rounds. The overall process, however, is usually similar:
- Application or referral: Your CV arrives through a form, a job board, or a person who knows you.
- Recruiter screen: A recruiter checks the basics. Does your recent experience match the role? Are you in the right location? Can you explain yourself clearly in a short call? At larger employers, software increasingly helps with this step. It may rank applications before a recruiter looks at them, and some companies now run the first interview with an AI agent.
- Hiring manager: The person who’ll lead the team looks for what you actually built or did and at what scale.
- Assessment and interviews: Through a practical task, a technical round, or conversations with the team, people probe whether your stories hold up.
- Offer: Someone weighs everything and makes the call.
Each stage has a different reader. The recruiter may not have an engineering background, while the engineering lead who reads your application an hour later wants depth. You tell the same story to both, tailored to each. That’s why the rest of this course keeps asking who’s reading this and what they’re deciding.
Many employers also train interviewers to ask every candidate the same questions and score the answers against agreed criteria. The US Office of Personnel Management’s page on structured interviews shows what that looks like from the employer’s side.
The Two Questions Every Reader Asks
Despite all this variation, every reader asks two questions:
- Can this person do this job?
- Will it work out here?
The first question, about skills, projects, and experience, is the one most people prepare for. People often dismiss the second as fluff, but the answer provides real evidence too.
Imagine two candidates with the same SQL and Python skills. One writes, “I’m applying because I want a job in data.” The other writes, “Your team publishes the city’s transport data. I spent eight years explaining numbers to teenagers, and now I want to explain them to commuters.” Which one would you call first?
Your motivation, how you communicate, and a believable reason for wanting this particular role all answer the second question. A typo in your email answers it too, just not in your favor!
What an ATS Really Does
You may have heard the claim that an applicant tracking system (ATS) silently rejects most applications before a human ever sees them. The precise-sounding percentage often attached to that claim traces back to a vendor’s sales pitch, and no research backs it up.
An ATS is mostly the filing cabinet and search box that recruiters use. Automatic rejections usually come from knockout questions the employer set up, such as questions about work authorization or location.
What has changed is ranking. Many systems now use AI to score applications against the posting and sort the pile. When a single role draws a couple of hundred applications, a recruiter may only read the top of that list. So software rarely says no to you outright, but it can decide whether a person gets to your application at all. You’ll take a closer look at what an ATS does with your CV in How a CV Gets Read.
Silence Isn’t a Verdict
That brings you back to waiting for a reply. Say you’ve applied to twenty roles and heard nothing back. It’s tempting to blame a robot, but the explanation is usually more ordinary.
More likely, a recruiter didn’t see a match for the role, the employer filled it or paused hiring, or so many applications came in that no one got to yours. When software ranks the pile, a weak match with the posting makes that more likely. Roles go quiet for many reasons that have nothing to do with you. Maybe an internal candidate got the job, the budget froze, or a hundred people applied in two days.
You can control how relevant your application is to the posting, how readable its layout is, and how you approach people for a way in. Silence after one application tells you almost nothing about your worth. For one developer’s firsthand account of a search, listen to Python Job Hunting in a Pandemic on the Real Python Podcast.
You can learn from patterns. Across many applications, which ones were close matches? Which were tailored? Which came through a person? You’ll set up a way to track those patterns near the end of the course.
There’s one more thing to notice. A referral changes who reads your application first and what they already believe about you. You’ll come back to that in the Get Noticed section.
Try It: Annotate a Real Process
Grab a pen and paper and find one posting that interests you. Many postings or careers pages describe the hiring process. Sketch the stages as boxes, and next to each one, write who you’ll meet and what that person is deciding. Then sort a few signals under the two questions, such as a relevant project, a referral, a thoughtful question about the team, a career gap explained in a line.
If the posting doesn’t describe the hiring process, sketch the typical stages above and mark where you’re unsure. You’ll get better at reading postings in the next lesson, where you’ll choose your target role and map what employers actually ask for.
