Security architect job description: annotated template
How to write a security architect job description: main focus, mandate, responsibilities, skills, conditions and an annotated template to adapt block by block.
A vague security architect job description attracts two kinds of applicants: engineers who want the title before they have designed anything, and consultants looking for one more assignment. Experienced architects simply move on. This annotated template helps you describe the role precisely enough for the right person to recognise themselves, and take the time to reply.
What a security architect reads first
A security architect in post gets approached regularly and reads job ads with a critical eye. They look for answers to a few questions, usually in this order:
- What is the main focus? Infrastructure and network, cloud, or applications.
- What is the mandate? Can they approve, reject or reshape a project, or only give advisory opinions?
- When do they step in? At the design stage, or the day before go-live.
- Who do they work with? The CISO, IT architects, product teams, the CTO.
- What is the starting point? Foundations to build, a patchwork estate to rationalise, a cloud journey under way.
If these points are not settled internally yet, start with our guide to hiring a security architect, which covers the three profiles behind the same title and how to assess them. The job description translates that scoping; it does not replace it.
Pick the main focus before you write
The most common mistake is the ad that asks for an expert in everything: network, cloud, identity, secure development, compliance and project management. That person rarely exists, and those who come close know it. Commit to one focus, even if you expect a reasonable level on the rest.
| Focus | Responsibilities to highlight | Example titles |
|---|---|---|
| Infrastructure and network | Segmentation, identity, remote access, hardening the existing estate | "Infrastructure Security Architect" |
| Cloud | Environment structure, guardrails, reference patterns for teams | "Cloud Security Architect" |
| Application | Service design, authentication, APIs, development pipeline | "Application Security Architect" |
| Cross-functional | Shared standards, project support, foundations roadmap | "Security Architect" |
A cross-functional role is perfectly reasonable in a mid-sized company. If that is your case, state the area where you expect depth and the rough split of time ("mostly project support, a smaller share on standards"). It says far more than a flat list of duties.
The annotated template
Here is a structure to adapt. Each block is followed by a note on what it should contain and the traps to avoid.
1. The title
- Example: "Cloud Security Architect, Lyon, hybrid".
- Note: the focus and the location are enough. Avoid "Senior Cybersecurity Expert" or "Security Champion": nobody searches for those, and they say nothing about the role.
2. The context
- Your business in two sentences and the state of your IT estate: recent foundations, legacy systems, migration under way.
- The projects behind the opening: a new internet-facing service, a cloud journey, an identity overhaul, requirements from a client or a regulation.
- The size of the security team and of the technical teams, in qualitative terms.
- The reporting line: CISO, CTO or an enterprise architecture function.
- Note: an architect wants to know whether they are coming to build or to bring order. Both are attractive, but not to the same people. Say it plainly.
3. The mandate
This is the block most often missing, and the one the best candidates read most carefully.
- Where the architect sits in the project lifecycle: architecture board, design reviews, sign-off before go-live.
- What they can decide alone, what they propose, what they escalate to the CISO or management.
- How exceptions are handled: who accepts residual risk, and how it is recorded.
- Note: one sentence often does it: "The security architect sits on the architecture board and can block internet-facing projects." If the opinion is only advisory, say so too. A candidate who later discovers they have no leverage leaves quickly.
4. Responsibilities
For a cloud focus, for example:
- Support projects from the design stage: risk analysis, target architecture, prioritised recommendations.
- Define and maintain reusable reference patterns (exposing a service, secrets management, user and service authentication).
- Evolve the structure of cloud environments and the guardrails applied across the organisation.
- Document architecture decisions with their reasons, alternatives and accepted residual risk.
- Advise the CISO on the foundations roadmap and investment priorities.
Note: four to six responsibilities, ordered by how much time they take. Drop "contribute to" when the role actually owns the topic. And keep operational work (day-to-day administration, alert handling) out of an architect description: that is a different job.
5. Technical environment
- The main building blocks: directory and identity federation, cloud providers, network, logging and detection tooling.
- Development and deployment practices, if the role has an application side.
- Note: present these as context. An architect thinks beyond any one vendor; an ad that demands three specific products attracts tool experts, not designers.
6. The profile
Keep two short, separate lists.
Must have:
- Has designed or evolved architectures in production, and can explain the choices.
- Can run a structured risk analysis starting from a business need.
- Solid fundamentals: identity and access, segmentation, encryption and secrets management, logging.
- Writes a clear architecture document and persuades teams that do not report to them.
Nice to have:
- Experience with EBIOS Risk Manager, the method published by ANSSI, or with a threat modelling practice.
- Experience in a second area (cloud for an infrastructure profile, development for a cloud profile).
- Knowledge of a regulatory framework that applies to you (NIS2, DORA, public sector accreditation).
- A recognised certification in security architecture or security management.
Note: phrase skills as observable actions. "Can say no to a project while offering an acceptable alternative" says far more than "excellent interpersonal skills". Our article on soft skills in cybersecurity helps describe these qualities without empty phrases.
7. Conditions
- Salary range.
- Remote work policy and how often travel to other sites is expected.
- Training budget and time set aside for keeping up to date.
- Note: architect pay varies widely with focus, sector, region and the scope of the mandate. A realistic range beats "depending on profile", which puts off candidates who already have a job, and that is most of them.
8. The hiring process
- The number of stages, their length and the nature of the case study.
- Note: see the dedicated section below.
Phrases that drive candidates away
- "Responsible for the security of the entire IT estate": without a mandate or resources, that is accountability without leverage. An experienced architect reads it as a future scapegoat.
- Mixing architect and project manager: if the job is mostly tracking schedules and suppliers, call it a security project manager.
- A list of ten certifications: it filters on credentials, not on design ability. Our look at certifications in hiring explains why they belong in the "nice to have" column.
- A required number of years: what matters is design work actually delivered. An engineer who designed their company's identity foundations may be readier than an "architect" who has only reviewed documents.
- Empty jargon: "passionate", "exciting environment", "true conductor". The candidate wants to know which projects they will work on in their first six months.
Announce the case study
An architect knows an interview alone does not show how they think. Announcing a realistic case study shows the team knows what it is looking for. A typical process:
- A first conversation about the candidate's background, the architectures they have designed and the decisions they are proudest of.
- A case study prepared in advance, on a fictional scenario with no sensitive data: a new service to design, with its business constraints.
- A presentation to a panel with a member of the security team, a technical lead and, ideally, someone from a project team.
- A final conversation with the manager, often the CISO, about the mandate and governance.
State the expected preparation time in the ad, to respect the schedule of someone already in a job. Our guide to assessing cybersecurity skills explains how to build a scoring grid shared by the panel. The same structure works for other senior roles, as our CISO job description shows.
Checklist before publishing
- The focus appears in the title and is reflected in the responsibilities.
- The mandate is described: boards, approval power, exception handling.
- The starting point of the IT estate and the projects behind the opening are explained.
- The must-haves fit in four or five lines, phrased as actions.
- No day-to-day operational duties have crept into the list.
- A salary range is shown.
- The case study and its preparation time are announced.
In short
A good security architect job description commits to a focus, describes a real mandate, explains the starting point, separates must-haves from nice-to-haves and announces a case study. That is what persuades a well-settled professional to take the time to reply.
Opening a security architect role and want to scope it with a technical eye? At Cyber Recrut, a recruiter and a security practitioner build the job description with you, then our shortlisted candidates prove their skills on hands-on labs. See how we work or share your hiring need.