> Markdown version of [/videos/1748-emergency-discussion-can-t-hire-the-right-developers-here-s-what-everyone-else-misses?t=1489](https://www.wearedevelopers.com/videos/1748-emergency-discussion-can-t-hire-the-right-developers-here-s-what-everyone-else-misses?t=1489). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Emergency Discussion: Can’t Hire the Right Developers? Here’s What Everyone Else Misses Traditional tech recruitment is broken. Discover how to bypass automated AI filters and HR clichés to attract elite, passive developers through authentic culture and real-world skills evaluation. - **Speakers:** [Rudi Bauer](https://www.wearedevelopers.com/@rudi-bauer), [Ana Gospodinova](https://www.wearedevelopers.com/@ana-gospodinova), [Chris Heilmann](https://www.wearedevelopers.com/@chris-heilmann) - **Event:** Cappuccino with HR - **Published:** October 29, 2025 - **Duration:** 54:20 - **URL:** https://www.wearedevelopers.com/videos/1748-emergency-discussion-can-t-hire-the-right-developers-here-s-what-everyone-else-misses ## Summary The traditional tech recruitment playbook is obsolete. With 70% of developers acting as passive candidates, generic job board listings fail to reach the technical talent companies desperately need. Instead, developers are looking for authenticity, stability, and engaging tech environments. Relying on "AI applying to AI"—where automated resume filters meet AI-generated applications—creates a foggy, non-human candidate experience. To hire effectively, companies must move beyond keyword-stuffed CVs and ambiguous "rockstar" job titles, focusing instead on a skills-based, human-centric approach that prioritizes clear communication over historical interrogation. Gaining developer trust requires dismantling common HR clichés. Promising candidates that they are joining a "family" often backfires because, as the tech community has learned, "you don't lay off your family." Furthermore, avoiding salary transparency signals a lack of internal fairness; compensation must be positioned clearly upfront. Developers possess a highly calibrated "BS detector" and instantly recognize when a job description is bloated or disconnected from the actual work. Evaluating talent should shift toward seeing how candidates approach problem-solving and collaboration. Letting individuals complete paid, real-world tasks or reviewing their communication on pull requests in GitHub offers a far better measure of capability than traditional whiteboard hazing. The most powerful employer branding strategy is actively mobilizing internal engineers as brand ambassadors. Allowing developers to contribute to open-source communities, publish honest technical post-mortems, and speak at industry conferences builds far more credibility than outsourced marketing campaigns. Companies must also offer distinct technical career tracks that do not force senior individual contributors into management merely to secure a promotion. By providing clear growth roadmaps, empowering technical voices, and engaging talent in the specialized communities where they naturally gather, organizations can successfully attract the invisible majority of top-tier developers. **Keywords:** passive candidate sourcing, tech talent acquisition, employer branding authenticity, developer interview process, salary transparency, developer advocacy, skills-based hiring, candidate experience, AI resume screening, technical career roadmaps, open source contributions, developer relations strategy, job description optimization, tech community engagement, github portfolio evaluation, chatgpt job descriptions ## Chapters 1. **Transitioning from engineering to developer advocacy** (03:17) — How the developer advocate role emerged as a vital bridge between technical staff and non-technical stakeholders. 1. **Adapting recruitment for modern technical talent** (06:13) — Why organizations must abandon generalized hiring workflows in favor of highly individualized candidate experiences. 1. **Evaluating job stability versus technical excitement** (09:20) — How recent industry layoffs have shifted developer priorities toward seeking a balance of enduring stability and technological relevance. 1. **Moving beyond traditional resume screening methods** (14:26) — Why focusing on backward-looking documents like resumes limits the ability to hire for future organizational needs. 1. **Building authentic developer community touchpoints** (17:22) — How organizations can attract top talent by establishing a meaningful presence in platforms where developers naturally group. 1. **Establishing a credible employer brand footprint** (20:29) — Why empowering existing technical employees to communicate publicly builds more candidate trust than sanitized corporate branding. 1. **Connecting with talent at developer conferences** (24:49) — A selected overview of community-driven events where companies can organically connect with engineering talent. 1. **Standardizing technical job titles and expectations** (26:21) — The importance of avoiding overly creative job titles and aligning roles closely with sensible organizational models. 1. **Navigating the influx of ai-generated applications** (30:00) — Why injecting direct human contact early in the recruitment process cuts through automated application spam. 1. **Involving engineering teams in recruitment material** (33:12) — How validating job descriptions with internal technical staff prevents misaligned expectations and attracts better candidates. 1. **Assessing practical technical skills and teamwork** (34:46) — Methods for evaluating candidates based on their real-world code contributions and interactions on technical platforms. 1. **Structuring a transparent and fair interview process** (37:57) — How utilizing transparent stages or paid technical trials optimizes hiring time for both the company and the applicant. 1. **Identifying key soft skills in engineering candidates** (40:45) — Why the capacity to intuitively communicate technical concepts and maintain curiosity distinguish exceptional developers. 1. **Translating company culture into compelling technical narratives** (42:14) — How publicly sharing internal problem-solving stories and technical post-mortems effectively highlights company purpose. 1. **Embracing salary transparency in technical job listings** (48:10) — The critical necessity for upfront compensation details and how modern tools can baseline fair salary brackets. ## Related Moments - [Experience requirements and empathy in developer relations](https://www.wearedevelopers.com/videos/1109-the-power-of-developer-communities) (from "The Power of Developer Communities") - [Introducing the technical recruiter perspective in software hiring](https://www.wearedevelopers.com/videos/1363-ai-vs-recruiters-and-applicants-turmoil-in-the-games-industry-what-to-put-on-a-cv) (from "AI vs Recruiters and Applicants, Turmoil in the Games Industry, What to Put on a CV") - [Addressing the issue of generic messaging in technical recruitment](https://www.wearedevelopers.com/videos/1494-breaking-the-ice-debunking-myths-between-recruiters-and-developers) (from "Breaking the Ice: Debunking Myths Between Recruiters and Developers") - [Bridging the disconnect between technical recruiters and engineering candidates](https://www.wearedevelopers.com/videos/1724-why-developers-don-t-care-about-your-employer-brand-and-how-to-fix-it) (from "Why Developers Don't Care About Your Employer Brand and How to Fix it") - [Bridging the trust gap between software engineers and recruiters](https://www.wearedevelopers.com/videos/1363-ai-vs-recruiters-and-applicants-turmoil-in-the-games-industry-what-to-put-on-a-cv) (from "AI vs Recruiters and Applicants, Turmoil in the Games Industry, What to Put on a CV") - [Improving employer branding through specialized developer relations roles](https://www.wearedevelopers.com/videos/1315-ai-dei-community-what-s-next-for-talent-acquisition-in-2025) (from "AI, DEI & Community: What’s Next for Talent Acquisition in 2025?") ## Related Articles - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Exploring AI: Opportunities and Risks for Developers](https://www.wearedevelopers.com/magazine/522-exploring-ai-opportunities-and-risks-for-developers) - [Résumé-Driven Development: How IT trends affect the job market for software developers](https://www.wearedevelopers.com/magazine/59-resume-driven-development-how-it-trends-affect-the-job-market-for-software-developers) - [What is Software Engineering in the Age of AI?](https://www.wearedevelopers.com/magazine/640-what-is-software-engineering-in-the-age-of-ai) ## Related Jobs - [Staff Developer Advocate, GitHub Security Lab](https://www.wearedevelopers.com/jobs/ext/1921051-staff-developer-advocate-github-security-lab) at **GitHub** - [Senior Software Engineer](https://www.wearedevelopers.com/jobs/ext/15942-senior-software-engineer) at **GitHub** - [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx** - [Principal Software Engineer, Enterprise AI Platform](https://www.wearedevelopers.com/jobs/ext/1467292-principal-software-engineer-enterprise-ai-platform) at **GitHub** - [Principal Product Manager, Agent Platform](https://www.wearedevelopers.com/jobs/ext/277541-principal-product-manager-agent-platform) at **GitHub** - [Senior Engineer, Infrastructure Platform](https://www.wearedevelopers.com/jobs/ext/328836-senior-engineer-infrastructure-platform) at **Intercom, Inc.**