Full-Stack Engineer 4 (Golang, AWS)

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove immigration sponsorship statement? That's legal/EEO? It's about work authorization; likely considered legal boilerplate, should be removed. Also remove "Capital One offers a comprehensive..." benefits description? That's benefits content, we can keep but need to format as Benefits section. Also need Pay section: salary ranges given. Schedule? Not mentioned. So we should not include Schedule heading if no content. We need to parse the posting for sections: - About the role: introductory paragraph(s) describing role, mission, etc. The first 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 about the role. - What You’ll Do: responsibilities list. That's responsibilities. - Basic Qualifications: qualifications (maybe Requirements). Preferred Qualifications: also qualifications or skills? We'll treat as Requirements (basic) and Preferred Qualifications as additional qualifications or maybe Skills. But we have separate sections: Requirements, Qualifications, Skills. We need to decide mapping. We have Basic Qualifications (education, experience). Preferred Qualifications (more experience, skills). Also list of technologies used: programming languages, tools etc. That could be Skills. We need to avoid duplication. We'll create sections: - About the role (intro paragraph) - Responsibilities (the "What You’ll Do:" bullet list) - Requirements (Basic Qualifications) - Qualifications (Preferred Qualifications) maybe combine? But we have both sections; we can put Basic under Requirements, Preferred under Qualifications. - Skills (the list of programming languages, tools, etc.) Actually the responsibilities already list many technologies; but also there is a list under "Utilize programming languages like ..." which is part of responsibilities. Could treat that as Skills. However we need to avoid duplication. Perhaps we can put the technology list under Skills, and keep responsibilities focused on actions. Let's extract responsibilities bullet points from "What You’ll Do:" after colon. The text after colon is a long sentence with multiple items separated by line breaks? Actually it's a paragraph with multiple clauses separated by line breaks? Let's parse: "What You’ll Do: 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 companyShare 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 communityCollaborate with digital product managers, and deliver robust cloud-based solutions that drive powerful experiences to help millions of Americans achieve financial empowermentUtilize 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 servicesProvide technical leadership and direction across Agile teams, setting standards for design, development, and operational excellencePartner with architects to define service boundaries, integration patterns, and reusable frameworksProactively identify areas for improvement, implementing targeted refactoring and contributing to efforts that reduce technical debt and enhance system performanceInfluence long-term technology strategy through evaluation of emerging tools and practices in a ‘you build it, you own it’ environment" It seems missing spaces between clauses; but we can split by capital letters after a period? Actually there are no periods. We'll need to manually separate into sensible bullet points: - 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 That seems reasonable. Now 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 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: maybe we can extract the list of programming languages, tools etc from responsibilities and also from preferred qualifications. But to avoid duplication, we could put a Skills section that lists the technologies: Java, Scala, Python, Go, Node.js, JavaScript, TypeScript, Open Source RDBMS, NoSQL databases, Docker, Kubernetes, AWS tools/services, etc. Also maybe mention front-end JS/TS frameworks, CI/CD, IaC, automated testing, Git, observability, AI coding tools, etc. However many of those appear in Preferred Qualifications. To avoid duplication, we could decide to not have a separate Skills section and instead put those under Responsibilities or Qualifications. But the instruction says we can have Skills section if posting has real specific content. The posting does have specific content about technologies used. So we can include Skills section summarizing the technologies (maybe combine from responsibilities and preferred). However we must not invent or summarize away detail; we must preserve ALL substantive information. If we put them in Skills, we need to ensure we don't lose any detail from other sections. We can keep the responsibilities bullet points as is (they already mention technologies). If we also list them in Skills, that would be duplication but maybe acceptable? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited but might be redundant. Better to avoid duplication by not repeating same info. We could keep responsibilities as actions, and Skills as a list of technologies/tools (non-action). However responsibilities already mention technologies in a bullet; we could keep that bullet but maybe rephrase to focus on action and keep technologies in Skills. But we must not lose the detail that they utilize those languages etc. If we move that detail to Skills, we still preserve it. So we can adjust responsibilities bullet to not list the technologies, but keep the action "Utilize programming languages...". However that bullet includes the list; if we remove the list, we lose detail. Better to keep the bullet as is and not have a separate Skills section, or have Skills section that lists additional technologies not already mentioned. But many are mentioned. Given the instruction to prefer a few substantive sections over many thin ones, maybe we skip Skills section and keep tech list under Responsibilities. Then we have About the role, Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay. Benefits: we have a paragraph about 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 content. We'll keep that. Pay: salary ranges for locations. Schedule: none. We must remove boilerplate: immigration sponsorship statement, EEO statements, accommodation contact, legal disclaimers, etc. Also remove "This role is expected to accept applications for a minimum of 5 business days. No agencies please." That's application instructions; remove. Also remove "Capital One is an equal opportunity employer..." etc. Remove all that. Now produce HTML fragment with sections as needed. Structure:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Benefits

...

Pay

...

We must not include Schedule. Now ensure we preserve all substantive info from sections we kept. About the role paragraph: we need to include the exact sentences? We can combine them but must not summarize away detail. We'll keep the paragraph as is: "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. Responsibilities bullets: we need to ensure we keep all content from the "What You’ll Do:" section. We'll list as above. Check that we didn't miss any content: The responsibilities also included "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". Good. "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