Director of Software Engineering
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We need to extract content.
From posting:
- About Us: description of company. Could be "About the role"? Actually "About Us" is company description. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" maybe includes description of role? The posting includes "Job Description" with details about role. So we can put that under "About the role". Also there is "About Us" separate but maybe not needed as heading; we could incorporate into About the role? But they said do NOT repeat the job title as a heading. They didn't forbid About Us heading; but they gave examples. We could include "About the role" containing the job description narrative. The "About Us" could be omitted or placed in a paragraph without heading? Probably better to include a short paragraph about company under "About the role" or separate "About Us" not in list; but they said use those headings only. We could still include a
about company without heading? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they want those for sections. Safer to follow: include sections only when posting has real specific content. So we need sections: About the role (job description), Responsibilities, Requirements (maybe Qualifications), Qualifications (maybe separate?), Skills, Benefits, Pay, Schedule.
We have content:
- Responsibilities: detailed bullet points under "Responsibilities" heading in posting. We'll capture those.
- Qualifications: there is a "Qualifications Required" and "Preferred". Also there is "Technical fluency..." etc. Could treat as Requirements and Qualifications? The instruction distinguishes Requirements and Qualifications. We could put required qualifications under "Requirements" and preferred under "Qualifications"? Or combine. Let's interpret: Requirements = mandatory; Qualifications = maybe preferred or additional. We'll split.
- Skills: not explicitly listed but could infer from qualifications: technical fluency, etc. Might be thin. Better to not create Skills section unless we have explicit skills list. Not present. So omit Skills.
- Benefits: not mentioned. No benefits details. So omit Benefits.
- Pay: salary range given: "The salary range in United States of America for this position is 184,000.00 to 231,000.00 USD Annual." Also note about commission etc. So we can include Pay section with that info.
- Schedule: not mentioned. Omit.
- About the role: we can include the job description narrative (the paragraphs under "Job Description" before Responsibilities). Also maybe include "About Us" company description? Could be part of About the role? Might be okay to include a short paragraph about company under About the role. But we must not invent content. We have About Us paragraph; we can include it as part of About the role (makes sense). Ensure we preserve all substantive information.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. At end there is EEO statement etc. Remove that.
Also remove "Additional Information" about confidentiality, background checks, etc. That's boilerplate? It's somewhat generic but maybe not boilerplate; but it's about confidentiality and background checks. Might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The confidentiality statement is legal; could be removed. Background checks maybe also legal. Safer to remove that.
Also remove "Learn more at insightsoftware.com." maybe not boilerplate but it's a link; could keep? It's part of About Us. Might keep as part of description.
We need to output only HTML fragment.
Structure:
About the role
... (combined About Us and Job Description narrative)
Responsibilities
- ... each bullet
Requirements
- ... mandatory qualifications
Qualifications
- ... preferred qualifications
Pay
... salary range
We must not include empty sections. Now extract content. About Us paragraph: "insightsoftware is a global provider of reporting, analytics, and performance management solutions that unlock the potential of business data and transform the way finance and data teams operate. We empower leaders from over 32,000 organizations to make timely and intelligent decisions. Our comprehensive solutions span Financial Planning and Analysis (FP&A), Controllership, and Data and Analytics. We deliver finance teams the insights required to navigate any economic climate and drive greater financial intelligence, while increasing productivity, visibility, accuracy, and compliance. Learn more at insightsoftware.com." Job Description narrative (before Responsibilities): "The Equity Management team is looking for a seasoned Director of Software Engineering to take on one of the most consequential roles in the organization — leading the Platform & Architecture vertical. Reporting to the Senior Director of Engineering, you will be responsible for greenfield development as well as the core existing application with a mature enterprise customer base and multiple Fortune 100 broker relationships. You will own the success of a true 0-to-1 platform modernization — a ground-up greenfield project to build an equity platform as an Azure cloud-native application. You will join the initiative in its early phase and drive the teams through MVP and GA on an aggressive timeline. insightsoftware is an AI-first organization, and this initiative is utilizing pure AI Spec-Driven Development (SDD) with GitHub SpecKit and Claude Code in the Azure stack (Azure SQL, Data Lake, Fabric, AKS, Entra, .NET, Angular). This is the single-most strategically important initiative in the organization. You'll partner directly with Solution Architecture, Engineering, Product Management, and UX in achieving cross-functional success. Technical direction for the modernization sits with the Solution Architect, functional direction sits with the Product team, execution sits with the Engineering Manager — your role owns the program delivery and holds every contributing team accountable. You will also own the existing application ecosystem running the business today — the core CEM platform and all broker integrations that 1,200+ customers depend on every day, top to bottom, from front-end to database. You'll own the stability, health, and delivery of the legacy application, and migration to the new platform when it is ready. You are the right person for this role if you thrive in leaning into ambiguity and forging the path ahead, are not afraid to fail fast, and recognize that sometimes it's better to proceed without all the facts rather than standing at the fork in the road waiting for the perfect circumstances. Extreme accountability, cross-team collaboration & leadership, client-facing, strong communication — these are a few of the traits that describe the ideal candidate. You'll lead these initiatives with somewhere between 4-6 teams, all with Managers and Senior Managers reporting directly to you." We can combine About Us and Job Description into oneor maybe two
s. Use
for prose. Could separate into two paragraphs. Now Responsibilities bullet list: need to extract each bullet from the "Responsibilities" section. The posting lists: Modernization Initiative - Ownership & Delivery Accountability - Own overall delivery accountability for the modernization initiative — defining the plan, sequencing execution, and driving it to completion. - Partner closely with the Solution Architect, who owns technical direction and architecture decisions for the initiative; this role owns translating that direction into a resourced, sequenced, accountable delivery plan. - Continue to push boundaries in Spec-Driven Development (SDD), encouraging Lean and fail-fast experimentation. - Grow the usage and adoption of modern AI development practices. - Own Engineering and QA/Automation directly for the modernization initiative, while driving Product and UI/UX as a matrixed, non-reporting partner toward the same outcome. - Establish and enforce delivery standards and definition-of-done discipline consistently across Engineering, Product, and UX/Design. - Proactively identify misalignment, blockers, and undecided cross-functional questions before they surface on their own - engineering, product, and design each report through different leaders, and this role is accountable for the seams between them. - Hold Engineering, Product, and UX/Design equally accountable for delivery commitments. - This is a cross-functional accountability role - success requires driving outcomes with partners outside your direct reporting line, not just within it. - Communicate program status with complete candor to the Sr Director, VP, and executive stakeholders — including surfacing bad news early rather than smoothing it over in status reporting. Broker & Core CEM Portfolio Delivery - Own end-to-end delivery accountability for insightsoftware's broker integration programs. - Own delivery accountability for the core Certent Equity Management (CEM) platform serving 1,200+ global customers, ensuring committed roadmap items and client-critical fixes are delivered on schedule. - Balance capacity and prioritization across the initiative, broker programs, and core CEM delivery; escalate tradeoffs to the Sr Director directly and early when competing demands threaten committed dates. - Serve as the single point of delivery accountability across this full portfolio — executive leadership should get one clear, consistent narrative regardless of which program they're asking about. Team Leadership & People Management - Own people leadership across 4-6 teams, each led by a Manager or Senior Manager, spanning platform modernization, Broker Applications & Broker Integrations, Core CEM Application, and Platform Services. - Coach and develop the managers and senior managers reporting to you — including calibrating what kind of leadership a given team or program actually needs, and adjusting staffing decisions as needed. - Own hiring, onboarding, performance management, and retention across your organization; partner with the Sr Director on headcount and org design for the vertical. - Shield your teams' capacity from competing delivery pulls; escalate conflicts when external threats threaten committed delivery. - Build a high-trust, high-accountability culture — explicitly encouraging fast, reversible decisions over prolonged research cycles, and rewarding people who proactively surface risk. We need to capture each bullet as