Why you are getting rejected: What recruiters actually see in your candidacy.
The feedback you get when a firm rejects you is usually polished, generic, and legally cautious. "We have decided to move forward with another candidate." Sometimes there is a line about fit or alignment. Rarely is there a specific reason you can act on.
This post is the candid version of what hiring managers and recruiters actually see when they decide to pass. It is not flattering, but it is specific, and specific is useful.
Why the feedback you get is so generic
Hiring managers are trained, correctly, to be careful about rejection feedback. Detailed feedback can create legal exposure. It can also create a protracted back-and-forth with a candidate who wants to re-argue the decision.
Recruiters, internal or external, often have better feedback to share but limited permission to share it. The candidate is not their client; the firm is. The recruiter's incentive is to preserve the relationship with the firm, which sometimes means delivering a softer version of the feedback than the candidate would get in a direct conversation.
None of that changes the reality of why candidates actually get passed over. Here are the five most common reasons, in rough order.
1. The resume does not match the specific thing the posting asked for
This is the most common and the most fixable. The posting asks for "10 years of experience in healthcare project delivery, with Ontario hospital projects preferred." Your resume shows 12 years of mixed project experience, including some healthcare, but the healthcare projects are not named or dated. The hiring manager reads your resume in 45 seconds and does not find what they were looking for.
You may be more qualified than the candidate who got the interview. You did not make that legibility easy for the reader. In an inbox of 150 applications, legibility is the filter.
Fix: tailor your resume to the specific posting. Name the projects that match the posting's criteria. Put those projects at the top. Cut or compress the projects that do not match. If the posting asks for specific software, credentials, or project typologies, reflect that language back in your resume.
2. The portfolio or work sample does not support the resume
This applies to architecture, design, and increasingly to engineering and digital practice roles where portfolios are becoming standard. The resume says you led a healthcare project. The portfolio shows three competition projects from school and two interior fit-outs.
When the portfolio and resume tell different stories, the reader assumes the portfolio is closer to the truth. If you have done strong work that is under NDA or hard to show, say so explicitly in the portfolio or cover letter. Do not leave the reader to wonder.
Fix: treat the portfolio as the proof document. Every claim on the resume that can be shown in the portfolio should be shown there. If it cannot be shown, address the gap in the cover letter.
3. The interview signals that something is off
The most common interview-stage reasons for rejection are not technical. They are signals about how the candidate will operate in the job.
Insufficient preparation. A candidate who cannot describe the firm's recent work, has not read the posting carefully, or has no specific questions about the role signals a lack of interest. In a competitive pool, this is often enough to eliminate.
Over-polished answers. Responses that feel rehearsed or that answer the generic version of the question instead of the specific one being asked. Hiring managers notice when a candidate is talking at them rather than with them.
Missing curiosity. A candidate who answers questions but does not ask them, or asks only transactional questions about salary and hours, signals a narrow interest in the work itself.
Difficulty with specifics. When asked for a concrete example of a specific situation and the candidate stays at the general level or cannot produce one, the hiring manager loses confidence in the resume claims.
Fix: prepare specifically. Research the firm. Read their recent projects. Come with three or four questions about the specific role, team, and projects. Rehearse specific examples for the common competency questions (a challenging project, a conflict with a team member, a mistake you learned from).
4. The cultural fit question. And what it actually means.
"Fit" is a word that does a lot of work in hiring conversations, most of it unstated. What it usually means in AEC firms:
Can this person operate in our review culture? Some firms have intense studio critiques. Others are more private and written. Candidates who do not thrive in the firm's feedback culture often do not last, and hiring managers try to screen for this.
Can this person handle the pace and stakes? A candidate who has done great work at a firm known for 40-hour weeks and long timelines may struggle at a firm running project deadlines every two weeks, and vice versa.
Is this person going to work well with the specific team? Hiring managers often have a very clear picture of the team dynamic they are adding to, and they are looking for someone who will improve that dynamic, not disrupt it.
Fit is not a code word for something else, most of the time. It is real, and it is legitimate, and it is often the reason you are passed over even when the technical fit is strong.
Fix: research the firm's culture before the interview. Ask specific questions about how feedback is given, how teams are structured, and what a typical week looks like. If the fit is not there, recognize it. You do not want to be hired into a firm where the fit is not right.
5. Timing
Sometimes you are rejected because someone else was slightly stronger, or started their process earlier, or was available to start two weeks sooner. This is not something you could have controlled, and it is the reason that so many rejections come with no useful feedback. There is no lesson to offer.
This is also why applying early in the posting window matters. By day 20, the shortlist is usually set. Your application, however strong, is competing for second choice.
What to do with the pattern
If you have been rejected from three or four roles in a row, the pattern usually points to one or two of the issues above. Three diagnostic questions to ask yourself.
First, are you getting interviews? If you are applying and not getting interviews, the issue is resume match and legibility, not interview performance. Fix the top of the funnel before worrying about the rest.
Second, are you getting to final rounds and losing? If you are reaching finals and being passed over, the issue is often the fit question or very close technical calls. Ask a recruiter you trust for a candid read.
Third, is there a category of firm you keep interviewing at and not getting offers from? That usually signals a specific fit or culture mismatch. The firms where you get further in the process are usually the ones where the real fit exists.
Most rejections are not about you alone. They are about you relative to a specific posting, at a specific firm, at a specific moment. The pattern across rejections is more useful than any single one of them.
Sources
Axis Recruitment internal placement and candidate data, 2024 to 2026.
Axis Recruitment, "Why you are not getting responses to AEC applications."
Axis Recruitment, "The candidate experience: Why it's the most important part of the hiring process." https://www.axisrecruitment.ca/blog/the-candidate-experience-why-its-the-most-important-part-of-the-hiring-process
