Full-stack Engineer 4
Capital One · Richmond, VA · 3 wk ago
Engineering$197k–$225k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- Intro paragraph: "Do you love building..." etc. That's about the role? Could be "About the role". We'll put that as
About the role
withcontaining the intro sentences. - Responsibilities: The bullet list after "What You’ll Do:" includes many items. We'll put under
Responsibilities
with- each bullet.
- Basic Qualifications: list of bullet points. Could be under
Requirements
(or Qualifications). The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide mapping. Basic Qualifications likely go under Requirements. Preferred Qualifications maybe under Qualifications or Skills? The posting includes "Preferred Qualifications:" with many bullet points. Could treat as Qualifications. Also there is a list of specific technical skills (languages, tools) within responsibilities; but we could also have Skills section summarizing those? However we must not invent content; we can extract skills from responsibilities and qualifications. But we must not summarize away detail; we need to preserve all substantive info. If we create a Skills section, we must include the specific skills mentioned. Could we just put them under Responsibilities? The responsibilities already list languages etc. Might be okay to not have separate Skills section if not needed. But we need to include sections only when posting has real specific content for it. We have content for About the role, Responsibilities, Requirements (basic qualifications), Qualifications (preferred qualifications). Benefits: 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 generic but still mentions benefits. It's not specific like health insurance etc. It says "Learn more at the Capital One Careers website." That's vague. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The benefits statement is somewhat generic but still states that there are benefits. Is that enough? It says "Capital One offers a comprehensive, competitive, and inclusive set of health, financial and other benefits". That's specific enough to mention benefits exist. We could include a Benefits section with that sentence. However we must not invent details; we can just put that sentence. Pay: The posting includes salary ranges per location. That's specific. So we need a Pay section with that info. Should we list each location with ranges? Yes. Schedule: Not mentioned. No info about schedule (full-time implied). Not specific. So we should not create Schedule section. Now we need to ensure we don't repeat job title as heading. The job title is "Full-stack Software Engineer". Not used as heading. We need to strip boilerplate: EEO, immigration statement, etc. Remove lines like "At this time, Capital One will not sponsor a new applicant..." etc. Also remove "No agencies please." etc. Also remove "Capital One is an equal opportunity employer..." etc. Also remove accommodation contact lines etc. Also remove legal disclaimer about third-party products etc. Also remove the paragraph about Capital One Financial entities etc. Also remove the line about "This role is expected to accept applications for a minimum of 5 business days." That's maybe boilerplate but it's substantive? It's about application timeline; could be considered boilerplate but it's specific. However instruction says remove application instructions. That line is about application period, maybe considered application instruction. Safer to remove. Also remove "Learn more at the Capital One Careers website." That's part of benefits sentence; we could keep it as part of benefits? It's a reference; maybe keep but it's not boilerplate? It's a link suggestion. Might be okay to keep as part of benefits paragraph. We need to preserve all substantive information: responsibilities, basic qualifications, preferred qualifications, pay ranges, benefits statement. Now craft HTML. Structure: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 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
Requirements
- 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
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
- 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 leveraging modern AI-based coding tools and IDE copilots
- 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
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.
Pay
- McLean, VA: $197,300 - $225,100 for Full-stack Engineer 4
- New York, NY: $215,200 - $245,600 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
- Riverwoods, IL: $179,400 - $204,700 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.