Full-Stack Engineer 4 (Python, Java, AWS, CI/CD, GenAI) (Enterprise Platforms Technology)
or drop it." This immigration note is not minor metadata? It's a condition. Could be placed under Requirements as a note. But we need to preserve all substantive information. So we need to include that statement somewhere. Then salary info: "The minimum and maximum full-time annual salaries for this role are listed below, by location.... McLean, VA: $197,300 - $225,100 for Full-stack Engineer 4 ..." Also mention performance based incentive compensation. That's Pay section. 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." That's Benefits. Schedule: Not explicitly mentioned. No schedule info. So we should not create Schedule section. Also there is "This role is expected to accept applications for a minimum of 5 business days. No agencies please." That's application instruction, should be removed. EEO etc: remove. Thus sections we have: About the role (intro), Responsibilities (What You’ll Do), Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Skills (maybe list of technologies? Could be part of Responsibilities? But we have a list of programming languages etc in responsibilities. Could create Skills section from that list. However we need to avoid thin sections. The responsibilities already include that list; we could keep it there. But we could also extract skills. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we keep Responsibilities includes the tech stack. Skills section may be thin if we just list languages. Better to keep within Responsibilities. Qualifications: we have Basic and Preferred. Could combine into Requirements and Qualifications sections. Basic Qualifications as Requirements, Preferred as Qualifications. Pay: we have salary range and incentive compensation. Benefits: we have description. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Benefits. We must not include Schedule. Now format: Use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. So we must include all points from each section.
Let's extract About the role prose: The initial paragraph(s) before "What You’ll Do:":
"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. Enterprise Platforms Technology (EPTech) comprises many of Capital One’s most important enterprise platforms. We play an essential role in establishing practices for building technology solutions across the company, while also delivering capabilities that exemplify those practices."
We need to keep that as prose in
.
Now Responsibilities: list after "What You’ll Do:" each bullet starts with a verb. Let's capture them:
- 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
We need to keep all these as list items.
Now Requirements (Basic Qualifications):
- 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
We need to keep that.
Now Qualifications (Preferred Qualifications): list many items. Let's capture each bullet:
- 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
- 5+ years of experience with AWS
- 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
We need to keep all.
Now Pay: The salary info and incentives.
Paragraph: "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. McLean, VA: $197,300 - $225,100 for Full-stack Engineer 4 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."
We need to keep all that as prose. Could also make a list? It's prose. Use
.
Now 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 keep as prose.
Now we must remove boilerplate: immigration note, EEO, equal opportunity, etc. Also remove "At this time, Capital One will not sponsor a new applicant for employment authorization, or offer any immigration related support for this position..." That's substantive? It's a condition about sponsorship. Should we keep? It's substantive info about visa sponsorship. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep that note somewhere. Where to place? Could be under Requirements as a note, or maybe a separate section like "Work Authorization". But we don't have a heading for that; we could fold into Requirements as a short paragraph. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." This is not minor metadata; it's a condition. So we should keep it, maybe as a paragraph under Requirements or a separate section like "Eligibility". But we don't have a heading for that; we could add a section "Work Authorization" but that's not in the allowed headings list? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could add a new heading only if posting has real specific content for it. The instruction: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid adding a section not in the list, but the list is given as examples. However they said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That suggests we should stick to those headings. So we should fold the sponsorship note into one of those sections, likely Requirements (as it's about eligibility). So we can add a paragraph after the list under Requirements.
Similarly, there is a line: "This role is expected to accept applications for a minimum of 5 business days. No agencies please." That's application instruction, should be removed per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So drop that.
EEO etc: remove.
Now we need to ensure we don't include any duplicated lines.
Now produce HTML fragment.
Structure:
About the role
... (the intro paragraph)
Responsibilities
- ...
...
Requirements
- ...
...
At this time, Capital One will not sponsor a new applicant for employment authorization, or offer any immigration related support for this position (e.g. H1B, F-1 OPT, F-1 STEM OPT, F-1 CPT, J-1, TN, E-3, and O-1, or any other forms of work authorization that require immigration support from an employer).
Qualifications
- ...
...
Pay
... (
for prose. We need to preserve all substantive information, not invent or summarize away detail. So we must include all points from each section. Let's extract About the role prose: The initial paragraph(s) before "What You’ll Do:": "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. Enterprise Platforms Technology (EPTech) comprises many of Capital One’s most important enterprise platforms. We play an essential role in establishing practices for building technology solutions across the company, while also delivering capabilities that exemplify those practices." We need to keep that as prose in
. Now Responsibilities: list after "What You’ll Do:" each bullet starts with a verb. Let's capture them: - 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 We need to keep all these as list items. Now Requirements (Basic Qualifications): - 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 We need to keep that. Now Qualifications (Preferred Qualifications): list many items. Let's capture each bullet: - 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 - 5+ years of experience with AWS - 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 We need to keep all. Now Pay: The salary info and incentives. Paragraph: "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. McLean, VA: $197,300 - $225,100 for Full-stack Engineer 4 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." We need to keep all that as prose. Could also make a list? It's prose. Use
. Now 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 keep as prose. Now we must remove boilerplate: immigration note, EEO, equal opportunity, etc. Also remove "At this time, Capital One will not sponsor a new applicant for employment authorization, or offer any immigration related support for this position..." That's substantive? It's a condition about sponsorship. Should we keep? It's substantive info about visa sponsorship. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep that note somewhere. Where to place? Could be under Requirements as a note, or maybe a separate section like "Work Authorization". But we don't have a heading for that; we could fold into Requirements as a short paragraph. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." This is not minor metadata; it's a condition. So we should keep it, maybe as a paragraph under Requirements or a separate section like "Eligibility". But we don't have a heading for that; we could add a section "Work Authorization" but that's not in the allowed headings list? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could add a new heading only if posting has real specific content for it. The instruction: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid adding a section not in the list, but the list is given as examples. However they said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That suggests we should stick to those headings. So we should fold the sponsorship note into one of those sections, likely Requirements (as it's about eligibility). So we can add a paragraph after the list under Requirements.
Similarly, there is a line: "This role is expected to accept applications for a minimum of 5 business days. No agencies please." That's application instruction, should be removed per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So drop that.
EEO etc: remove.
Now we need to ensure we don't include any duplicated lines.
Now produce HTML fragment.
Structure:
About the role
... (the intro paragraph)
Responsibilities
- ... ...
Requirements
- ... ...
At this time, Capital One will not sponsor a new applicant for employment authorization, or offer any immigration related support for this position (e.g. H1B, F-1 OPT, F-1 STEM OPT, F-1 CPT, J-1, TN, E-3, and O-1, or any other forms of work authorization that require immigration support from an employer).
Qualifications
- ... ...
Pay
... (