Jobs · Engineering · Virginia

Staff Full Stack Engineer (Reliability Engineering)

Capital One · Richmond, VA · 3 wk ago
Engineering$245k–$279k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We need to parse the posting. First, the posting includes a description: "As a Staff Engineer at Capital One, you will be part of a community...". That's about the role. Then "What You’ll Do:" list of responsibilities. Then "Basic Qualifications:" and "Preferred Qualifications:" which are qualifications. Also there is mention of "Capital One will consider sponsoring a new qualified applicant for employment authorization for this position." That's maybe a note but not a section. Salary info: "The minimum and maximum full-time annual salaries for this role are listed below, by location." Then list of locations with salary ranges. That's Pay. Benefits: "Capital One offers a comprehensive, competitive, and inclusive set of health, financial and other benefits that support your total well-being." Also mention of eligibility etc. So we have benefits content. Schedule: Not mentioned. No schedule info. So we should not include Schedule. Skills: Not explicitly listed as a separate section; but we could embed skills within qualifications or responsibilities. The instruction: Use sections only when posting has real, specific content. There's no explicit "Skills" heading. Could we infer skills from qualifications? Probably better not to create a Skills section if not explicitly present. The posting does not have a "Skills" heading. So we omit Skills. Requirements: Could be Basic Qualifications? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what goes where. Likely "Basic Qualifications" and "Preferred Qualifications" go under Requirements and Qualifications? Actually they separate Requirements and Qualifications. Usually Requirements = basic qualifications, Qualifications = preferred qualifications. We'll map Basic Qualifications to Requirements, Preferred Qualifications to Qualifications. About the role: initial paragraph(s) before "What You’ll Do:". Responsibilities: the bullet list after "What You’ll Do:". Requirements: Basic Qualifications list. Qualifications: Preferred Qualifications list. Benefits: paragraph about benefits. Pay: salary table. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: EEO, accommodation, legal, etc. Also remove "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: that includes the description, responsibilities, qualifications, benefits, pay. We need to format lists with
  • . For prose use

    . We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About the role: The initial paragraph(s) before "What You’ll Do:". Text: "As a Staff Engineer at Capital One, you will be part of a community of technical experts working to define the future of banking in the cloud. You will work alongside our talented team of developers, machine learning experts, product managers and people leaders. Our Staff Engineers are leading experts in their domains, helping devise practical and reusable solutions to complex problems. You will drive innovation at multiple levels, helping optimize business outcomes while delivering strong technology solutions. At Capital One, we believe diversity of thought strengthens our ability to influence, collaborate and provide the most innovative solutions across organizational boundaries. You will promote a culture of engineering excellence and strike the right balance between lending expertise and providing an inclusive environment where the ideas of others can be heard and championed. You will lead the way in creating next-generation talent for Capital One Tech, mentoring engineers and actively recruiting to keep building our community. Staff Engineers are expected to lead through technical contribution. You will operate as a trusted advisor for our key technologies, platforms and capability domains, creating clear and concise communications, code samples, blog posts and other materials to share knowledge both inside and outside the organization. You will specialize in a particular subject area, but your input and impact will be sought and expected throughout the organization. As a Staff Engineer on our Reliability Engineering team, you will build developer-first platform solutions that transform system resilience from a compliance mandate into an intuitive, desirable standard for every engineer. You will treat our internal platform with the rigor of a competitive commercial product, mastering simplicity and driving out unnecessary complexity at scale. By embedding automated, real-time measurement directly into our infrastructure, you will prove that deep technical rigor and exceptional ease of use must always coexist." That's the about role. Now Responsibilities: after "What You’ll Do:" list: - Articulate and evangelize a bold technical vision for your domain - Decompose complex problems into practical and operational solutions - Ensure the quality of technical design and implementation - Serve as an authoritative expert on non-functional system characteristics, such as performance, scalability and operability - Continue learning and injecting advanced technical knowledge into our community - Handle several projects simultaneously, balancing your time to maximize impact - Act as a role model and mentor within the tech community, helping to coach and strengthen the technical expertise and know-how of our engineering and product community - Drive modernization of monolithic systems into microservice architectures and event-driven platforms - Collaborate with senior engineering and architecture leaders to define long-term platform strategy and API standards - Serve as a force-multiplier for the team, balancing deep, hands-on technical contribution and innovation with mentoring and elevating the skills of peers and junior engineers. - Lead cross-divisional projects and impacts that promote technological best practices and enhancements Note: The last bullet maybe missing period but fine. 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 7 years of experience in all of the following: Software engineering and solution architecture Enterprise architecture and design patterns Cloud computing (AWS, Microsoft Azure, Google Cloud) Data architecture" We need to preserve as list items. Now Preferred Qualifications: "Master’s Degree in Computer Science or Software Engineering 10+ years of experience in all of the following: Software engineering and solution architecture Enterprise architecture and design patterns Web technologies (JavaScript, TypeScript and SPA frameworks) Designing and building distributed HPC and ML systems Cloud computing (AWS, Microsoft Azure, Google Cloud) Data architecture 10+ years of professional experience coding in commonly used languages like Go, Java, JavaScript/Typescript, Python, Rust, C#, Scala 8+ years of experience with database and database management systems 10+ years of professional experience in the full lifecycle of system development, from conception through architecture, implementation, testing, deployment and production support 5+ years of experience with public cloud platforms (AWS, GCP, Azure), cloud-based productivity tools, or virtualization technologies 10+ years of experience with Networking protocols and integration with third party distributed systems 5+ years of experience mentoring senior engineers and driving professional development within technical teams 2+ years of experience leading cross-domain architectural reviews and establishing coding and design standards Expertise in the strategic application of agentic AI coding tools to solve systemic development challenges" 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 should keep that. Also maybe mention "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." That's also benefits/compensation. Could be part of Benefits or Pay? It's incentive compensation. Could be part of Benefits. We'll include it in Benefits section. Now Pay: "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. Chicago, IL: $244,700 - $279,200 for Staff Full-stack Engineer McLean, VA: $269,100 - $307,200 for Staff Full-stack Engineer New York, NY: $293,600 - $335,100 for Staff Full-stack Engineer Plano, TX: $244,700 - $279,200 for Staff Full-stack Engineer Richmond, VA: $244,700 - $279,200 for Staff Full-stack Engineer San Francisco, CA: $293,600 - $335,100 for Staff Full-stack Engineer 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." We need to preserve that. We'll format as a

    • each location line. Now we must not include Schedule. Now we need to output HTML with headings

      for each section. We'll have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to ensure we don't add empty sections. Now we need to strip any boilerplate like "Learn more at the Capital One Careers website." That's okay to keep as part of benefits. Now we need to ensure we don't include any duplicated lines. Now produce HTML. Let's craft. We'll start with

      About the role

      then

      ... the paragraph(s). The about role text is multiple sentences; we can keep as one

      containing all. Then

      Responsibilities

      then
      • each bullet. Then

        Requirements

        then
        • each bullet. Note: The basic qualifications includes a leading sentence "Bachelor's Degree or higher..." and then "At least 7 years of experience in all of the following:" then list. We could treat each line as separate
        • . Might be better to keep as separate items: Bachelor's Degree..., At least 7 years..., Software engineering..., Enterprise architecture..., Cloud computing..., Data architecture. We'll do that. Then

          Qualifications

          then
          • each bullet from preferred qualifications. Then

            Benefits

            then

            combine the benefits paragraph(s). We'll have two paragraphs: first about benefits, second about incentive compensation. Could combine into one

            with both sentences. Then

            Pay

            then
            • each location line. We need to ensure we don't include extra fluff like "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." That's substantive; we should include as prose maybe as a

              before the list. Also the line about candidates hired to work in other locations etc. Also include as prose. Thus Pay section: a

              with the explanatory sentences, then

              • location lines, then another

                for the final sentence about other locations. Now let's write. Check for any leftover boilerplate: We removed EEO, accommodation, legal, etc. Also removed "No agencies please." and

Similar jobs