Director, Software Engineering
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not include sections with filler like "commensurate with experience". No Pay/Benefits/Schedule unless explicitly stated. The posting mentions "Fidelity’s Onsite Working Model" which describes onsite expectations; that could be considered Schedule? It's about working model, not explicit schedule like hours. Might be considered Schedule? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state onsite working model; that is about schedule/location. Could be considered Schedule. But we need to see if it's specific enough: "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." That's specific enough to include as Schedule section.
Benefits: Not mentioned explicitly. No benefits listed. So we should not include Benefits.
Pay: Not mentioned. So no Pay.
Qualifications: Could be "Required Expertise" and "Preferred Experience". Could combine into Requirements and Qualifications? The instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content.
We have: About the role: could be the initial paragraph describing role, plus "How Your Work Impacts The Organization", "The Team". Could combine into About the role.
Responsibilities: Primary Responsibilities (Engineering and Delivery, Standards and Craft, Team Building and Leadership). Could list as bullet points.
Requirements: Required Expertise (list). Could be Requirements.
Qualifications: Preferred Experience (list). Could be Qualifications.
Skills: maybe we could extract skills from Required Expertise (Java, Spring Boot, etc.) but we already have them in Requirements. Might not need separate Skills section if content thin. Better to avoid thin sections.
Schedule: Onsite Working Model.
We must not include boilerplate like EEO, legal, immigration note? The note "Fidelity will not provide immigration sponsorship for this position." is substantive? It's a restriction; we could include as a short p maybe under About the role or separate note. It's not boilerplate; it's specific. We'll include as a p.
Also "Fidelity will reasonably accommodate associates with disabilities..." is EEO/accommodation statement; that's boilerplate? It's about accommodation; could be considered EEO. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So remove that.
Also legal stuff about laws and regulations: remove.
Certifications Category: Information Technology - maybe a qualification? Could be included as a p under Qualifications? It's minor metadata; we could fold into a short p.
We need to preserve all substantive information; not invent or summarize away detail. So we need to keep the details from Required Expertise list, Preferred Experience list, responsibilities list, etc.
Let's extract content.
The Role paragraph:
"Enterprise Digital Operations, a product within Brokerage Recordkeeping Technology, is seeking a Director of Software Engineering who combines deep technical expertise with a strong engineering mindset and a passion for delivering business outcomes. This leader will provide hands-on technical guidance, elevate engineering practices, and coach teams in building scalable, resilient, and high-quality solutions. The ideal candidate will influence the adoption of modern engineering approaches, including AI-enabled development tools, while fostering a culture of continuous improvement, accountability, and effective delivery. As the organization grows, this leader will build and develop a high-performing engineering team capable of scaling enterprise platforms and driving operational excellence."
That's About the role.
How Your Work Impacts The Organization paragraph:
"Enterprise Digital Operations is embarking on a multi-year strategic initiative to bolster the digital experience for our clients and customers by leveraging consistent patterns and adhering to higher security standards to keep the client and technology secure and resilient."
That's also about role impact.
The Team paragraph:
"Fidelity's Brokerage Recordkeeping Technology team designs, develops, implements, and supports applications for our industry leading brokerage platforms. The team focuses on delivering innovative solutions which meet the needs of our customers. Our systems professionals thrive, with a steadfast dedication to innovation, which cultivates a culture of continuous improvement and significant achievement. We see ourselves as a vital link to Fidelity's customers. This is a fast-paced group delivering technology solutions to the complex needs of our clients using distributed and cloud-based technologies."
That's also about team.
We can combine these into About the role section with multiple paragraphs.
Primary Responsibilities: we have three sub-sections: Engineering and Delivery, Standards and Craft, Team Building and Leadership. Each contains multiple sentences. We can turn each bullet into
- items.
Let's list them:
Engineering and Delivery:
- Provide strong technical leadership guiding architectural decisions, ensuring alignment between business objectives and technical strategy, and enabling teams to deliver high-quality solutions.
- Drive engineering excellence through mentorship, technical coaching, and the establishment of scalable development practices that improve delivery effectiveness, quality, and operational resilience.
- Own engineering delivery for your domain end-to-end: from specification through production, including testing strategy, pipeline design, and operational readiness.
- Manage external technical partnerships where your domain is the integration point — own API contracts, integration test harnesses, and ongoing governance as partner platforms evolve.
Standards and Craft:
- Establish and enforce engineering standards across the platform: contract-first API development, OpenAPI specifications, code review standards, CI/CD pipeline design, and observability practices.
- Drive engineering excellence by guiding technical strategy, influencing solution design, and fostering the adoption of proven engineering patterns and practices.
- Lead the integration of AI-powered tools and streamlined delivery methodologies that accelerate innovation and improve delivery outcomes.
- Guide teams in making sound technical decisions by focusing on business impact, challenging conventional thinking, and driving solutions that improve efficiency, scalability, and customer experience.
Team Building and Leadership:
- Build and develop a high-performing engineering organization by attracting top talent, aligning team capabilities with strategic priorities, and fostering a culture of continuous learning, coaching, and technical excellence.
- Partner with the Engineering Leader, architect, and product stakeholders to shape technical direction and represent engineering credibly in senior forums.
- Assume accountability for resolving critical delivery and organizational challenges, collaborating across engineering, product, and business teams to accelerate execution and achieve desired outcomes.
Required Expertise list:
- Advanced proficiency in Java and Spring Boot for production backend service development.
- Strong working knowledge of event-driven and distributed systems: Kafka-based architectures, messaging patterns, microservices, and asynchronous design — sufficient to evaluate architectural decisions, lead technical discussions, and set direction for the team.
- Contract-first API development: deep understanding of OpenAPI/Swagger standards, RESTful API design, API lifecycle management, and consumer-driven contract practices.
- Cloud-native platform experience: AWS (preferred), container orchestration (Kubernetes), IAM, secrets management, and multi-account operational patterns.
- Engineering practice leadership: building and enforcing standards for testing, delivery pipelines, observability (distributed tracing, structured logging, metrics), and code quality.
- Experience delivering in regulated industries, financial services, or compliance-driven platforms where accuracy and reliability are non-negotiable.
Preferred Experience list:
- Experience leading a Cloud migration program: replacing or transforming a legacy platform while maintaining production operations.
- Familiarity with AI-assisted engineering practices — spec-driven development, code transformation, AI-accelerated delivery — and a track record of driving adoption across a team.
- Background in financial services, brokerage technology, or communications-heavy platforms.
How Your Work Impacts The Organization (we already used). The Team (used). Fidelity will reasonably accommodate... (remove). Fidelity’s Onsite Working Model (schedule). Certifications Category: Information Technology (maybe a note). Also note about immigration sponsorship.
We need to include a short p for immigration note and maybe certifications.
Let's decide sections:
About the role
Enterprise Digital Operations, a product within Brokerage Recordkeeping Technology, is seeking a Director of Software Engineering who combines deep technical expertise with a strong engineering mindset and a passion for delivering business outcomes. This leader will provide hands-on technical guidance, elevate engineering practices, and coach teams in building scalable, resilient, and high-quality solutions. The ideal candidate will influence the adoption of modern engineering approaches, including AI-enabled development tools, while fostering a culture of continuous improvement, accountability, and effective delivery. As the organization grows, this leader will build and develop a high-performing engineering team capable of scaling enterprise platforms and driving operational excellence.
Enterprise Digital Operations is embarking on a multi-year strategic initiative to bolster the digital experience for our clients and customers by leveraging consistent patterns and adhering to higher security standards to keep the client and technology secure and resilient.
Fidelity's Brokerage Recordkeeping Technology team designs, develops, implements, and supports applications for our industry leading brokerage platforms. The team focuses on delivering innovative solutions which meet the needs of our customers. Our systems professionals thrive, with a steadfast dedication to innovation, which cultivates a culture of continuous improvement and significant achievement. We see ourselves as a vital link to Fidelity's customers. This is a fast-paced group delivering technology solutions to the complex needs of our clients using distributed and cloud-based technologies.
Responsibilities
- Provide strong technical leadership guiding architectural decisions, ensuring alignment between business objectives and technical strategy, and enabling teams to deliver high-quality solutions.
- Drive engineering excellence through mentorship, technical coaching, and the establishment of scalable development practices that improve delivery effectiveness, quality, and operational resilience.
- Own engineering delivery for your domain end-to-end: from specification through production, including testing strategy, pipeline design, and operational readiness.
- Manage external technical partnerships where your domain is the integration point — own API contracts, integration test harnesses, and ongoing governance as partner platforms evolve.
- Establish and enforce engineering standards across the platform: contract-first API development, OpenAPI specifications, code review standards, CI/CD pipeline design, and observability practices.
- Drive engineering excellence by guiding technical strategy, influencing solution design, and fostering the adoption of proven engineering patterns and practices.
- Lead the integration of AI-powered tools and streamlined delivery methodologies that accelerate innovation and improve delivery outcomes.
- Guide teams in making sound technical decisions by focusing on business impact, challenging conventional thinking, and driving solutions that improve efficiency, scalability, and customer experience.
- Build and develop a high-performing engineering organization by attracting top talent, aligning team capabilities with strategic priorities, and fostering a culture of continuous learning, coaching, and technical excellence.
- Partner with the Engineering Leader, architect, and product stakeholders to shape technical direction and represent engineering credibly in senior forums.
- Assume accountability for resolving critical delivery and organizational challenges, collaborating across engineering, product, and business teams to accelerate execution and achieve desired outcomes.
Requirements
- Advanced proficiency in Java and Spring Boot for production backend service development.
- Strong working knowledge of event-driven and distributed systems: Kafka-based architectures, messaging
for prose. We must not include sections with filler like "commensurate with experience". No Pay/Benefits/Schedule unless explicitly stated. The posting mentions "Fidelity’s Onsite Working Model" which describes onsite expectations; that could be considered Schedule? It's about working model, not explicit schedule like hours. Might be considered Schedule? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state onsite working model; that is about schedule/location. Could be considered Schedule. But we need to see if it's specific enough: "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." That's specific enough to include as Schedule section. Benefits: Not mentioned explicitly. No benefits listed. So we should not include Benefits. Pay: Not mentioned. So no Pay. Qualifications: Could be "Required Expertise" and "Preferred Experience". Could combine into Requirements and Qualifications? The instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. We have: About the role: could be the initial paragraph describing role, plus "How Your Work Impacts The Organization", "The Team". Could combine into About the role. Responsibilities: Primary Responsibilities (Engineering and Delivery, Standards and Craft, Team Building and Leadership). Could list as bullet points. Requirements: Required Expertise (list). Could be Requirements. Qualifications: Preferred Experience (list). Could be Qualifications. Skills: maybe we could extract skills from Required Expertise (Java, Spring Boot, etc.) but we already have them in Requirements. Might not need separate Skills section if content thin. Better to avoid thin sections. Schedule: Onsite Working Model. We must not include boilerplate like EEO, legal, immigration note? The note "Fidelity will not provide immigration sponsorship for this position." is substantive? It's a restriction; we could include as a short p maybe under About the role or separate note. It's not boilerplate; it's specific. We'll include as a p. Also "Fidelity will reasonably accommodate associates with disabilities..." is EEO/accommodation statement; that's boilerplate? It's about accommodation; could be considered EEO. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So remove that. Also legal stuff about laws and regulations: remove. Certifications Category: Information Technology - maybe a qualification? Could be included as a p under Qualifications? It's minor metadata; we could fold into a short p. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep the details from Required Expertise list, Preferred Experience list, responsibilities list, etc. Let's extract content. The Role paragraph: "Enterprise Digital Operations, a product within Brokerage Recordkeeping Technology, is seeking a Director of Software Engineering who combines deep technical expertise with a strong engineering mindset and a passion for delivering business outcomes. This leader will provide hands-on technical guidance, elevate engineering practices, and coach teams in building scalable, resilient, and high-quality solutions. The ideal candidate will influence the adoption of modern engineering approaches, including AI-enabled development tools, while fostering a culture of continuous improvement, accountability, and effective delivery. As the organization grows, this leader will build and develop a high-performing engineering team capable of scaling enterprise platforms and driving operational excellence." That's About the role. How Your Work Impacts The Organization paragraph: "Enterprise Digital Operations is embarking on a multi-year strategic initiative to bolster the digital experience for our clients and customers by leveraging consistent patterns and adhering to higher security standards to keep the client and technology secure and resilient." That's also about role impact. The Team paragraph: "Fidelity's Brokerage Recordkeeping Technology team designs, develops, implements, and supports applications for our industry leading brokerage platforms. The team focuses on delivering innovative solutions which meet the needs of our customers. Our systems professionals thrive, with a steadfast dedication to innovation, which cultivates a culture of continuous improvement and significant achievement. We see ourselves as a vital link to Fidelity's customers. This is a fast-paced group delivering technology solutions to the complex needs of our clients using distributed and cloud-based technologies." That's also about team. We can combine these into About the role section with multiple paragraphs. Primary Responsibilities: we have three sub-sections: Engineering and Delivery, Standards and Craft, Team Building and Leadership. Each contains multiple sentences. We can turn each bullet into
About the role
Enterprise Digital Operations, a product within Brokerage Recordkeeping Technology, is seeking a Director of Software Engineering who combines deep technical expertise with a strong engineering mindset and a passion for delivering business outcomes. This leader will provide hands-on technical guidance, elevate engineering practices, and coach teams in building scalable, resilient, and high-quality solutions. The ideal candidate will influence the adoption of modern engineering approaches, including AI-enabled development tools, while fostering a culture of continuous improvement, accountability, and effective delivery. As the organization grows, this leader will build and develop a high-performing engineering team capable of scaling enterprise platforms and driving operational excellence.
Enterprise Digital Operations is embarking on a multi-year strategic initiative to bolster the digital experience for our clients and customers by leveraging consistent patterns and adhering to higher security standards to keep the client and technology secure and resilient.
Fidelity's Brokerage Recordkeeping Technology team designs, develops, implements, and supports applications for our industry leading brokerage platforms. The team focuses on delivering innovative solutions which meet the needs of our customers. Our systems professionals thrive, with a steadfast dedication to innovation, which cultivates a culture of continuous improvement and significant achievement. We see ourselves as a vital link to Fidelity's customers. This is a fast-paced group delivering technology solutions to the complex needs of our clients using distributed and cloud-based technologies.
Responsibilities
- Provide strong technical leadership guiding architectural decisions, ensuring alignment between business objectives and technical strategy, and enabling teams to deliver high-quality solutions.
- Drive engineering excellence through mentorship, technical coaching, and the establishment of scalable development practices that improve delivery effectiveness, quality, and operational resilience.
- Own engineering delivery for your domain end-to-end: from specification through production, including testing strategy, pipeline design, and operational readiness.
- Manage external technical partnerships where your domain is the integration point — own API contracts, integration test harnesses, and ongoing governance as partner platforms evolve.
- Establish and enforce engineering standards across the platform: contract-first API development, OpenAPI specifications, code review standards, CI/CD pipeline design, and observability practices.
- Drive engineering excellence by guiding technical strategy, influencing solution design, and fostering the adoption of proven engineering patterns and practices.
- Lead the integration of AI-powered tools and streamlined delivery methodologies that accelerate innovation and improve delivery outcomes.
- Guide teams in making sound technical decisions by focusing on business impact, challenging conventional thinking, and driving solutions that improve efficiency, scalability, and customer experience.
- Build and develop a high-performing engineering organization by attracting top talent, aligning team capabilities with strategic priorities, and fostering a culture of continuous learning, coaching, and technical excellence.
- Partner with the Engineering Leader, architect, and product stakeholders to shape technical direction and represent engineering credibly in senior forums.
- Assume accountability for resolving critical delivery and organizational challenges, collaborating across engineering, product, and business teams to accelerate execution and achieve desired outcomes.
Requirements
- Advanced proficiency in Java and Spring Boot for production backend service development.
- Strong working knowledge of event-driven and distributed systems: Kafka-based architectures, messaging