Full-stack Engineer 4 (IC)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: 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. Could be "About the role". Then "What You’ll Do:" list of responsibilities. Then "Basic Qualifications:" list. Then "Preferred Qualifications:" list. Then "At this time, Capital One will not sponsor a new applicant for employment authorization..." That's legal/immigration note; we should remove as boilerplate. Then salary info: "The minimum and maximum full-time annual salaries for this role are listed below, by location. Please note that this salary information is solely for candidates hired to perform work within one of these locations, and refers to the amount Capital One is willing to pay at the time of this posting. Salaries for part-time roles will be prorated based upon the agreed upon number of hours to be regularly worked." Then list of locations with ranges. Then "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." Then 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." Then "This role is expected to accept applications for a minimum of 5 business days. No agencies please." That's application instruction; remove. Then EEO etc: remove. Thus sections we have: About the role (intro paragraph), Responsibilities (What You’ll Do), Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Skills (maybe combine tech stack from responsibilities?), Benefits, Pay, Schedule (maybe not present). There's no explicit schedule info. So we should not create Schedule section. We need to decide what goes into Skills section. The posting mentions technologies used: 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. Also mention front-end JavaScript or TypeScript frameworks, etc. Could put under Skills. But we must not invent content; we can extract from responsibilities and qualifications. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep each bullet point as is. Let's extract responsibilities bullet list: - 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 and direction across Agile teams, setting standards for design, development, and operational excellence - Partner with architects to define service boundaries, integration patterns, and reusable frameworks - Proactively identify areas for improvement, implementing targeted refactoring and contributing to efforts that reduce technical debt and enhance system performance - Influence long-term technology strategy through evaluation of emerging tools and practices in a ‘you build it, you own it’ environment Now Basic Qualifications bullet list: - Bachelor's Degree or higher in Computer Science or a related quantitative field (Statistics, Economics, Operations Research, Analytics, Mathematics, Engineering) - At least 4 years of experience in software engineering (Internship experience does not apply) - At least 2 years of experience with public cloud platforms (AWS, GCP, Azure), cloud-based productivity tools, or virtualization technologies Preferred Qualifications bullet list: - Master’s Degree in Computer Science or a related field - 7+ years of experience coding with more than two of the following: Go, Java, JavaScript/TypeScript, Python, Rust, C#, Scala - 3+ years of experience with database and database management systems - 3+ years of experience with AWS, GCP, Azure, or cloud-based productivity tools or virtualization technologies - 4+ years of experience contributing to open source frameworks - 3+ years of experience with front-end JavaScript or TypeScript frameworks - 4+ years of experience creating synchronous and asynchronous APIs - 3+ years of experience with CI/CD pipelines, infrastructure as code, and automated testing frameworks - 3+ years of experience using Git-based version-control systems (e.g., Git, GitHub, Bitbucket) - 3+ years of experience troubleshooting technical issues within cloud environments - Experience leveraging modern AI-based coding tools and IDE copilots - 1+ year of experience mentoring engineers and driving professional development within technical teams - 1+ year of experience leveraging observability to identify and optimize performance bottlenecks in distributed systems - 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 - Experience establishing and enforcing coding standards and design patterns across teams Now Skills: we could combine the tech stack from responsibilities and maybe from preferred qualifications. But we must not invent; we can list the technologies mentioned: Java, Scala, Python, Go, Node.js, JavaScript, TypeScript, Open Source RDBMS, NoSQL databases, Docker, Kubernetes, AWS tools and services, front-end JavaScript/TypeScript frameworks, etc. Also mention CI/CD, IaC, automated testing, Git, observability, AI-based coding tools, interactive AI tooling. However, some of those appear in preferred qualifications; we could still list them under Skills as they are substantive. But we need to ensure we are not duplicating content excessively; but it's okay to have overlapping info as long as we preserve all substantive info. However, we must not invent; we can list each technology as separate bullet points? Might be too granular but acceptable. Better: create a Skills section with a

  listing the technologies and tools mentioned across the posting. Ensure we don't miss any. Let's collect all distinct technologies/tools: Programming languages: Java, Scala, Python, Go, Node.js, JavaScript, TypeScript, Rust, C# (mentioned in preferred), maybe also others. Databases: Open Source RDBMS, NoSQL databases. Container Orchestration: Docker, Kubernetes. Cloud platforms: AWS, GCP, Azure. Cloud-based productivity tools (generic). Virtualization technologies (generic). Front-end JavaScript or TypeScript frameworks. CI/CD pipelines. Infrastructure as code. Automated testing frameworks. Git-based version-control systems (Git, GitHub, Bitbucket). Observability tools. Modern AI-based coding tools and IDE copilots. Interactive AI tooling. Also mention: microservices, distributed systems, Agile, etc. But those are more practices. We could include them as skills. But we need to be careful not to create too thin sections. However, the instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Skills into Responsibilities or Qualifications? But they asked to use sections like Skills if there is real specific content. There is specific content about technologies used; we can make a Skills section. Now Benefits: we have a paragraph about benefits. We can put that as

  . Pay: we have salary ranges per location. That's specific content; we should include Pay section with maybe a

  of locations and ranges. Schedule: no info; omit. Now About the role: we have intro paragraph(s). Could be two paragraphs; we can combine into one

  . Now we must not include boilerplate like "At this time, Capital One will not sponsor..." etc. Remove. Also remove "This role is expected to accept applications for a minimum of 5 business days. No agencies please." etc. Remove EEO, legal, accommodation, etc. Now produce HTML fragment. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Skills

  • ...
  ...

  Benefits

  ...

  Pay

  • Cambridge, MA: $197,300 - $225,100 for Full-stack Engineer 4
  • McLean, VA: $197,300 - $225,100 for Full-stack Engineer 4
  • New York, NY: $215,200 - $245,600 for Full-stack Engineer 4
  • Richmond, VA: $179,400 - $204,700 for Full-stack Engineer 4
  • San Francisco, CA: $215,200 - $245,600 for Full-stack Engineer 4
  • San Jose, CA: $215,200 - $245,600 for Full-stack Engineer 4
  Potentially also note that candidates hired to work in other locations will be subject to the pay range associated with that location. That's substantive; we could add a

  after the list. But we must not invent; we can include that statement as a

  . Now ensure we don't include any heading with empty content. Now check for any duplicated lines: we must not repeat. Now produce final HTML. Let's craft the About the role paragraph: "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 fine. Now Responsibilities list as above. Now Requirements list (Basic Qualifications). Now Qualifications list (Preferred Qualifications). Now Skills list: we need to decide what to include. Let's list each distinct technology/tool as bullet. But we must ensure we don't miss any from responsibilities: "Utilize programming languages like Java, Scala, Python, Go, Node.js, Java