The Careers Page Audit Checklist for 2026 (39 Signals Engineers Actually Look For)

Your careers page is the single most under-audited surface in your entire talent operation. You spent months on the marketing site. You had a design agency polish the pricing page. And then somebody in HR built the careers page out of a Greenhouse template three years ago, and nobody has touched the copy since. Meanwhile, every serious engineering candidate you want to hire spends about sixty seconds there before deciding whether you are worth another five minutes.

What follows is a 39-point checklist we use internally when we audit the careers pages of the companies we profile. It is written for hiring managers, heads of talent, and founders who want to know exactly what an experienced engineer is looking for — and exactly which small failures are quietly costing you great candidates every week.

Read it once end-to-end. Then open your own careers page in an incognito tab and score yourself honestly. If you find fewer than five things to fix this quarter, you are the exception. Everyone else has a to-do list waiting.

The five-second scan

Before we get to the checklists, understand what happens in the first five seconds. A senior engineer clicks your careers page from a recruiter email, a job board, or a link a friend sent them. Their brain runs a rapid pattern-match. If enough signals hit “this is a real engineering company,” they scroll. If enough signals hit “this is a marketing site with a jobs tab bolted on,” they close the tab.

The signals in the first five seconds are boring and mechanical. Does the page load in under two seconds, or is it stuttering behind three tracking scripts? Are the roles listed at the top actually engineering roles, or is the first section “we’re hiring in every department” with no real invitation to engineers? Is the hero image a photo of your actual team, or is it a stock photo of a laptop next to a coffee cup on a wooden desk? Stock photos of laptops are a candidate-repellent. Real faces are not.

If your careers page fails the five-second scan, none of the deeper checklists matter. Fix the top of the page first. Then work down.

The trust checklist (10 items)

Trust is the currency of your careers page. Every one of these items either builds it or leaks it.

1. Transparent compensation bands on every role. Not “competitive.” Not “based on experience.” A number range with a currency symbol. Candidates who see bands walk into the first interview trusting you materially more than candidates who had to guess.
2. Response-time expectation stated in writing. “We reply to every application within seven days” is a promise. Keep it. Candidates remember who ghosted them and who did not.
3. The full interview loop laid out publicly. Number of rounds, format of each, who they’ll meet. Mystery interview processes signal disorganization inside the company.
4. A working reply-to email for candidates. Not careers@ that bounces into a black hole. A human name, checked daily. Test it once a month by emailing yourself from an outside address.
5. No dark patterns in the ATS. No forced account creation before viewing a role. No sign-up-with-LinkedIn as the only option. No re-uploading a resume you already parsed correctly. Every extra step loses candidates.
6. Application time budget stated up front. “This application takes about eight minutes” is a courtesy. Ninety-minute applications with essay questions are hostile.
7. Honest role status. If a role has been open for six months because you cannot fill it, say so. If it is a pipeline role with no immediate hire planned, say so. Candidates find out either way.
8. Location clarity. “Remote” that actually means “US-only Pacific time zone” is a bait-and-switch. Say the real thing.
9. Visa sponsorship stance per role. Yes, no, or case-by-case. Ambiguity here wastes weeks of candidate time.
10. Real, current employees on the careers page or team page. Not stock photos. Not the founder from 2019 who left last year.

The culture-page checklist (9 items)

Your About or Culture page is where marketing usually wins and candidates usually lose. The tell is a page that reads like a mission statement rather than a description of a real place where real people work.

1. Written by a human who works there — ideally an engineer or an early employee. Culture pages written by an outside branding agency have a specific bland flavor experienced candidates smell instantly.
2. Names specific rituals, not vibes. “Every engineer runs at least one incident postmortem” is a ritual. “We believe in learning” is a vibe.
3. Has a cons section or an honest “this is who this job is not for” paragraph. Nothing builds trust like admitting the trade-offs.
4. Values evidenced with examples. If you say “we ship fast,” link to a public deploy log or a changelog. If you say “we care about craft,” link to an engineering blog post.
5. Answers the on-call question before the candidate asks. Rotation length, expected page volume, who covers holidays. This is one of the most-asked questions in interviews; answer it on the page.
6. Explains decision-making. How do disagreements get resolved? Who owns technical direction? Is there a written RFC process? Ambiguity here reads as politics.
7. Publishes the operating rhythm. Weekly all-hands, monthly demos, quarterly planning. Candidates want to picture their calendar, not decode it.
8. Is dated or updated. Culture pages last edited in 2022 are worse than no culture page at all — they scream that nobody has thought about this in years.
9. Links to real culture artifacts — a handbook, an engineering blog, a values doc. The link itself is a signal that culture is documented, not folklore.

The team-page checklist (7 items)

The team page is where candidates look to verify that the culture story matches the people. It is also the page most companies quietly hide because the reality does not match the marketing.

