Hiring direction to Nathan - prioritize background diversity, broaden beyond Amazon blood

June 18, 2026 at 8:52 PMpeoplelow

Situation

In Nathans 1:1, as Nathan described two engineers entering his pipeline (both Amazon backgrounds), Peter directed him to prioritize diversity of background - people who have been at multiple companies, not more Amazon hires, because CIQ has more Amazon blood than Peter wants for its size. He framed it as part of deciding who we want to be as we grow to this next stage. Not a veto on Amazon backgrounds (I do not mind Amazon, but make sure they have been other places too).

Reasoning

Monoculture is a growth risk: too many hires from one company imports one companys assumptions, while diversity of background widens the orgs problem-solving range as CIQ scales. This is identity-defining for the company, not just headcount. It functions as a guardrail on Nathans hiring rather than a hard veto.

Additional Context

Confirmed by Peter as a directional decision worth tracking. Connects to his build-the-team-you-want doctrine.

Observed Evidence

Direct quotes in Nathan 1:1; directional guardrail on Nathans pipeline.

Confidence Breakdown

28/35
Evidence
12/30
Pattern
12/20
Source
6/15
Corroboration

Reasoning Depth Analysis

Org Signal:Hiring managers should weight background diversity, not just familiar pedigree.
Who Affected:Nathans two pipeline candidates, future Linux-eng hires.
Precedent:A hiring heuristic for the orgs growth phase.
Consequences:Modest, slow-acting - shapes who gets interviewed over time.
Timing:Now, as Nathan is actively building his pipeline.

People Involved

Source

reflection

AI Confidence

58%

Related Context

🎥
Nathan <> Peter 1:1 (6/18)

fathom

I do not mind somebody having been at Amazon, but I want to make sure they have been other places too... we have got more blood from just Amazon than I would want in our size. And for me it is about diversity... as we grow to this next stage, I want to get some more diversity in the building.

Outcome

No outcome recorded yet.

Decision ID: ff91df4a-81c5-4013-b371-6e021e40b946