Senior Software Engineer

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Who We Are & What We Offer", "Our Mission", "Our Values", "Our Culture & Benefits" maybe some parts are benefits. But we need to extract Benefits, Pay, Schedule if present. The posting includes Compensation section with base salary range and variable incentive compensation and competitive benefits. Also mentions Hybrid Work Schedule. Also mentions Flex Time or Paid Time Off and Sick Time Off, 401K – 6% Employer Match, Medical, Dental, Vision – HDHP or PPO, HSA – Employer contribution (HDHP only), Volunteer Time Off, Career Development / Recognition, Fitness Reimbursement, Hybrid Work Schedule. So we have Benefits and Pay and Schedule. We also have sections: About the role (maybe the introductory paragraphs). Responsibilities (Key Responsibilities). Required Skills & Qualifications (maybe split into Requirements and Qualifications? The instruction says use headings for Requirements, Qualifications, Skills. We need to decide how to split. The posting has "Required Skills & Qualifications" and "Preferred Qualifications". Also "Why Join AssetMark?" maybe not needed. We'll create sections: About the role (intro). Responsibilities (Key Responsibilities). Requirements (maybe the required skills/qualifications). Qualifications (maybe preferred qualifications). Skills (maybe we could combine but we need to follow instruction: use headings for Skills if there is content. Could put required skills under Requirements, preferred under Qualifications, and maybe Skills separate? But we have limited content. Could treat "Required Skills & Qualifications" as Requirements, and "Preferred Qualifications" as Qualifications. Skills maybe not separate; we could omit Skills heading if no specific content beyond those. But instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one section? But headings are prescribed; we should only include heading if there is real specific content. We could include Requirements (required skills), Qualifications (preferred qualifications), and maybe Skills (we could list key skills extracted). However we risk creating thin sections. Better to include Requirements (required skills) and Qualifications (preferred qualifications) and maybe Skills omitted. But we need to follow instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory to use all. So we can choose which to include. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We need to ensure we preserve all substantive information. Let's extract. About the role: The first paragraphs: "AssetMark is a leading wealth management platform dedicated to empowering independent financial advisors. AssetMark's mission is to enable financial advisors to make a profound difference in the lives of their clients. Over 10,000 advisors partner with AssetMark for our investment offerings, innovative technology, advanced services, and expertise, which they use to delight their clients and grow their businesses. The Opportunity We are seeking a Senior Software Engineer to help shape the future of software delivery and engineering productivity at AssetMark. In this role, you will design, build, and evolve the platforms, tooling, and workflows that enable our engineering teams to deliver software quickly, safely, and reliably. You will lead initiatives focused on developer productivity, deployment automation, self-service platforms, and continuous delivery. Working across engineering teams, you will identify friction points throughout the software development lifecycle and create scalable solutions that improve the developer experience while increasing engineering velocity, reliability, and quality. This is a hands-on senior engineering role that combines software engineering, platform engineering, cloud-native technologies, and organizational influence. You will play a key role in establishing modern engineering practices and building the foundations that enable teams to ship software with confidence. We can only consider candidates for this position who are able to accommodate a hybrid work schedule and are close to our Charlotte, NC office." That's about the role. Responsibilities: The bullet list under Key Responsibilities. We need to preserve all substantive info. We'll convert each bullet into

. The bullet points are sentences; we need to keep them. List: - Developer Experience & Engineering Productivity Champion developer experience as a first-class engineering concern by identifying and eliminating friction throughout the software development lifecycle. - Design and implement self-service developer platforms that enable engineers to provision infrastructure, deploy applications, manage environments, and access platform services independently. - Build paved-road solutions that provide secure, scalable, and opinionated paths for software delivery. - Partner with engineering teams to understand productivity challenges and develop solutions that improve developer workflows. - Improve onboarding experiences, development environments, documentation, templates, and automation that accelerate time-to-productivity for engineers. - Establish and track engineering effectiveness metrics, including DORA, SPACE, and other developer productivity measurements. - CI/CD & Deployment Automation Design, build, and optimize CI/CD platforms using GitHub Actions, Azure DevOps, and related technologies. - Drive adoption of true Continuous Integration and Continuous Deployment practices, enabling teams to deploy changes safely and frequently through automated pipelines. - Build deployment automation, release orchestration, environment management, and rollback capabilities. - Improve build reliability, deployment speed, and developer feedback loops through automation and platform enhancements. - Establish standards and best practices for testing, deployment validation, release management, and software delivery governance. - Platform Engineering & Cloud Infrastructure Design and maintain cloud-native platform capabilities running on Azure and Kubernetes. - Develop reusable infrastructure patterns and self-service capabilities using Terraform and Infrastructure as Code principles. - Create shared platform services that simplify application development and operations. - Collaborate with SRE, Security, and Platform Engineering teams to ensure scalability, reliability, and compliance requirements are met. - Drive platform modernization initiatives that improve operational efficiency and reduce engineering toil. - Technical Leadership & Engineering Excellence Lead complex technical initiatives spanning multiple engineering teams. - Influence technical direction and platform strategy through architecture, standards, and best practices. - Mentor engineers on platform engineering, cloud-native development, CI/CD, and DevEx principles. - Balance platform innovation, technical debt reduction, and operational stability. - Foster a culture of automation, continuous improvement, and engineering excellence. We need to ensure each bullet is a separate

