Senior Software Engineer

We need to produce HTML fragment with sections: About the team, About the opportunity, In This Role, You Will (maybe split into subsections?), About You, You Have, Differentiators, All Roles At College Board Require, About Our Process, What We Offer, About College Board, Mission, What Guides Us, We Value and Provide Growth, Recognition, and Purpose. But we must follow rules: Use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we can use other headings? The instruction says: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use

for any section headings we include. Likely we should map the content to those standard headings where appropriate. But we can also use other headings? The examples are just examples; they say use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use

for each section heading we include. We should not repeat the job title as a heading. Also we should not put Job ID/requisition numbers as headings. We need to include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to decide which sections have content. We have content for: - About The Team -> could map to "About the role"? Actually "About the team" is about team. Could be "About the role"? But we have "About The Opportunity" which is more like role description. Could map to "About the role". However the instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should probably use those exact headings where applicable. Let's map: - About The Team -> maybe "About the role"? But that seems off. Could also be "About the team" not in list but still a heading; we can still use

for it. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

for section headings (e.g. those). Likely they want us to use

for any section heading we output. So we can use

for any heading we decide to include. Thus we will output sections with

headings. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEOC statement, etc. Also remove "All Roles At College Board Require" maybe? That is a list of requirements that apply to all roles; but it's substantive? It lists: passion for expanding educational..., authorization to work in US, curiosity..., clear communication, learner's mindset, drive for impact, collaborative approach. That's substantive; we should keep it. However it's under "All Roles At College Board Require". We could treat that as a section like "Requirements". But we already have a "Requirements" section maybe from "About You, You Have". We'll need to decide. We also have "About Our Process" which includes application process details; we should remove application instructions? The instruction says remove application instructions. "About Our Process" includes: Application review will begin immediately..., preferred application deadline, office closed dates, while hiring process may vary, it generally includes: resume and application submission, recruiter phone/video screen, hiring manager interview, performance exercise such as live coding, a panel interview, a conversation with leadership and reference checks. That's basically application instructions; we should remove that section. So we should omit "About Our Process". "What We Offer" includes compensation and benefits; we should keep that as it's substantive. It includes salary range, bonuses, mission-driven workplace, team invests in development. That's good. "About College Board" is descriptive; we can keep. "Mission" and "What Guides Us" and "We Value and Provide Growth, Recognition, and Purpose" are also substantive; we can keep. We also have "Differentiators" which is a list of nice-to-haves; we can keep as a section maybe "Skills" or "Qualifications". But we need to avoid filler. It's specific. We also have "About You, You Have" which includes requirements: love of learning, software engineering craft, demonstrated software engineering experience proficiency using JavaScript and TypeScript, 5+ years experience, deep understanding of AWS services, working knowledge of IP networking, experience establishing software engineering guidelines, performing code and design reviews, documenting design and architecture artifacts, presenting artifacts for architectural review, comfortable operating in fast-moving environments, proactively define guardrails. That's requirements. We also have "In This Role, You Will" with bullet points broken into percentages. That's responsibilities. Thus we can map: - About The Team -> maybe "About the team" (but not in list). Could be "About the role"? But we have separate "About The Opportunity". Might be better to keep both as separate sections: "About the team" and "About the opportunity". Use

for each. - About The Opportunity -> maybe "About the role". We'll use heading "About the role". - In This Role, You Will -> maybe "Responsibilities". We'll use heading "Responsibilities". - About You, You Have -> maybe "Requirements". We'll use heading "Requirements". - Differentiators -> maybe "Preferred qualifications" or "Skills". We'll use heading "Skills". - All Roles At College Board Require -> maybe "Qualifications" (general). We'll use heading "Qualifications". - What We Offer -> maybe "Benefits". We'll use heading "Benefits". Also includes Pay (salary range). Could also have Pay section separate. But we can include pay within Benefits. However instruction says include Pay/Schedule/Benefits sections only if posting actually states them. It does state salary range, so we could have a Pay section. Benefits also includes annual bonuses, mission-driven workplace, team invests in development. We could split: Pay section for salary range, Benefits section for other offerings. But we have limited content; maybe combine into Benefits and include pay there. However instruction says prefer a few substantive sections over many thin ones. So maybe combine Pay and Benefits into one "Benefits" section that includes salary range and other offerings. That's fine. - About College Board -> maybe "About College Board". Not in list but okay. - Mission -> maybe "Mission". Could be part of About College Board but it's separate; we can keep. - What Guides Us -> maybe "What guides us". Keep. - We Value and Provide Growth, Recognition, and Purpose -> maybe "We value and provide growth, recognition, and purpose". Keep. We must not include filler like "commensurate with experience". Not present. We must remove duplicated lines. Ensure we don't repeat same content. We need to use

