Senior Full Stack Engineer (C#, .NET, Java)
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like immigration sponsorship note? That's a note but maybe considered minor metadata; we can fold into short
or drop. The note "Fidelity will not provide immigration sponsorship for this position" is a piece of info; we can include in a short paragraph maybe under About the role? But it's not a section heading. We'll include as a paragraph. We need to preserve all substantive information. Let's parse the job description. Content: - Intro: "A Senior Full Stack Engineer that thrives in an environment where we are using innovative technologies to provide first class digital experience for our clients and customers. You will be involved in building or enhancing existing capabilities that help millions of Fidelity’s customers prepare better for retirement while delivering industry best experiences." - The Team: description about being member of 401k or Defined Contribution (DC) Online Recordkeeping technology chapter within Workplace Investing business unit of Fidelity, responsibilities: design, development, testing, Production Support and deployment of scalable and innovative solutions that help 28+ million Fidelity’s customers plan and invest for retirement, manage and transact from their DC retirement accounts. Part of agile engineering scrum team, fast-paced, collaborating with product, architecture and other engineering teams. Based in Raleigh/Durham, NC. - The Experience You Have: list of qualifications/experience: * Bachelor’s or Master’s degree in Computer Science or a related technology discipline * 3+ years of software development experience on business critical, enterprise-wide applications * Aspirations to Tech Lead projects is a strong plus * Experience in designing, developing, and maintaining high-volume transactional systems. * Experience in building scalable, server-side enterprise applications, domain logic intensive RESTful APIs * Experience in developing cloud neutral applications in AWS/Azure * Ability to debug through legacy systems, C++ and COM, and capture current state to aid with modernization * Actively participates in and contributes to formal reviews of architecture, design, and code * Provides support for software releases into production environments * Experience leading and mentoring junior software developers * Fosters teamwork and collaboration across global development teams, business and systems partners. * Experience building technology solutions in the financial services industry is preferred. * Experience with Agile and Scrum Methodologies is preferred. - The Skills You Bring: list: * RESTful API design and development using JAVA / Microsoft .NET Core frameworks (C#). * Experience in design patterns and principles such as OO, DD, SOA, Microservices etc. * CI/CD experience using Azure DevOps and Jenkins. * Production Support experience required. * Leverage AI dev assist tools to speed up and deliver/contribute at a faster pace * Financial domain understanding. * An understanding of Micro-services Architecture and domain driven design patterns * Developing and deploying 12-factor, containerized (Docker, Kubernetes) API’s to AWS/Azure * Collaboration with producer and consumer teams to implement end-to-end solutions in a customer obsessed * Experience developing software utilizing relational databases * Experience with Test automation for unit, functional and non-functional testing (SOATEST, SOASTA, Cucumber) * Ability to develop technical artifacts based on analysis of business and systems requirements * Aptitude to discover/document implementations from legacy systems, C++, Java. .NET, as part of re- platform. * Experience in Tech leading medium sized projects is not required, but is a plus * Knowledge of the current technologies and evolving trends * Detail oriented coupled with strong analytical and problem-solving skills for Production support * Strong organizational skills coupled with effective written and verbal communication skills * Must be an organized self-starter with a collaborative work style, and the ability to multi-task. * Strong Team player and collaborator - Fidelity’s Onsite Working Model: description about transitioning to full-time onsite working model, phased rollout, currently some roles require 100% onsite, others less, expectations evolve, does not apply to fully remote roles. - Certifications Category: Information Technology - Legal boilerplate: "Please be advised that Fidelity’s business is governed by the provisions of the Securities Exchange Act of 1934, the Investment Advisers Act of 1940, the Investment Company Act of 1940, ERISA, numerous state laws governing securities, investment and retirement-related financial activities and the rules and regulations of numerous self-regulatory organizations, including FINRA, among others. Those laws and regulations may restrict Fidelity from hiring and/or associating with individuals with certain Criminal Histories." We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The legal paragraph is likely boilerplate; we should remove it. Also "Certifications Category: Information Technology" maybe minor metadata; could be folded into a short p or dropped. Probably we can include as a short p under a section like "Additional Info". But we have no heading for that; we could just include as a paragraph after sections. We must not create Pay/Schedule/Benefits sections unless posting actually states them. There's no explicit pay, schedule, benefits. There's onsite working model description; that could be considered Schedule? But it's not explicit schedule like full-time/part-time; it's about onsite expectations. Could be considered Schedule? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does mention onsite working model, which is about schedule/location. Might be considered Schedule? However they said "Schedule" heading for schedule info like full-time/part-time, shift etc. The onsite model is more about work location. Could be considered under "About the role" or a separate section like "Work Model". But we only allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put onsite model under About the role or Responsibilities. Probably better to include under About the role as a paragraph. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment. We'll structure:
About the role
... intro + team + location + onsite model ...
Responsibilities
- ... list of responsibilities from The Team section? Actually responsibilities include design, development, testing, Production Support, deployment, collaborating, etc. We'll extract.
Requirements
Maybe combine Experience You Have and Skills You Bring? But we have headings: Requirements, Qualifications, Skills. We need to decide which to use. The posting has "The Experience You Have" (qualifications) and "The Skills You Bring" (skills). We could map Experience You Have to Requirements or Qualifications. Skills You Bring to Skills. We'll produce sections: Requirements (maybe for experience), Qualifications (maybe for education?), Skills (for skills). But we must not create thin sections; better to have a few substantive sections. Could combine Experience and Skills into one "Requirements" and another "Skills". But we have both headings allowed. Let's think: The posting includes both experience and skills; we could have: -About the role
-Responsibilities
-Qualifications
(Education + years experience) -Skills
(technical skills) But we also have "Requirements" heading; maybe we can use Requirements for the experience + qualifications combined, and Skills for technical skills. However we need to avoid duplication. Let's decide: We'll use:About the role
Intro + team + location + onsite model.
Responsibilities
- list of responsibilities from The Team: design, development, testing, Production Support, deployment of scalable solutions; collaborate with product, architecture, other engineering teams; agile scrum team; fast-paced environment; etc.
Qualifications
- list from The Experience You Have: degree, 3+ years experience, aspirations to Tech Lead (plus), high-volume transactional systems, scalable server-side enterprise apps, domain logic intensive RESTful APIs, cloud neutral AWS/Azure, debug legacy systems, participate in architecture/design/code reviews, support software releases, lead/mentor junior devs, foster teamwork across global teams, financial services industry experience preferred, Agile/Scrum experience preferred.
Skills
- list from The Skills You Bring: RESTful API design using Java/.NET Core, design patterns OO/DD/SOA/Microservices, CI/CD Azure DevOps/Jenkins, Production Support required, leverage AI dev assist tools, financial domain understanding, microservices architecture & domain driven design, 12-factor containerized Docker/K8s APIs to AWS/Azure, collaboration with producer/consumer teams for end-to-end solutions customer obsessed, experience with relational databases, test automation unit/functional/non-functional (SOATEST, SOASTA, Cucumber), develop technical artifacts from business/system requirements, discover/document implementations from legacy systems C++/Java/.NET as part of re-platform, experience tech leading medium sized projects plus, knowledge of current tech/trends, detail oriented strong analytical/problem-solving for production support, strong organizational skills effective written/verbal communication, organized self-starter collaborative multi-task, strong team player collaborator.
We should also include the note about immigration sponsorship? Could be a short p under About the role: "Note: Fidelity will not provide immigration sponsorship for this position." We'll include as a paragraph.
We must not include legal boilerplate. Remove Certifications Category line? Could be minor metadata; we can drop.
Now ensure we don't repeat job title as heading. Not.
We must not include any empty sections. All sections have content.
We'll output HTML fragment.
Let's craft the content precisely, preserving all substantive information. Avoid inventing or summarizing away detail. Must preserve all details; we can paraphrase but must keep meaning. We'll try to keep the details as close as possible.
Let's write.
About the role paragraph:
"A Senior Full Stack Engineer that thrives in an environment where we are using innovative technologies to provide first class digital experience for our clients and customers. You will be involved in building or enhancing existing capabilities that help millions of Fidelity’s customers prepare better for retirement while delivering industry best experiences. As a member of the 401k or Defined Contribution (DC) Online Recordkeeping technology chapter within the Workplace Investing business unit of Fidelity, you will be responsible for design, development, testing, Production Support and deployment of scalable and innovative solutions that help 28+ million Fidelity’s customers plan and invest for retirement, manage and transact from their DC retirement accounts. You will be part of an agile engineering scrum team working in a fast-paced environment, closely collaborating with product, architecture and other engineering teams. This position is based in Raleigh/Durham, NC. Fidelity is transitioning to a full-time onsite working model through a phased rollout across regions and roles; currently some roles and locations require 100% onsite presence, while others require less, and onsite expectations are likely to evolve as the rollout continues. Note: Fidelity will not provide immigration sponsorship for this position."
That seems to capture all.
Responsibilities: We can list bullet points:
- Design, develop, test, provide Production Support, and deploy scalable and innovative solutions for the 401k/DC Online Recordkeeping platform.
- Collaborate with product, architecture, and other engineering teams within an agile scrum team.
- Contribute to formal reviews of architecture, design, and code.
- Support software releases into production environments.
- Lead and mentor junior software developers