Principal Software Engineer (Java, Spring Boot, REST)
Fidelity Investments · Denver, CO · 1 mo ago
On-siteEngineering$107k–$216k/yrFull-time
We need to output HTML fragment with sections: h3 headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. Let's parse the job description.
Content:
- Note about immigration sponsorship: "Fidelity will not provide immigration sponsorship for this position." This is a note; could be part of a short paragraph.
- "The Team Fidelity is looking for a Principal Full Stack Engineer to join the Fidelity Institutional Technology Development Team. This candidate will be applying strong software development and test automation skills to design, develop, test, deploy, maintain, and improve FIT customer-facing software solutions. You will also be enabling your Scrum team in accepting the development and automation frameworks and standard methodologies to ensure we are building the right product the right way."
That's about the role. Could be "About the role" section.
- "The Expertise You Have" bullet list: many items. That's qualifications/requirements.
- "The Skills You Bring" bullet list: skills.
- "The Value You Deliver" bullet list: maybe responsibilities? Actually value delivered could be responsibilities or impact.
- "Company Overview" paragraph: could be about company but maybe not needed as section? Could be omitted if not requested; but we can include as "About the company"? Not in allowed headings. Probably we should not include company overview unless we map to a section like "About the role"? But it's separate. The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. So we need to map content to those.
We have:
- About the role: description of team and what candidate will do.
- Responsibilities: maybe "The Value You Deliver" or "You will also be enabling your Scrum team..." Actually responsibilities could be derived from "The Expertise You Have"? No that's qualifications. Responsibilities could be tasks: design, develop, test, deploy, maintain, improve FIT customer-facing software solutions; enabling Scrum team; etc. Also "Developing/Deploying software in a fast-paced environment", "Collaborating with colleagues...", "Working closely with Architecture...", "Keeping up to date...", "Mentoring junior team members", etc. Those are from "The Value You Deliver". So we can put those under Responsibilities.
- Requirements: maybe "The Expertise You Have" (education, years experience, specific tech). Could be Requirements.
- Qualifications: maybe overlapping; but we can treat Requirements as hard requirements, Qualifications as preferred? The posting includes "Experience with brokerage and financial services application development is a plus", "Working knowledge of design system is a plus", "Knowledge of web security attack methods...". Those are pluses, could be Qualifications.
- Skills: "The Skills You Bring" list.
- Benefits: The posting mentions benefits: "We offer a wide range of benefits to meet your evolving needs..." includes health care, retirement, paid time off, parental leave, charitable giving match, educational assistance including student loan repayment, tuition reimbursement, learning resources. So we have benefits content.
- Pay: "The base salary range for this position is $107,000-216,000 USD per year." Also mention bonus/variable compensation. So we have Pay.
- Schedule: "Fidelity is transitioning to a full-time onsite working model..." includes onsite expectations. So we have schedule info.
Thus we can include all sections.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: immigration note? It's not boilerplate; it's a note about sponsorship; we should keep it? It's substantive? It's a note about immigration sponsorship; we can include as a short paragraph maybe under About the role or separate note. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Immigration note is not exactly those; it's a condition. Keep it.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the lists.
We need to format lists with
- . For prose use
. We must not emit heading followed by filler/placeholder text. All sections have real content. We need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:
About the role
Fidelity is looking for a Principal Full Stack Engineer to join the Fidelity Institutional Technology Development Team. The candidate will apply strong software development and test automation skills to design, develop, test, deploy, maintain, and improve FIT customer‑facing software solutions. They will also enable their Scrum team to adopt development and automation frameworks and standard methodologies to ensure the right product is built the right way. Note: Fidelity will not provide immigration sponsorship for this position.
Responsibilities
- Developing and deploying software in a fast‑paced environment
- Collaborating with colleagues on technical implementation and process improvement
- Working closely with Architecture, Development, User Experience, and Product Owner to design new features
- Keeping up to date with latest technologies and frameworks
- Mentoring junior team members to improve team velocity
- Taking initiative, being a decisive decision maker, showing confidence in decisions, and seeing tasks through to completion
- Working with new technologies to solve test challenges and drive process improvements
Requirements
- Bachelor's degree or equivalent experience in computer science, computer engineering, information systems (preferred)
- At least 8 years of development experience
- Expertise in building scalable web and middle‑tier applications using Java, JavaScript, Spring, Spring Boot, and Angular
- Solid understanding and hands‑on experience with API authentication, RBAC authorization, and SAML/OIDC
- Strong foundation of software design, data structures, and algorithms
- Strong experience with web services (JSON, XML, REST, SOAP, etc.)
- Experience building cloud‑enabled applications leveraging 12‑factor design
- Experience with Docker containerization and AWS cloud deployment/application management
- Experience with unit testing and test automation libraries/strategies
- Experience with CI/CD pipelines, Kubernetes, Terraform, and Jenkins
- Experience delivering software in an Agile environment
- Experience coaching and mentoring junior engineers and performing code reviews
- Strong verbal and written communication skills, with ability to understand and parse business logic into technical requirements, experienced in an Agile Scrum environment
Qualifications
- Experience with brokerage and financial services application development (a plus)
- Working knowledge of design systems (a plus)
- Knowledge of web security attack methods and measures to defend against them (a plus)
Skills
- Multi‑stack engineer with knowledge in a breadth of development technologies and test automation frameworks (Java/J2EE, Spring Boot, JUnit, Cucumber, Selenium, Serenity, Angular/JavaScript, TypeScript, Web Services, REST, HTTP)
- Passionate about business‑driven development, developing robust software, writing testable and maintainable code
- Strong leadership skills to guide, encourage, mentor, and motivate other software engineers within the squad and product area
- Strong communication and problem‑solving skills
- Desire to collaborate and work closely with others within the product area
- Experience working in an Agile environment
- Exposure to test automation
- Ability to step into the customer’s shoes and understand the value delivered each sprint
- Keen attention to detail, wanting to detect and solve hard problems
- Able to learn large software systems end‑to‑end quickly
- Keen interest in learning new technologies and their adoption
- Able to work with remote and international team members
- Obsessed with creating the best end‑to‑end customer experience
- Owns the outcome by taking personal accountability for delivering strong results
Benefits
- Comprehensive health care coverage
- Emotional well‑being support
- Market‑leading retirement plans
- Generous paid time off and parental leave
- Charitable giving employee match program
- Educational assistance including student loan repayment, tuition reimbursement, and learning resources for career development
Pay
The base salary range for this position is $107,000–216,000 USD per year. Placement in the range varies based on job responsibilities and scope, geographic location, candidate’s relevant experience, and other factors. Base salary is only part of the total compensation package; depending on the position and eligibility, the offer may also include bonus or other variable compensation.
Schedule
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. Onsite expectations are likely to evolve as the rollout continues. This transition does not apply to fully remote roles.
Check we didn't miss any substantive info: The note about immigration sponsorship included in About the role paragraph. Also we included "Note: Fidelity will not provide immigration sponsorship for this position." Good. We didn't include the "Company Overview" paragraph; but that is substantive. Should we include it? The allowed headings don't include "Company Overview". Could we incorporate it into About the role? It's about Fidelity's mission, values, etc. Could be considered part of About the role or maybe we could add a separate section like "About Fidelity" but not allowed. The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should stick to those? It says "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should only use those headings. So we should not add a heading like "Company Overview". We could incorporate that content into About the role paragraph as extra description. Let's add a sentence about Fidelity's mission. Add to About the role: "At Fidelity, we are focused on making our financial expertise broadly accessible and effective in helping people live the lives they want. We are a privately held company that values creating and nurturing a work environment that attracts the best talent and reflects our commitment to our associates. We are proud of our diverse and inclusive workplace where we respect and value our associates for their unique perspectives and experiences." That's from Company Overview. Good. Also we have "Fidelity Investments is an equal opportunity employer." That's EEO boilerplate; we should remove it. Also the paragraph about laws and regulations etc. That's legal boilerplate; remove. Also "Certifications Category: Information Technology" maybe minor metadata; we can drop or fold into short p. It's minor; we could drop as per instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can drop that line. Also "Note, the application window closes when the position is filled or unposted." That's application instruction; remove. Also "Please be advised that Fidelity’s business is governed by the provisions