• Home
  • BVSSH
  • Engineering Enablement
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Standard : Hiring and growth practices are inclusive and fair

Purpose and Strategic Importance

This standard ensures our hiring and growth practices are inclusive, transparent, and fair-helping us attract, retain, and support diverse talent. It promotes equity in opportunity, experience, and advancement.

Aligned to our "Inclusive & Diverse Engineering Culture" policy, this standard builds stronger, more resilient teams by valuing varied perspectives. Without it, we risk bias, exclusion, and missed potential across our engineering organisation.

Strategic Impact

Clearly defined impacts of meeting this standard include improved delivery flow, reduced risk, higher system resilience, and better alignment to business needs. Over time, teams will see reduced rework, faster time to value, and stronger system integrity.

Risks of Not Having This Standard

  • Reduced ability to respond to change or failure
  • Accumulation of technical debt or friction
  • Poor developer experience and morale
  • Decreased confidence in releases and features
  • Misalignment between technical implementation and business priorities

CMMI Maturity Model

  • Level 1 – Initial: Hiring and promotion are informal, with limited attention to fairness or inclusion.

  • Level 2 – Managed: Teams adopt basic inclusive hiring practices inconsistently.

  • Level 3 – Defined: Inclusive hiring and progression practices are standardised and embedded.

  • Level 4 – Quantitatively Managed: Diversity and inclusion metrics are actively tracked and reviewed.

  • Level 5 – Optimising: Hiring and growth practices are continuously improved to enhance equity and inclusion across the organisation.


Key Measures

  • Adoption metrics relevant to the standard (to be defined)
  • Quality, throughput, and system health metrics aligned to capability
  • Maturity scores based on structured assessment
Associated Policies
  • Inclusive & Diverse Engineering Culture
  • Psychological Safety First
Associated Practices
  • Collaborative Story Refinement
  • Engineering Onboarding Playbooks
  • Guilds & Chapters
  • Architecture Decision Records (ADRs)
  • Dev-Product Pairing
  • Engineering Office Hours
  • Mob Programming
  • Pair Programming
  • Psychological Safety Practices
  • Retrospective Action Loops
  • Shared Learning Days
  • Swarming on Issues
  • Tech Talks & Showcases

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering