Enterprise Architect Job Description Template 2026

Last updated: July 7, 2026

An enterprise architect owns the technology strategy for an entire organization, aligning every major system, platform, and IT investment with the business roadmap three to five years out, and earns $150,000 to $230,000 base in the U.S. in 2026. That is a different job from a solutions architect, and the confusion between the two is the single biggest reason enterprise architect roles sit open for months. The template below scopes the real thing.

Two companies post an “Enterprise Architect” opening in the same week. One wants a person to own the technology direction for a 4,000-employee company still digesting three acquisitions. The other wants a senior engineer to draw cleaner diagrams for one product team. Same two words. Both sit at the top of the posting. The gap between those jobs runs about $80,000 in comp and close to eight years of experience, and the description almost never says which one it is.

So the wrong people apply. The genuine enterprise architects, the ones who have actually steered a portfolio through a merger, read the first few bullets, decide the company does not really have an EA function, and move on. What is left in the pile is a mix of solutions architects, frustrated senior developers, and consultants who can quote TOGAF chapter and verse but have never owned a roadmap that survived a budget cut. Three months later the req is still open. Nobody can say why. Nobody stops to notice that the posting described two different jobs at once, promised the salary of the bigger one, and committed to the scope of neither, which is the actual reason it will not close.

I’m Mike Carter. Enterprise architecture roles cross my desk at KORE1 more than almost any other senior title, and they are the ones hiring managers scope worst, because the role sits at the seam between business and technology where job descriptions go to get vague. We collect a placement fee when you hire through us, so read the recommendations with that in mind. The template and the scoping logic work the same whether you run the search with a partner or on your own. If you want the broader picture first, our IT staffing services practice places these roles across 30+ U.S. metros.

Enterprise Architect vs Solutions Architect vs Domain Architect

An enterprise architect works at the organization level on a three-to-five-year horizon, a solutions architect works at the project level on a single business problem, and a domain architect goes deep on one technology area like data or security.

This is the distinction the whole hire turns on. Miss it, and the shortlist comes back wrong. Every time.

The enterprise architect looks across the whole company. What systems do we run, which ones overlap, what do we sunset, where does the next three years of spend go, and does any of it move the business where leadership says it needs to be. They write the standards and reference architectures that everyone else builds inside of. They sit with the CIO and the CFO as often as with engineers. According to The Open Group, the body behind TOGAF, an enterprise architect sets “strategies, policies, standards and practices” at the cross-organizational level. That is the job in one line.

A solutions architect lives one layer down. Give them a defined problem, a payments platform to redesign, a Salesforce-to-billing integration to untangle, and they own the design end to end until it ships. Their authority stops at the edge of the project. If you are hiring for that, you want the solutions architect job description template, not this one. A domain architect goes narrower still. Deep in one area. A data architect owning the data platform is the common example.

Here is how the three compare on the axes that actually change who applies.

Read the middle rows before you write the posting. Out loud. If the role you have in mind reports to a delivery lead and lives inside one project, you are not hiring an enterprise architect. You are hiring a solutions architect and paying an enterprise architect’s salary to find out.

The Four Domains an Enterprise Architect Actually Owns

The reason the role is hard to scope is that it spans four architecture domains at once, the four that TOGAF and most enterprise frameworks organize around. Four, not one. A strong EA is fluent in all four. Expert in one or two. A posting that names which domains matter most for your org will pull a sharper pool than one that lists “enterprise architecture experience” and hopes. Name the domains.

Business architecture. Capability maps, value streams, operating-model design. This is the domain most technologists underrate and most EA searches fail on. The architect has to sit with a VP of Operations, understand what the business is trying to become, and translate that into a technology picture. No code here. Just the ability to model how a company actually works and where the friction lives.

Data architecture. How data moves, where it lives, who owns it, and how the organization stops rebuilding the same customer record in nine systems. In 2026 this is where a lot of EA time goes, because every AI initiative that leadership is excited about dies quietly on top of data nobody governed. Snowflake, Databricks, a lakehouse strategy, master data management. If your EA will own it, say so. Plainly.

Application architecture is the third. The full portfolio of applications, the overlaps, the shadow IT, the six tools that do roughly the same thing because three different teams bought them in three different years. The EA runs application portfolio management, decides what gets invested in versus retired, and often uses Gartner’s TIME model, tolerate, invest, migrate, or eliminate, to make those calls defensible to a budget committee.

Technology architecture. The infrastructure and platform layer. Cloud strategy across AWS, Azure, or GCP, integration patterns, the standards that keep engineering teams from each inventing their own way to do the same thing. This is the domain closest to a solutions architect’s world, which is exactly why the two roles get conflated so often that hiring managers lose the ability to tell their own postings apart. The difference is simple. The EA sets the guardrails. The solutions architect builds inside them.

One more thing lives on top of all four. Governance. The architecture review board, the decision records, the standards that have teeth because leadership backs them. An EA without governance authority is a person writing documents nobody has to read. If your org is not ready to give the role real weight, hire a senior architect for a specific problem instead and save the money.

Enterprise Architect Job Description Template

Here is the block. Take it, replace the bracketed prompts with your real scope, and delete the italic notes before the posting goes live. Those notes are for whoever fills it in, not for candidates. It assumes a senior enterprise architect inside an established IT organization. Dial the ownership language up for a chief or head-of role, down for your first EA hire.

Where Enterprise Architect JDs Go Wrong

I read a lot of these before a search opens. The failure patterns are consistent, and each one bleeds candidates in a way the hiring manager rarely notices until the req has been open for two months. Five show up the most.

The solutions architect role wearing an enterprise title. The most common one. By a mile. The responsibilities describe designing a system, integrating two platforms, shipping a project. That is solutions architecture. Dressing it in the enterprise title does two things, both bad. Real EAs skip it because there is no cross-org scope. And the solutions architects who apply expect enterprise-architect money for solutions-architect work. Scope the posting to the actual altitude of the job.

Second failure. Framework theater with no delivery accountability. The JD reads like a TOGAF study guide, ArchiMate models, Zachman rows, governance boards, and never once mentions a business outcome the architecture is supposed to produce. Strong EAs have watched a pure-framework architecture practice get shut down in a downturn because it could not point to a dollar it moved. They want to know the role connects to delivery. Name the transformation, the migration, the AI program the architecture actually serves. Give it a target.

Third, no executive sponsor and no authority. An enterprise architect with no seat near the CIO and no power over the review board is a librarian for diagrams. Nothing more. The posting that describes influence “through relationships” and never names who the role reports to is telling experienced candidates the function has no teeth. If leadership will not back the standards, the best EAs will not take the job, because they have lived that movie before.

Certification alphabet soup. TOGAF and Zachman and every cloud professional cert and a PMP, all required. That combination describes nobody real. The candidates who could do the work read a stacked cert wall and assume the rest of the JD was written by someone who has never hired this role. List one framework as preferred and weigh the actual track record instead.

Last, all technology and no business language. A JD for a role whose entire point is business-technology alignment, and every bullet is about platforms and none about outcomes. The person who can sit across from a VP of Operations and model an operating change reads that posting and hears a role that will never get out of the infrastructure weeds. Write at least half the responsibilities in the language of the business, because that half is the harder half to hire for.

Frameworks and Tools to Name in the Posting

Naming the specific frameworks and tools your org runs on does two things. It filters for people who have used them, and it signals to a strong EA that your practice is real rather than aspirational. Vague beats specific in exactly zero cases here.

Frameworks. TOGAF is the default in most enterprises, useful as a common vocabulary even when the working sessions ignore half of it. Zachman if your org thinks in that grid. FEAF if you are in or adjacent to federal government. ArchiMate is the modeling language, not a framework, and it is worth naming if your team actually models in it. Name the one you use in practice. Skip the ones that live on an old slide.

EA management and modeling tools. LeanIX (now part of SAP), Ardoq, BizzDesign, MEGA HOPEX, and Sparx Enterprise Architect are the ones that come up most in our searches. ServiceNow’s application portfolio management module counts too if that is where your inventory lives. If the architect will own the tool, say which one. A candidate who has run LeanIX for three years is a different hire from one who has only seen it in a demo.

The platforms the architecture spans. Name them. AWS, Azure, or GCP for cloud. SAP, Salesforce, Workday, ServiceNow for the enterprise application core. Snowflake or Databricks if data architecture is central. The specific list tells a candidate whether your landscape is a modern cloud estate, a legacy consolidation project, or the messy middle most enterprises actually live in.

Enterprise Architect Salary Benchmarks 2026

Compensation data for this title is noisier than for most. The noise is informative. The aggregators disagree by a wide margin because they measure different things and pool different roles. Sort out which number means what before you set your band.

Now the aggregators, and why they scatter. Salary.com puts the base average near $128,000 with a typical band of roughly $119,000 to $138,000, because it reports base pay and pools junior titles in. PayScale lands around $160,000. Indeed sits near $155,000 from posted listings. Glassdoor headlines about $208,000, but that is total pay with bonus and profit sharing folded in, not base. Read the label before you read the number. The spread between a $128,000 base figure and a $208,000 total-pay figure is not two different jobs. It is one enterprise architect role measured two different ways by two aggregators using two different methodologies. Same person. Two numbers.

The Bureau of Labor Statistics has no line for enterprise architect specifically. Its closest category, computer network architects, reports a $130,390 median wage for 2024 and projects 12% growth through 2034, faster than the average across all occupations. Treat that as a floor and a direction, not a match, since it skews toward network design and pulls the median down. Different job, mostly. Where the role sits geographically moves the band more than most hiring managers expect. A senior EA in San Francisco, New York, or Seattle runs 15% to 25% above the same role in Denver, Atlanta, or most of the Midwest, and the candidates who could take either offer usually run that comparison themselves before a recruiter ever finishes the first call. KORE1 places these roles across 30+ U.S. metros, and the full level-by-level breakdown lives in our enterprise architect salary guide.

Adapting the Template by Company Stage

The block above is a skeleton. Where your company sits changes which parts carry the weight.

Your first enterprise architect. If nobody has held this seat before, the role is as much about standing up the function as running it. Say that. This person writes the first standards, builds the review board from nothing, and spends the first year earning the authority the role needs to work. That is a specific temperament. Someone who likes a blank page, and who can build political capital fast, faster than the org expects, before the goodwill that comes with being the new hire quietly runs out. Lead with the mandate and name the executive backing it, because without that backing the job is impossible and the right candidate knows it.

A mature EA practice. If there is already an architecture team, a framework in use, and a review board, the role narrows and deepens. Now you are hiring for a domain gap or a leadership layer. Name the existing practice, the tool, the framework, and the specific gap this hire fills. A strong EA reads that specificity as a sign the function is real, and reads a vague enterprise post as a sign it is not.

What Hiring Managers Ask Before Posting an EA Role

Enterprise architect or solutions architect, which one am I actually filling?

Scope decides it, not the title on the req. An enterprise architect owns technology strategy across the whole organization on a multi-year horizon; a solutions architect owns the design of one system or project until it ships. If the work lives inside a single project and reports to a delivery lead, you want a solutions architect and should scope and pay it as one. If the work spans business units and sets standards others build within, it is an enterprise architect. Write the responsibilities first, and the right title falls out of them.

Does an enterprise architect still build anything, or is it all strategy decks?

Mostly not hands-on code, but the credible ones stay close enough to delivery to keep their judgment sharp. An EA produces reference architectures, standards, roadmaps, and decision records, not pull requests. The trap is the pure-slides architect who has drifted so far from real systems that engineering stops trusting the guidance. The best EAs can still read a design doc, question a technology choice on the merits, and prototype an idea when it matters. Ivory-tower distance is the failure mode to screen for.

How much experience should an enterprise architect posting require?

Ten to fifteen years for most true EA roles, with at least four spent owning architecture above the single-project level. The breadth the job needs, business fluency plus technical depth plus the political skill to make standards stick, takes that long to build. Fewer years usually means a strong solutions architect who has not yet operated at organization scope. Years are a proxy, though. The sharper screen is asking a candidate to walk through a portfolio or transformation they steered, what went wrong, and what they changed because of it.

Is TOGAF certification a real requirement or resume decoration?

It depends entirely on whether your organization runs on a framework or just name-drops one. If your practice genuinely uses TOGAF or FEAF day to day, listing it as preferred is fair and filters usefully. If it does not, requiring the cert screens for test-takers over practitioners and tells strong candidates you value the credential over the work. Weight the track record first. A TOGAF certificate with no delivery behind it is decoration, and experienced EAs know it reads that way.

What salary range should I put on an enterprise architect posting?

$150,000 to $230,000 base covers most senior enterprise architect roles in 2026, with chief and head-of positions climbing higher on total comp. Post the range. A growing list of states, California, Colorado, New York, and Washington among them, now requires it, and even where it is optional, senior candidates filter out postings with no comp signal. Use a $40,000 spread. It reads as leveling flexibility, not indecision, and it screens out the mismatches before anyone spends four rounds discovering the gap.

Should I hire an enterprise architect as a contractor or a direct hire?

Direct hire for the standing seat, contract for a bounded transformation. Enterprise architecture compounds through institutional knowledge and the trust to make standards stick, and a six-month contractor rarely builds either. Where a contract fits is a defined program with an end date, a post-merger consolidation, an ERP migration, a cloud target-state design, where you want senior depth without a permanent line on the org chart. Contract-to-hire is the middle path when you want to see the work before committing. KORE1 staffs these roles as direct hire, contract, and contract-to-hire, and the right model tracks the shape of the work.

Next Steps

Take the template. Make it yours. Pick the level, name the domains that matter, list the framework and tools you actually run, post the range, and cut anything that does not describe your hire. A short, specific enterprise architect JD beats a long generic one in every search we run.

If you want a second read on a posting that has been open too long, help leveling a role that sits between solutions and enterprise architecture, or a shortlist of people who have genuinely owned a portfolio, that is our desk. Reach out to a recruiter on our team. KORE1 places enterprise architects and senior IT talent across 30+ U.S. metros through direct hire, contract, and contract-to-hire, with an average time-to-fill of 17 days and 92% of those hires still in seat a year later. When the shortlist is in front of you, our enterprise architect interview questions help separate the strategists from the diagram collectors, and the full guide to hiring an enterprise architect walks the search end to end.