• for any list of duties/requirements/benefits. So for sections that have lists, we need to wrap in
  • . For prose, use

    . We need to preserve ALL substantive information; do not invent or summarize away detail. Thus we need to extract each bullet and keep them as list items. Let's parse content. **About The Team** paragraph: "The College Board’s Cloud and Platform Security Engineering (CPSE) team designs, builds, and secures the cloud foundation that powers our most critical applications and services. We partner closely with product engineering, platform, risk, compliance, and application teams to design, automate, and operationalize scalable security controls, building reusable tooling and guardrails that make secure application deployments the default across AWS environments. Rather than operating as a reactive review function, we implement preventive and detective controls that reduce systemic risk while enabling teams to move quickly. Our work spans multi-account cloud architecture, identity and access management, network segmentation, automation, detection engineering, and compliance alignment. We focus on scalable, repeatable solutions that strengthen security posture across the enterprise." We'll keep as prose (

    ). **About The Opportunity** paragraph: "As a Senior Full Stack Engineer within CPSE, you will collaborate closely with other engineers on the team using ensemble or mob programming methodologies to build and operate product security solutions in support of College Board’s mission. You will use a variety of technologies to build, operate, and maintain software and automation solutions in an ever-growing cloud environment. The team’s solutions will support the secure delivery of all College Board digital products, and ensure security of College Board infrastructure. You will work across cloud environments to expand automated guardrails, improve external exposure management, and reduce high-risk misconfigurations through enforceable, enterprise-wide controls. This role emphasizes secure-by-default architecture, infrastructure automation, and measurable risk reduction, ensuring security controls are consistently applied as the organization scales. In partnership with Cloud Engineering, Product Security, and Cyber Operations, you will enhance vulnerability management workflows, increase automation across intake and response processes, and strengthen detection and triage capabilities. You will help drive improved remediation velocity, clearer security posture visibility, and more efficient security operations through engineering-led solutions. You will also contribute to the resilience and reliability of critical security platforms, ensuring continuity of monitoring and posture management capabilities while supporting modernization efforts. Success in this role means delivering durable, scalable security outcomes: stronger preventive coverage, reduced exposure windows, improved operational efficiency, and measurable improvements in enterprise security posture." We'll keep as prose. **In This Role, You Will** has three sub-sections with percentages and bullet points. We need to preserve all bullet points. Let's extract them. First sub-section: "Strengthen Cloud Guardrails and Preventive Controls (50%)" - Design, implement, and operationalize automated preventive and detective guardrails across enterprise cloud environments. - Build and enforce enterprise-wide controls that prevent or automatically remediate high-risk misconfigurations. - Improve protection coverage for internet-facing systems by validating asset inventories and expanding enforcement mechanisms. - Continuously evaluate control effectiveness through telemetry, compliance validation, and risk trend analysis. - Partner with cloud platform teams to embed secure-by-default infrastructure patterns into reusable modules and deployment workflows. Second sub-section: "Advance Vulnerability Management (UVM) and Security Automation (30%)" - Enhance and operationalize Unified Vulnerability Management (UVM) workflows to improve prioritization, remediation velocity, and cross-team accountability. - Increase automation across vulnerability intake, enrichment, ticketing, and response workflows to reduce manual triage burden. - Design and deliver engineering solutions that improve detection quality and response speed in collaboration with Cyber Operations. - Translate security requirements into scalable technical implementations using infrastructure-as-code and automation frameworks. - Measure and report on workflow efficiency and risk reduction outcomes using operational metrics. Third sub-section: "Improve Security Posture Visibility and CSPM Continuity (20%)" - Design and implement standardized, automated security checks in Backstage across prioritized domains (e.g., code security, CSPM, vulnerability management). - Establish a quantifiable product security maturity model backed by Backstage telemetry and Security Scorecard outputs. - Partner with Product Security to ensure continuity of CSPM coverage and dependent tool integrations (e.g., Tines, WAF dashboard) throughout replacement of the CloudGuard platform. - Deliver a proof-of-concept (POC) of the replacement CSPM tool and address identified capability gaps through engineering solutions (e.g., supplemental guardrails). - Contribute to documentation, engineering standards, and continuous improvement practices that promote long-term maintainability. We'll keep these as list items under a

    maybe grouped under a heading "Responsibilities". Could also keep subheadings but we are not supposed to create extra headings unless needed. Could keep as a single list; but we might lose the grouping. However we can keep them as list items; the percentages are part of the heading text maybe we can include them in the list