Jobs · Engineering · Virginia

Full-stack Engineer 4 (GoLang)

Capital One · McLean, VA · 4 wk ago
Engineering$179k–$205k/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 specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Must preserve all substantive info. We need to parse the posting. Content: Intro 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. Then "What You’ll Do:" list of responsibilities. 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 Then "Basic Qualifications:" list. - 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 Then "Preferred Qualifications:" list. - 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 Then immigration note: "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)." This is likely boilerplate/legal; we should remove it as per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is legal/immigration note; likely remove. Then salary info: "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: $179,400 - $204,700 for Full-stack Engineer 4 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 include Pay section if posting actually states them. Yes, they give salary ranges for two locations. So we should include Pay section with that info. 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 info. Should include Benefits section. Schedule: Not mentioned explicitly. There's "This role is expected to accept applications for a minimum of 5 business days." That's about application period, not schedule. No schedule info. So we should not include Schedule section. Also there is EEO statement: "Capital One is an equal opportunity employer (EOE, including disability/vet) committed to non-discrimination in compliance with applicable federal, state, and local laws." That's boilerplate; remove. Also drug-free workplace, criminal history accommodation, etc. Remove. Also technical support email etc. Remove. Also note about Capital One entities in Canada etc. Remove. Thus sections: About the role (intro paragraph), Responsibilities (list under What You’ll Do), Requirements (maybe Basic Qualifications?), Qualifications (Preferred Qualifications?), Skills (maybe combine technical skills from responsibilities? But we have separate sections for Requirements and Qualifications; we could put Basic Qualifications under Requirements, Preferred Qualifications under Qualifications. Skills maybe we could extract from responsibilities like programming languages, tools etc. But we already have those in responsibilities. Could also create Skills section summarizing technical skills: Java, Scala, Python, Go, Node.js, JavaScript, TypeScript, Open Source RDBMS, NoSQL, Docker, Kubernetes, AWS tools, etc. However we must not invent or summarize away detail; we can extract from responsibilities. The responsibilities already list those; we could keep them there. But we need to decide sections. We have: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to avoid thin sections. If we put Skills, we need substantive content. Could we combine Skills into Responsibilities? Probably better to keep Responsibilities as is, and not create Skills unless we have distinct skill list not already covered. The responsibilities list includes many technologies; we could still create Skills section summarizing them, but that would be duplicative. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we skip Skills section and keep Responsibilities covering skills. Requirements and Qualifications sections are substantive. Benefits and Pay also. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now we need to format. Use

for section headings. Use
  • for any list of duties/requirements/benefits. Use

    for prose. Do not repeat job title as heading. Do not put Job ID/requisition numbers as headings. We must preserve ALL substantive information; do not invent or summarize away detail. We need to include all substantive info from the posting, except boilerplate removed. Let's extract substantive info: About the role paragraph: The intro paragraph before "What You’ll Do:" includes multiple sentences. We'll keep as

    . Responsibilities: list items as above. Requirements: Basic Qualifications list. Qualifications: Preferred Qualifications list. Benefits: The 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." We should keep that as

    maybe with a note about learning more. Pay: Salary ranges and incentive info. We need to include the salary ranges for Chicago, IL and McLean, VA, plus note about other locations, part-time proration, performance based incentive compensation. We should keep that as

    maybe with

      for locations? The instruction: Use
      • for any list of duties/requirements/benefits. Pay is not a list but could be presented as prose. Could also list locations as
          . But it's not a list of duties/requirements/benefits; it's pay info. Could be

          . We'll keep as

          . We must not include boilerplate like "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 substantive; keep. Also "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." Keep. Now we need to remove duplicated lines: There's no duplication. Now produce HTML. Structure:

          About the role

          ...

          Responsibilities

          • ...
          • ...

          Requirements

          • ...
          • ...

          Qualifications

          • ...
          • ...

          Benefits

          ...

          Pay

          ...

          Make sure no extra whitespace? It's fine. Now craft the content precisely. About the role paragraph: Combine the intro sentences: "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 the paragraph. Now Responsibilities list items exactly as given. Check each: - 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,

Similar jobs