Senior Offensive Security Engineer

We need to output HTML fragment with sections: About the team + role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections are present. The posting includes: "About the team + role" (maybe treat as About the role). Then "What You’ll Do" (Responsibilities). Then "What You Bring" (Requirements/Qualifications/Skills). Then "What We Offer" (Benefits). Also includes base pay range details (Pay). Also schedule: "in-person attendance expected at least 3 days per week." That's schedule info. So we need sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly also Qualifications but we can combine Requirements. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: mission statement at top? The first paragraph: "Join us in building the future of finance..." That's marketing but still substantive? It's not a section heading; we can keep as

before sections? The instruction: output only HTML fragment, no extra. We can include that as a

before sections. Also "At Robinhood, we believe..." is part of About the team + role? Might be part of About the role. We'll incorporate. We need to ensure we don't create sections with filler like "commensurate with experience". Not present. We need to use

• for any list of duties/requirements/benefits. So we need to convert bullet points into lists. Let's extract content. First paragraph: "Join us in building the future of finance. Our mission is to democratize finance for all. An estimated $124 trillion of assets will be inherited by younger generations in the next two decades. The largest transfer of wealth in human history. If you’re ready to be at the epicenter of this historic cultural and financial shift, keep reading." Second paragraph: "About the team + role We are building an elite team, applying frontier technologies to the world’s biggest financial problems. We’re looking for thoughtful problem-solvers and builders who want to make a meaningful contribution. Robinhood is a place where people take ownership of their work and help improve financial access for all. We operate with high standards, clear accountability, and a strong focus on security and ethics in everything we build! The Red Team’s mission is to identify and reduce real-world security risks across Robinhood by simulating adversary behavior and testing defenses. As a Staff Offensive Security Engineer, you will plan and execute security assessments across applications, infrastructure, and physical environments, and partner closely with engineering and security teams to strengthen detection and response capabilities. You will help prioritize risk, contribute to remediation efforts, and develop tools and techniques that improve how we test and secure our systems. Your work will directly support the safety and reliability of products used by millions of customers. This role is based in our Bellevue, WA, New York, NY, Denver, CO or Menlo Park, CA office(s), with in-person attendance expected at least 3 days per week. At Robinhood, we believe in the power of in-person work to accelerate progress, spark innovation, and strengthen community. Our office experience is intentional, energizing, and designed to fully support high-performing teams." Then "What You’ll Do" list bullet points. Then "What You Bring" list bullet points. Then "What We Offer" list bullet points. Then base pay range details. We need sections:

  About the role

  -> include the paragraphs about team+role, maybe also the mission statement? Could include mission as part of About the role.

  Responsibilities

  -> list of What You’ll Do.

  Requirements

  -> list of What You Bring (maybe split into Requirements and Skills? But we can just put all under Requirements). Could also have Skills but not needed.

  Benefits

  -> list of What We Offer.

  Pay

  -> base pay range details.

  Schedule

  -> in-person attendance expected at least 3 days per week. We must not repeat job title. Good. We need to preserve all substantive info. Ensure we don't lose any bullet points. Let's extract bullet points. What You’ll Do bullet points (as in text): - Evangelize the Offensive Security Team’s Findings and Projects with stakeholders throughout the company and collaborate with other teams to create solutions that balance security with other priorities. - Mentor and provide guidance to the members of the Offensive Security team. - Plan and execute red team exercises, including long-term assessments that simulate real-world attack scenarios - Perform threat modeling and penetration testing across applications, infrastructure, and corporate environments - Develop scripts and tools to support and automate security testing activities - Partner with detection and response teams to run adversarial simulations and improve incident readiness - Communicate findings clearly and work with engineering teams to remediate identified risks - Lead Security Incidents when Pentest or Red Team findings require them. - Plan and participate in Adversarial Simulation exercises with various security teams. Note some lines missing period; we keep as is. What You Bring bullet points: - 6+ years of experience conducting red team operations or advanced penetration testing - Experience mentoring or supporting the development of other security engineers - Passion and demonstrated experience for challenging security assumptions. - Excellent written and verbal communication skills and ability to communicate your findings at many different levels of abstraction from Engineers to Executives. - Passion for fixing security issues and not just identifying security issues. - Familiarity with common network protocols and standards such as DNS and TCP/IP. - Experience with MacOS and Linux. - Experience with leveraging components of a modern software development stack to attack companies, including CI, container orchestration systems (Kubernetes/Docker), cloud providers (AWS, GCP), etc and be able to give hardening suggestions. - Experience/knowledge of defensive tools/techniques (IDS/IPS, Packet Capture, Network Analysis, AV, EDR, etc.) and how to evade them. - Deep understanding of Mitre’s ATT&CK Framework. - Strong understanding of the security fundamentals of access and identity. - Comfortable reading / writing python, go, and javascript. - Ability to research and execute a testing plan to access a new technology or process. - Demonstrated experience working with a distributed team. - Proficiency to communicate over a text-based medium (Slack, JIRA Issues, GitHub issues, & Email) and can succinctly document technical details. - Bonus Points Experience in the Financial Technology domain. - Experience being a technical lead at other organizations. Note "Bonus Points" lines maybe separate bullet? They are separate bullet points but start with "Bonus Points". We'll keep as bullet. What We Offer bullet points: - Market competitive and pay equity-focused compensation structure - 100% paid health insurance for employees with 90% coverage for dependents - Annual lifestyle wallet for personal wellness, learning and development, and more! - Lifetime maximum benefit for family forming and fertility benefits - Dedicated mental health support for employees and eligible dependents - Generous time away including company holidays, paid time off, sick time, parental leave, and more! - Lively office environment with catered meals, fully stocked kitchens, and geo-specific commuter benefits Also note: "In addition to the base pay range listed below, this role is also eligible for bonus opportunities + equity + benefits." That's part of compensation but we already have Pay section; we can include that sentence in Pay section. Pay section: base pay range details: - Base pay for the successful applicant will depend on a variety of job-related factors, which may include education, training, experience, location, business needs, or market demands. - The expected base pay range for this role is based on the location where the work will be performed and is aligned to one of 3 compensation zones. - For other locations not listed, compensation can be discussed with your recruiter during the interview process. - Base Pay Range Zone 1 (Menlo Park, CA; New York, NY; Bellevue, WA; Washington, DC) $187,000—$220,000 USD - Zone 2 (Denver, CO; Westlake, TX; Chicago, IL) $165,000—$194,000 USD - Zone 3 (Lake Mary, FL; Clearwater, FL; Gainesville, FL) $146,000—$172,000 USD - Click here to learn more about our Total Rewards, which vary by region and entity. We should keep that as prose maybe

  or

  . Since it's a list, we can use
  • . However the instruction: use
    • for any list of duties/requirements/benefits. Pay is not explicitly listed but could be considered list. Safer to use

      for prose. But we have multiple sentences; we could keep as

      . However the instruction says use

      • for any list of duties/requirements/benefits. Pay is not duties/requirements/benefits, so we can use

        . We'll include the pay details in a

        . Schedule: "This role is based in our Bellevue, WA, New York, NY, Denver, CO or Menlo Park, CA office(s), with in-person attendance expected at least 3 days per week." Also earlier: "At Robinhood, we believe in the power of in-person work to accelerate progress, spark innovation, and strengthen community. Our office experience is intentional, energizing, and designed to fully support high-performing teams." That's also schedule/location info. We'll combine. We'll put schedule section with that sentence. Now we need to output only HTML fragment, no markdown fences. Let's craft. Start with introductory paragraph(s) before sections? The instruction didn't forbid having

        before sections. We'll include the mission/intro as a

        . Thus:

        Join us in building the future of finance. Our mission is to democratize finance for all. An estimated $124 trillion of assets will be inherited by younger generations in the next two decades. The largest transfer of wealth in human history. If you’re ready to be at the epicenter of this historic cultural and financial shift, keep reading.

        Then

        About the role

        then a

        containing the About the team + role paragraph(s). We'll combine the two paragraphs: "About the team + role We are building an elite team..." and the later "At Robinhood, we believe..." maybe belongs to schedule but we already used schedule separate. Actually the "At Robinhood, we believe..." is about in-person work; could be schedule. We'll keep it in schedule. Thus About the role paragraph: "We are building an elite team, applying frontier technologies to the world’s biggest financial problems. We’re looking for thoughtful problem-solvers and builders who want to make a meaningful contribution. Robinhood is a place where people take ownership of their work and help improve financial access for all. We operate with high standards, clear accountability, and a strong focus on security and ethics in everything we build! The Red Team’s mission is to identify and reduce real-world security risks across Robinhood by simulating adversary behavior and testing defenses. As a Staff Offensive Security Engineer, you will plan and execute security assessments across applications, infrastructure, and physical environments, and partner closely with engineering and security teams to strengthen detection and response capabilities. You will help prioritize risk, contribute to remediation efforts, and develop tools and techniques that improve how we test and secure our systems. Your work will directly support the safety and reliability of products used by millions of customers. This role is based in our Bellevue, WA, New York, NY, Denver, CO or Menlo Park, CA office(s), with in-person attendance expected at least 3 days per week." But we moved schedule line to schedule section; maybe we should keep location line in About the role and schedule separate just the attendance expectation. However the location line includes office(s