aisecurity.llc

The Frankenstein Role

AI Security Engineer role language often bundles five historically separate capability families into one requisition.

Talent and role-design crisis

What this finding measures

Ready for Public Claim

AI Security Engineer role language often bundles five historically separate capability families into one requisition.

Use as a primary report finding with methodology caveat.

Based on analyzed job-description signals, not proof of any individual company’s internal security maturity.

Role breadth signal

Flagship thesis

Chart targets

  • chart_frankenstein_role_distribution
  • chart_frankenstein_role_by_industry
  • chart_role_archetype_by_industry
  • chart_survey_maturity_by_persona
  • chart_survey_distinct_discipline
  • chart_survey_hardest_skills
  • chart_survey_best_background
  • chart_survey_discipline_by_persona
  • chart_survey_risk_by_persona

Active filters: period=all, industry=all, seniority=all

Clear

Evidence charts

Current chart outputs for this finding

Finding Evidence

Frankenstein Role Score Distribution

Distribution of role-breadth pressure across analyzed job descriptions.

v_job_score_distribution
Source: v_job_score_distribution
Higher values indicate broader role-specification language, not proof of poor company maturity.

Spec title: Frankenstein Role Score Distribution

Chart ID: chart_frankenstein_role_distribution

Source: v_job_score_distribution

Caption: This chart shows how frequently job descriptions exhibit broad cross-domain AI security role language.

Chart caveat: Higher values indicate broader role-specification language, not proof of poor company maturity.

Deck note: Use this chart to introduce role-breadth pressure.

Vertical Benchmarks

Frankenstein Role Score by Industry

Industry-level comparison of role breadth and cross-domain responsibility language.

v_industry_score_benchmarks
Source: v_industry_score_benchmarks
Segment sample sizes vary; smaller industries should be read as directional.

Spec title: Frankenstein Role Score by Industry

Chart ID: chart_frankenstein_role_by_industry

Source: v_industry_score_benchmarks

Caption: Industries ranked by average Frankenstein Role Score.

Chart caveat: Segment sample sizes vary; smaller industries should be read as directional.

Deck note: Use this chart to tee up vertical subreports.

Role Architecture

Role Family Frankenstein Score by Period

How role breadth pressure evolved across security role families from 2024 to 2026.

export.v_chart_ai_security_archetype_bars
Source: export.v_chart_ai_security_archetype_bars
Based on analyzed job-description signals, not proof of any individual company's internal security maturity.

Chart ID: chart_role_archetype_by_industry

Source: export.v_chart_ai_security_archetype_bars

Survey Research

Average Program Maturity by Persona

Self-reported AI security program maturity (0–5 scale). Dashed line = developing threshold (2.5).

survey_aggregate.cross_persona.maturity_avg_by_persona
Source: survey_aggregate.cross_persona.maturity_avg_by_persona
Self-reported maturity index. Not an independent audit of organizational capability.

Chart ID: chart_survey_maturity_by_persona

Source: survey_aggregate.cross_persona.maturity_avg_by_persona

Caption: Program maturity per respondent persona. Hiring managers lowest at 1.8/5 (emerging).

Chart caveat: Self-reported maturity index. Not an independent audit of organizational capability.

Deck note: Maturity scores cluster in emerging-to-developing. Use this to show the structural gap in program delivery.

Survey Research

Is AI Security Engineering a Distinct Discipline?

Cross-persona belief distribution. 57% describe it as Yes or Yes (still immature).

survey_aggregate.cross_persona.distinct_discipline
Source: survey_aggregate.cross_persona.distinct_discipline
Self-reported cross-persona belief. Does not reflect formal organizational recognition.

Chart ID: chart_survey_distinct_discipline

Source: survey_aggregate.cross_persona.distinct_discipline

Caption: Practitioner belief about whether AI Security Engineering is its own field.

Chart caveat: Self-reported cross-persona belief. Does not reflect formal organizational recognition.

Deck note: Market recognition is outpacing formal role definition — use this to show the urgency.

Hardest AI Security Skills to Hire (Hiring Managers)

No rows matched current filters or export rows are not populated yet.

Preferred Candidate Background (Hiring Managers)

No rows matched current filters or export rows are not populated yet.

"Distinct Discipline" Belief — Compared Across Personas

No rows matched current filters or export rows are not populated yet.

AI Security Risk Priorities — By Persona

No rows matched current filters or export rows are not populated yet.

Recommended actions

What leaders should do next

Define one primary ownership domain before posting the role.
Separate engineering delivery from governance evidence expectations.
Use role-architecture interviews instead of generic security interviews.

Browse the full citation library for supporting research and source quotes.

Evidence library →