Jobs · Engineering · Washington

Senior Software Engineer, AI Security

Robinhood · Bellevue, WA · 1 mo ago
On-siteEngineering$196k–$230k/yrFull-time
We need to output HTML fragment with sections: About the team + role? Actually headings: "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We must only include sections when posting has real specific content. The posting includes "About the team + role" which is like About the role. We'll use

About the role

with content. Responsibilities: there is a "What You’ll Do" list. That is responsibilities. Requirements/Qualifications/Skills: The posting has "What You Bring" which includes experience, skills, etc. Could split into Requirements (experience) and Skills (technologies). But we can combine? The instruction: prefer few substantive sections over many thin ones. We could have one section for Requirements/Qualifications/Skills combined? But headings are prescribed; we must use those headings if we include them. We could include "Requirements" and "Skills" separately if content exists. Let's see: "What You Bring" includes bullet-like sentences: 5+ years software dev, 3+ years large-scale distributed systems, experience building AI platforms, proficiency in Go or Python, experience with cloud-native platforms, strong understanding of security fundamentals, experience designing reusable platform capabilities, proven experience delivering large engineering projects, strong technical judgment, ability to solve complex engineering problems and collaborate. That's a mix of requirements and skills. Could put under "Requirements" (experience) and "Skills" (technologies). But we can also put all under "Requirements". However we need to follow headings: we can include "Requirements" with list of items. "Skills" maybe not needed if we already covered. But we could include "Skills" with list of specific technologies: Go/Python, AWS, Kubernetes, gRPC, Kafka, etc. That seems specific. Benefits: posting includes "What We Offer" with many benefits: challenging work, performance driven compensation, bonus programs, equity, 401(k) matching, top tier benefits (100% paid health insurance, 90% dependents), Robinhood Employee Fund, access to AI tools, lifestyle wallet, employer-paid life & disability insurance, fertility benefits, mental health benefits, time off, exceptional office experience, catered meals, etc. Also base pay range info. So we have Benefits and Pay sections. Pay: base pay range zones listed. So we need Pay section with that info. Schedule: mentions role based in Menlo Park, CA and Bellevue, WA office(s), with in-person attendance expected at least 3 days per week. That's schedule info (hybrid). So we can include Schedule section. We must not include boilerplate like EEO, privacy policy, etc. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must preserve all substantive information. We need to use
  • for any list of duties/requirements/benefits, and

    for prose. Thus each section: heading

    then either

    prose or

    • list. We need to decide what goes as list vs prose. For About the role: we have a paragraph describing mission and team. Could be prose. Responsibilities: list of duties from "What You’ll Do". Use
      • . Requirements: list of experience requirements from "What You Bring". Could be list. Skills: list of specific technologies: Go/Python, AWS, Kubernetes, gRPC, Kafka, etc. Could be list. Benefits: list of benefits from "What We Offer". Use list. Pay: list of base pay ranges per zone. Could be list. Schedule: maybe prose about in-person attendance 3 days per week, location. We must not include filler like "commensurate with experience". Not present. Let's extract content precisely. About the team + role 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. About the team + role We are building an elite team, applying frontier technologies to the world’s biggest financial problems. We’re looking for bold thinkers. Sharp problem-solvers. Builders who are wired to make an impact. Robinhood isn’t a place for complacency, it’s where ambitious people do the best work of their careers. We’re a high-performing, fast-moving team with ethics at the center of everything we do. Expectations are high, and so are the rewards. The mission of our team is to build a scalable and secure AI platform that enables security teams across Robinhood to develop and operate AI-powered agents and security solutions with confidence. As a Senior Software Engineer on the AI Security team, you’ll help build the foundational platform, infrastructure, and security primitives that make it easier for teams to develop AI-powered security capabilities at scale. You’ll work on complex engineering problems at the intersection of AI, distributed systems, and security, with a particular focus on areas such as identity, authentication, authorization, encryption, and platform safety. You’ll partner closely with security and engineering teams across Robinhood to create systems that make AI development easier while ensuring security is built into the platform from the start. This is a hands-on engineering role for someone who enjoys building platforms, solving complex technical problems, and helping shape how AI is securely adopted across security. This role is based in our Menlo Park, CA and Bellevue, WA 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." We need to separate About the role (maybe first paragraph up to before responsibilities). The "About the team + role" includes mission etc. We'll put that as About the role. Responsibilities: "What You’ll Do" list: - Design and build a scalable AI platform that enables security teams to develop, deploy, and operate AI-powered agents and security capabilities - Build foundational platform services, APIs, libraries, and SDKs that make it easier for teams to integrate AI into security workflows - Design secure systems with strong identity, authentication, authorization, encryption, and data protection controls - Build and operate reliable, large-scale distributed systems that support AI-powered security use cases - Develop platform capabilities and guardrails that enable teams to safely build and operate AI agents - Partner with security, infrastructure, and engineering teams to understand their needs and translate them into reusable platform capabilities - Identify opportunities to improve platform performance, developer experience, reliability, and security through automation - Help shape the technical direction and architecture of Robinhood’s AI Security platform as the team and platform continue to grow Requirements: from "What You Bring" bullet-like sentences: - 5+ years of software development experience - 3+ years of experience building large-scale distributed systems, with experience designing systems around security concepts such as authentication, authorization, identity, or encryption - Experience building AI platforms, AI infrastructure, or production systems that support AI-powered applications or agents - Proficiency in Go or Python, with strong problem-solving and production debugging skills - Experience with cloud-native platforms and distributed systems technologies such as AWS, Kubernetes, gRPC, or Kafka - Strong understanding of security fundamentals and experience incorporating security into the design of production systems - Experience designing and building reusable platform capabilities, APIs, libraries, or developer tooling - Proven experience delivering large engineering projects with meaningful, long-term impact - Strong technical judgment and the ability to make thoughtful trade-offs across security, reliability, scalability, and developer experience - Ability to solve complex engineering problems and collaborate effectively across security and engineering teams Skills: maybe we separate out the specific technologies: Go/Python, AWS, Kubernetes, gRPC, Kafka, etc. But those are already in requirements. Could still list them under Skills. However to avoid duplication, maybe we put all under Requirements and skip Skills. But instruction: prefer few substantive sections over many thin ones. So we could combine Requirements and Skills into one section? But headings are prescribed; we could still include both but if Skills duplicates content, it's thin. Better to include only Requirements and maybe Skills if we have distinct content not covered. The "What You Bring" includes proficiency in Go or Python, experience with cloud-native platforms etc. That's skills. So we could treat those as Skills. But then Requirements would be experience years etc. Let's split: Requirements (experience): - 5+ years of software development experience - 3+ years of experience building large-scale distributed systems, with experience designing systems around security concepts such as authentication, authorization, identity, or encryption - Experience building AI platforms, AI infrastructure, or production systems that support AI-powered applications or agents - Experience designing and building reusable platform capabilities, APIs, libraries, or developer tooling - Proven experience delivering large engineering projects with meaningful, long-term impact - Strong technical judgment and the ability to make thoughtful trade-offs across security, reliability, scalability, and developer experience - Ability to solve complex engineering problems and collaborate effectively across security and engineering teams Skills (technical): - Proficiency in Go or Python, with strong problem-solving and production debugging skills - Experience with cloud-native platforms and distributed systems technologies such as AWS, Kubernetes, gRPC, or Kafka - Strong understanding of security fundamentals and experience incorporating security into the design of production systems That seems reasonable. Benefits: from "What We Offer": - Challenging, high-impact work to grow your career - Performance driven compensation with multipliers for outsized impact, bonus programs, equity ownership, and 401(k) matching - Top Tier benefits to fuel your work, including 100% paid health insurance for employees with 90% coverage for dependents - Access to the Robinhood Employee Fund that gives eligible US employees the opportunity to invest in a private employee fund that provides exposure to Robinhood Ventures funds. - Access to the best AI tools on the market and continuous AI skill-building for every employee, technical or not. - Lifestyle wallet - a highly flexible benefits spending account for wellness, learning, and more - Employer-paid life & disability insurance, fertility benefits, and mental health benefits - Time off to recharge including company holidays, paid time off, sick time, parental leave, and more! - Exceptional office experience with catered meals, events, and comfortable workspaces. 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 bonus etc. Pay: Base pay range zones: - Zone 1 (Menlo Park, CA; New York, NY; Bellevue, WA; Washington, DC) $196,000—$230,000 USD - Zone 2 (Denver, CO; Westlake, TX; Chicago, IL) $172,000—$202,000 USD - Zone 3 (Lake Mary, FL; Clearwater, FL; Gainesville, FL) $153,000—$179,000 USD Also note: "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." Could include as prose. Schedule: "This role is based in our Menlo Park, CA and Bellevue, WA 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, energ

Similar jobs