TOGAF Hiring Leans on Consultancies, Not Federal Contractors

TOGAF's Top Employers Are Consultancies and Software Vendors, Not Contractors

Ask which employers actually ask for TOGAF, The Open Group's enterprise-architecture framework certification, and the pattern looks different from most other IT and security credentials in this dataset. Its largest employer is a management consultancy. Its second-largest is a federal contractor, but from there the roster tilts hard toward consulting firms and enterprise software vendors, not government work.

We looked at active Solutions Architect, Cloud Architect, and Security Architect postings, the three roles TOGAF maps to most directly, 6,286 postings from a 90-day window on the InterviewStack.io job board. TOGAF showed up in 350 of them, 5.6%, and every comparison in this post uses that three-role scope as the baseline, not the broader job market.

That employer mix turns out to matter for more than curiosity. It's usually the first place to look when postings that mention a certification pay less than postings that don't, and here it doesn't supply an answer. TOGAF-mentioning postings advertise a lower median salary than postings that don't mention it, and neither the employer mix nor either of the two composition checks we normally run against a salary gap accounts for it.

Key Findings

• TOGAF appears in 5.6% of postings across Solutions Architect, Cloud Architect, and Security Architect roles (350 of 6,286 postings analyzed).
• Only 12.2% of the 131 classified mentions call TOGAF a required qualification; 87.8% call it preferred, and 62.6% of all mentions don't specify either way.
• TOGAF-mentioning postings advertise a median $161,475 US base salary, about 9.1% below the $177,650 median for postings in the same three roles that don't mention it.
• That gap holds at mid-level too (-7.6%), the only seniority band with enough TOGAF-mentioning salary data to report.
• Neither seniority mix nor role mix explains the gap: TOGAF-mentioning postings' average seniority level (1.46) is nearly identical to the rest of the market (1.45), and TOGAF over-indexes into Solutions Architect, the highest-paying of the three roles in scope.
• None of the 350 TOGAF-mentioning postings are entry-level.
• Consulting firms and software vendors outnumber federal contractors among TOGAF's top employers by nearly 5 to 1 (67 versus 14 mentions across the top 12).
• CISSP is the dominant co-occurring certification (18.3% of TOGAF mentions), more than double any cloud-vendor certification.

Employer	TOGAF-Mentioning Postings
PA Consulting	11
CACI International Inc	10
Ntt Limited	8
Adobe	8
DXC Technology	7
SAP	7
Celonis SE	6
Intetics	6
Kyndryl	6
AtkinsRéalis	4
Booz Allen Hamilton	4
Royal Bank of Canada	4

PA Consulting, a UK-based management and technology consultancy, tops the list at 11 mentions, just ahead of CACI International, a US federal contractor, at 10. From there the roster splits three ways. Consulting and IT-services firms, PA Consulting, DXC Technology, Kyndryl (the IT-infrastructure-services company spun out of IBM), Intetics (a software-development outsourcing firm), and AtkinsRéalis (a global engineering and design consultancy), together supply 42.0% of the mentions in this table. Enterprise software vendors, SAP, Celonis (a process-mining software company), and Adobe, add another 25.9%. Federal contractors, CACI International and Booz Allen Hamilton, account for 17.3%. The rest splits between Ntt Limited, the global telecom and IT-services company, at 9.9%, and Royal Bank of Canada at 4.9%.

Add it up and non-government employers outnumber federal contractors in this table by nearly 5 to 1 (67 mentions versus 14). That fits what TOGAF actually is: a framework for structuring enterprise IT transformation, the kind of work consultancies sell as engagements and software vendors build tooling around, rather than a technical skill tied to one industry's compliance requirements.

How Evenly Does TOGAF Demand Actually Split Across the Three Roles?

Not very unevenly, which is itself notable. Solutions Architect postings mention TOGAF at 6.1%, the highest of the three roles, but Security Architect (5.5%) and Cloud Architect (4.0%) aren't far behind. Solutions Architect over-indexes slightly at 1.10x the aggregate rate, Security Architect sits almost exactly at parity (0.98x), and Cloud Architect under-indexes the most at 0.73x. None of the three role rates is a rounding error, but none dominates the comparison either.

Role	Postings Scanned	TOGAF Mentions	Mention Rate	Share of All TOGAF Mentions
Solutions Architect	4,104	252	6.1%	72.0%
Security Architect	696	38	5.5%	10.9%
Cloud Architect	1,486	60	4.0%	17.1%

Solutions Architect's mention rate barely edges out the other two roles, but it's also by far the biggest of the three (65.3% of all postings scanned), so it supplies 72.0% of every TOGAF mention by volume. If you're deciding whether TOGAF fits a specific role among these three, the honest read is that it's a reasonable credential across all of them; it's not a credential tightly gatekept by one title the way a highly specialized certification might be.

One nuance worth flagging on that Solutions Architect number: close to half of the sampled titles behind it read as Enterprise Architect, Enterprise Integration Architect, or Director of Enterprise Architecture rather than a plain Solutions Architect title, a known pattern in how this dataset's role classifier groups adjacent architecture titles together. That's less a contamination problem here than a confirming one: TOGAF's primary audience is enterprise architects, so a TOGAF-filtered sample skewing toward Enterprise-Architect-flavored titles inside the Solutions Architect bucket is closer to what you'd expect than a distortion of it.

The TOGAF Pay Gap Doesn't Trace to Seniority or Role Mix

Among postings that disclose a US base salary (equity, bonus, and other compensation aren't captured in postings and aren't part of this comparison), TOGAF-mentioning postings across the three-role scope advertise a median of $161,475, about 9.1% below the $177,650 median for postings in the same three roles that don't mention it (n=90 with TOGAF, n=1,916 without). That gap isn't explained away by seniority or by which role is doing the asking, the two checks that usually account for a certification's salary story in this dataset.

Seniority Level	Without TOGAF (Median US Base)	With TOGAF (Median US Base)	Difference
Entry	$97,500 (n=25)	Not reportable (n=0)	N/A
Mid-level	$162,250 (n=1,062)	$150,000 (n=60)	-7.6%
Senior	$184,000 (n=573)	Not reportable (n=14)	N/A
Staff	$185,000 (n=256)	Not reportable (n=16)	N/A

Mid-level is the only band where the TOGAF-mentioning sample clears the 25-posting reporting floor (n=60); entry has zero TOGAF-mentioning postings with disclosed salary at all, and senior (n=14) and staff (n=16) both fall just short. At the one level we can actually check, the gap is smaller than the aggregate (-7.6% versus -9.1%) but still real and still negative, not a rounding difference.

The obvious first explanation is that TOGAF-mentioning postings skew toward a cheaper seniority band. They don't. The average seniority level across TOGAF-mentioning postings (1.46) is nearly identical to postings that don't mention it (1.45), a gap of well under 1%. TOGAF-mentioning postings actually have zero entry-level share (against 2.2% for the rest of the market) and a bigger staff share (14.3% versus 11.5%), offset by a smaller senior share (17.7% versus 24.7%). The composition is different, but it nets out to almost the same average level, so a seniority story can't explain a lower median.

One methodology caveat on that comparison: seniority here is inferred from title keywords, and just over half of this dataset's sampled titles carry no explicit level word at all (bare "Enterprise Architect," "Solution Architect," "System Architect," and similar). Postings like that default to a mid_level bucket, which compresses the measured spread for both the TOGAF-mentioning and non-mentioning groups. That doesn't reverse the finding, since it would take a very different default-rate between the two groups to explain away a real, negative salary gap, but it does mean the 1.46-versus-1.45 comparison is a coarser instrument than two decimal places suggest.

Role mix runs the same way. Solutions Architect, the role TOGAF over-indexes into (1.10x the aggregate rate), is also the highest-paying of the three roles by baseline salary ($180,700 median for postings that don't mention TOGAF), and Cloud Architect, the role TOGAF under-indexes out of (0.73x), is the lowest-paying ($174,900). If anything, that composition should pull the pooled TOGAF-mentioning median up toward Solutions Architect's higher baseline, not down. The three baseline salaries sit close together to begin with (within about 3.3% of each other), so this isn't a large effect either way, but it runs opposite to what would be needed to explain a negative gap.

That leaves the gap sitting inside the postings themselves rather than in who's applying, or at what level. It's a real, modest discount, not a large one, and it's worth reading alongside the employer pattern above: consulting and enterprise-software work doesn't obviously pay less than the market it's compared against here, so this isn't a case where the salary story and the employer story point to the same explanation the way they often do for other certifications.

Is a TOGAF Mention Usually a Real Requirement?

Rarely, and a large share of postings don't even say. Of the 350 postings that mention TOGAF, only 131 (37.4%) use wording specific enough within 160 characters of the mention to classify as required or preferred; the other 219 (62.6%) don't specify either way. Within the 131 that are classified, just 16 (12.2%, roughly 1 in 8) state TOGAF as a required qualification. The other 115 (87.8%) call it preferred.

That high unspecified share means the required rate above is closer to a floor than a precise number: some of those 219 unspecified mentions are almost certainly hard requirements phrased in ways that don't classify cleanly, and some are throwaway lines in a long list of nice-to-haves. What's not ambiguous is the direction: even read generously, a hard TOGAF requirement is the exception, not the rule, across Solutions Architect, Cloud Architect, and Security Architect postings.

What Does TOGAF Actually Pair With, Cloud Skills or Security Certifications?

Both, but not in the same place. Look at individual skills and TOGAF-mentioning postings read like any other multi-cloud architecture role: AWS appears in 52.6% of them, Azure in 52.3%, and Google Cloud in 28.6%, all three major public clouds inside the top four skills, alongside Agile (30.0%) and Stakeholder Management (26.9%).

Skill	Share of TOGAF-Mentioning Postings
AWS	52.6%
Azure	52.3%
Agile	30.0%
Google Cloud	28.6%
Stakeholder Management	26.9%
Automation	22.9%
Data Analysis	21.4%
Security Architecture	18.9%

Look at which other certifications show up alongside TOGAF, though, and the picture tilts toward governance and security rather than any single cloud vendor. CISSP leads at 18.3% of TOGAF mentions, more than double the next closest credential, and well ahead of any cloud-specific certification like AWS Certified Solutions Architect - Associate.

Certification	Share of TOGAF-Mentioning Postings
CISSP	18.3%
AWS Certified Solutions Architect - Associate	6.9%
CCSP	6.3%
CISM	4.9%
CompTIA Security+	4.6%
Azure Solutions Architect Expert (AZ-305)	3.7%

That split fits what TOGAF actually is. It's a vendor-neutral framework for governing enterprise IT decisions, not a technical certification tied to a specific cloud platform, so postings that name it tend to also ask for a governance-and-risk credential like CISSP rather than a second cloud-specific one. The multi-cloud skill list backs that up too: a posting built entirely around one cloud platform's own certification path usually doesn't also demand fluency in the other two the way TOGAF-mentioning postings do.

Putting the TOGAF Numbers to Work in Your Search

If you're weighing whether to study for TOGAF, the data above points toward role fit over hype. It shows up at broadly similar rates across Solutions Architect, Cloud Architect, and Security Architect postings rather than belonging to one of them, and it's asked for more often as a nice-to-have than gated on. Given how often it appears alongside CISSP, candidates targeting governance-heavy architecture roles likely get more mileage pairing the two than treating TOGAF as a standalone signal.

To prepare for interviews where enterprise-architecture governance or multi-cloud tradeoffs come up, practice with AI mock interviews that simulate stakeholder and architecture-tradeoff conversations rather than framework trivia. The Question Bank is a faster way to drill topics like stakeholder management, cloud architecture, and security architecture that show up repeatedly in TOGAF-adjacent postings. If your cloud fundamentals need work before the interview, InterviewStack's interactive courses cover the underlying cloud-platform concepts these postings actually test for. When you're ready to apply, browse current openings across all three roles, or filter directly to Solutions Architect postings that ask for Stakeholder Management or Cloud Architect postings built around AWS.

FAQ

Q. What percentage of architect postings ask for TOGAF?

TOGAF appears in 5.6% of postings across the three roles it maps to most directly: Solutions Architect, Cloud Architect, and Security Architect (350 of 6,286 postings analyzed over a 90-day window on the InterviewStack.io job board).

Q. Which role is most likely to mention TOGAF?

Solutions Architect, though only slightly. TOGAF appears in 6.1% of Solutions Architect postings, compared with 5.5% of Security Architect postings and 4.0% of Cloud Architect postings, a range of about 0.73x to 1.10x relative to the overall 5.6% rate.

Q. Is TOGAF usually required or just preferred?

Preferred, when postings say anything at all. Of the 350 TOGAF mentions, only 131 (37.4%) use wording specific enough to classify as required or preferred; the rest don't specify either way. Within that classified group, just 12.2% (roughly 1 in 8) call TOGAF required, and 87.8% call it preferred.

Q. Do TOGAF-mentioning postings pay more than similar postings that don't mention it?

No. Postings that mention TOGAF advertise a median US base salary of $161,475, about 9.1% below the $177,650 median for postings in the same three roles that don't mention it. That gap holds at mid-level too (-7.6%), the only seniority band with enough TOGAF-mentioning salary data to report. Neither of the usual explanations account for it: TOGAF-mentioning postings' average seniority level is nearly identical to the rest of the market (seniority is inferred from title keywords, and titles with no explicit level word default to mid-level, so this comparison is directional rather than precise), and TOGAF actually over-indexes in Solutions Architect, the highest-paying of the three roles in scope, which should push the comparison up, not down.

Q. Who is hiring for TOGAF?

Mostly consulting firms and enterprise software vendors, not government contractors. Among the top 12 employers asking for TOGAF, consulting and IT-services firms account for about 42% of mentions and software vendors another 26%, while the two federal contractors in the table account for about 17%. Non-government employers outnumber federal contractors in this table by nearly 5 to 1.

Q. What certification most often appears alongside TOGAF?

CISSP, by a wide margin. 18.3% of postings that mention TOGAF also mention CISSP, more than double the next closest certification and well ahead of any cloud-vendor certification like AWS Certified Solutions Architect - Associate (6.9%).

Q. Does TOGAF show up in entry-level postings?

Never in this dataset. None of the 350 TOGAF-mentioning postings are entry-level, though that's not unique to TOGAF: only 2.2% of non-TOGAF postings in this same three-role scope are entry-level either, since Solutions Architect, Cloud Architect, and Security Architect are inherently senior-leaning titles.

TOGAF Is a Governance Credential, Not a Salary Signal

TOGAF's employer list, its modest and fairly even demand across three architect roles, and its pairing with CISSP rather than a second cloud certification all point to the same place: it signals enterprise-architecture governance fluency, the kind of work consultancies sell and enterprise software vendors build around, not a scarce technical skill that commands a premium on its own. The pay comparison backs that reading up rather than complicating it. Postings that ask for it advertise a bit less, not more, and that gap doesn't unwind under either the seniority or role-mix checks that usually explain a certification's salary story in this dataset. Worth holding if enterprise-architecture governance is the actual career target; not worth chasing for a pay bump.