Director of Software Engineering (Federal Health)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
Content:
Description paragraph: "At Commence, we’re the start of a new age of data-centric transformation, elevating health outcomes and powering better, more efficient process to program and patient health. We combine quality data-driven solutions that fuel answers, technology that advances performance, and clinical expertise that builds trust to create a more efficient path to quality care. With human-centered, healthcare-relevant, and value-based solutions, we create new possibilities with data. We provide proof beyond the concept and performance beyond the scope with a focus on efficiencies that transform the lives of those we serve. With a culture driven by purpose, straightforward communication and clinical domain expertise, Commence cuts straight to better care."
Then "Requirements" heading (actually the posting says "Requirements" but then includes a description of role responsibilities). Actually after description, there is "Requirements Commence is seeking a Director of Software Engineering to lead the teams building our go-forward technology platforms across federal health IT and commercial healthcare markets. This role owns engineering execution, technical quality, and team health. The Director of Software Engineering is accountable for how engineering work gets planned, sequenced, and delivered, and for building an organization that can scale as the customer base grows. This is a hands-on leadership role. The Director is expected to stay close enough to the technology to make sound architectural tradeoffs, review designs, and hold a high bar on engineering quality, while leading people and improving how the organization operates. Lead and develop a multi-team engineering organization across platform development, program build, production support, and applied AI, including hiring, coaching, performance management, and career development for team leads and individual contributors.Own engineering execution and delivery outcomes for the platform portfolio, including velocity, quality, technical debt posture, and the balance between roadmap work and program commitments.Refine and enforce engineering standards and practice across teams: SDLC, code review, testing strategy, release management, secure development, and documentation.Operate a capacity and allocation model across multiple work modes, protecting platform roadmap capacity while meeting program and production support demand.Partner with Technical Delivery leadership on resource allocation for program work, and with Technical Product on roadmap intake, sequencing, and prioritization.Partner with the Lead Software Architect and Chief Architect on platform design direction, standards governance, and technical feasibility of commitments made during pursuits.Drive continuous improvement in engineering throughput and predictability, using delivery metrics to identify constraints.Champion configuration over customization in platform design, ensuring customer specific needs are met through configuration wherever possible and that genuine platform gaps are surfaced into the roadmap.Partner with DevSecOps, Infrastructure, and Security to ensure engineering practice meets ATO, FISMA, and applicable compliance obligations without becoming a delivery bottleneck.Contribute engineering input to capture and pursuit activity as needed, in coordination with the Chief Architect."
Then "Qualifications" heading: list of qualifications bullet points? Actually it's a paragraph with sentences separated by periods. We need to turn into list items? The rule: Use
- for any list of duties/requirements/benefits. The qualifications are a list of items; we can treat each sentence as a list item. Similarly responsibilities could be list items.
Then "Preferred Qualifications" heading: list of items.
Then "Work Environment/Physical Demands" heading: paragraph.
Then EEO boilerplate etc to remove.
Also there is a line: "Commence is an equal employment opportunity employer..." etc. Remove.
Also there is contact info for accommodation: "If you require a reasonable accommodation to participate in the application process due to a disability, please contact Human Resources at (757) 306-4920 or hr@commence.ai. Please note that unless you are requesting an accommodation, all applications must be submitted through our online application system." This is application instructions; remove.
Thus we need sections: About the role (maybe from description), Responsibilities (the block after "Requirements" heading? Actually that block is responsibilities), Qualifications (the bullet list after "Qualifications"), Preferred Qualifications (maybe as a subsection under Qualifications? But we could make separate section "Preferred Qualifications". The rules allow any of the headings list; we can include Preferred Qualifications as a heading if content exists. It does.
Work Environment/Physical Demands: we can include as a section maybe "Work Environment". The heading list includes "Benefits, Pay, Schedule". Not work environment. But we can still create a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we can use other headings if appropriate, but better to stick to those. However "Work Environment/Physical Demands" is not in the list but could be considered as "Responsibilities"? No. Might be better to include as a section with heading "Work Environment". The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to include only those headings that have content. We have About the role, Responsibilities, Requirements, Qualifications, maybe Skills? Not present. Benefits, Pay, Schedule not present. So we will not create those.
We could incorporate Work Environment/Physical Demands into Responsibilities or Qualifications? Probably better to make a separate section "Work Environment". Since it's substantive. The instruction didn't forbid; it just gave examples. So we can.
Thus sections:
About the role
... description paragraph ...
Responsibilities
- ... each responsibility sentence ...
Qualifications
- ... each qualification sentence ...
Preferred Qualifications
- ... each preferred qualification sentence ...
Work Environment
... work environment paragraph ...
We need to ensure we preserve all substantive information. Let's extract sentences.
Description paragraph: It's one paragraph with multiple sentences. We'll keep as .
Now responsibilities block: Let's split by periods that end sentences. Need to be careful not to split abbreviations like "SDLC," etc. But we can approximate.
Responsibilities text:
"Lead and develop a multi-team engineering organization across platform development, program build, production support, and applied AI, including hiring, coaching, performance management, and career development for team leads and individual contributors.Own engineering execution and delivery outcomes for the platform portfolio, including velocity, quality, technical debt posture, and the balance between roadmap work and program commitments.Refine and enforce engineering standards and practice across teams: SDLC, code review, testing strategy, release management, secure development, and documentation.Operate a capacity and allocation model across multiple work modes, protecting platform roadmap capacity while meeting program and production support demand.Partner with Technical Delivery leadership on resource allocation for program work, and with Technical Product on roadmap intake, sequencing, and prioritization.Partner with the Lead Software Architect and Chief Architect on platform design direction, standards governance, and technical feasibility of commitments made during pursuits.Drive continuous improvement in engineering throughput and predictability, using delivery metrics to identify constraints.Champion configuration over customization in platform design, ensuring customer specific needs are met through configuration wherever possible and that genuine platform gaps are surfaced into the roadmap.Partner with DevSecOps, Infrastructure, and Security to ensure engineering practice meets ATO, FISMA, and applicable compliance obligations without becoming a delivery bottleneck.Contribute engineering input to capture and pursuit activity as needed, in coordination with the Chief Architect."
Note there are missing spaces after periods in some places (e.g., "...contributors.Own"). We'll need to add spaces for readability but must preserve info. We can keep as is but better to add a space after period when splitting. We'll produce list items each sentence.
Let's split:
1. Lead and develop a multi-team engineering organization across platform development, program build, production support, and applied AI, including hiring, coaching, performance management, and career development for team leads and individual contributors.
2. Own engineering execution and delivery outcomes for the platform portfolio, including velocity, quality, technical debt posture, and the balance between roadmap work and program commitments.
3. Refine and enforce engineering standards and practice across teams: SDLC, code review, testing strategy, release management, secure development, and documentation.
4. Operate a capacity and allocation model across multiple work modes, protecting platform roadmap capacity while meeting program and production support demand.
5. Partner with Technical Delivery leadership on resource allocation for program work, and with Technical Product on roadmap intake, sequencing, and prioritization.
6. Partner with the Lead Software Architect and Chief Architect on platform design direction, standards governance, and technical feasibility of commitments made during pursuits.
7. Drive continuous improvement in engineering throughput and predictability, using delivery metrics to identify constraints.
8. Champion configuration over customization in platform design, ensuring customer specific needs are met through configuration wherever possible and that genuine platform gaps are surfaced into the roadmap.
9. Partner with DevSecOps, Infrastructure, and Security to ensure engineering practice meets ATO, FISMA, and applicable compliance obligations without becoming a delivery bottleneck.
10. Contribute engineering input to capture and pursuit activity as needed, in coordination with the Chief Architect.
Now Qualifications block:
"12+ years of software engineering experience, including 5+ years leading engineering teams, with at least 2 years managing managers or team leads.Demonstrated experience leading engineering organizations of 15 or more across multiple concurrent workstreams.Hands on background in modern cloud native application development; able to review designs and make architectural tradeoffs credibly.Experience operating in a regulated environment with formal security and compliance requirements.Experience with Agile or SAFe delivery and with Atlassian Jira and Confluence or equivalent tooling.Track record of hiring, developing, and retaining strong engineers.Excellent written and verbal communication, including the ability to explain engineering tradeoffs to non technical executives.Bachelor's degree in Computer Science, Engineering, or related technical field; equivalent experience considered.Ability to obtain and maintain a public trust government clearance.Must physically have lived in the United States for a cumulative total of at least three of the past five years."
Split sentences (note missing spaces after periods):
1. 12+ years of software engineering experience, including 5+ years leading engineering teams, with at least 2 years managing managers or team leads.
2. Demonstrated experience leading engineering organizations of 15 or more across multiple concurrent workstreams.
3. Hands on background in modern cloud native application development; able to review designs and make architectural tradeoffs credibly.
4. Experience operating in a regulated environment with
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Content: Description paragraph: "At Commence, we’re the start of a new age of data-centric transformation, elevating health outcomes and powering better, more efficient process to program and patient health. We combine quality data-driven solutions that fuel answers, technology that advances performance, and clinical expertise that builds trust to create a more efficient path to quality care. With human-centered, healthcare-relevant, and value-based solutions, we create new possibilities with data. We provide proof beyond the concept and performance beyond the scope with a focus on efficiencies that transform the lives of those we serve. With a culture driven by purpose, straightforward communication and clinical domain expertise, Commence cuts straight to better care." Then "Requirements" heading (actually the posting says "Requirements" but then includes a description of role responsibilities). Actually after description, there is "Requirements Commence is seeking a Director of Software Engineering to lead the teams building our go-forward technology platforms across federal health IT and commercial healthcare markets. This role owns engineering execution, technical quality, and team health. The Director of Software Engineering is accountable for how engineering work gets planned, sequenced, and delivered, and for building an organization that can scale as the customer base grows. This is a hands-on leadership role. The Director is expected to stay close enough to the technology to make sound architectural tradeoffs, review designs, and hold a high bar on engineering quality, while leading people and improving how the organization operates. Lead and develop a multi-team engineering organization across platform development, program build, production support, and applied AI, including hiring, coaching, performance management, and career development for team leads and individual contributors.Own engineering execution and delivery outcomes for the platform portfolio, including velocity, quality, technical debt posture, and the balance between roadmap work and program commitments.Refine and enforce engineering standards and practice across teams: SDLC, code review, testing strategy, release management, secure development, and documentation.Operate a capacity and allocation model across multiple work modes, protecting platform roadmap capacity while meeting program and production support demand.Partner with Technical Delivery leadership on resource allocation for program work, and with Technical Product on roadmap intake, sequencing, and prioritization.Partner with the Lead Software Architect and Chief Architect on platform design direction, standards governance, and technical feasibility of commitments made during pursuits.Drive continuous improvement in engineering throughput and predictability, using delivery metrics to identify constraints.Champion configuration over customization in platform design, ensuring customer specific needs are met through configuration wherever possible and that genuine platform gaps are surfaced into the roadmap.Partner with DevSecOps, Infrastructure, and Security to ensure engineering practice meets ATO, FISMA, and applicable compliance obligations without becoming a delivery bottleneck.Contribute engineering input to capture and pursuit activity as needed, in coordination with the Chief Architect." Then "Qualifications" heading: list of qualifications bullet points? Actually it's a paragraph with sentences separated by periods. We need to turn into list items? The rule: Use
- for any list of duties/requirements/benefits. The qualifications are a list of items; we can treat each sentence as a list item. Similarly responsibilities could be list items.
Then "Preferred Qualifications" heading: list of items.
Then "Work Environment/Physical Demands" heading: paragraph.
Then EEO boilerplate etc to remove.
Also there is a line: "Commence is an equal employment opportunity employer..." etc. Remove.
Also there is contact info for accommodation: "If you require a reasonable accommodation to participate in the application process due to a disability, please contact Human Resources at (757) 306-4920 or hr@commence.ai. Please note that unless you are requesting an accommodation, all applications must be submitted through our online application system." This is application instructions; remove.
Thus we need sections: About the role (maybe from description), Responsibilities (the block after "Requirements" heading? Actually that block is responsibilities), Qualifications (the bullet list after "Qualifications"), Preferred Qualifications (maybe as a subsection under Qualifications? But we could make separate section "Preferred Qualifications". The rules allow any of the headings list; we can include Preferred Qualifications as a heading if content exists. It does.
Work Environment/Physical Demands: we can include as a section maybe "Work Environment". The heading list includes "Benefits, Pay, Schedule". Not work environment. But we can still create a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we can use other headings if appropriate, but better to stick to those. However "Work Environment/Physical Demands" is not in the list but could be considered as "Responsibilities"? No. Might be better to include as a section with heading "Work Environment". The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to include only those headings that have content. We have About the role, Responsibilities, Requirements, Qualifications, maybe Skills? Not present. Benefits, Pay, Schedule not present. So we will not create those. We could incorporate Work Environment/Physical Demands into Responsibilities or Qualifications? Probably better to make a separate section "Work Environment". Since it's substantive. The instruction didn't forbid; it just gave examples. So we can. Thus sections:
About the role
... description paragraph ...
Responsibilities
- ... each responsibility sentence ...
Qualifications
- ... each qualification sentence ...
Preferred Qualifications
- ... each preferred qualification sentence ...
Work Environment
... work environment paragraph ...
We need to ensure we preserve all substantive information. Let's extract sentences. Description paragraph: It's one paragraph with multiple sentences. We'll keep as. Now responsibilities block: Let's split by periods that end sentences. Need to be careful not to split abbreviations like "SDLC," etc. But we can approximate. Responsibilities text: "Lead and develop a multi-team engineering organization across platform development, program build, production support, and applied AI, including hiring, coaching, performance management, and career development for team leads and individual contributors.Own engineering execution and delivery outcomes for the platform portfolio, including velocity, quality, technical debt posture, and the balance between roadmap work and program commitments.Refine and enforce engineering standards and practice across teams: SDLC, code review, testing strategy, release management, secure development, and documentation.Operate a capacity and allocation model across multiple work modes, protecting platform roadmap capacity while meeting program and production support demand.Partner with Technical Delivery leadership on resource allocation for program work, and with Technical Product on roadmap intake, sequencing, and prioritization.Partner with the Lead Software Architect and Chief Architect on platform design direction, standards governance, and technical feasibility of commitments made during pursuits.Drive continuous improvement in engineering throughput and predictability, using delivery metrics to identify constraints.Champion configuration over customization in platform design, ensuring customer specific needs are met through configuration wherever possible and that genuine platform gaps are surfaced into the roadmap.Partner with DevSecOps, Infrastructure, and Security to ensure engineering practice meets ATO, FISMA, and applicable compliance obligations without becoming a delivery bottleneck.Contribute engineering input to capture and pursuit activity as needed, in coordination with the Chief Architect." Note there are missing spaces after periods in some places (e.g., "...contributors.Own"). We'll need to add spaces for readability but must preserve info. We can keep as is but better to add a space after period when splitting. We'll produce list items each sentence. Let's split: 1. Lead and develop a multi-team engineering organization across platform development, program build, production support, and applied AI, including hiring, coaching, performance management, and career development for team leads and individual contributors. 2. Own engineering execution and delivery outcomes for the platform portfolio, including velocity, quality, technical debt posture, and the balance between roadmap work and program commitments. 3. Refine and enforce engineering standards and practice across teams: SDLC, code review, testing strategy, release management, secure development, and documentation. 4. Operate a capacity and allocation model across multiple work modes, protecting platform roadmap capacity while meeting program and production support demand. 5. Partner with Technical Delivery leadership on resource allocation for program work, and with Technical Product on roadmap intake, sequencing, and prioritization. 6. Partner with the Lead Software Architect and Chief Architect on platform design direction, standards governance, and technical feasibility of commitments made during pursuits. 7. Drive continuous improvement in engineering throughput and predictability, using delivery metrics to identify constraints. 8. Champion configuration over customization in platform design, ensuring customer specific needs are met through configuration wherever possible and that genuine platform gaps are surfaced into the roadmap. 9. Partner with DevSecOps, Infrastructure, and Security to ensure engineering practice meets ATO, FISMA, and applicable compliance obligations without becoming a delivery bottleneck. 10. Contribute engineering input to capture and pursuit activity as needed, in coordination with the Chief Architect. Now Qualifications block: "12+ years of software engineering experience, including 5+ years leading engineering teams, with at least 2 years managing managers or team leads.Demonstrated experience leading engineering organizations of 15 or more across multiple concurrent workstreams.Hands on background in modern cloud native application development; able to review designs and make architectural tradeoffs credibly.Experience operating in a regulated environment with formal security and compliance requirements.Experience with Agile or SAFe delivery and with Atlassian Jira and Confluence or equivalent tooling.Track record of hiring, developing, and retaining strong engineers.Excellent written and verbal communication, including the ability to explain engineering tradeoffs to non technical executives.Bachelor's degree in Computer Science, Engineering, or related technical field; equivalent experience considered.Ability to obtain and maintain a public trust government clearance.Must physically have lived in the United States for a cumulative total of at least three of the past five years." Split sentences (note missing spaces after periods): 1. 12+ years of software engineering experience, including 5+ years leading engineering teams, with at least 2 years managing managers or team leads. 2. Demonstrated experience leading engineering organizations of 15 or more across multiple concurrent workstreams. 3. Hands on background in modern cloud native application development; able to review designs and make architectural tradeoffs credibly. 4. Experience operating in a regulated environment with