Full-stack Engineer 5 (Java, Scala, AWS)

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Content: Intro: "Do you love building and pioneering in the technology space? Do you enjoy solving complex business problems in a fast-paced, collaborative, inclusive and iterative delivery environment? At Capital One, you'll be part of a big group of makers, breakers, doers and disruptors who solve real problems and meet real customer needs. We are seeking Full-stack Software Engineers who are passionate about leveraging cutting-edge open source frameworks and emerging technologies. In this role, you’ll be at the forefront of driving a major transformation across Capital One." That's about the role description. Then "What You’ll Do:" bullet list (actually sentences). Let's extract responsibilities: - Lead a portfolio of diverse technology projects and a team of developers with deep experience in distributed microservices, and full stack systems to create solutions that help meet regulatory needs for the company - Share your passion for staying on top of tech trends, experimenting with and learning new technologies, participating in internal & external technology communities, mentoring other members of the engineering community - Collaborate with digital product managers, and deliver robust cloud-based solutions that drive powerful experiences to help millions of Americans achieve financial empowerment - Utilize programming languages like Java, Scala, Python, Go, Node.js, JavaScript and TypeScript, Open Source RDBMS and NoSQL databases, Container Orchestration services including Docker and Kubernetes, and a variety of AWS tools and services - Provide technical leadership across multiple teams, shaping system architecture and long-term technology direction - Drive end-to-end design and implementation of large-scale, distributed, or cloud-native systems with high reliability and performance requirements - Partner with architects and product leaders to define platform roadmaps and shared services strategy That's responsibilities. Then "Basic Qualifications:" list: - Bachelor's Degree or higher in Computer Science or a related quantitative field (Statistics, Economics, Operations Research, Analytics, Mathematics, Engineering) - At least 6 years of experience in software engineering (Internship experience does not apply) - At least 3 years of experience with public cloud platforms (AWS, GCP, Azure), cloud-based productivity tools, or virtualization technologies Then "Preferred Qualifications:" long list. We need to decide sections: Basic Qualifications and Preferred Qualifications could be under Requirements and Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map. We have About the role (intro). Responsibilities (What You’ll Do). Requirements (Basic Qualifications). Qualifications (Preferred Qualifications). Skills maybe from responsibilities? Could also include technologies list as Skills. Benefits: The posting mentions "Capital One offers a comprehensive, competitive, and inclusive set of health, financial and other benefits that support your total well-being." That's a benefits statement. Also mentions performance based incentive compensation. So we have benefits content. Pay: The posting includes salary ranges for location: "McLean, VA: $229,900 - $262,400 for Full-stack Engineer 5". Also mentions performance based incentive compensation. So we have pay info. Schedule: Not mentioned. No schedule info. So we should not include Schedule section. We must not include boilerplate like EEO, etc. Remove those. We need to preserve all substantive information. So we need to include the salary range and mention incentive compensation. Also mention benefits description. We need to output HTML fragment only, no /. Use

for headings. Use