. Some lines have two sentences combined; we keep as is. Requirements: Required Skills & Qualifications bullet list. List: - Bachelor's degree in Computer Science, Software Engineering, or a related technical field, or equivalent practical experience. - 5–8 years of experience in Software Engineering, Platform Engineering, Developer Experience, Site Reliability Engineering, or related roles. - Demonstrated experience building and operating CI/CD platforms at scale. - Experience implementing Continuous Integration and Continuous Deployment practices in production environments. - Proven track record of improving developer productivity through platform engineering and automation. - Hands-on experience with Kubernetes, cloud infrastructure, and Infrastructure as Code. - Experience with GitHub Actions, Azure DevOps, or comparable CI/CD technologies. - Experience building internal tooling, developer platforms, or engineering productivity solutions. - Experience working in highly regulated environments is preferred, particularly financial services or fintech Note: last bullet says "is preferred". It's still part of required? We'll keep. Qualifications: Preferred Qualifications bullet list. List: - Experience building Internal Developer Platforms using Backstage or similar developer portals. - Experience with GitOps practices and technologies such as ArgoCD. - Experience with progressive delivery, feature flagging, canary deployments, or blue-green deployment strategies. - Experience implementing engineering effectiveness programs using DORA, SPACE, or similar frameworks. - Familiarity with OpenTelemetry, distributed tracing, and modern observability platforms. - Azure, Kubernetes, Cloud, or DevOps certifications. - Experience leveraging AI-powered development tools to improve developer productivity and software delivery. Benefits: from "Why Join AssetMark?" and "Our Culture & Benefits". We need to capture benefits: Flex Time or Paid Time Off and Sick Time Off, 401K – 6% Employer Match, Medical, Dental, Vision – HDHP or PPO, HSA – Employer contribution (HDHP only), Volunteer Time Off, Career Development / Recognition, Fitness Reimbursement, Hybrid Work Schedule. Also maybe "Help define and scale the developer experience..." etc are not benefits but why join. We'll focus on benefits list. Pay: Compensation section: Base Salary range $165,000-$190,000, plus variable incentive compensation and competitive benefits. We'll include that. Schedule: Hybrid Work Schedule mentioned. Also maybe "We can only consider candidates for this position who are able to accommodate a hybrid work schedule and are close to our Charlotte, NC office." So schedule is hybrid. We need to output HTML fragment only, no markdown fences. We'll structure:

About the role

... paragraphs ...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Benefits

• Flex Time or Paid Time Off and Sick Time Off
• 401K – 6% Employer Match
• Medical, Dental, Vision – HDHP or PPO
• HSA – Employer contribution (HDHP only)
• Volunteer Time Off
• Career Development / Recognition
• Fitness Reimbursement
• Hybrid Work Schedule

Pay

The base salary range for this position is between $165,000-$190,000. This position is also eligible for additional variable incentive compensation and competitive benefits.

Schedule

Hybrid work schedule (candidates must be able to accommodate a hybrid schedule and be near the Charlotte, NC office).

We need to ensure we didn't repeat job title. No mention of AssetMark as heading. Good. Check for any boilerplate: We removed "Who We Are & What We Offer", "Our Mission", "Our Values", "Our Culture & Benefits" (except we extracted benefits). Also removed EEO statement at end. Also removed "Candidates must be legally authorized to work in the US to be considered. We are unable to provide visa sponsorship for this position." That's substantive? It's a requirement about work authorization. Should we preserve? It's substantive info about eligibility. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should include that somewhere. Where? Could be under Requirements or a separate section like Eligibility. But we have no heading for Eligibility. Could add a

under Requirements or after Requirements. Since we must not invent headings, we can add a paragraph under Requirements after the list, or under About the role. Probably best to add a short paragraph under Requirements: "Candidates must be legally authorized to work in the US; visa sponsorship is not provided." That preserves info. Also we need to include location proximity: "close to our Charlotte, NC office." Already in About the role and Schedule. Also note: "We can only consider candidates for this position who are able to accommodate a hybrid work schedule and are close to our Charlotte, NC office." Already captured. Now check for any duplicated lines: We have hybrid schedule mentioned twice; that's fine. Now ensure we didn't include any boilerplate like "As an Equal Opportunity Employer, AssetMark is committed to building a diverse and inclusive workplace where everyone feels valued." That's EEO; we should remove. Now output HTML. Let's craft the About the role paragraph(s). Could be two paragraphs: first about company mission, second about