1. Real faces. Not silhouettes, not avatars, not “photo coming soon.” If someone is uncomfortable being on the team page, ask why before you ask a candidate to trust them.
2. Real names. Full names, not first names. Candidates look people up. That is fine. That is normal.
3. Technical role titles. “Head of Engineering” is a title. “Team Lead, Payments” is a signal. Vague titles suggest an org chart nobody has thought about.
4. Engineering leadership visible, not just the C-suite. Candidates want to see the person they would report to, not only the founder.
5. Diversity that reflects the actual team, not a curated highlight reel. Photographing the same three employees on every page is a red flag.
6. A path to reach out — an email, a Twitter handle, a “grab a coffee” link. Team pages that let candidates DM someone technical consistently outperform pages that offer only an application button.
7. Refreshed within the last quarter. A team page that still lists people who left a year ago is a broken window. Candidates notice.

The job-description checklist (8 items)

Job descriptions are where the pipeline lives or dies. Most job descriptions are copy-pasted from a template a recruiter used at their last job. Candidates can tell.

1. Specific tech stack. Not “modern JavaScript.” The actual frameworks, the database, the cloud provider, the deployment pipeline. Vagueness signals you either do not know or do not want the candidate to know.
2. A real day in the life. What does Monday morning look like? What does Friday afternoon look like? Candidates hire based on how their calendar will feel, not how the org chart looks.
3. Salary band on every role. See item 1 of the trust checklist. This one is worth repeating.
4. Interview loop summarized inside the JD, not buried in the ATS confirmation email.
5. Requirements that are actually required. Not the 15-line wish list that scares off two-thirds of qualified women and underrepresented candidates. Three to five real must-haves.
6. “Nice-to-haves” that are honestly optional, not gatekeeping in disguise. If the recruiter rejects candidates for missing them, they are requirements — move them up.
7. Success metrics for the first six months. What will this person have shipped, learned, or influenced by month six? Vague roles attract vague candidates.
8. Written by the hiring manager, not the recruiter. Hiring-manager-written JDs read differently and convert better. Every time. Read our guide to writing inclusive job descriptions for the specifics.

The engineering-blog checklist (5 items)

An engineering blog is a candidate’s fastest way to evaluate the caliber of technical work happening inside your company. It is also the surface most engineering leaders promise to invest in and then quietly abandon after two quarters.

1. A post in the last quarter. If your last engineering blog post is from ten months ago, candidates read that as “engineering is not a priority here anymore.”
2. Written by engineers, not marketing. Byline matters. “By the Acme Team” is a marketing signal. “By Priya, Staff Engineer” is a technical signal.
3. Technical substance. Real trade-offs, real code, real numbers. Not case studies and customer logos. Not thought-leadership fluff.
4. Links to open-source contributions, if any exist. Even one repository the team actively maintains is worth ten posts about culture.
5. Discoverable from the careers page. If a candidate cannot find your engineering blog from the careers page in two clicks, they will not find it. Add the link.

Anti-patterns that predict candidate ghosting

Beyond the checklists, there are specific failure modes we see over and over again. Any one of these will silently kill your top-of-funnel — and candidates will not tell you why they ghosted.

• The 30-minute application form. Long applications signal disrespect. Every field beyond resume, email, and one short question is a candidate you just lost.
• Asking for salary expectations upfront. This is a negotiation trap and every candidate knows it. Publish your band. Save both sides the game.
• “We’re a family” language. Families cannot fire each other. Companies can. This phrase reads as “we expect unpaid emotional labor” to anyone who has been burned before — which is everyone senior.
• RTO backdoor buried in the FAQ. If the role is remote at the top of the page and “three days in office quarterly” in the footnote, candidates feel tricked. Say it at the top.
• Perks stack as the top section. Snacks and pool tables at the top of the careers page tell senior engineers you do not understand what they value. Move perks below the actual work.
• The 45-day interview loop. Six rounds spread over six weeks. By the time you send an offer, the candidate has three others. Compress the loop.
• No public reference to the CTO. If the technical leader is invisible from the outside — no blog, no talks, no LinkedIn presence — candidates infer that engineering has no voice in leadership.
• Career page hero video autoplays with sound. An avoidable, disrespectful default. Fix this today.

What to do this quarter

You cannot fix everything at once. Here is the prioritized order we recommend to the hiring leaders we work with.

1. This week: add salary bands to every open role. This is the single highest-impact change and the fastest to ship. If legal pushes back, start with US roles where pay-transparency laws already require it.
2. This week: test your careers-page load time and remove any tracking script that adds more than 300ms. Speed is a trust signal.
3. Within two weeks: update the team page. Real faces, current employees, technical role titles. Delete anyone who has left.
4. Within a month: rewrite every open engineering JD with the hiring manager, using the eight-item JD checklist above. Kill the 15-item wish lists.
5. Within a month: ship one substantive engineering blog post written by an engineer. Not a marketing post. A trade-off post, a postmortem, or a decision log. Then commit to one per month.
6. Within the quarter: compress your interview loop by at least one round. Every extra week costs you candidates.
7. Within the quarter: publish your interview process, response-time promise, and on-call expectations directly on the careers page. Stop making candidates ask.
8. Ongoing: get profiled somewhere candidates already look. Third-party culture data outperforms your own careers page for one simple reason — you did not write it. Read our companion pieces on employer branding and attracting senior engineers for the full playbook.

None of this is expensive. None of it requires a new hire or a rebrand or a consultant. It requires an afternoon with a red pen and the willingness to see your careers page the way a stranger sees it in five seconds.

Do the audit. Ship the fixes. Watch what happens to your response rates.