• for lists. Use

  for prose. We need to avoid repeating job title as heading. Not needed. We need to not include Job ID etc. We need to ensure we don't create sections with filler like "commensurate with experience". Not present. Let's craft sections:

  About the role

  Do you love building and pioneering in the technology space? Do you enjoy solving complex business problems in a fast-paced, collaborative, inclusive and iterative delivery environment? At Capital One, you'll be part of a big group of makers, breakers, doers and disruptors who solve real problems and meet real customer needs. We are seeking Full-stack Software Engineers who are passionate about leveraging cutting-edge open source frameworks and emerging technologies. In this role, you’ll be at the forefront of driving a major transformation across Capital One.

  Responsibilities

  • Lead a portfolio of diverse technology projects and a team of developers with deep experience in distributed microservices, and full stack systems to create solutions that help meet regulatory needs for the company
  • Share your passion for staying on top of tech trends, experimenting with and learning new technologies, participating in internal & external technology communities, mentoring other members of the engineering community
  • Collaborate with digital product managers, and deliver robust cloud-based solutions that drive powerful experiences to help millions of Americans achieve financial empowerment
  • Utilize programming languages like Java, Scala, Python, Go, Node.js, JavaScript and TypeScript, Open Source RDBMS and NoSQL databases, Container Orchestration services including Docker and Kubernetes, and a variety of AWS tools and services
  • Provide technical leadership across multiple teams, shaping system architecture and long-term technology direction
  • Drive end-to-end design and implementation of large-scale, distributed, or cloud-native systems with high reliability and performance requirements
  • Partner with architects and product leaders to define platform roadmaps and shared services strategy

  Requirements

  • Bachelor's Degree or higher in Computer Science or a related quantitative field (Statistics, Economics, Operations Research, Analytics, Mathematics, Engineering)
  • At least 6 years of experience in software engineering (Internship experience does not apply)
  • At least 3 years of experience with public cloud platforms (AWS, GCP, Azure), cloud-based productivity tools, or virtualization technologies

  Qualifications

  • Master’s Degree in Computer Science or a related field
  • 9+ years of experience coding with more than two of the following: Go, Java, JavaScript/TypeScript, Python, Rust, C#, Scala
  • 5+ years of experience contributing to open source frameworks
  • 5+ years of experience with front-end JavaScript or TypeScript frameworks
  • 5+ years of experience creating synchronous and asynchronous APIs
  • 4+ years of experience with database and database management systems
  • 4+ years of experience with AWS, GCP, Azure, or cloud-based productivity tools or virtualization technologies
  • 4+ years of experience with CI/CD pipelines, infrastructure as code, and automated testing frameworks
  • 4+ years of experience using Git-based version-control systems (e.g., Git, GitHub, Bitbucket)
  • 4+ years of experience troubleshooting technical issues within cloud environments
  • 3+ years of experience mentoring senior engineers and driving professional development within technical teams
  • 2+ years of experience leveraging observability to identify and optimize performance bottlenecks in distributed systems
  • 1+ year of experience leading architectural design reviews and influencing enterprise-wide technical standards and methodologies
  • 1+ year of experience establishing and enforcing coding standards and design patterns across teams
  • 1+ year of experience implementing observability and reliability practices at scale
  • Experience leveraging modern AI-based coding tools and IDE copilots
  • Experience influencing technology strategy at the portfolio or business unit level
  • Experience with interactive AI tooling to accelerate productivity, utilizing capabilities beyond basic code completion
  • Experience leading cross-functional engineering efforts or large-scale technical initiatives

  Skills

  We could extract skills from responsibilities: programming languages, cloud, containers, etc. But we already have many in qualifications. However we could still create a Skills section summarizing key technologies: Java, Scala, Python, Go, Node.js, JavaScript, TypeScript, Open Source RDBMS, NoSQL, Docker, Kubernetes, AWS, etc. But we need to avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we create Skills section, we need to include the skills mentioned elsewhere, but that's okay as long as we don't lose info. However we might be duplicating content; but that's allowed as long as we preserve all info. However we risk creating thin sections. The instruction: Prefer a few substantive sections over many thin ones. We already have About, Responsibilities, Requirements, Qualifications, Benefits, Pay. Skills could be considered thin if we just list technologies already covered. Might be better to omit Skills section and let the responsibilities and qualifications cover skills. The instruction says we can include Skills heading only if posting has real specific content for it. The posting does mention specific skills in responsibilities and qualifications, but not a dedicated "Skills" section. However we could still create a Skills section if we want, but risk being considered thin. Safer to omit Skills. Benefits: The posting says: "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." Also mentions performance based incentive compensation. That's benefits. We need to output Benefits section with that info. Pay: Salary range and incentive compensation. We need to ensure we don't include boilerplate like "Learn more at the Capital One Careers website." That's substantive? It's a reference; we can keep. We also need to remove EEO etc. Already omitted. Now construct HTML. Check for any other substantive content: "Capital One will consider sponsoring a new qualified applicant for employment authorization for this position." That's about visa sponsorship. Should we include? It's substantive. Where to put? Could be under About the role or maybe a separate section like "Visa Sponsorship". But we don't have a heading for that. Could incorporate into About the role paragraph. We'll add a sentence. Also: "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." That's pay/benefits. Also: "Capital One offers a comprehensive, competitive, and inclusive set of health, financial and other benefits that support your total well-being." That's benefits. Also: "Eligibility varies based on full or part-time status, exempt or non-exempt status, and management level." That's benefits detail. Also: "This role is expected to accept applications for a minimum of 5 business days." That's about application timeline; but instruction says remove application instructions. This is not instruction but maybe considered boilerplate? It's about application period. Might be considered administrative. Safer to remove? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This line is about application timeline, could be considered application instructions. Safer to remove. Also: "No agencies please." That's application instruction; remove. Also: "Capital One is an equal opportunity employer..." remove. Also: "Capital One promotes a drug-free workplace." remove. Also: "Capital One will consider for employment qualified applicants with a criminal history..." remove. Also: "If you have visited our website..." remove (accommodation). Actually accommodation request is maybe substantive? It's about accommodation request. Might be considered EEO/legal. Probably remove. Also: "For technical support or questions about Capital One's recruiting process..." remove. Also: "Capital One does not provide, endorse nor guarantee