A Senior Backend Developer applies to a company they’ve heard good things about. Sends CV. One week - silence. Two weeks - silence. After three weeks an email: invitation to screening call. Conversation goes well. “We’ll get back to you by end of week.” Week passes. Two weeks. Sends follow-up. Silence. After a month an automated email: “Thank you for your interest, but we’ve decided on another candidate.” Zero feedback, zero respect for invested time.
Developer talks to friends: “Don’t even bother with that company.” Glassdoor review: 2/5 for “interview experience.” Next 10 potential candidates see the review and don’t apply. Company complains: “We can’t find people, market is tough.”
It’s not the market that’s tough - it’s the recruitment process that’s bad. In IT, where specialists have choices, candidate experience is competitive advantage or competitive disadvantage. Every candidate you treat poorly is potentially dozens more who will never apply.
Why does candidate experience matter more than ever?
“87% of companies worldwide report that they either already have a skills gap or expect to have one within the next few years.”
— McKinsey & Company, Closing the IT Skills Gap | Source
Supply and demand. Demand for IT specialists exceeds supply. Candidates choose where to apply and with whom to continue. They have options. Bad experience = they go to competition.
Word of mouth in IT community. Developers talk. On Slack, Discord, conferences, meetups. “How did it go at company X?” - “Terrible, 5 rounds and ghosted at the end.” Information spreads.
Glassdoor, Blind, Teamblind. Public reviews of recruitment process. One bad review stays for years. Future candidates read before applying.
Employer branding is fragile. Years of building reputation can be destroyed by a series of bad recruitment experiences. Even the best company can have a reputation as “a place hard to get into and not worth trying.”
Rejected candidates are potential clients, partners, referrals. The Senior Developer you didn’t hire - in 2 years might be a decision maker choosing vendors. They remember how you treated them.
Cost of bad experience is measurable. Lost hires, extended time-to-fill, higher agency fees, damaged brand. Hard to measure precisely, but real.
What frustrates IT candidates most in recruitment processes?
Ghosting - no response at all. Candidate applies, spends time preparing, customizing CV - and silence. Not even an automated “we received your CV.” Basic lack of respect.
Unrealistic timeline promises. “We’ll get back to you this week” - and silence for a month. Better to say “process takes 3-4 weeks” and deliver than promise fast and fail.
Too many interview rounds. 5-6 interview rounds is standard at Big Tech, but smaller companies copy without reason. Each round is candidate’s time. Respect it.
Unpaid homework requiring days of work. “Build a complete CRUD application with authentication and AWS deployment. Deadline: weekend.” This is work that should be paid for, not a free demo.
No feedback after rejection. “We decided on another candidate” - and zero information why. Candidate doesn’t know what to improve, feels ignored.
Organizational chaos. Interview with 3 different people, each asking the same things. Hiring manager didn’t read CV. Recruiter doesn’t know role details. Sign the company is chaotic.
Outdated job descriptions. Apply for “Backend Developer,” turns out they’re looking for someone who’ll also do frontend, DevOps, and support. Bait and switch.
How to measure candidate experience at your company?
Candidate NPS (Net Promoter Score). After process ends (hired or rejected) - short survey: “How likely are you to recommend others apply to us?” (0-10). Promoters (9-10) minus Detractors (0-6) = NPS.
Post-interview surveys. Automatic survey after each round: “How do you rate today’s interview?” Quick feedback allows quick corrections.
Time-based metrics. Time to first response (after application). Time between stages. Total process duration. Long times = bad experience.
Drop-off rates. How many candidates withdraw between stages? High drop-off after technical task might mean the task is inadequate.
Glassdoor/Blind monitoring. Regularly check what candidates write about the process. Respond to negative reviews (public response shows you care).
Hiring manager feedback. Ask hiring managers: “How do you rate candidates from last week?” - if they say “weak candidates” and candidates say “bad process” - the problem is the process.
Offer acceptance rate. How many people who received offers accepted them? Low acceptance rate = something is wrong (maybe offer, maybe process experience).
How to shorten and streamline recruitment without lowering quality?
Define real requirements. Not “nice to have,” only “must have.” The more precise - the faster screening and less wasted time (candidate’s and yours).
Consolidated interview rounds. Instead of 5 separate interviews - panel interview with 2-3 people at once. Candidate says the same thing once, not five times.
Homework alternatives. Instead of 10-hour homework - 1-2 hour pair programming session on-site (or remote). Or code review of existing code. Or discussion of past projects.
Pay for longer tasks. If you really need a 4+ hour task - pay for candidate’s time. 300-500 PLN shows respect and filters those who aren’t serious.
Parallel processing. Technical interview and culture fit can be same day (with break). Don’t stretch across 3 separate meetings in 3 different weeks.
Decision SLAs. Internal commitment: decision after each stage within 48h. If hiring manager can’t decide - escalation.
Empower recruiters. Recruiter should be able to reject obvious mismatches without involving hiring manager in every case. Faster “no” is better than weeks of waiting.
How to improve communication with candidates?
Auto-acknowledgment immediately. Candidate applies - within minutes (not days) receives: “We received your CV, we’ll review within X days.”
Proactive updates. If process is delayed - say so. “Sorry, decision maker is on vacation, we’ll get back after January 15” is 100x better than silence.
Clear timeline upfront. On first call: “Our process is 3 stages, usually takes 2-3 weeks. Next step is X, we’ll let you know by Friday.”
Single point of contact. One recruiter who knows the candidate’s case and answers questions. Not “write to careers@” where nobody responds.
Human rejection emails. Not “after careful consideration we’ve decided…” Template is ok but should sound human and give reason (general) for rejection.
Close the loop always. Every candidate who entered the process (even one call) gets information about outcome. Zero ghosting.
How to give feedback to rejected candidates?
Why feedback matters. Candidate invested time. They want to know what they can improve. Professional feedback builds respect for company even with rejection.
General vs. specific feedback. For screening: general (“we’re looking for more experience in X”). For later stages: more specific (“in technical task, edge case handling was missing”).
Legal considerations. Some companies fear feedback “because they’ll sue for discrimination.” In practice: objective, merit-based feedback based on job-related criteria is safe. Avoid comments about personality, appearance, protected characteristics.
Template with personalization. Have template rejection email, but add 2-3 sentences specific to candidate. “We appreciated your Kubernetes experience, however we were looking for someone with stronger security background.”
Verbal feedback for final stages. Candidate who reached final round deserves a phone call, not email. 10 minutes of conversation with specific feedback.
Open door for future. “Your skills are interesting, but right now we’re looking for X. We invite you to apply for future roles.” - don’t burn bridges.
How to design recruitment tasks that don’t repel candidates?
Respect candidate’s time. Maximum 2-4 hours for homework. Beyond that - either pay, or replace with live session.
Realistic but scoped. Task should show real skills, but be well-defined. “Build API endpoint for X with tests” - ok. “Build complete system Y” - too much.
Clear expectations. Instructions: what’s being evaluated, how long it should take, what stack, can they use libraries, when’s deadline. No ambiguity.
Sample solutions. After process ends - show candidate example solution. They learn even from rejection.
Take-home alternatives. Not every candidate can dedicate a weekend to task (children, other job, care responsibilities). Offer alternative: paid live coding, portfolio review, past project discussion.
Review with care. If you ask candidate for 4 hours of work - spend 30 minutes on proper review and feedback. Not 5 minutes of cursory glance.
No spec work. Task shouldn’t be a real project the company will use. That’s unethical and candidates recognize it.
How to ensure interviewer professionalism?
Interview training. Not every good developer is a good interviewer. Training: how to conduct interview, what questions to ask, how to evaluate, what to avoid (illegal questions).
Structured interviews. Defined set of questions, evaluation rubric. Less “gut feeling,” more objectivity. Also easier to compare candidates.
Preparation requirement. Interviewer MUST read CV before interview. “Sorry, just looking at your CV” - disqualifies company in candidate’s eyes.
Punctuality. Interview at 2:00 PM starts at 2:00 PM, not 2:15 PM. Being late is disrespectful. If something urgent - apologize and reschedule.
Post-interview huddle. After interview - immediately write down evaluation and notes. Not a week later when everything blurs.
Accountability. If interviewer gives bad candidate experience (feedback from surveys) - coaching. Persistent offenders don’t conduct interviews.
How does candidate experience differ for remote vs. onsite?
Remote interviews have specific challenges. Technical issues (Zoom doesn’t work, audio cuts out). “Can you see my screen?” - 5 minutes troubleshooting. Awkward silences. Difficult to read body language.
Remote interview best practices:
- Test setup before interview (camera, audio, screen share)
- Backup plan if Zoom fails (phone, Google Meet)
- Give candidate extra buffer time for technical issues
- Be explicit about who speaks when (harder without physical cues)
- Shorter sessions (Zoom fatigue is real)
Onsite experience. Candidate comes to office - what do they see? Does reception know they’re expected? Do they have somewhere to sit? Did someone greet them? Small details build impression.
Hybrid option. Give candidate choice: “Do you prefer remote or coming to office?” Flexibility is positively received.
Virtual office tour. For remote - show candidate the office via camera, introduce future team (even via video). Humanizes the process.
How to measure and iterate on candidate experience?
Data collection. After every completed process - survey. Short, 3-5 questions. Rating + open comment. Automation via ATS.
Regular review. Monthly or quarterly - review feedback. Patterns? Recurring complaints? Specific stages with low scores?
A/B testing process changes. Want to shorten homework from 6h to 3h? Test on subset of candidates, compare: completion rate, quality of submissions, candidate feedback.
Benchmarking. How does your process compare to market? How many interview rounds is standard for this role? Competitive intelligence.
Continuous improvement mindset. Candidate experience isn’t a project “to be done” but ongoing process. Market changes, expectations rise.
Celebrate wins. When candidate NPS rises, when time-to-fill drops, when accepted offer rate rises - celebrate with team. Shows that metrics matter.
Table: Candidate experience audit checklist
| Process Stage | Element to Check | Good Practice | Red Flag | Action if Red Flag |
|---|---|---|---|---|
| Application | Auto-acknowledgment | Within 24h, personalized | None or > 3 days | Configure auto-response in ATS |
| Application | Clear job description | Specific requirements, salary range | Vague, no salary, “wear many hats” | Rewrite with hiring manager |
| Screening | Response time | < 5 business days | > 2 weeks | Dedicate recruiter time, set SLA |
| Screening | Recruiter knowledge | Knows role, team, tech stack | Reads from script, doesn’t know details | Brief before call, documentation |
| Technical interview | Interviewer preparation | Read CV, prepared questions | ”Tell me about yourself” without context | Interview training, accountability |
| Technical interview | Interview duration | 45-60 min with time for candidate questions | 2h+ marathon | Redesign interview structure |
| Take-home task | Time requirement | 2-4h, clear instructions | 10h+, vague specs | Shorten or replace with live session |
| Take-home task | Feedback on submission | Specific feedback | ”Didn’t pass” without explanation | Process change: reviewer writes feedback |
| Offer stage | Time to offer | < 1 week from last interview | > 3 weeks | Decision SLA, escalation process |
| Offer stage | Offer clarity | Written, complete (salary, benefits, start date) | Verbal only, missing details | Template offer letter |
| Rejection | Communication | Personal email/call with feedback | Ghost or generic template only | Train recruiters, accountability |
| Throughout | Updates | Proactive info when delays | Silence for weeks | Communication SLAs, candidate portal |
Candidate experience isn’t a “soft” topic - it’s business advantage. In competitive IT market, companies that treat candidates with respect win talent wars. Those that ghost, drag out processes, and ignore feedback - lose.
Key takeaways:
- Ghosting is unacceptable - every candidate deserves a response
- Timeline promises must be kept - or proactively communicate delays
- Respect candidate’s time - shorter processes, pay for long tasks
- Feedback is valued - even brief, constructive comment on rejection
- Measure and iterate - candidate NPS, surveys, drop-off rates show truth
- Interviewers represent company - training and accountability are necessary
- Word of mouth works both ways - good experience is marketing, bad is anti-marketing
Investment in candidate experience pays back in: better candidates, shorter time-to-fill, higher acceptance rate, and stronger employer brand.
ARDURA Consulting provides IT recruitment services with emphasis on positive candidate experience. Our recruiters are trained in professional communication, we keep timeline commitments, and give every candidate feedback. Let’s talk about recruitment that builds your company’s reputation.