Full-stack Engineer 4 (Distributed data & AWS) (Cloud Operations Resilience Engineering)
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to extract content. Let's parse the posting: - Intro: "Do you love building and pioneering in the technology space? ..." This is about the role, maybe "About the role". We'll put that as prose in
. - Then description of role: "At Capital One, you'll be part of a big group..." etc. Could be part of About the role. - Then "What You’ll Do:" list of duties. That's Responsibilities. - Then "Basic Qualifications:" list. That's Requirements (or Qualifications). They also have "Preferred Qualifications:" list. Could be Qualifications (maybe combine basic and preferred). But we need sections: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Pay info: salary ranges per location. That's Pay. We have Benefits: mention of comprehensive benefits, performance based incentive compensation, health, financial, other benefits. That's Benefits. We have Schedule? Not mentioned explicitly. No schedule info. So we should not include Schedule section. We have Skills? Could extract from qualifications: languages, tools, etc. Could put under Skills section. But we already have Qualifications (basic and preferred). Might be better to have Requirements (basic qualifications) and Qualifications (preferred). Skills could be derived from the list of technologies: Java, Scala, Python, Go, Node.js, JavaScript, TypeScript, Open Source RDBMS and NoSQL databases, Docker, Kubernetes, AWS tools, etc. Could be a Skills section. We need to avoid repeating job title as heading. No Job ID. We must remove boilerplate: EEO, immigration statement, accommodation, etc. Also remove "At this time, Capital One will not sponsor..." that's immigration statement, remove. Also remove "Learn more at the Capital One Careers website." etc. Also remove "Eligibility varies..." etc. Also remove "This role is expected to accept applications for a minimum of 5 business days. No agencies please." etc. Also remove "Capital One is an equal opportunity employer..." etc. Also remove "Capital One promotes a drug-free workplace." etc. Also remove "Capital One will consider for employment qualified applicants with a criminal history..." etc. Also remove accommodation contact lines. Also remove "For technical support or questions..." etc. Also remove "Capital One does not provide, endorse nor guarantee..." etc. Also remove the note about Canada/UK/Philippines. We must preserve all substantive information: duties, qualifications, pay, benefits. Let's extract substantive content: About the role / overview: - "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 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. The Cloud Operations Resilience Engineering (CORE) Technology division is responsible for enabling and evolving Capital One’s foundational cloud infrastructure layer, including observability, connectivity, resilience and availability." That's substantive. Responsibilities (What You’ll Do): List items: - 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 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 Preferred Qualifications: - Master’s Degree in Computer Science or a related quantitative field. - 7+ years of experience coding with two or more of the following: Go, Java, JavaScript/TypeScript, Python, Rust, C#, or Scala. - 4+ years of experience creating synchronous and asynchronous APIs. - 4+ years of experience with public cloud platforms (AWS, Microsoft Azure, Google Cloud), including cloud-based productivity tools, virtualization, and troubleshooting technical issues. - 4+ years of experience with distributed data/computing tools (e.g., MapReduce, Hadoop, Hive, EMR, Kafka, Spark, Gurobi, or MySQL). - 4+ years of experience building real-time data and streaming applications. - 3+ years of experience with database design and database management systems (DBMS). - 4+ years of experience using and contributing to open-source frameworks. - 3+ years of experience with CI/CD pipelines, Infrastructure as Code (IaC), and automated testing frameworks. - 3+ years of experience using Git-based version control systems (e.g., Git, GitHub, Bitbucket). - 1+ years of experience leveraging observability platforms to identify and optimize performance bottlenecks in distributed systems. - 1+ years of experience mentoring engineers and driving professional development within technical teams. - Experience leveraging modern, interactive AI tooling, IDE copilots, and AI-based coding assistants to accelerate productivity 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 engineering teams. Pay: - McLean, VA: $197,300 - $225,100 for Full-stack Engineer 4 - Plano, TX: $179,400 - $204,700 for Full-stack Engineer 4 - Richmond, VA: $179,400 - $204,700 for Full-stack Engineer 4 - 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. - Eligibility varies based on full or part-time status, exempt or non-exempt status, and management level. (But that's somewhat boilerplate; but it's about benefits eligibility. Might keep as part of benefits.) We should not include "Eligibility varies..." if it's considered boilerplate? It's about benefits eligibility, but it's generic. Might keep as part of benefits but it's not specific. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Eligibility varies based on full or part-time status, exempt or non-exempt status, and management level." is generic but still about benefits. Might keep. We also have "Learn more at the Capital One Careers website." that's application instruction? Remove. We also have "This role is expected to accept applications for a minimum of 5 business days. No agencies please." Remove. We also have "Capital One is an equal opportunity employer..." Remove. We also have "Capital One promotes a drug-free workplace." Remove. We also have "Capital One will consider for employment qualified applicants with a criminal history..." Remove. We also have accommodation contact lines. Remove. We also have "For technical support or questions about Capital One's recruiting process, please send an email to Careers@capitalone.com" Remove. We also have "Capital One does not provide, endorse nor guarantee and is not liable for third-party products..." Remove. We also have the note about Canada/UK/Philippines. Remove. Now we need to decide sections. We could have:
About the role
...overview...
Responsibilities
- ...
Requirements
- ... basic qualifications ...
Qualifications
- ... preferred qualifications ...
Skills
- maybe list of technologies: Java, Scala, Python, Go, Node.js, JavaScript, TypeScript, Open Source RDBMS, NoSQL databases, Docker, Kubernetes, AWS tools/services, etc. But we already have many in responsibilities and qualifications. Could still create a Skills section summarizing key technical skills: programming languages, cloud platforms, container orchestration, observability, CI/CD, etc. But we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one "Qualifications" section, and have Skills separate? Or we could have Requirements (basic) and Qualifications (preferred) as separate sections. That's two sections. Skills could be derived from responsibilities but maybe not needed. However we have a "Skills" heading in the list of allowed headings. We could include it if we have specific skill content not already covered. The posting includes many specific skills in responsibilities and qualifications. Could create a Skills section that enumerates them: Java, Scala, Python, Go, Node.js, JavaScript, TypeScript, Open Source RDBMS, NoSQL databases, Docker, Kubernetes, AWS, observability platforms, CI/CD, IaC, Git, etc. That would be substantive and not just a repeat. But we already have them in qualifications. However it's okay to have some overlap as long as we preserve all info. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep all details. If we put them in Qualifications and also in Skills, we would be duplicating info, which is allowed? It says do not repeat the job title as a heading and do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. It doesn't forbid repeating content across sections, but we should avoid unnecessary duplication. Better to keep qualifications (basic and preferred) and maybe not have a separate Skills section unless we can extract skills not already captured. But the qualifications already list many skills. However the responsibilities also list usage of languages etc. So we could have a Skills section that aggregates the technologies mentioned across responsibilities and qualifications, but that would be summarizing, which might be okay but risk losing detail? The instruction says do NOT invent or summarize away detail. Summarizing could be considered summarizing away detail if we omit some specifics. Better to keep the details as they appear in qualifications and responsibilities. So we can skip Skills section. Benefits: we have a paragraph about benefits. We'll put that. Pay: we have salary ranges and incentive compensation. We