Director, Software Engineering & Development

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications), Skills maybe, Benefits, Pay, Schedule. Must include only sections with real content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invention. Must remove boilerplate like cookie/navigation/legal/EEO etc. Also remove application instructions. The posting includes many paragraphs. We need to extract sections. We need headings:

for each section. We need to decide which sections to include. Content: - Position Summary: description of role, responsibilities, etc. Could be "About the role" or "Responsibilities". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings. We have: Position Summary: description of role, responsibilities, team, etc. Could be "About the role". Then "Responsibilities" list bullet points: Growing and developing engineering talent, Creating a high-performance team culture, Supporting delivery of enterprise AI platform capabilities, Improving engineering practices..., Partnering..., Helping the team move quickly..., Occasionally contributing hands-on... Then "What We’re Looking For": list of desired traits. Could be "Requirements" or "Qualifications". Then "Required Qualifications": bullet list of qualifications. Then "Preferred Qualifications": bullet list. Then "What Success Looks Like": bullet list of success criteria. Could be "Skills" maybe? Or could be part of responsibilities. Also "The national average salary range for this role is $170-220k in base pay..." => Pay section. "Other rewards and benefits may include: 401(k) match, Medical, Dental, Vision, Paid-Time-Off, etc." => Benefits section. Schedule: not mentioned. So we should not include Schedule. We must not include sections with filler like "commensurate with experience". Not present. We must not repeat job title. We must not include application instructions (like "For more information, please visit careers.ascensus.com/#Benefits." maybe that's benefits link but it's okay? It's more like a link for benefits info. Might be considered application instruction? It's not exactly applying. But it's a reference to benefits. Could keep as part of Benefits. Also "Be aware of employment fraud..." is boilerplate scam warning, should remove. We need to preserve all substantive info. So we need to include all bullet points from Responsibilities, Required Qualifications, Preferred Qualifications, What Success Looks Like, etc. We need to format as

• for any list of duties/requirements/benefits. For prose, use

  . We need to decide which content is prose vs list. Position Summary: could be prose paragraph(s). We'll put in

  . Responsibilities: list bullet points. What We’re Looking For: could be list of traits; we can treat as Requirements or Qualifications. But we already have Required Qualifications and Preferred Qualifications sections. The "What We’re Looking For" is more like desired attributes; could be part of Requirements or Skills. We could make a section "Skills" for those traits. But we already have Required and Preferred Qualifications; maybe we combine them into Requirements (Required) and Preferred Qualifications separate. The instruction says we can use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have: - About the role (Position Summary) - Responsibilities - Required Qualifications - Preferred Qualifications - Skills (maybe from What We’re Looking For and What Success Looks Like? But Success Looks Like is more about outcomes; could be part of Responsibilities? Might be separate section "What Success Looks Like" but not in allowed headings. Could treat as Skills or Responsibilities. Probably better to include as "Skills" (since they are abilities needed for success). However the instruction says prefer a few substantive sections over many thin ones. So we could combine Required and Preferred Qualifications into one "Qualifications" section, with sub-bullets? But we need to preserve all info; we can still have two sub-sections but headings only allowed as listed; we could have

  Qualifications

  and then within that we could have

  Required:

  ... and

  Preferred:

  ... That's okay. Similarly, we could have

  Skills

  for What We’re Looking For and What Success Looks Like combined. But we need to avoid too many thin sections. Let's think: we could have: - About the role (Position Summary) - Responsibilities - Qualifications (with Required and Preferred) - Skills (What We’re Looking For + What Success Looks Like) - Benefits - Pay That's 6 sections. Check if any content missing: The "Position Summary" includes details about team composition, hands-on leadership, etc. That's covered. Responsibilities list: we have bullet points from "You will be responsible for:" and also the earlier sentence about "While this is a management role, the person ... may contribute directly..." but that is part of responsibilities; we can include in responsibilities list. What We’re Looking For: list of traits. What Success Looks Like: list of outcomes. We need to ensure we don't invent. Now we need to strip boilerplate: The lines about "Be aware of employment fraud..." remove. Also "For more information, please visit careers.ascensus.com/#Benefits." maybe keep as part of Benefits? It's a link for more info; could be considered application instruction? It's not exactly applying but it's a reference. Might be okay to keep as part of Benefits. Also "The national average salary range for this role is $170-220k in base pay, exclusive of any bonuses and benefits." That's Pay. Now we need to format. Let's extract exact text. Position Summary: "Ascensus is the leading independent technology and service platform powering savings plans across America, providing products and expertise that help nearly 16 million people save for a better today and tomorrow. Position Summary As a Software Engineering Manager, Enterprise AI Platform, you will lead a team responsible for building, operating, and continuously improving production-grade AI-enabled software. This role manages a cross-functional engineering team that may include: Software EngineersSDETsDevOps EngineersSupport Engineers This is a hands-on engineering leadership role for someone who has strong software engineering experience, cares deeply about people development, and can help teams deliver practical AI-powered solutions with speed, quality, and discipline. While this is a management role, the person in this position is expected to stay close to the codebase and technical workflow. When the situation calls for it, they may contribute directly to implementation, debugging, automation, technical spikes, or code reviews to help the team move faster, remove blockers, or solve critical problems." We need to avoid repeating job title; we already have "Position Summary". We'll keep the content after "Position Summary". Might start with "As a Software Engineering Manager..." but that's okay. We'll produce a paragraph. Responsibilities bullet points: From "You will be responsible for:" list: - Growing and developing engineering talent - Creating a high-performance team culture - Supporting delivery of enterprise AI platform capabilities - Improving engineering practices across software development, testing, DevOps, support, and operations - Partnering with product, architecture, AI, business, and technology leaders - Helping the team move quickly while maintaining quality, security, reliability, and maintainability - Occasionally contributing hands-on to implementation, debugging, automation, technical spikes, or code reviews when the situation calls for it Also earlier sentence: "While this is a management role, the person in this position is expected to stay close to the codebase and technical workflow. When the situation calls for it, they may contribute directly to implementation, debugging, automation, technical spikes, or code reviews to help the team move faster, remove blockers, or solve critical problems." This is similar to the last bullet; we can incorporate but not duplicate. We'll keep as part of responsibilities maybe as a bullet: "Stay technically engaged with the codebase and contribute hands-on to implementation, debugging, automation, technical spikes, or code reviews when needed." But we already have that. To avoid duplication, we can keep the bullet list as given; the earlier sentence is somewhat covered. We'll keep the bullet list as is. What We’re Looking For bullet points (the ideal candidate is someone who: list): - Has a strong software engineering background - Understands how modern software teams build, test, deploy, and operate production systems - Can coach software engineers, SDETs, DevOps engineers, and support engineers - Stays technically engaged with the team’s codebase, architecture, development workflow, and operational tooling - Knows when to guide, when to delegate, and when to contribute hands-on to help the team move forward - Knows how to create clarity in ambiguous environments - Can translate business and platform goals into team execution - Has strong instincts around quality, automation, observability, reliability, and supportability - Is comfortable working in a fast-moving AI environment - Can partner well with product owners, architects, data scientists, business stakeholders, and senior leaders - Wants to grow into broader engineering leadership responsibility over time Required Qualifications bullet points: - 5+ years of professional software engineering or related technical experience. - 2+ years of technical leadership, team leadership, people leadership, or engineering management experience. - Experience leading, coaching, or mentoring software engineers or related technical team members. - Ability and willingness to stay technically engaged with the team’s codebase, architecture, development workflow, and operational tooling, including occasional hands-on contribution when needed. - Strong understanding of modern software engineering practices, including: Clean code, Source control, Unit testing, CI/CD, Design patterns, Refactoring, Maintainability, Production support - Experience working with software delivery teams that include roles such as: Software Engineers, SDETs, DevOps Engineers, Support Engineers, Quality Engineers - Experience supporting production software systems, including troubleshooting, incident response, root-cause analysis, or operational improvement. - Strong understanding of Agile delivery practices and modern engineering team workflows. - Ability to develop associates through coaching, feedback, goal setting, performance conversations, and career development planning. - Ability to create a high-performance team environment built on ownership, accountability, trust, and continuous improvement. - Strong communication skills with technical and non-technical audiences. - Strong problem-solving, prioritization, and decision-making skills. - Ability to partner with product, architecture, operations, support, and business teams to drive successful outcomes. - Experience participating in hiring, interviewing, candidate evaluation, or team growth activities. - Bachelor’s degree in Computer Science, Computer Information Systems, Business Information Systems, a related technical field, or equivalent practical experience. Preferred Qualifications bullet points: - Experience with one or more of the following is helpful, but not required: Managing or leading teams that build enterprise platforms, internal developer platforms, AI platforms, or shared services - Experience with AI-enabled applications, LLM-powered systems, RAG, chatbots, agent workflows, or AI-assisted engineering practices - Familiarity with Azure, Azure AI Foundry, Azure DevOps, or related Microsoft cloud and engineering tools - Experience with engineering teams using AI-powered development tools such as Cursor, Claude Code, or similar platforms - Experience leading teams that use automated testing, SDET practices, Playwright, Python-based test automation, or end-to-end testing - Experience with DevOps practices, CI/CD pipelines, release automation, infrastructure automation, or cloud operations - Experience with observability tools such as New Relic, Langfuse, OpenTelemetry, Azure Log Analytics, or similar platforms - Experience managing geographically distributed teams - Experience improving production support models, incident management, operational readiness, or service reliability - Experience working with enterprise systems such as Salesforce, internal platforms, APIs, workflow systems, or service-oriented architectures - Experience leading teams through ambiguity, rapid change, or emerging technology adoption - Experience building succession plans, development plans, hiring strategies, or team capability roadmaps - Interest in continuing to grow leadership responsibility What Success Looks Like bullet points