--- title: "What Developers Love and Hate About Your Hiring Process | CoderPad" description: "Seasoned recruiters and developers share insights on the candidate experience and reveal what programmers love vs. what they hate about the technical hiring process." canonical: "https://coderpad.io/blog/hiring-developers/what-developers-love-and-hate-about-your-hiring-process/" last_modified: "2026-04-15 16:20:40" --- [Back to blog](https://coderpad.io/blog/) # What Developers Love and Hate About Your Hiring Process September 21, 2023 5 Minute Read By Nathalie Figuière [Hiring Developers](https://coderpad.io/blog/hiring-developers/) The technical hiring process can be a source of frustration and disappointment for both candidates and recruiters. We recently hosted a [tech recruitment roundtable](https://coderpad.io/events/candidate-experience-what-developers-hate-most-about-the-hiring-process-what-recruiters-should-do-instead/), where experienced software engineers and recruitment professionals shed light on what developers dislike about the hiring process vs. what they value and expect. Here are some of the key takeaways: ## What developers dislike about the hiring process 💔 ### 1. Overemphasis on automation While automation can streamline initial assessments, it shouldn’t come at the cost of human interaction during the hiring process. As [Gerardo Tobar](https://www.linkedin.com/in/gerardo-tobar/?originalSubdomain=sv), Sr. Talent Acquisition Leader at Telus, points out, “There’s a very fine line between attracting a candidate and pushing them away.” Developers appreciate personal communication with recruiters and companies rather than being subjected to an immediate barrage of automated screening. ### 2. Excessive assessments Many developers get frustrated with lengthy and complex coding assessments, especially as the initial step in the hiring process. Developers prefer [coding challenges that are relevant](https://coderpad.io/platform/technical-screening/), reasonable in scope, and align with the actual job requirements. ### 3. Vague job descriptions Vague, generic or overly extensive job descriptions can be a major turn-off for developers. [Pablo Portillo](https://www.linkedin.com/in/pablo-portillo/), Google Cloud Specialist at Telus, encourages companies to be clear and specific about responsibilities and technical requirements. He points out that “all-in-one” roles with long “laundry lists” of responsibilities often reflect a lack of clear expectations and internal alignment. > “I’ve seen these “all-in-one” roles that combine skills for DBA, full-stack, network, DevOps… all in one single profile, and that for me is a red flag. It means that there is no clear expectation for the candidate and the role.” – Pablo Portillo, Google Cloud Specialist at Telus [Louis Coulon](https://www.linkedin.com/in/louiscoulon/), co-founder of [CleverConnect](https://www.cleverconnect.com/), also warns against “fake”, generic job ads. In his experience, certain companies with regular needs for tech profiles permanently advertise generic, open roles for software developers, in an attempt to fuel their talent pool and save time. This is mis-leading for candidates and can lead to frustration. ### 4. Ghosting candidates Leaving candidates in the dark about their application status is a common source of frustration. > “When I was looking for my first role, I went through a very long interview process. It took about eight interviews. It consisted of two initial, “get-to-know-you” interviews […] and then we transitioned into four different live coding interviews […] and then it ended with another two interviews where I met members of the team. I was finally told to wait for about a week to get a response and to see if I was a fit for the company. A week went by, I sent a follow-up email, got no response. A month went by… nothing.” – [Ricardo Tovar](https://www.linkedin.com/in/j-ricardo-tovar/), Software Engineer and candidate Providing timely feedback or updates, even if it’s a rejection, can greatly improve the candidate experience and improve your chances of returning candidates. ## What developers value and expect in the hiring process ❤️ ### 1. Clear, upfront communication The consensus among developers is that clear and open communication is crucial throughout the hiring process. This includes explaining the process upfront, setting expectations, and maintaining ongoing dialogue with candidates. > “Developers really appreciate getting an overview of the whole interview process, from the get go. I like to be aware of how many rounds there’s going to be, and a rough timeline. When is the company looking to hire by? What kind of coding challenges am I going to be doing? It’s hard to come in and be put on the spot with no context around what you’re doing and the aim of the exercise […] Just give us a little time to prepare mentally.” – Ricardo Tovar, Software Engineer and candidate ### 2. Transparency Developers appreciate transparency regarding job details such as remote work options, salary, and benefits. It’s essential to be upfront about what your company can offer to align candidate expectations with reality. In fact, it’s counterproductive to try and entice candidates with false or misleading claims. Does your company allow full remote? Say so. Does your company expect employees to travel to the office on Mondays, Tuesdays and Wednesdays? Also say so. > “Be honest, answer those questions. Even if they’re hard questions. ‘Is this a remote job?’, ‘No, you’ll have to come on-site’. That’s fine. It is what it is. There’s a job for everybody, a position for everybody, you just have to find the correct person for the correct slot.” – Gerardo Tobar, Sr. Talent Acquisition Leader at Telus ### 3. Feedback Providing constructive feedback, even in rejection, can greatly benefit candidates. Ricardo highlights that candidates appreciate “personalized feedback on what they did well and what they did wrong.” It helps them improve and understand where they stand. If you’re dealing with a high volume of candidates and have limited resources, it may not be feasible to offer feedback to every applicant. Louis offers his recommendation: > “I think a best practice is to go for the ‘in-bewteen’. To say ‘Sorry, we’ve decided not to move forward with you. If you want us to go through the reasons behind our decision, feel free to reach out’, rather than sending over a detailed, personalized email. That way, you make sure that you spend that time with those, maybe 20% of candidates, that actually want to discuss it. And the others still get a good impression, since you offered.” – Louis Coulon, co-founder of CleverConnect ### 4. Information on coding challenges Before a coding interview, developers value information about the coding challenges they will face. What can you tell them about the question format? The technologies? The evaluation criteria? The duration? Any information you can share in advance will help candidates prepare and feel more at ease during the assessment. However, do make sure to communicate the same information to every candidate (with an interview prep template, for example), so as to keep a level playing field. If you can include a tutorial or a [sandbox](https://app.coderpad.io/sandbox?_ga=2.255180808.1482311545.1695028281-269016500.1678177444&_gl=1*h0zxup*_ga*MjY5MDE2NTAwLjE2NzgxNzc0NDQ.*_ga_XBQ5N5CE2N*MTY5NTMwMDAyMy4zMTcuMS4xNjk1MzAwOTE2LjU3LjAuMA..*_gcl_au*NDY1NjYyMTg2LjE2OTI2MDYwNDI.), even better. This allows developers to get their bearings, take a look at the IDE and get a feel for the user experience. ### 5. Awareness of AI tools With the rise of AI tools like ChatGPT, and their increased presence in interviews, developers appreciate transparency regarding use in the hiring process. Candidates should be informed if, when and how they are expected, allowed or encouraged to utilize such tools during assessments. > 🔖 Related read: [How Interviewers Are Leveraging ChatGPT to Hire Developers](https://coderpad.io/blog/interviewing/how-interviewers-are-leveraging-chatgpt-to-hire-developers/) In tech recruitment, clarity, communication, and empathy go a long way. By embracing these values, recruiters can enhance the candidate journey and hire top tech talent. Pablo urges recruiters to keep in mind that “people are investing their lives, their time in your process, so keep communication two-way.” ## Subscribe for more CoderPad insights ## Trending Articles Previous slide Next slide [Hiring Developers ## 5 Reasons Why Developers Are Ghosting You & How to Avoid It Discover the top 5 reasons why developers may ghost you and learn practical tips to avoid it. Stay ahead in the game by understanding the key challenges faced by developers and take proactive measures to build long-lasting relationships. Read the post](https://coderpad.io/blog/hiring-developers/candidate-experience-ghosted-by-developers/) [Hiring Developers ## 5 Ways to Strengthen Collaboration Between Talent Acquisition and Engineering Hiring Managers Alignment between talent acquisition and engineering managers is essential for hiring top developer talent. Read expert insights on how to improve collaboration. Read the post](https://coderpad.io/blog/hiring-developers/strengthen-collaboration-talent-acquisition-engineering-hiring-managers/) [Hiring Developers ## 8 Non-traditional Tactics for Reaching Developer Candidates Discover 8 unconventional and non-obvious channels that can help you enhance your outreach efforts and tap into a pool of skilled developers. Read the post](https://coderpad.io/blog/hiring-developers/8-non-traditional-tactics-for-reaching-developer-candidates/) [Hiring Developers ## How to Hire for AI Fluency Now That It’s a Critical Skill Based on the CoderPad webinar featuring Bayo Ojuri (CoderPad), Bonnie Dilber (Zapier), and Melany Austin (GoDaddy). “AI fluency” has quietly become a line item in nearly every technical job description. The problem: most teams added the requirement long before they had a reliable way to assess it. You can ask a candidate whether they use […] Read the post](https://coderpad.io/blog/hiring-developers/how-to-hire-for-ai-fluency-now-that-its-a-critical-skill/) [Hiring Developers ## Hot Takes on Hiring: “AI Fluency” Is a Myth Our CEO, Amanda Richardson, and our Head of Product, Frank Hauben, can’t agree on anything else. We put Amanda and Frank on camera, handed them five spicy hot takes about AI in hiring, and told them not to sit on the fence. They sat on the fence anyway. Here’s what they actually fought about. Amanda […] Read the post](https://coderpad.io/blog/hiring-developers/hot-takes-on-hiring-ai-fluency-is-a-myth/) [Hiring Developers ## 5 Unfiltered Takes on AI That Engineering Leaders Actually Believe We put a room full of senior engineering leaders together, took away the slides, added beer, and asked them to say the thing they’d never put in a LinkedIn post. No PR-approved talking points, no vendor gloss, just people who ship for a living telling the truth about what AI is doing inside their orgs […] Read the post](https://coderpad.io/blog/hiring-developers/5-unfiltered-takes-on-ai-that-engineering-leaders-actually-believe/) [Hiring Developers ## Your Developer Interview Loop Is a Year Old. Is It Still Finding Your Best Candidates? A YC-backed founder called me last week with some good questions. His 20-person startup hadn’t hired an engineer in over a year. Now they’re opening reqs again, and instead of just dusting off the old loop, he wanted to understand how interviews had changed and if candidates were ready for AI interviews. His process — […] Read the post](https://coderpad.io/blog/hiring-developers/your-developer-interview-loop-is-a-year-old-is-it-still-finding-your-best-candidates/) [Hiring Developers ## AI Fluency Is the New Technical Skill. Is Your Hiring Process Ready? Artificial intelligence has fundamentally changed software development. Developers are no longer working in isolation, writing every line of code from memory. AI has become part of the engineering workflow, helping developers brainstorm approaches, generate boilerplate code, and debug complex issues. The question isn’t whether engineers are using AI. It’s how effectively they’re using it. Hiring […] Read the post](https://coderpad.io/blog/hiring-developers/ai-fluency-is-the-new-technical-skill-is-your-hiring-process-ready/) [Hiring Developers ## AI Didn’t Kill Entry Level Hiring. Bad Screening Did. For the last two years, the narrative has been loud, confident, and mostly wrong: AI is coming for entry level engineering jobs. The story goes something like this: If AI can write code, summarize docs, generate tests, and debug basic issues, why would companies still hire junior engineers? It sounds logical. It is also incomplete. […] Read the post](https://coderpad.io/blog/hiring-developers/ai-didnt-kill-entry-level-hiring-bad-screening-did/) [Hiring Developers ## The Resume Is Dead. Most Teams Just Haven’t Admitted It Yet. Resumes made sense when applying for a job took real effort. That era is over. AI lets candidates apply to hundreds of roles in the time it once took to write a single cover letter. Employer-side AI systems process the flood. The result is a hiring funnel built almost entirely on artificial signals, where the […] Read the post](https://coderpad.io/blog/hiring-developers/the-resume-is-dead-most-teams-just-havent-admitted-it-yet/) [Hiring Developers ## Is Your Technical Hiring Process Screening Out Great Engineers? The short answer: Many technical hiring processes are doing the latter. High-friction interview loops, live coding under observation, and AI-restrictive assessments are measuring interview performance, not job performance. The fix isn’t rebuilding from scratch — it’s auditing whether your process measures engineering capability or something else entirely. If you attended our recent webinar with CoderPad […] Read the post](https://coderpad.io/blog/hiring-developers/is-your-technical-hiring-process-screening-out-great-engineers/) [Hiring Developers ## Junior Developers Are Your Strategic Advantage—If You Can Actually Evaluate Them Campus recruiting season arrives the same way every year: hundreds of applications, a narrow window, and a process that was never designed for this much volume or this much pressure. Meanwhile, the definition of “technical skill” is actively shifting—AI-polished resumes have made traditional screening nearly meaningless, and the skills that predict junior developer success look […] Read the post](https://coderpad.io/blog/hiring-developers/junior-developers-are-your-strategic-advantage-if-you-can-actually-evaluate-them/) ## Hire with confidence. See why engineering teams trust CoderPad to evaluate developers with realistic, AI-ready hiring workflows. [Request a demo](https://coderpad.io/sales/)