Senior/Staff DevSecOps Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the job posting.
Key sections:
- About The Company (company description)
- Mission | On Site | Full Time | U.S. Citizenship Required / No Active Clearance Required (metadata)
- Role Summary (description)
- What You'll Do (list of responsibilities)
- Who You Are (qualities)
- Must Have (requirements)
- Nice to Have (preferred)
- Tech Environment (You Might Work With) (tools)
- Security / Work Environment (clearance requirement)
- Benefits (list)
- Compensation Range: $159K - $263K (pay)
We need to decide which sections to output. The instruction says: use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can adapt: we have About the Company, Role Summary (maybe About the role), What You'll Do (Responsibilities), Who You Are (maybe Qualifications/Skills), Must Have (Requirements), Nice to Have (maybe Skills), Benefits, Pay (Compensation Range). Also maybe Tech Environment could be under Skills? But we can include as a separate section if it has substantive content. The instruction: Prefer a few substantive sections over many thin ones. So we might combine some.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated, Pay is stated (Compensation Range). Schedule? Not explicitly stated; there is "On Site | Full Time". That's schedule info: Full Time, On Site. Could be considered schedule. But we might not create a Schedule section unless we have real specific content. The posting includes "Mission | On Site | Full Time | U.S. Citizenship Required / No Active Clearance Required". That gives location (On Site) and employment type (Full Time). That's schedule/location info. Could be placed in a short
maybe under a heading like "About the role"? But we have to avoid filler.
We need to preserve all substantive information. So we need to include the company description, role summary, responsibilities list, who you are, must have, nice to have, tech environment, security/work environment, benefits, compensation.
We need to format using
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to avoid boilerplate: EEO, equal opportunity, accommodation, etc. Also remove duplicated lines.
We need to not repeat job title as heading (not present). No Job ID.
We need to output only HTML fragment.
Let's craft sections:
-
About the Company
with containing the company description (the paragraph about America under cyber attack, Twenty founded 2024, etc.)
-
Role Summary
with containing the role summary paragraph.
-
Responsibilities
with - each bullet from "What You'll Do". Need to preserve all bullet points.
-
Qualifications
maybe combine "Who You Are" and "Must Have"? But we need to follow instruction: use headings for Qualifications, Skills, etc. Could have separate sections: Qualifications
for "Who You Are" (traits) and Requirements
for "Must Have". And maybe Skills
for "Nice to Have" and Tech Environment? But we need to avoid many thin sections. Perhaps combine "Who You Are" and "Must Have" into Requirements? But they are distinct: Who You Are are soft traits, Must Have are hard requirements. Could put both under Requirements
with two sub-lists? But instruction says use - for any list of duties/requirements/benefits. Could have multiple lists under same heading.
Better: Use headings: Responsibilities, Requirements, Benefits, Pay. And maybe About the Company and Role Summary as prose.
But we need to preserve all substantive info; we can include Nice to Have and Tech Environment under Requirements or Skills. Let's decide:
We'll have:
About the Company
...
Role Summary
...
Responsibilities
...
Requirements
Who You Are:
...
Must Have:
...
Maybe also include Nice to Have and Tech Environment under Requirements as additional lists.
But we must not create sections with filler. All have content.
We also need Benefits and Pay sections.
Benefits: we have a list: Health..., Family..., Vacation..., Retirement..., etc. We'll put as .
Pay: Compensation Range: $159K - $263K. We'll put as maybe under
Pay
.
Schedule: we have On Site, Full Time. Could be included under Role Summary or a short paragraph. But we could add a Schedule
with On Site, Full Time
. However instruction says only create Schedule section if posting actually states them. It does state On Site and Full Time. So we can include.
But we also have U.S. Citizenship Required / No Active Clearance Required and Security clearance eligibility note. That could be under Requirements or a separate section like Security Clearance. But we can incorporate into Requirements.
We need to remove boilerplate: EEO, equal opportunity, accommodation, etc. Also remove duplicated lines: there is a line about "Due to U.S. government contract and security requirements, this role is limited to U.S. citizens. Some positions may also require eligibility to obtain and maintain a U.S. Government security clearance. Any active clearance requirement will be listed in the role description." That's somewhat boilerplate but it's substantive about citizenship and clearance. We'll keep that info but maybe condense.
We also need to remove the line "If this role sounds like you, apply and share with us your interest" (application instruction). Also remove "Twenty is an equal opportunity employer..." etc.
Now let's extract content.
Company description:
"About The Company America is under sustained cyber attack. Our adversaries infiltrate our networks, steal our IP, and degrade the digital infrastructure that modern life runs on. They’ve learned—correctly—that those attacks rarely produce consequences. Twenty was founded to change that, by making our adversaries think twice before they attack us. Our vision is American and allied primacy in cyberspace—a future where they cannot contest us, deterrence is assured, and the free world remains secure. Founded in 2024, Twenty Technologies (www.twenty.io) industrializes offensive cyber operations for the U.S. and its allies. Headquartered in Arlington, Virginia, Twenty has raised $168M from Khosla Ventures, Accel, Caffeinated Capital, Friends & Family Capital, Point72 Ventures, General Catalyst, and In-Q-Tel."
We'll put that in a .
Role Summary:
"Role Summary You'll build and own the security infrastructure that keeps Twenty's engineering systems safe without slowing engineers down. This role spans runtime security, access control, secrets management, compliance, and CI/CD hardening — but it's equally about making security the path of least resistance. You'll embed with our engineering teams, design secure-by-default foundations, and build the tooling and automation that lets developers move fast without cutting corners. You'll report directly to the VP of Engineering and operate as a shared function across our product teams."
We'll put that in a
.
Responsibilities (What You'll Do):
List:
- Own runtime security and vulnerability management across cloud and container environments, including triage, prioritization, and remediation tracking.
- Design and enforce identity and access management (IAM) across AWS and internal systems — least-privilege by default.
- Own secrets and credentials management: policies, tooling, rotation, and developer workflows that make doing the right thing easy.
- Lead security incident response: detection, containment, root cause analysis, and durable remediation.
- Manage AWS Organization structure, account boundaries, SCPs, and guardrails.
- Harden and maintain CI/CD pipelines, embedding security scanning and policy enforcement into the software delivery lifecycle.
- Drive compliance efforts — own the evidence, controls, and remediation work to meet and maintain relevant frameworks.
- Build and maintain secure-by-default templates for repos, pipelines, and infrastructure modules.
- Reduce friction through automation: certificate issuance, secrets access, policy-as-code, and developer-facing tooling.
- Produce lightweight, practical security guidance that engineers actually use.
- Shape the direction of the DSO function as it scales, and contribute to hiring and team-building as we grow.
We'll put each as
- .
Who You Are (traits):
- You believe security should be a force multiplier for engineering, not a gatekeeper.
- You take ownership end-to-end: from identifying a risk to designing the control to shipping the fix.
- You bring high judgment to tradeoffs — you know when to enforce hard controls and when friction kills adoption.
- You communicate clearly with both engineers and non-technical stakeholders, and you translate risk into plain language.
- You prefer automation over policy: if an engineer has to do something manually to stay secure, you see that as a bug.
- You hold a high bar for reliability and auditability in the systems you build.
- You're self-directed and thrive in an environment where the function is new and you're defining it.
We'll put as
under a heading maybe "Who You Are". But we could incorporate into Requirements.
Must Have (requirements):
- 8+ years in DevSecOps, platform security, or a closely related security engineering role.
- Deep hands-on experience with AWS — IAM, SCPs, Organizations, security services (GuardDuty, Security Hub, CloudTrail, etc.).
- Strong IaC experience with Terraform; you've used it to enforce security controls, not just provision infrastructure — and you've layered in policy-as-code tooling (e.g., OPA, Checkov, tfsec) or continuous compliance checks (e.g., AWS Config Rules) to catch drift and misconfigurations.
- Experience owning secrets management end-to-end in a production engineering environment.
- Proven track record designing and hardening CI/CD pipelines (we use GitHub Actions).
- Hands-on experience with container security, including image scanning and runtime controls.
- Experience leading or meaningfully contributing to a compliance program; CMMC Level 2 (or NIST SP 800-171) experience strongly preferred.
- You've run incident response — you've been on call, you've led the post-mortem, and you've shipped the fix.
- Strong communication skills and the ability to drive security adoption
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the job posting. Key sections: - About The Company (company description) - Mission | On Site | Full Time | U.S. Citizenship Required / No Active Clearance Required (metadata) - Role Summary (description) - What You'll Do (list of responsibilities) - Who You Are (qualities) - Must Have (requirements) - Nice to Have (preferred) - Tech Environment (You Might Work With) (tools) - Security / Work Environment (clearance requirement) - Benefits (list) - Compensation Range: $159K - $263K (pay) We need to decide which sections to output. The instruction says: use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can adapt: we have About the Company, Role Summary (maybe About the role), What You'll Do (Responsibilities), Who You Are (maybe Qualifications/Skills), Must Have (Requirements), Nice to Have (maybe Skills), Benefits, Pay (Compensation Range). Also maybe Tech Environment could be under Skills? But we can include as a separate section if it has substantive content. The instruction: Prefer a few substantive sections over many thin ones. So we might combine some. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated, Pay is stated (Compensation Range). Schedule? Not explicitly stated; there is "On Site | Full Time". That's schedule info: Full Time, On Site. Could be considered schedule. But we might not create a Schedule section unless we have real specific content. The posting includes "Mission | On Site | Full Time | U.S. Citizenship Required / No Active Clearance Required". That gives location (On Site) and employment type (Full Time). That's schedule/location info. Could be placed in a short
maybe under a heading like "About the role"? But we have to avoid filler. We need to preserve all substantive information. So we need to include the company description, role summary, responsibilities list, who you are, must have, nice to have, tech environment, security/work environment, benefits, compensation. We need to format using
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to avoid boilerplate: EEO, equal opportunity, accommodation, etc. Also remove duplicated lines.
We need to not repeat job title as heading (not present). No Job ID.
We need to output only HTML fragment.
Let's craft sections:
-
About the Company
with containing the company description (the paragraph about America under cyber attack, Twenty founded 2024, etc.)
-
Role Summary
with containing the role summary paragraph.
-
Responsibilities
with - each bullet from "What You'll Do". Need to preserve all bullet points.
-
Qualifications
maybe combine "Who You Are" and "Must Have"? But we need to follow instruction: use headings for Qualifications, Skills, etc. Could have separate sections: Qualifications
for "Who You Are" (traits) and Requirements
for "Must Have". And maybe Skills
for "Nice to Have" and Tech Environment? But we need to avoid many thin sections. Perhaps combine "Who You Are" and "Must Have" into Requirements? But they are distinct: Who You Are are soft traits, Must Have are hard requirements. Could put both under Requirements
with two sub-lists? But instruction says use - for any list of duties/requirements/benefits. Could have multiple lists under same heading.
Better: Use headings: Responsibilities, Requirements, Benefits, Pay. And maybe About the Company and Role Summary as prose.
But we need to preserve all substantive info; we can include Nice to Have and Tech Environment under Requirements or Skills. Let's decide:
We'll have:
About the Company
...
Role Summary
...
Responsibilities
...
Requirements
Who You Are:
...
Must Have:
...
Maybe also include Nice to Have and Tech Environment under Requirements as additional lists.
But we must not create sections with filler. All have content.
We also need Benefits and Pay sections.
Benefits: we have a list: Health..., Family..., Vacation..., Retirement..., etc. We'll put as .
Pay: Compensation Range: $159K - $263K. We'll put as maybe under
Pay
.
Schedule: we have On Site, Full Time. Could be included under Role Summary or a short paragraph. But we could add a Schedule
with On Site, Full Time
. However instruction says only create Schedule section if posting actually states them. It does state On Site and Full Time. So we can include.
But we also have U.S. Citizenship Required / No Active Clearance Required and Security clearance eligibility note. That could be under Requirements or a separate section like Security Clearance. But we can incorporate into Requirements.
We need to remove boilerplate: EEO, equal opportunity, accommodation, etc. Also remove duplicated lines: there is a line about "Due to U.S. government contract and security requirements, this role is limited to U.S. citizens. Some positions may also require eligibility to obtain and maintain a U.S. Government security clearance. Any active clearance requirement will be listed in the role description." That's somewhat boilerplate but it's substantive about citizenship and clearance. We'll keep that info but maybe condense.
We also need to remove the line "If this role sounds like you, apply and share with us your interest" (application instruction). Also remove "Twenty is an equal opportunity employer..." etc.
Now let's extract content.
Company description:
"About The Company America is under sustained cyber attack. Our adversaries infiltrate our networks, steal our IP, and degrade the digital infrastructure that modern life runs on. They’ve learned—correctly—that those attacks rarely produce consequences. Twenty was founded to change that, by making our adversaries think twice before they attack us. Our vision is American and allied primacy in cyberspace—a future where they cannot contest us, deterrence is assured, and the free world remains secure. Founded in 2024, Twenty Technologies (www.twenty.io) industrializes offensive cyber operations for the U.S. and its allies. Headquartered in Arlington, Virginia, Twenty has raised $168M from Khosla Ventures, Accel, Caffeinated Capital, Friends & Family Capital, Point72 Ventures, General Catalyst, and In-Q-Tel."
We'll put that in a .
Role Summary:
"Role Summary You'll build and own the security infrastructure that keeps Twenty's engineering systems safe without slowing engineers down. This role spans runtime security, access control, secrets management, compliance, and CI/CD hardening — but it's equally about making security the path of least resistance. You'll embed with our engineering teams, design secure-by-default foundations, and build the tooling and automation that lets developers move fast without cutting corners. You'll report directly to the VP of Engineering and operate as a shared function across our product teams."
We'll put that in a
.
Responsibilities (What You'll Do):
List:
- Own runtime security and vulnerability management across cloud and container environments, including triage, prioritization, and remediation tracking.
- Design and enforce identity and access management (IAM) across AWS and internal systems — least-privilege by default.
- Own secrets and credentials management: policies, tooling, rotation, and developer workflows that make doing the right thing easy.
- Lead security incident response: detection, containment, root cause analysis, and durable remediation.
- Manage AWS Organization structure, account boundaries, SCPs, and guardrails.
- Harden and maintain CI/CD pipelines, embedding security scanning and policy enforcement into the software delivery lifecycle.
- Drive compliance efforts — own the evidence, controls, and remediation work to meet and maintain relevant frameworks.
- Build and maintain secure-by-default templates for repos, pipelines, and infrastructure modules.
- Reduce friction through automation: certificate issuance, secrets access, policy-as-code, and developer-facing tooling.
- Produce lightweight, practical security guidance that engineers actually use.
- Shape the direction of the DSO function as it scales, and contribute to hiring and team-building as we grow.
We'll put each as
- .
Who You Are (traits):
- You believe security should be a force multiplier for engineering, not a gatekeeper.
- You take ownership end-to-end: from identifying a risk to designing the control to shipping the fix.
- You bring high judgment to tradeoffs — you know when to enforce hard controls and when friction kills adoption.
- You communicate clearly with both engineers and non-technical stakeholders, and you translate risk into plain language.
- You prefer automation over policy: if an engineer has to do something manually to stay secure, you see that as a bug.
- You hold a high bar for reliability and auditability in the systems you build.
- You're self-directed and thrive in an environment where the function is new and you're defining it.
We'll put as
under a heading maybe "Who You Are". But we could incorporate into Requirements.
Must Have (requirements):
- 8+ years in DevSecOps, platform security, or a closely related security engineering role.
- Deep hands-on experience with AWS — IAM, SCPs, Organizations, security services (GuardDuty, Security Hub, CloudTrail, etc.).
- Strong IaC experience with Terraform; you've used it to enforce security controls, not just provision infrastructure — and you've layered in policy-as-code tooling (e.g., OPA, Checkov, tfsec) or continuous compliance checks (e.g., AWS Config Rules) to catch drift and misconfigurations.
- Experience owning secrets management end-to-end in a production engineering environment.
- Proven track record designing and hardening CI/CD pipelines (we use GitHub Actions).
- Hands-on experience with container security, including image scanning and runtime controls.
- Experience leading or meaningfully contributing to a compliance program; CMMC Level 2 (or NIST SP 800-171) experience strongly preferred.
- You've run incident response — you've been on call, you've led the post-mortem, and you've shipped the fix.
- Strong communication skills and the ability to drive security adoption
for prose. We need to avoid boilerplate: EEO, equal opportunity, accommodation, etc. Also remove duplicated lines. We need to not repeat job title as heading (not present). No Job ID. We need to output only HTML fragment. Let's craft sections: -
About the Company
withcontaining the company description (the paragraph about America under cyber attack, Twenty founded 2024, etc.) -
Role Summary
withcontaining the role summary paragraph. -
Responsibilities
with- each bullet from "What You'll Do". Need to preserve all bullet points.
-
Qualifications
maybe combine "Who You Are" and "Must Have"? But we need to follow instruction: use headings for Qualifications, Skills, etc. Could have separate sections:Qualifications
for "Who You Are" (traits) andRequirements
for "Must Have". And maybeSkills
for "Nice to Have" and Tech Environment? But we need to avoid many thin sections. Perhaps combine "Who You Are" and "Must Have" into Requirements? But they are distinct: Who You Are are soft traits, Must Have are hard requirements. Could put both underRequirements
with two sub-lists? But instruction says use- for any list of duties/requirements/benefits. Could have multiple lists under same heading.
Better: Use headings: Responsibilities, Requirements, Benefits, Pay. And maybe About the Company and Role Summary as prose.
But we need to preserve all substantive info; we can include Nice to Have and Tech Environment under Requirements or Skills. Let's decide:
We'll have:
About the Company
...
Role Summary
...
Responsibilities
- ...
Requirements
Who You Are:
- ...
Must Have:
- ...
- .
Pay: Compensation Range: $159K - $263K. We'll put as
- .
Who You Are (traits):
- You believe security should be a force multiplier for engineering, not a gatekeeper.
- You take ownership end-to-end: from identifying a risk to designing the control to shipping the fix.
- You bring high judgment to tradeoffs — you know when to enforce hard controls and when friction kills adoption.
- You communicate clearly with both engineers and non-technical stakeholders, and you translate risk into plain language.
- You prefer automation over policy: if an engineer has to do something manually to stay secure, you see that as a bug.
- You hold a high bar for reliability and auditability in the systems you build.
- You're self-directed and thrive in an environment where the function is new and you're defining it.
We'll put as
- under a heading maybe "Who You Are". But we could incorporate into Requirements.
Must Have (requirements):
- 8+ years in DevSecOps, platform security, or a closely related security engineering role.
- Deep hands-on experience with AWS — IAM, SCPs, Organizations, security services (GuardDuty, Security Hub, CloudTrail, etc.).
- Strong IaC experience with Terraform; you've used it to enforce security controls, not just provision infrastructure — and you've layered in policy-as-code tooling (e.g., OPA, Checkov, tfsec) or continuous compliance checks (e.g., AWS Config Rules) to catch drift and misconfigurations.
- Experience owning secrets management end-to-end in a production engineering environment.
- Proven track record designing and hardening CI/CD pipelines (we use GitHub Actions).
- Hands-on experience with container security, including image scanning and runtime controls.
- Experience leading or meaningfully contributing to a compliance program; CMMC Level 2 (or NIST SP 800-171) experience strongly preferred.
- You've run incident response — you've been on call, you've led the post-mortem, and you've shipped the fix.
- Strong communication skills and the ability to drive security adoption
maybe under
Pay
. Schedule: we have On Site, Full Time. Could be included under Role Summary or a short paragraph. But we could add aSchedule
withOn Site, Full Time
. However instruction says only create Schedule section if posting actually states them. It does state On Site and Full Time. So we can include. But we also have U.S. Citizenship Required / No Active Clearance Required and Security clearance eligibility note. That could be under Requirements or a separate section like Security Clearance. But we can incorporate into Requirements. We need to remove boilerplate: EEO, equal opportunity, accommodation, etc. Also remove duplicated lines: there is a line about "Due to U.S. government contract and security requirements, this role is limited to U.S. citizens. Some positions may also require eligibility to obtain and maintain a U.S. Government security clearance. Any active clearance requirement will be listed in the role description." That's somewhat boilerplate but it's substantive about citizenship and clearance. We'll keep that info but maybe condense. We also need to remove the line "If this role sounds like you, apply and share with us your interest" (application instruction). Also remove "Twenty is an equal opportunity employer..." etc. Now let's extract content. Company description: "About The Company America is under sustained cyber attack. Our adversaries infiltrate our networks, steal our IP, and degrade the digital infrastructure that modern life runs on. They’ve learned—correctly—that those attacks rarely produce consequences. Twenty was founded to change that, by making our adversaries think twice before they attack us. Our vision is American and allied primacy in cyberspace—a future where they cannot contest us, deterrence is assured, and the free world remains secure. Founded in 2024, Twenty Technologies (www.twenty.io) industrializes offensive cyber operations for the U.S. and its allies. Headquartered in Arlington, Virginia, Twenty has raised $168M from Khosla Ventures, Accel, Caffeinated Capital, Friends & Family Capital, Point72 Ventures, General Catalyst, and In-Q-Tel." We'll put that in a. Role Summary: "Role Summary You'll build and own the security infrastructure that keeps Twenty's engineering systems safe without slowing engineers down. This role spans runtime security, access control, secrets management, compliance, and CI/CD hardening — but it's equally about making security the path of least resistance. You'll embed with our engineering teams, design secure-by-default foundations, and build the tooling and automation that lets developers move fast without cutting corners. You'll report directly to the VP of Engineering and operate as a shared function across our product teams." We'll put that in a
. Responsibilities (What You'll Do): List: - Own runtime security and vulnerability management across cloud and container environments, including triage, prioritization, and remediation tracking. - Design and enforce identity and access management (IAM) across AWS and internal systems — least-privilege by default. - Own secrets and credentials management: policies, tooling, rotation, and developer workflows that make doing the right thing easy. - Lead security incident response: detection, containment, root cause analysis, and durable remediation. - Manage AWS Organization structure, account boundaries, SCPs, and guardrails. - Harden and maintain CI/CD pipelines, embedding security scanning and policy enforcement into the software delivery lifecycle. - Drive compliance efforts — own the evidence, controls, and remediation work to meet and maintain relevant frameworks. - Build and maintain secure-by-default templates for repos, pipelines, and infrastructure modules. - Reduce friction through automation: certificate issuance, secrets access, policy-as-code, and developer-facing tooling. - Produce lightweight, practical security guidance that engineers actually use. - Shape the direction of the DSO function as it scales, and contribute to hiring and team-building as we grow. We'll put each as
- .
Who You Are (traits):
- You believe security should be a force multiplier for engineering, not a gatekeeper.
- You take ownership end-to-end: from identifying a risk to designing the control to shipping the fix.
- You bring high judgment to tradeoffs — you know when to enforce hard controls and when friction kills adoption.
- You communicate clearly with both engineers and non-technical stakeholders, and you translate risk into plain language.
- You prefer automation over policy: if an engineer has to do something manually to stay secure, you see that as a bug.
- You hold a high bar for reliability and auditability in the systems you build.
- You're self-directed and thrive in an environment where the function is new and you're defining it.
We'll put as
- for any list of duties/requirements/benefits. Could have multiple lists under same heading.
Better: Use headings: Responsibilities, Requirements, Benefits, Pay. And maybe About the Company and Role Summary as prose.
But we need to preserve all substantive info; we can include Nice to Have and Tech Environment under Requirements or Skills. Let's decide:
We'll have: