Staff Full-stack Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes "About the Position:" and "About the team:" and "What You’ll Do:" and "Basic Qualifications:" and "Preferred Qualifications:" and salary info (Pay) and benefits mention. Also mention about mentoring etc. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only when posting has real specific content. We have content for About the Position (could map to About the role). About the team maybe part of About the role or separate? Could be part of About the role. What You’ll Do maps to Responsibilities. Basic Qualifications and Preferred Qualifications map to Requirements/Qualifications/Skills. We need to decide mapping. We have Pay info: salary ranges per location. So we can create Pay section with that info. Benefits: mention comprehensive benefits, health, financial, etc. So we can create Benefits section. Schedule: not mentioned; no schedule info, so omit. We must not include boilerplate like EEO, accommodation, etc. Remove those. We must preserve all substantive info; not invent. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

About the role

... content from About the Position and About the team combined.

Responsibilities

• ... each bullet from What You’ll Do.

Requirements

Maybe combine Basic Qualifications and Preferred Qualifications? Could split into Qualifications and Skills. But we have headings: Requirements, Qualifications, Skills. We need to decide which to use. Could use Requirements for Basic Qualifications, Qualifications for Preferred Qualifications, Skills for specific technical skills? However we have a lot of detail; we could just use Requirements for Basic Qualifications and Qualifications for Preferred Qualifications, and maybe Skills for specific technologies? But we must not create thin sections; better to combine into one Requirements section that includes both basic and preferred? But we have headings list; we can choose to use only Requirements and Qualifications if we have content. The instruction: "Prefer a few substantive sections over many thin ones." So maybe use Requirements for Basic Qualifications, and Qualifications for Preferred Qualifications. Skills maybe not needed if we already covered skills in qualifications. Could omit Skills. Pay section:

Pay

with salary ranges. Benefits section:

Benefits

with description. We must not include schedule. Let's extract content. About the Position text (duplicate of first paragraph). We'll combine: "As a Staff Engineer at Capital One, you will be part of a community of technical experts working to define the future of banking in the cloud. You will work alongside our talented team of developers, machine learning experts, product managers and people leaders. Our Staff Engineers are leading experts in their domains, helping devise practical and reusable solutions to complex problems. You will drive innovation at multiple levels, helping optimize business outcomes while delivering strong technology solutions. At Capital One, we believe diversity of thought strengthens our ability to influence, collaborate and provide the most innovative solutions across organizational boundaries. You will promote a culture of engineering excellence and strike the right balance between lending expertise and providing an inclusive environment where the ideas of others can be heard and championed. You will lead the way in creating next-generation talent for Capital One Tech, mentoring engineers and actively recruiting to keep building our community. Staff Engineers are expected to lead through technical contribution. You will operate as a trusted advisor for our key technologies, platforms and capability domains, creating clear and concise communications, code samples, blog posts and other materials to share knowledge both inside and outside the organization. You will specialize in a particular subject area, but your input and impact will be sought and expected throughout the organization." About the team: "Card Intelligent Decisions & Experiences (CIDX) in Card Tech+ is responsible for the decisioning technology that guides our customers through their entire credit journey - from marketing, to product offers, real-time transaction approvals, and more. The Customer Resiliency team in Card Intelligent Decisions & Experiences (CIDX) is responsible for helping Capital One’s most vulnerable customers in times of financial difficulty. This team builds solutions and enablers that help our customers get back on their feet and reestablish themselves from their moments of difficulty." We can combine. Responsibilities bullets from "What You’ll Do:" list: - Articulate and evangelize a bold technical vision for your domain - Decompose complex problems into practical and operational solutions - Ensure the quality of technical design and implementation - Serve as an authoritative expert on non-functional system characteristics, such as performance, scalability and operability - Continue learning and injecting advanced technical knowledge into our community - Handle several projects simultaneously, balancing your time to maximize impact - Act as a role model and mentor within the tech community, helping to coach and strengthen the technical expertise and know-how of our engineering and product community - Drive modernization of monolithic systems into microservice architectures and event-driven platforms - Collaborate with senior engineering and architecture leaders to define long-term platform strategy and API standards - Serve as a force-multiplier for the team, balancing deep, hands-on technical contribution and innovation with mentoring and elevating the skills of peers and junior engineers. - Lead cross-divisional projects and impacts that promote technological best practices and enhancements Basic Qualifications: - Bachelor’s Degree In Computer Science or a related field - At least 7 years of experience in: - Software engineering and solution architecture - Enterprise architecture and design patterns - Cloud computing (AWS, Microsoft Azure, Google Cloud) - Data architecture Preferred Qualifications (long list). We'll need to capture all items. Let's list them: - Master’s Degree in Computer Science or Software Engineering - 10+ years of experience in all of the following: - Software engineering and solution architecture - Enterprise architecture and design patterns - Web technologies (Javascript, TypeScript and SPA frameworks) - Designing and building distributed HPC and ML systems - Cloud computing (AWS, Microsoft Azure, Google Cloud) - Data architecture - 10+ years of professional experience coding in commonly used languages like Go, Java, Javascript/Typescript, Python, Rust, C#, Scala - 8+ years of experience with database and database management systems - 10+ years of professional experience in the full lifecycle of system development, from conception through architecture, implementation, testing, deployment and production support - 8+ years of experience with public cloud platforms (AWS, GCP, Azure), cloud-based productivity tools, or virtualization technologies - 10+ years of experience with Networking protocols and integration with third party distributed systems - 5+ years of experience mentoring senior engineers and driving professional development within technical teams - 2+ years of experience leading cross-domain architectural reviews and establishing coding and design standards - Expertise in the strategic application of agentic AI coding tools to solve systemic development challenges - Working knowledge of AI/ML concepts, with demonstrated experience applying AI tools to accelerate delivery, improve decision-making, or drive measurable efficiency gains. Also note: "Capital One will consider sponsoring a new qualified applicant for employment authorization for this position." That's substantive; we could include in About the role or maybe a separate note but we can put in About the role paragraph. Pay: salary ranges per location: - McLean, VA: $269,100 - $307,200 for Staff Full-stack Engineer - New York, NY: $293,600 - $335,100 for Staff Full-stack Engineer - Richmond, VA: $244,700 - $279,200 for Staff Full-stack Engineer - Note: Candidates hired to work in other locations will be subject to the pay range associated with that location, and the actual annualized salary amount offered to any candidate at the time of hire will be reflected solely in the candidate’s offer letter. - This role is also eligible to earn performance based incentive compensation, which may include cash bonus(es) and/or long term incentives (LTI). Incentives could be discretionary or non discretionary depending on the plan. Benefits: "Capital One offers a comprehensive, competitive, and inclusive set of health, financial and other benefits that support your total well-being. Learn more at the Capital One Careers website. Eligibility varies based on full or part-time status, exempt or non-exempt status, and management level." We'll include that. Now produce HTML. We must not include any extra text outside HTML. Let's craft. We'll need to escape any HTML special characters? The text includes ampersand (&) in "etc."? Not needed. We have "&" in "etc."? Not present. We have "CIDX" fine. We have "AWS", "GCP". No issues. We'll use

