📝 Developer Psychometrics Blog

The Myth of the INTJ Developer: What 40 Years of Research Actually Shows

Ask any developer their MBTI type and you'll hear INTJ. The "architect" type has become synonymous with programmer identity. But is it actually the most common type among developers?

The Data Says No

Capretz (2003) studied personality types across software engineering populations and found:

• ISTJ — 25% is the most common developer type (not INTJ)
• INTJ — 16% comes second
• 57% of developers are introverted (vs 43% extraverted)
• 81% prefer Thinking over Feeling
• ~50% of developers are NT types (vs 6% of general population — an 8x over-index)

The ISTJ developer — methodical, reliable, detail-oriented — is actually the backbone of most engineering teams. They are the ones who write the tests, document the APIs, and show up to on-call rotation without complaint. They just don't talk about their MBTI type on Twitter.

Why This Matters for Hiring

If you're hiring only for the "visionary INTJ architect" profile, you're missing the ISTJs who will actually ship reliable code. The best teams have a mix: INTJs for architecture, ISTJs for reliability, ENTPs for creative problem-solving, and ESFJs for team cohesion.

Source: Capretz, L.F. (2003). Personality types in software engineering. ScienceDirect. Cruz et al. (2015). Forty years of personality research in SE.

Why Your Best Security Engineer Might Score High on Machiavellianism

A 2023 study from Oxford Academic analyzed the personality profiles of cybersecurity professionals and found something startling:

"Security professionals scored at the 72nd percentile on Machiavellianism — well above the general population average."

Before you worry about your security team, understand what this means in context:

• Offensive security (red team, penetration testing) requires thinking like an attacker — anticipating manipulation, exploiting trust, finding what others miss
• Defensive security requires paranoid thinking — assuming everyone is trying to break in, questioning every assumption, never trusting input
• The adversarial mindset that scores high on Machiavellianism is literally the job description

INTJ and INTP dominate offensive security. ISTJ dominates defensive security. The trait that makes someone "difficult" in a team meeting makes them excellent at finding vulnerabilities.

The Lesson for Team Composition

Don't hire security engineers expecting them to be agreeable team players. Hire them expecting them to question everything — including your decisions. That's the feature, not the bug.

Source: Oxford Academic (2023). Security Mindset: Characteristics and Consequences. Cyberpsychology.

Openness to Experience: The #1 Trait for Long-Term Developer Success

If you could measure only ONE personality trait in a developer candidate, which should it be? The research points to Openness to Experience.

• Openness predicts learning velocity — how fast someone picks up new languages, frameworks, and paradigms (Inkli, 2024)
• It's the strongest Big Five predictor of data science success (CareerExplorer)
• Intellectual curiosity — a facet of Openness — is the "third pillar" of achievement alongside intelligence and conscientiousness (Von Stumm, 2011)

In a field where the tech stack changes every 3-5 years, the ability and DESIRE to learn new things is more valuable than current expertise. A high-Openness developer who has never used your framework will outperform a low-Openness expert within 6 months.

How to Spot It

In interviews, ask: "What's the last technology you learned purely because it interested you, not because work required it?" High-Openness developers light up. Low-Openness developers struggle to answer.

Source: Von Stumm, S. (2011). The hungry mind. Perspectives on Psychological Science. Inkli (2024). Personality Profile of a Great Software Engineer.

Why 91% of Open Source Contributors Do It for Fun (Not Money)

A 2021 study analyzing open source contributor motivations (arxiv) found:

• 91% contribute because it's fun (intrinsic motivation)
• 85% for altruism — wanting to help others
• 80% for kinship — sense of belonging to a community
• 68% for reputation
• 67% for career advancement
• <30% for direct payment

The most fascinating finding: joining motivations transform into staying motivations. People join for extrinsic reasons (career, reputation) but stay for intrinsic ones (fun, community, altruism).

Personality Profile of OSS Contributors

High Openness + High Agreeableness + moderate Extraversion. They're explorers who enjoy collaboration and are generous with their time. In our framework: Explorer + Connector.

Source: arxiv (2021). Shifting Sands of Motivation in Open Source.

The Two Cognitive Styles of Programmers: Systematic vs Opportunistic

Petre & Green (1993) identified two fundamental approaches to programming:

• Systematic programmers: Plan before coding. Top-down. High Conscientiousness + Need for Closure. Write pseudocode first, design the architecture, then implement. "Measure twice, cut once."
• Opportunistic programmers: Explore and iterate. Bottom-up. High Openness + low Need for Closure. Start coding immediately, refactor as patterns emerge. "Make it work, make it right, make it fast."

Neither is superior. Systematic programmers excel at safety-critical systems, infrastructure, and large-scale architecture. Opportunistic programmers excel at prototyping, hackathons, and exploring new problem spaces.

The Team Implication

The best engineering teams contain both styles. Pair a systematic architect with an opportunistic explorer and watch them build things neither could alone. The friction between styles is productive — if managed well.

Source: Petre, M. & Green, T.R.G. (1993). Learning to Read Graphics. J. Visual Languages.