Cybersecurity Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe Basic Qualifications and Other Qualifications combined?), Benefits, Pay, Schedule. We must only include sections if posting has real specific content. We have content: About The Team (maybe not needed as heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They say do NOT repeat the job title as a heading. They didn't list "About The Team" as a heading to use, but we could include if relevant? They gave examples but not exclusive. Probably we should include sections that match content: About The Role (we have that), Responsibilities, About You (maybe Qualifications/Skills), Basic Qualifications, Other Qualifications (could be Skills), Pay (they gave salary ranges), Schedule (they gave flexible work description). Benefits: they mention "Workday Bonus Plan or a role-specific commission/bonus, as well as annual refresh stock grants." Also mention benefits link but not details. There's mention of comprehensive benefits but not specifics. Should we include Benefits section? They said only include if posting has real specific content. There's mention of bonus plan, stock grants. That's somewhat specific. Could include Benefits. We must not include boilerplate like EEO, legal, application instructions, etc. We need to preserve all substantive information, not invent or summarize away detail. So we need to include the details from About The Team? Possibly we could include as a paragraph under About the role? But they said About the role heading. The About The Team content is separate; maybe we could incorporate into About the role? But they said use headings for section headings (e.g. About the role...). Not mandatory to only those. Safer to include About the Team as a paragraph under About the role? Might be considered filler? The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine About The Team and About The Role into About the role section. We need to output only HTML fragment, no /, no markdown fences. Let's extract: About the role: The paragraph after "About The Role" includes description of role, responsibilities overview. We'll put that in

. Responsibilities: bullet list after "Responsibilities:" with items. About You: paragraph after "About You" describing traits. Basic Qualifications: list after "Basic Qualifications:" with items (each line ends with maybe no period). We'll put as

• . Other Qualifications: list after "Other Qualifications:" with items grouped by categories? It's a paragraph with bullet-like items separated by semicolons? Actually it's a paragraph: "Agent / eval - LangChain, LangGraph, LangSmith, or similar; LLM-as-judge or offline eval; tracing and observability for agent runsApplication / UI - frontend (React or similar) for internal tools; watchlist / dashboard / workflow UIs on security dataSecurity domain - hands-on with security tools or data for triage and investigation (SIEM, vulnerability scanners, identity systems, orchestration platforms such as Tines); curiosity about detection-engineering workflowsData / schema - comfort reasoning about shared schemas or data contracts that span team boundaries, treating what / who / state as a first-class artifactCloud / platform familiarity - working AWS fluency (enough to ship and operate); IaC (Terraform/Docker) is useful but not the daily jobComfort operating in ambiguous problem spaces where you help define the solution, not just implement it" We can split into
  • each bullet separated by line breaks? The original had line breaks? It appears as a paragraph with categories separated by line breaks? Actually after "Other Qualifications:" there is a line break then each category on new line? In the text it's shown as a single paragraph but with line breaks? We'll treat each category as a list item. Pay: they gave salary ranges: Primary Location Base Pay Range: $130,200 USD - $195,400 USD; Additional US Location(s) Base Pay Range: $117,800 USD - $210,000 USD; Additional Considerations: If performed in Colorado, the pay range for this job is $124,000 - $186,000 USD based on min and max pay range for that role if performed in CO. We'll put in

    maybe. Schedule: they gave flexible work description: "With Flex Work, we’re combining the best of both worlds: in-person time and remote. Our approach enables our teams to deepen connections, maintain a strong community, and do their best work. We know that flexibility can take shape in many ways, so rather than a number of required days in-office each week, we simply spend at least half (50%) of our time each quarter in the office or in the field with our customers, prospects, and partners (depending on role). This means you'll have the freedom to create a flexible schedule that caters to your business, team, and personal needs, while being intentional to make the most of time spent together. Those in our remote "home office" roles also have the opportunity to come together in our offices for important moments that matter." We'll put as

    under Schedule heading. Benefits: mention "Workday Bonus Plan or a role-specific commission/bonus, as well as annual refresh stock grants." Also maybe "comprehensive benefits" link but no detail. We'll include that as

    . We must not include boilerplate like EEO, legal, application instructions, etc. Also not include "Workday Pay Transparency Statement" heading? We'll incorporate pay info under Pay heading. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must not include duplicated lines. Now craft HTML:

    About the role

    ... (combined About The Team and About The Role?)

    But we have About The Team content separate; maybe we can include as a paragraph before responsibilities? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have About the role heading, then paragraph(s). We'll include both About The Team and About The Role description in that paragraph or two paragraphs. Let's extract About The Team paragraph: "Security Automation & Integration Engineering (SecAIE) transforms cybersecurity operations by architecting intelligent automation that turns manual processes into scalable, decision-accelerating systems. We're the engineering excellence partner within Cybersecurity and Trust - building the unified data foundation, intelligent automation, and decision support tools that enable security teams to make precise, data-driven decisions at machine speed. We partner closely with Security Leadership, Operational Teams, Engineering Teams, and Governance/Risk Teams to deliver platforms that multiply their effectiveness. Our current charter contributes directly to Workday's Active Defense pivot - building the reliable data and platform substrate that lets security teams execute at machine speed and out-adapt AI-driven threats. We're a small, high-impact team that values curiosity, pragmatism, and collaboration. We believe working solutions beat perfect designs, unified context beats massive datasets, and partner success is our success. Leveraging AI to augment how we do security engineering is an active opportunity for the team, and one we expect this role to help lean into." About The Role paragraph: "We're looking for a Cybersecurity Engineer to join SecAIE and take primary ownership of the agent, eval, and application work that Workday's Active Defense charter runs on. You'll spend most of your time engineering the layer partners actually use - eval harnesses, agent scaffolds, schemas, and application UIs on top of security data - so detection, response, and threat-intel teams can move from a vague ask to a working system. This role is ideal for someone who loves turning messy operational problems into clean, reusable software, who can walk into an ambiguous ask and come back with a proposal, and who treats AI tooling as a force multiplier rather than a novelty. You will bring working knowledge of cybersecurity concepts and best practices from day one - enough to reason about identity and access, secrets handling, and the shape of common security data (vulnerabilities, incidents, identity, threat intel, detections). You will not be expected to be the deepest security specialist in the room; you will partner with domain experts across our security organization and build the agents, eval, and applications that make their work faster, more reliable, and more measurable." We'll combine maybe two paragraphs. Responsibilities list: - Own agent-adjacent application work: eval harnesses, agent scaffolds, and the UIs that security partners use to inspect and act on results - Design, build, and evolve schemas and data contracts so agents and humans share the same objects rather than one-off payloads - Take partner requests from vague to shipped: scope the problem, propose approaches, choose one, and drive it through design, review, rollout, and operational readiness (eval, tracing, runbooks) - Build and maintain integrations across security tools and enterprise platforms - SOAR, SIEM, vulnerability scanners, ticketing - when the application or agent needs them - Raise the team's AI-augmented engineering floor: shared skills, reusable scaffolds, a review discipline for AI-generated code, and eval that catches drift - Iterate quickly: prototype, test, ship, learn, improve - and bring the team with you About You paragraph: "You're a curious engineer who owns problems rather than tickets. You're drawn to ambiguous, messy asks and you enjoy learning a domain deeply enough to propose the right solution, not just implement one that was handed to you. You bring high agency: you can move a partner's rough problem statement to a shipped, operational answer without waiting to be told each next step. You're comfortable turning a partner's Slack thread into a written proposal, and comfortable when the answer to "whose ticket is this?" is "nobody's yet - I'll draft one." You know when to escalate and when to just close the loop yourself. You default to reusable components over copy-paste, eval over vibes, and reliable defaults over one-off heroics. You use AI tooling deliberately and can articulate where it accelerates you and where it does not. You communicate clearly, ask good questions, and genuinely enjoy collaborating across teams to solve hard problems." Basic Qualifications list: - Strong Python skills with hands-on experience shipping production software (APIs, services, batch jobs, or application backends), including code review, testing, and operational follow-through - Hands-on experience building or evaluating LLM / agent systems (harnesses, eval, tracing, or agentic pipelines) or strong software-engineering fundamentals plus demonstrated AI-augmented development (Copilot, coding agents) with a point of view on where they help - Comfort designing or evolving schemas / data contracts and application UIs that sit on real data - not mock-only prototypes - Working knowledge of core cybersecurity practices - identity and access, secrets handling, secure-by-default configuration, and reasoning over common security data (vulnerabilities, incidents, identity, threat intel) - so you can build for security outcomes. - Comfortable owning what you ship (runbooks, basic observability, eval that still runs after you merge) Other Qualifications list (split by categories): - Agent / eval - LangChain, LangGraph, LangSmith, or similar; LLM-as-judge or offline eval; tracing and observability for agent runs - Application / UI - frontend (React or similar) for internal tools; watchlist / dashboard / workflow UIs on security data - Security domain - hands-on with security tools or data for triage and investigation (SIEM, vulnerability scanners, identity systems, orchestration platforms such as Tines); curiosity about detection-engineering workflows - Data / schema - comfort reasoning about shared schemas or data contracts that span team boundaries, treating what / who / state as a first-class artifact - Cloud / platform familiarity - working AWS fluency (enough to ship and operate); IaC (Terraform/Docker) is useful but not the daily job - Comfort operating in