Director, AI Assisted Software Engineering
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions.
We need to parse the job description.
Key info:
- Type of Requisition: Regular (metadata)
- Clearance Level Must Currently Possess: None
- Clearance Level Must Be Able To Obtain: Secret
- Public Trust/Other Required: None
- Job Family: Data Science and Data Engineering
- Skills: (list? Actually "Skills:" then "Job Qualifications: Artificial Intelligence (AI), Emerging Technologies, Software Solutions")
- Certifications: None
- Experience: 5 + years of related experience
- US Citizenship Required: Yes
- Job Description: paragraph about senior engineering leader building AI-Assisted Development capability.
- Education & Experience: BA/BS in Computer Science, Engineering, or related field (or equivalent experience) 5+ years progressive software engineering experience with 3-5+ years in technical leadership roles required; 10+ years progressive software engineering experience with 3-5+ years in technical leadership roles preferred; Proven experience building and leading high‑performing engineering teams, including coaching, mentorship, and capability development; Must be able to obtain and maintain a Secret clearance; US Citizenship Required; Location: Remote
- AI-Assisted Development Expertise: bullet list (actually paragraphs) describing abilities.
- Capability Building: bullet list.
- Technical Leadership & Architecture: bullet list.
- Software Engineering Experience: bullet list.
- Preferred Skills: bullet list.
- GDIT IS YOUR PLACE: paragraphs about growth, support, rewards, flexibility, community.
- OWN YOUR OPPORTUNITY: paragraph about exploring career.
- #GDITLA (maybe ignore)
- The likely salary range for this position is $170,144 - $230,000. This is not, however, a guarantee of compensation or salary. Rather, salary will be set based on experience, geographic location and possibly contractual requirements and could fall outside of this range.
- Scheduled Weekly Hours: 40
- Travel Required: Less than 10%
- Telecommuting Options: Remote Work Location: Any Location / Remote
- Additional Work Locations: (maybe none)
- Total Rewards At GDIT: description of benefits.
- Our Identity Verification Process: description (maybe consider boilerplate? It's about hiring process, but not exactly EEO; could be considered part of process but maybe we keep as part of "About the role"? Might be considered boilerplate? It's specific to hiring process; but instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Identity verification is not exactly those, but could be considered legal. Safer to drop? Might be considered part of process but not required. I'd drop it as it's procedural.
- About Our Work: description of GDIT.
- Equal Opportunity Employer ... (drop)
We need to decide sections.
Potential sections:
- About the role (summary paragraph)
- Responsibilities (maybe from "You will serve as a senior engineering leader ..." and bullet lists of duties)
- Requirements (education, experience, clearance, citizenship)
- Qualifications (maybe same as Requirements? But we can combine)
- Skills (list of technical skills)
- Benefits (from Total Rewards)
- Pay (salary range)
- Schedule (Scheduled Weekly Hours: 40, Travel Required: Less than 10%, Telecommuting Options: Remote)
We must not create sections with filler like "commensurate with experience". We have actual content.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. Not include Job ID.
We must preserve all substantive info; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them.
We need to be careful not to lose any details.
Let's extract content.
First, the introductory paragraph: "You will serve as a senior engineering leader responsible for building and scaling our AI‑Assisted Development capability. This role goes far beyond “using AI tools” – you will establish the strategy, operating model, practices, and technical foundations required to transform how our teams design, build, test, and deliver software solutions and products using modern AI-enabled development approaches. You will evaluate and rationalize existing AI-enabled tools and platforms across the organization, become the internal expert on their use and integration, define best practices, upskill our engineers, and operationalize AI‑assisted development as an enterprise capability we can confidently take to market. The role blends technical leadership, architecture, go-to-market, organizational change management, and hands-on engineering expertise. This is a highly strategic and highly technical leadership role designed for an experienced engineering leader who thrives in emerging technology spaces and enjoys scaling new capabilities from the ground up."
That's the core description.
Then "Education & Experience:" bullet-ish sentences.
We can treat that as Requirements.
Then "Location: Remote" maybe part of Requirements or Schedule? Could be in Schedule? Actually location is remote, but schedule section includes weekly hours, travel, telecommuting. Location could be in About the role or Requirements. We'll include location in Requirements maybe.
Then "AI-Assisted Development Expertise:" list of abilities.
Then "Capability Building:" list.
Then "Technical Leadership & Architecture" list.
Then "Software Engineering Experience:" list.
Then "Preferred Skills:" list.
Then GDIT IS YOUR PLACE: paragraphs about Growth, Support, Rewards, Flexibility, Community. That's benefits-ish.
Then OWN YOUR OPPORTUNITY paragraph.
Then salary range.
Then Scheduled Weekly Hours: 40
Travel Required: Less than 10%
Telecommuting Options: Remote Work Location: Any Location / Remote
Additional Work Locations: (maybe none)
Total Rewards At GDIT: description of benefits.
We need to avoid duplication: GDIT IS YOUR PLACE already mentions Rewards etc. Total Rewards At GDIT repeats benefits. We need to preserve all substantive info, but we should not duplicate lines. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to detect duplicate content and keep only one instance.
GDIT IS YOUR PLACE includes: "Growth: AI-powered career tool that identifies career steps and learning opportunitiesSupport: An internal mobility team focused on helping you achieve your career goalsRewards: Comprehensive benefits and wellness packages, 401K with company match, and competitive pay and paid time offFlexibility: Full-flex work week to own your priorities at work and at homeCommunity: Award-winning culture of innovation and a military-friendly workplace"
Total Rewards At GDIT: longer description of benefits. Not exactly duplicate but overlapping. The instruction says remove duplicated lines, not necessarily overlapping content. Since they are not identical lines, we may keep both but could be considered redundant. However, we need to preserve all substantive information; we could combine them into a single Benefits section that includes all details from both. That would avoid duplication while preserving info.
Thus we can create a Benefits section that includes:
- Growth: AI-powered career tool that identifies career steps and learning opportunities
- Support: Internal mobility team focused on helping you achieve your career goals
- Rewards: Comprehensive benefits and wellness packages, 401K with company match, competitive pay and paid time off
- Flexibility: Full-flex work week to own your priorities at work and at home
- Community: Award-winning culture of innovation and a military-friendly workplace
- Plus details from Total Rewards: medical plan options, HSAs, dental, vision, 401(k) pre/post-tax contributions, company match, paid time off plans (vacation, sick, personal, holidays, paid parental, military, bereavement, jury duty), typically 15 days paid leave per calendar year + 10 paid holidays, prorated, Paid Family Leave up to 160 hours, short/long-term disability, life, AD&D, personal accident, critical illness, business travel accident insurance, regular review to ensure competitiveness.
We should keep all that.
Now schedule: Scheduled Weekly Hours: 40; Travel Required: Less than 10%; Telecommuting Options: Remote Work Location: Any Location / Remote.
We could also include Location: Remote from earlier.
Now Pay: salary range $170,144 - $230,000 with disclaimer.
Now Responsibilities: we can list duties from the description and the bullet lists under AI-Assisted Development Expertise, Capability Building, Technical Leadership & Architecture, Software Engineering Experience. Those are more like qualifications/skills. But we can treat them as Responsibilities? Actually they are more like required skills/experience. The instruction says use
- for any list of duties/requirements/benefits. So we can have separate sections: Responsibilities (duties), Requirements (education/experience/clearance/citizenship), Skills (technical skills), Qualifications (maybe overlapping). But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section called "Requirements & Qualifications". But headings must be from the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include only those that have real content.
We have:
- About the role: we have the introductory paragraph (the role description). Good.
- Responsibilities: we could list the duties: building and scaling AI-Assisted Development capability, establishing strategy, operating model, practices, technical foundations, evaluating/rationalizing existing AI-enabled tools, becoming internal expert, defining best practices, upskilling engineers, operationalizing AI-assisted development as enterprise capability, blending technical leadership, architecture, go-to-market, organizational change management, hands-on engineering expertise. That's from the paragraph. Could also include the bullet points under AI-Assisted Development Expertise etc. but those are more like skills/experience.
- Requirements: education (BA/BS in CS, Engineering, or related field or equivalent experience), experience (5+ years progressive software engineering experience with 3-5+ years in technical leadership roles required; 10+ years progressive software engineering experience with 3-5+ years in technical leadership roles preferred), proven experience building and leading high-performing engineering teams, must be able to obtain and maintain a Secret clearance, US Citizenship Required, Location: Remote.
- Qualifications: maybe we can list the specific expertise areas: AI-Assisted Development Expertise, Capability Building, Technical Leadership & Architecture, Software Engineering Experience. But those are more like skills. Could treat them as Qualifications.
- Skills: list of technical skills: Full-Stack development experience including proficiency across multiple programming languages (Java, JavaScript, Python, .NET, etc.), hands-on experience using modern front-end and back-end frameworks (Angular, React, Spring Boot, Django, Next.js, etc.), experience implementing and integrating solutions across variety of operating systems (Linux, Unix) and Platforms as a Service (RHEL, OpenShift), deep experience with API/webservice design, secure coding standards, scalable architectural patterns, plus Preferred Skills list (understanding of Federal acquisition and security compliance including FedRAMP and ATO implications, experience building enterprise AI-assisted development capability or platform offering, prior experience productizing internal capabilities into customer-facing solutions/services, familiar with Cloud-native platforms (AWS, Azure, GCP) and related AI/ML services including experience managing vendor relationships with OEM and ISVs, expertise with CI/CD automation, IaC, Policy as Code, governance automation frameworks (Terraform, Ansible, etc.), ability to translate technical concepts for non-technical stakeholders and influence across senior leadership levels, demonstrated ability to stay current with emerging AI, development, and architecture trends, and drive organizational adoption strategies).
We need to
- for any list of duties/requirements/benefits. Use
for prose. We must not repeat job title as heading. Not include Job ID. We must preserve all substantive info; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We need to be careful not to lose any details. Let's extract content. First, the introductory paragraph: "You will serve as a senior engineering leader responsible for building and scaling our AI‑Assisted Development capability. This role goes far beyond “using AI tools” – you will establish the strategy, operating model, practices, and technical foundations required to transform how our teams design, build, test, and deliver software solutions and products using modern AI-enabled development approaches. You will evaluate and rationalize existing AI-enabled tools and platforms across the organization, become the internal expert on their use and integration, define best practices, upskill our engineers, and operationalize AI‑assisted development as an enterprise capability we can confidently take to market. The role blends technical leadership, architecture, go-to-market, organizational change management, and hands-on engineering expertise. This is a highly strategic and highly technical leadership role designed for an experienced engineering leader who thrives in emerging technology spaces and enjoys scaling new capabilities from the ground up." That's the core description. Then "Education & Experience:" bullet-ish sentences. We can treat that as Requirements. Then "Location: Remote" maybe part of Requirements or Schedule? Could be in Schedule? Actually location is remote, but schedule section includes weekly hours, travel, telecommuting. Location could be in About the role or Requirements. We'll include location in Requirements maybe. Then "AI-Assisted Development Expertise:" list of abilities. Then "Capability Building:" list. Then "Technical Leadership & Architecture" list. Then "Software Engineering Experience:" list. Then "Preferred Skills:" list. Then GDIT IS YOUR PLACE: paragraphs about Growth, Support, Rewards, Flexibility, Community. That's benefits-ish. Then OWN YOUR OPPORTUNITY paragraph. Then salary range. Then Scheduled Weekly Hours: 40 Travel Required: Less than 10% Telecommuting Options: Remote Work Location: Any Location / Remote Additional Work Locations: (maybe none) Total Rewards At GDIT: description of benefits. We need to avoid duplication: GDIT IS YOUR PLACE already mentions Rewards etc. Total Rewards At GDIT repeats benefits. We need to preserve all substantive info, but we should not duplicate lines. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to detect duplicate content and keep only one instance. GDIT IS YOUR PLACE includes: "Growth: AI-powered career tool that identifies career steps and learning opportunitiesSupport: An internal mobility team focused on helping you achieve your career goalsRewards: Comprehensive benefits and wellness packages, 401K with company match, and competitive pay and paid time offFlexibility: Full-flex work week to own your priorities at work and at homeCommunity: Award-winning culture of innovation and a military-friendly workplace" Total Rewards At GDIT: longer description of benefits. Not exactly duplicate but overlapping. The instruction says remove duplicated lines, not necessarily overlapping content. Since they are not identical lines, we may keep both but could be considered redundant. However, we need to preserve all substantive information; we could combine them into a single Benefits section that includes all details from both. That would avoid duplication while preserving info. Thus we can create a Benefits section that includes: - Growth: AI-powered career tool that identifies career steps and learning opportunities - Support: Internal mobility team focused on helping you achieve your career goals - Rewards: Comprehensive benefits and wellness packages, 401K with company match, competitive pay and paid time off - Flexibility: Full-flex work week to own your priorities at work and at home - Community: Award-winning culture of innovation and a military-friendly workplace - Plus details from Total Rewards: medical plan options, HSAs, dental, vision, 401(k) pre/post-tax contributions, company match, paid time off plans (vacation, sick, personal, holidays, paid parental, military, bereavement, jury duty), typically 15 days paid leave per calendar year + 10 paid holidays, prorated, Paid Family Leave up to 160 hours, short/long-term disability, life, AD&D, personal accident, critical illness, business travel accident insurance, regular review to ensure competitiveness. We should keep all that. Now schedule: Scheduled Weekly Hours: 40; Travel Required: Less than 10%; Telecommuting Options: Remote Work Location: Any Location / Remote. We could also include Location: Remote from earlier. Now Pay: salary range $170,144 - $230,000 with disclaimer. Now Responsibilities: we can list duties from the description and the bullet lists under AI-Assisted Development Expertise, Capability Building, Technical Leadership & Architecture, Software Engineering Experience. Those are more like qualifications/skills. But we can treat them as Responsibilities? Actually they are more like required skills/experience. The instruction says use
- for any list of duties/requirements/benefits. So we can have separate sections: Responsibilities (duties), Requirements (education/experience/clearance/citizenship), Skills (technical skills), Qualifications (maybe overlapping). But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section called "Requirements & Qualifications". But headings must be from the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include only those that have real content. We have: - About the role: we have the introductory paragraph (the role description). Good. - Responsibilities: we could list the duties: building and scaling AI-Assisted Development capability, establishing strategy, operating model, practices, technical foundations, evaluating/rationalizing existing AI-enabled tools, becoming internal expert, defining best practices, upskilling engineers, operationalizing AI-assisted development as enterprise capability, blending technical leadership, architecture, go-to-market, organizational change management, hands-on engineering expertise. That's from the paragraph. Could also include the bullet points under AI-Assisted Development Expertise etc. but those are more like skills/experience. - Requirements: education (BA/BS in CS, Engineering, or related field or equivalent experience), experience (5+ years progressive software engineering experience with 3-5+ years in technical leadership roles required; 10+ years progressive software engineering experience with 3-5+ years in technical leadership roles preferred), proven experience building and leading high-performing engineering teams, must be able to obtain and maintain a Secret clearance, US Citizenship Required, Location: Remote. - Qualifications: maybe we can list the specific expertise areas: AI-Assisted Development Expertise, Capability Building, Technical Leadership & Architecture, Software Engineering Experience. But those are more like skills. Could treat them as Qualifications. - Skills: list of technical skills: Full-Stack development experience including proficiency across multiple programming languages (Java, JavaScript, Python, .NET, etc.), hands-on experience using modern front-end and back-end frameworks (Angular, React, Spring Boot, Django, Next.js, etc.), experience implementing and integrating solutions across variety of operating systems (Linux, Unix) and Platforms as a Service (RHEL, OpenShift), deep experience with API/webservice design, secure coding standards, scalable architectural patterns, plus Preferred Skills list (understanding of Federal acquisition and security compliance including FedRAMP and ATO implications, experience building enterprise AI-assisted development capability or platform offering, prior experience productizing internal capabilities into customer-facing solutions/services, familiar with Cloud-native platforms (AWS, Azure, GCP) and related AI/ML services including experience managing vendor relationships with OEM and ISVs, expertise with CI/CD automation, IaC, Policy as Code, governance automation frameworks (Terraform, Ansible, etc.), ability to translate technical concepts for non-technical stakeholders and influence across senior leadership levels, demonstrated ability to stay current with emerging AI, development, and architecture trends, and drive organizational adoption strategies). We need to