The Art of Hiring Good Engineers

Summary

Building and scaling engineering teams requires adapting recruitment strategies across different organizational sizes, from initial hires to hundreds of engineers. Teams often begin with small groups of battle-tested engineers before designing formal hiring pipelines. The recruitment approach outlines four key steps: sourcing top-tier talent from platforms like GitHub and LinkedIn, assessing technical fit through tailored screens or assignments, evaluating cross-functional and culture fit via group interviews, and optimizing the process. This optimization includes routing candidates strategically to strict bar-raiser interviewers to prevent burnout and expedite decisions.

Context

Tech leads and teams in niche fields need efficient and useful hiring processes to build and scale engineering teams from scratch without burning out existing staff or lowering standards.

Approach / What changed

A four-step hiring framework consisting of sourcing candidates from open-source and professional networks, evaluating technical competence via targeted tests or screens, assessing culture fit across product and design teams, and optimizing candidate routing with designated bar-raisers.

Takeaways

• Targeting only the top 2% to 5% of engineers may require processing roughly 500 profiles to hire 5 to 10 people.
• Assigning strict bar-raiser interviewers only to super strong profiles helps prevent interviewer burnout while maintaining pipeline speed.
• Initial technical pre-screening rounds commonly take 1 to 2 hours of a candidate's time, with phone screens ranging from 20 minutes to 1.5 hours.

Related reading

• Grab · Jul 24, 2017

  So You Need to Hire Good Engineers

  Hiring strategies in fast-growing technology startups dictate the quality and scalability of expanding engineering teams. Insights gathered from conversations with over one hundred engineering leaders identify crucial evaluation criteria across technical competence, cultural alignment, and problem-solving capability. Candidates rarely present a perfect technical fit, requiring hiring managers to weigh passion, willingness to learn, and risk appetite against baseline technical requirements. Rather than focusing solely on static factual questions, interviewers gain deeper insights by probing the rationale behind candidates' architectural and implementation choices. High-caliber engineers ultimately elevate team capability by simplifying complex challenges, writing cleaner code, and learning quickly.

  Rachel Lee

• Salesforce · Jul 30, 2026

  How Salesforce Built an Agentic Engineering Enablement Strategy for Thousands of Software Engineers

  Salesforce addressed the challenge of scaling agentic engineering across thousands of software developers by focusing on organizational learning rather than tooling. While individual engineers initially developed disparate, uncoordinated workflows, the Technology, People, Innovation, and Learning (TPIL) team unified these approaches into the Proficiency Level (PL) Framework. The framework maps developer growth across four mindset-driven stages: AI-Assisted, AI-Validating, AI-Orchestrating, and AI-Native. To facilitate progress across these stages, TPIL introduced global AI camps, weekly working sessions, and manager coaching guides. Rather than tracking course completions or telemetry scores, Salesforce measured transformation through behavioral indicators, such as shifts toward validating agent output, designing multi-agent workflows, and asking higher-level questions regarding human judgment.

  Scott Nyberg

• Grab · Sep 25, 2019

  Being a Principal Engineer at Grab

  Grab's rapid growth resulted in roughly 350 microservices powering its superapp, creating the need for defined individual contributor career milestones. At Grab, a principal engineer oversees the architecture of an entire Tech Family, a sub-organisation containing over 50 engineers and 20 or more microservices. Responsibilities include translating broad, ambiguous problems into concrete projects, managing technical debt, and aligning multiple engineering teams across global R&D centres. The role demands continuous technical leadership through RFC design reviews, cross-functional communication, mentorship, and self-directed prioritization alongside engineering leadership. Ultimately, principal engineers amplify engineering quality and operational stability without directly managing people.

  Roman Atachiants

• Grab · Feb 16, 2017

  How Grab Hires Engineers in Singapore

  Grab maintains a selective engineering recruitment process in Singapore, with only three to five percent of candidates ultimately receiving an offer. The evaluation pipeline typically spans three to four weeks and includes an initial HR phone screen, an online coding round, and consecutive technical interviews. Recruiters assess candidate capability via public GitHub projects, presentations, and technical blogs rather than traditional CV qualifications alone. The company prioritizes experience in low-latency distributed systems and microservices design alongside strong cultural alignment with peer collaboration.

  Daniel Tay