> Markdown version of [/videos/1493-hr-tech-why-can-t-we-be-friends?t=103](https://www.wearedevelopers.com/videos/1493-hr-tech-why-can-t-we-be-friends?t=103). 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).

---

# HR & Tech: Why can't we be friends?

Why do developers often view HR as a necessary evil? Uncover the deep cognitive divide keeping your technical and human resources teams apart. Learn to dismantle these dangerous silos.

- **Speakers:** [Sibila Erdei](https://www.wearedevelopers.com/@sibila-erdei)
- **Event:** World Congress 2025
- **Published:** August 20, 2025
- **Duration:** 21:33
- **URL:** https://www.wearedevelopers.com/videos/1493-hr-tech-why-can-t-we-be-friends

## Summary

The persistent friction between technical teams and human resources often stems from deep behavioral and communicative divides rather than mere organizational bureaucracy. Recent sentiment surveys reveal that developers frequently view HR as technologically illiterate or a necessary administrative evil, rating their effectiveness and modern tool usage poorly. This disconnect is primarily rooted in cognitive friction: HR professionals typically navigate high-context, nuanced environments relying on diplomacy and ambiguity, while technical teams require low-context, highly direct communication to prevent system failures. Furthermore, implicit gender dynamics frequently exacerbate this divide, as male-dominated technical cultures using aggressive terminology—like "ninjas" or "cutting the fluff"—often dismiss the crucial emotional and maintenance labor provided by female-dominated HR departments.

Bridging this gap is no longer optional, primarily due to the rapid integration of artificial intelligence into core business operations. Building ethical AI infrastructure requires marrying the developer's raw code with HR's human context. To achieve mutual understanding, HR teams must shift from projecting needs to actively co-designing programs alongside engineers, cultivating genuine psychological safety where risk and candor are permitted over forced pleasantries. By translating abstract cultural values into concrete, actionable developer behaviors—and backing initiatives with robust, evidence-based data—organizations can effectively dismantle silos. Fostering this deep alignment eliminates innovation bottlenecks, prevents unnoticed engineering burnout, and paves the way for forward-thinking systems like cross-role skill mapping and predictive feedback.

**Keywords:** hr and tech collaboration, high-context vs low-context communication, developer perception of hr, cognitive friction in the workplace, psychological safety in tech teams, ethical ai policies, co-designing hr programs, tech industry gender gap, skills mapping frameworks, predictive feedback systems, data-driven hr metrics, cross-departmental silos, emotional labor in hr, workplace behavioral mismatch

## Chapters

1. **Experiences of feeling isolated across tech startup environments** (00:05) — Working as the only human resources professional in early-stage engineering teams often creates unnecessary barriers to cross-functional collaboration.
1. **Surveying developer sentiment regarding modern capabilities of human resources** (01:43) — Asking developers about the data-driven systems and modern tools utilized by people operations teams reveals a deep industry skepticism.
1. **Analyzing developer feedback on systemic human resources issues** (03:56) — The perception of human resources as administrative bureaucracy leads to developers feeling treated as mere resources instead of humans.
1. **Psychological factors driving the divide between engineers and human resources** (06:51) — Cognitive ease and the need to preserve professional identity cause different departments to operate in defensive and isolated silos.
1. **Bridging high context and low context workplace communication styles** (09:10) — Translating abstract company values into clear behavioral expectations reduces frustration among software engineers who rely heavily on direct clarity.
1. **Understanding how gender demographics affect department communication and preferences** (12:11) — Acknowledging the gender imbalances between technical and people operations teams highlights the systemic devaluation of essential emotional labor.
1. **The business costs of misaligned technical and people operations** (14:19) — Friction between departments directly leads to tangible innovation bottlenecks, unnoticed employee burnout, and severe damage to overall employer reputation.
1. **Uniting human resources and developers to manage artificial intelligence** (15:33) — The ethical implementation of upcoming automation tools requires coding expertise combined seamlessly with the deep contextual understanding of people operations.
1. **Establishing mutual trust through cross functional design and data** (17:21) — Utilizing objective metrics and actively involving engineers in program creation firmly establishes the psychological safety needed for candid communication.

## Related Moments

- [Fostering active interactions between human resources and technology leaders](https://www.wearedevelopers.com/videos/1726-behind-the-scenes-putting-hr-and-tech-on-the-same-stage) (from "Behind the Scenes: Putting HR and Tech on the Same Stage")
- [Overcoming HR apprehension toward technology stacks](https://www.wearedevelopers.com/videos/1721-robots-don-t-drink-coffee-but-they-might-hire-you) (from "Robots Don’t Drink Coffee, But They Might Hire You")
- [Bridging the gap between HR and engineering](https://www.wearedevelopers.com/videos/1721-robots-don-t-drink-coffee-but-they-might-hire-you) (from "Robots Don’t Drink Coffee, But They Might Hire You")
- [Sustaining HR credibility through direct AI technological proficiency](https://www.wearedevelopers.com/videos/1813-empowering-people-in-a-digital-world-hr-s-next-big-chapter) (from "Empowering People in a Digital World: HR’s Next Big Chapter")
- [Addressing psychological safety and ethical risks of AI adoption](https://www.wearedevelopers.com/videos/1950-the-scrum-master-as-an-orchestrator-guiding-human-ai-collaboration-in-modern-teams) (from "The Scrum Master as an Orchestrator: Guiding Human–AI Collaboration in Modern Teams")
- [Merging software development and human resources practices](https://www.wearedevelopers.com/videos/1500-code-meets-culture-engineering-the-future-of-hiring) (from "Code meets Culture: Engineering the Future of Hiring")

## Related Articles

- [Exploring AI: Opportunities and Risks for Developers](https://www.wearedevelopers.com/magazine/522-exploring-ai-opportunities-and-risks-for-developers)
- [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift)
- [WWC24 Talk - Scott Hanselman - AI: Superhero or Supervillain?](https://www.wearedevelopers.com/magazine/469-wwc24-talk-scott-hanselman-ai-superhero-or-supervillain)
- [Panel Discussion: Responsible AI in Practice - Real-World Examples and Challenges](https://www.wearedevelopers.com/magazine/488-panel-discussion-responsible-ai-in-practice-real-world-examples-and-challenges)

## Related Jobs

- [AI Operations Manager (all genders)](https://www.wearedevelopers.com/jobs/48263-ai-operations-manager-all-genders) at **envelio**
- [Senior Engineer, Infrastructure Platform](https://www.wearedevelopers.com/jobs/ext/328836-senior-engineer-infrastructure-platform) at **Intercom, Inc.**
- [AI Full Stack Engineer](https://www.wearedevelopers.com/jobs/ext/1354435-ai-full-stack-engineer) at **Almedia**
- [Principal Software Engineer, Enterprise AI Platform](https://www.wearedevelopers.com/jobs/ext/1467292-principal-software-engineer-enterprise-ai-platform) 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**
- [Senior People Systems Analyst](https://www.wearedevelopers.com/jobs/ext/73055-senior-people-systems-analyst) at **Intercom**