• for lists. For Basic Qualifications we have a nested list: main bullet "At least 7 years of experience in:" then sublist. We'll represent as
• At least 7 years of experience in:
  • Software engineering and solution architecture
  ... etc.
Similarly for Preferred Qualifications: many items; some have sublists. We'll need to be careful to preserve all info. Let's construct. First section About the role:

About the role

As a Staff Engineer at Capital One, you will be part of a community of technical experts working to define the future of banking in the cloud. You will work alongside our talented team of developers, machine learning experts, product managers and people leaders. Our Staff Engineers are leading experts in their domains, helping devise practical and reusable solutions to complex problems. You will drive innovation at multiple levels, helping optimize business outcomes while delivering strong technology solutions. At Capital One, we believe diversity of thought strengthens our ability to influence, collaborate and provide the most innovative solutions across organizational boundaries. You will promote a culture of engineering excellence and strike the right balance between lending expertise and providing an inclusive environment where the ideas of others can be heard and championed. You will lead the way in creating next-generation talent for Capital One Tech, mentoring engineers and actively recruiting to keep building our community. Staff Engineers are expected to lead through technical contribution. You will operate as a trusted advisor for our key technologies, platforms and capability domains, creating clear and concise communications, code samples, blog posts and other materials to share knowledge both inside and outside the organization. You will specialize in a particular subject area, but your input and impact will be sought and expected throughout the organization. Card Intelligent Decisions & Experiences (CIDX) in Card Tech+ is responsible for the decisioning technology that guides our customers through their entire credit journey - from marketing, to product offers, real-time transaction approvals, and more. The Customer Resiliency team in Card Intelligent Decisions & Experiences (CIDX) is responsible for helping Capital One’s most vulnerable customers in times of financial difficulty. This team builds solutions and enablers that help our customers get back on their feet and reestablish themselves from their moments of difficulty. Capital One will consider sponsoring a new qualified applicant for employment authorization for this position.

Second: Responsibilities.

Responsibilities

• Articulate and evangelize a bold technical vision for your domain
• Decompose complex problems into practical and operational solutions
• Ensure the quality of technical design and implementation
• Serve as an authoritative expert on non-functional system characteristics, such as performance, scalability and operability
• Continue learning and injecting advanced technical knowledge into our community
• Handle several projects simultaneously, balancing your time to maximize impact
• Act as a role model and mentor within the tech community, helping to coach and strengthen the technical expertise and know-how of our engineering and product community