- Chaotic and disorganized tech job interview processes are common, leading to frustration among candidates.
- Even well-funded startups often fail to treat candidates with basic professionalism, causing a negative impression.
- Speed and ego can override respect and transparency in tech hiring, leading to problematic interview experiences.
- Unprepared interviewers and lack of structure can make a tech job interview feel unprofessional and unproductive.
- Candidates deserve basic respect and professionalism during the hiring process, including clear communication and structure.
Software developer Oliverio Cayuelas recently detailed his worst job interview experience at an unnamed tech startup, describing a chaotic, disorganized process marked by last-minute cancellations, unprepared interviewers, and a complete lack of structure—issues that resonate with a growing number of tech workers frustrated by broken hiring systems. His account, published on his personal blog and later amplified on Hacker News with over 246 comments and 293 upvotes, highlights how even well-funded startups often fail to treat candidates with basic professionalism. The incident matters not just as an outlier but as a symptom of deeper cultural and operational problems in tech hiring, where speed and ego too often override respect and transparency.
What Went Wrong During the Interview
The interview process began with a promising outreach from a recruiter, but quickly unraveled. Cayuelas was scheduled for multiple technical rounds with different team members, only to face repeated last-minute cancellations and rescheduling, sometimes with less than 15 minutes’ notice. When the interviews finally proceeded, several engineers appeared unprepared, unfamiliar with his resume, and unable to articulate the purpose of the session. One interviewer joined from a noisy public space, while another spent most of the time promoting the company’s ‘revolutionary’ vision without asking technical questions. The technical challenge itself was poorly defined, with shifting requirements and no clear success criteria. At no point was there a coherent evaluation framework, leaving Cayuelas unsure whether he was being assessed for coding ability, system design, or cultural fit. The experience culminated in radio silence after the final round—no feedback, no rejection, no closure.
How Tech Hiring Lost Its Way
The dysfunction Cayuelas described is not new. For over a decade, tech hiring has grappled with inconsistencies, bias, and performative rigor. In the 2010s, companies like Google and Facebook popularized grueling whiteboard interviews that prioritized algorithmic puzzles over real-world problem-solving, leading to widespread criticism and eventual reforms. Yet, even as larger firms adopted more structured processes, many startups—especially those in hypergrowth mode—have continued to operate with ad hoc, improvisational hiring. Engineers often double as interviewers without proper training, and leadership may prioritize speed over candidate experience. A 2023 Stack Overflow survey found that 37% of developers reported having at least one unprofessional interview experience in the prior year. The lack of accountability, combined with a power imbalance favoring employers, enables these patterns to persist, even in companies that claim to value engineering excellence.
The People Behind the Process
At the heart of flawed hiring are the people conducting it—often overworked engineers and time-pressed founders who view interviews as a necessary distraction rather than a core function. In early-stage startups, there may be no dedicated HR or talent team, leaving technical staff to design and execute hiring without formal support. Recruiters, meanwhile, are often incentivized to move candidates quickly through the funnel, not to ensure quality or dignity in the process. Cayuelas’ interviewers likely weren’t malicious; they were probably under pressure to fill roles rapidly while managing their own deliverables. But without clear guidelines, training, or accountability, even well-intentioned individuals can perpetuate toxic norms. The blog post’s virality suggests that many developers recognize this cycle—and are increasingly unwilling to tolerate it.
Consequences for Candidates and Companies
When companies mishandle interviews, the damage extends beyond a single candidate’s frustration. Poor experiences spread quickly through developer communities, eroding employer reputation and making it harder to attract top talent. In a competitive market, a company known for disrespectful hiring may lose strong candidates to rivals with more thoughtful processes. Internally, disorganized hiring can lead to misaligned hires, increased turnover, and cultural drift. Conversely, a transparent, respectful interview process can serve as a powerful differentiator. Companies like GitLab and Shopify have invested in public interview guides, standardized rubrics, and candidate feedback loops—practices that not only improve fairness but also reflect operational maturity. Cayuelas’ experience underscores that how a company hires is often a proxy for how it operates.
The Bigger Picture
This story matters because it reflects a broader tension in tech: the gap between aspirational culture and everyday practice. Many startups proclaim values like transparency, empathy, and meritocracy, yet fail to apply them in high-stakes, human-centered processes like hiring. The industry’s fixation on scaling fast and shipping quickly often comes at the cost of foundational practices that sustain long-term success. As remote work and global talent pools expand, the need for consistent, respectful hiring will only grow. Developers are no longer passive participants in this system—they are vocal critics and advocates for change, using platforms like Hacker News and GitHub to hold companies accountable.
What comes next may be a shift toward candidate-centric hiring, driven by peer pressure and competition for talent. Some startups are already adopting open interview rubrics, recording sessions for review, and compensating candidates for technical assignments. As Oliverio Cayuelas’ story shows, one person’s bad experience can spark a much larger conversation—one that could ultimately redefine what professionalism means in tech.
Source: Oliverio




