Sr Advanced Applications Developer Specialist
General Dynamics Mission Systems · Chantilly, VA · 3 wk ago
On-siteEngineering$133k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content.
From posting:
- Basic Qualifications (education/experience, citizenship, certification). That's qualifications.
- Responsibilities For This Position (multiple paragraphs). We'll put under
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content.
From posting:
- Basic Qualifications (education/experience, citizenship, certification). That's qualifications.
- Responsibilities For This Position (multiple paragraphs). We'll put under Responsibilities
.
- What You'll Own and What You Won't Own and What Makes This Role Different: these are part of responsibilities? Could be separate sections but we can combine under Responsibilities.
- Required Qualifications: list of qualifications.
- Preferred Qualifications: list.
- What Sets You Apart: could be Skills or maybe Qualifications? Might be considered "Skills" or "Qualifications". Could be a separate "Skills" section.
- Target salary range: Pay section.
- Benefits: Not explicitly mentioned besides "highly competitive benefits" in Company Overview. That's vague; not specific. So we should not create Benefits section unless specific benefits listed. There's no list.
- Schedule: Not mentioned.
- About the role: Could be from Company Overview: description of company. Could be "About the role" or "About the company". The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the role" likely corresponds to a brief description of the role. We have a description: "Turn the Enterprise Growth AI Platform vision into a secure, reliable enterprise capability..." etc. That's more responsibilities. Could treat as About the role.
We need to preserve all substantive info, not invent.
We'll create sections:
About the role
with prose summarizing the role description (the first paragraph after Responsibilities heading? Actually the posting: "Responsibilities For This Position Turn the Enterprise Growth AI Platform vision into a secure, reliable enterprise capability. You will partner..." That's basically responsibilities. But we can still put that under About the role as a short description. However we must not repeat content; we can split.
Better: Use About the role for the high-level description: "Turn the Enterprise Growth AI Platform vision into a secure, reliable enterprise capability. You will partner with Growth community subject-matter experts to develop prototypes and refine selected concepts into enterprise-scale applications. You will shape the technical roadmap, work with designated architects to define solutions that align with enterprise architecture, build and operate the shared platform, and guide safe deployment. This is a hands-on individual-contributor role for someone who can move from strategy to production code and communicate clearly with engineers, business partners, and senior executives."
Then Responsibilities section for the detailed bullet list (What You'll Own, What You Won't Own, What Makes This Role Different). We'll format as - each bullet.
Then Qualifications section: could split into Required Qualifications and Preferred Qualifications as sub-sections? The instruction says use headings like Qualifications (maybe one). Could combine but we need to preserve all info. Could have
Required Qualifications
and Preferred Qualifications
but those are not in the allowed list? The allowed list includes Qualifications (generic). It didn't forbid subheadings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those exact headings? It says e.g., meaning examples; we can use those headings. Probably we should use those exact headings. So we have: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have no Requirements separate from Qualifications? Could treat Requirements as same as Qualifications. But we have both Required and Preferred Qualifications. Could put Required under Qualifications and Preferred under Skills? Not ideal.
Maybe we can use Requirements for Required Qualifications, and Qualifications for Preferred? Or combine both under Qualifications with subheadings ? But only allowed for section headings; we could still use inside? Not prohibited but likely they want only those headings. Safer to use Qualifications for both required and preferred, maybe separate with inside? Might be okay.
But we need to include Pay section with salary range.
We have no Benefits specific; skip.
Schedule: none.
Skills: we have "What Sets You Apart" which describes skills/attributes. Could put under Skills.
Thus sections:
- About the role (description)
- Responsibilities (detailed bullets)
- Requirements (maybe we can put Required Qualifications here)
- Qualifications (Preferred Qualifications)
- Skills (What Sets You Apart)
- Pay (salary range)
We must not include empty sections.
Let's extract content.
About the role: Use the first paragraph after "Responsibilities For This Position": "Turn the Enterprise Growth AI Platform vision into a secure, reliable enterprise capability. You will partner with Growth community subject-matter experts to develop prototypes and refine selected concepts into enterprise-scale applications. You will shape the technical roadmap, work with designated architects to define solutions that align with enterprise architecture, build and operate the shared platform, and guide safe deployment. This is a hands-on individual-contributor role for someone who can move from strategy to production code and communicate clearly with engineers, business partners, and senior executives."
That's good.
Responsibilities: Need to capture all bullet points under "What You'll Own:", "What You Won't Own:", "What Makes This Role Different:".
We'll create list items for each bullet.
Let's list them:
What You'll Own:
- Platform strategy and delivery. Translate the Growth Platform vision into a sequenced roadmap, investment options, measurable outcomes, and delivery plans, working with designated enterprise and solution architects to define the target architecture.
- Community prototyping and maturation. Work with Growth subject-matter experts to clarify business problems, develop and evaluate prototypes, and refine selected concepts into secure, supportable, enterprise-scale applications.
- AI-Driven Platform and application development. Build, test, deploy, document, and improve shared Python services, APIs, data and AI capabilities, developer tooling, and selected enterprise applications.
- Safe application onboarding. Assess applications developed by others against architectural patterns defined with architects and requirements for integration, dependencies, identity, security, data, reliability, observability, and support readiness before deployment.
- Platform operations. Monitor health, troubleshoot incidents, maintain operational procedures, manage technical debt and lifecycle needs, and improve the platform as demand grows.
- Technical standards and enablement. Create reusable patterns, reference implementations, automated delivery controls, and guidance that help other developers build and integrate applications effectively.
- Technical influence and storytelling. Explain choices, tradeoffs, risks, value, and progress in a way that enables decisions across technical, business, and executive audiences.
What You Won't Own:
- Every prototype-to-production effort. The Growth community originates ideas, subject-matter experts remain essential through discovery and validation, and multiple team members continue to develop and mature applications that will live on the Growth Platform.
- Enterprise architecture ownership. You will contribute platform and application expertise and work with designated architects; architecture governance, standards ownership, and formal architectural approval remain with those roles.
- The primary relationship with Enterprise AI, IT, cybersecurity, or other enterprise organizations. You will provide technical analysis, support & recommendations as the technical lead; the Manager, Growth Systems & Analytics remains the primary interface.
- Unilateral deployment approval. You will make technical-readiness recommendations within the team's governance and prioritization process.
What Makes This Role Different:
- You will help determine what the platform should become and turn that vision into measurable capability.
- You will work across strategy, prototyping, architecture collaboration, development, deployment, operations, and continuous improvement - not just implementation.
- You will build selected applications directly while making the shared platform safer and easier for other developers to use.
- Innovation is distributed: you will help subject-matter experts develop and evaluate prototypes, work with architects on enterprise alignment, and help the team refine selected concepts into deployable applications.
- You will join a high-performing team whose members combine technical depth, business judgment, collaboration, and executive-ready communication.
We'll put all these as
- items.
Requirements: Required Qualifications list:
- Advanced application-development experience across design, development, testing, deployment, administration, support, and modernization.
- Strong Python development skills and experience building secure APIs and integrations with enterprise systems, data, identity, and infrastructure.
- Experience partnering with subject-matter experts to frame problems, translate outcomes into requirements, develop prototypes, incorporate feedback, and mature solutions for enterprise use.
- Experience collaborating with enterprise or solution architects to turn requirements and technical constraints into scalable, compliant application designs.
- Experience with automated functional and nonfunctional testing, peer review, CI/CD, security scanning, dependency management, observability, and DevSecOps practices.
- Demonstrated experience applying AI, machine learning, or large language models in production-oriented applications.
- Advanced problem-solving ability for ambiguous, cross-domain, high-visibility work, including converting uncertainty into options, risks, and mitigation actions.
- Demonstrated technical leadership through judgment, delivery, mentoring, and influence.
- Strong written, verbal, presentation, and interpersonal skills across technical, business, and executive audiences.
Also Basic Qualifications: Bachelor's degree in IT, Engineering and/or related field or equivalent relevant experience, plus 8 years of related experience; or Master's degree plus 6 years of related experience. Certified application developer indicating an advanced or expert degree of application development knowledge is strongly preferred. Due to the nature of work performed within our facilities, U.S. citizenship is required.
These are also qualifications; could be placed under Requirements as well. We'll combine all required qualifications (including basic) under Requirements.
Preferred Qualifications list:
- Experience managing the lifecycle of an enterprise platform, shared service layer, or integrated application portfolio.
- Experience delivering business applications from prototype through enterprise deployment, operations, and modernization.
- Experience with LLM APIs, retrieval-augmented generation, agentic workflows, knowledge services, data pipelines, and model evaluation.
- Experience with containers, automated delivery, configuration management, monitoring, capacity planning, backup, and recovery.
- Experience influencing technical standards and organizational change.
We'll put under Qualifications.
Skills: What Sets You Apart list:
- You can see the destination and build the next practical increment. Strategy and execution are part of the same job for you.
- You can draw out subject-matter expertise, turn it into a useful prototype and carry it through production deployment and improvement.
- You communicate with range, preserving technical accuracy while making value, risk, decisions, and progress clear to senior leaders.
- You influence change by creating clarity, building trust, demonstrating what works, and helping peers succeed.
- You balance capability with reliability, security, traceability, maintainability, and user outcomes.
We'll put as
- under Skills.
Pay: Target salary range: USD $132,930.00/Yr. - USD $143,835.00/Yr. This estimate represents the typical salary range for this position based on experience and other factors (geographic location, etc.). Actual pay may vary. This job posting will remain open until the position is filled.
We'll put that as
maybe.
We must not include boilerplate like Company Overview, Equal Opportunity, etc. So we omit that.
Now produce HTML fragment:
About the role
Turn the Enterprise Growth AI Platform vision into a secure, reliable enterprise capability. You will partner with Growth community subject-matter experts to develop prototypes and refine selected concepts into enterprise-scale applications. You will shape the technical roadmap, work with designated architects to define solutions that align with enterprise architecture, build and operate the shared platform, and guide safe deployment. This is a hands-on individual-contributor role for someone who can move from strategy to production code and communicate clearly with engineers, business partners, and senior executives.
Responsibilities
- Platform strategy and delivery. Translate the Growth Platform vision into a sequenced roadmap, investment options, measurable outcomes, and delivery plans, working with designated enterprise and solution architects to define the target architecture.
- Community prototyping and maturation. Work
Required Qualifications
andPreferred Qualifications
but those are not in the allowed list? The allowed list includes Qualifications (generic). It didn't forbid subheadings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those exact headings? It says e.g., meaning examples; we can use those headings. Probably we should use those exact headings. So we have: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have no Requirements separate from Qualifications? Could treat Requirements as same as Qualifications. But we have both Required and Preferred Qualifications. Could put Required under Qualifications and Preferred under Skills? Not ideal.
Maybe we can use Requirements for Required Qualifications, and Qualifications for Preferred? Or combine both under Qualifications with subheadings ? But only allowed for section headings; we could still use inside? Not prohibited but likely they want only those headings. Safer to use Qualifications for both required and preferred, maybe separate with inside? Might be okay.
But we need to include Pay section with salary range.
We have no Benefits specific; skip.
Schedule: none.
Skills: we have "What Sets You Apart" which describes skills/attributes. Could put under Skills.
Thus sections:
- About the role (description)
- Responsibilities (detailed bullets)
- Requirements (maybe we can put Required Qualifications here)
- Qualifications (Preferred Qualifications)
- Skills (What Sets You Apart)
- Pay (salary range)
We must not include empty sections.
Let's extract content.
About the role: Use the first paragraph after "Responsibilities For This Position": "Turn the Enterprise Growth AI Platform vision into a secure, reliable enterprise capability. You will partner with Growth community subject-matter experts to develop prototypes and refine selected concepts into enterprise-scale applications. You will shape the technical roadmap, work with designated architects to define solutions that align with enterprise architecture, build and operate the shared platform, and guide safe deployment. This is a hands-on individual-contributor role for someone who can move from strategy to production code and communicate clearly with engineers, business partners, and senior executives."
That's good.
Responsibilities: Need to capture all bullet points under "What You'll Own:", "What You Won't Own:", "What Makes This Role Different:".
We'll create list items for each bullet.
Let's list them:
What You'll Own:
- Platform strategy and delivery. Translate the Growth Platform vision into a sequenced roadmap, investment options, measurable outcomes, and delivery plans, working with designated enterprise and solution architects to define the target architecture.
- Community prototyping and maturation. Work with Growth subject-matter experts to clarify business problems, develop and evaluate prototypes, and refine selected concepts into secure, supportable, enterprise-scale applications.
- AI-Driven Platform and application development. Build, test, deploy, document, and improve shared Python services, APIs, data and AI capabilities, developer tooling, and selected enterprise applications.
- Safe application onboarding. Assess applications developed by others against architectural patterns defined with architects and requirements for integration, dependencies, identity, security, data, reliability, observability, and support readiness before deployment.
- Platform operations. Monitor health, troubleshoot incidents, maintain operational procedures, manage technical debt and lifecycle needs, and improve the platform as demand grows.
- Technical standards and enablement. Create reusable patterns, reference implementations, automated delivery controls, and guidance that help other developers build and integrate applications effectively.
- Technical influence and storytelling. Explain choices, tradeoffs, risks, value, and progress in a way that enables decisions across technical, business, and executive audiences.
What You Won't Own:
- Every prototype-to-production effort. The Growth community originates ideas, subject-matter experts remain essential through discovery and validation, and multiple team members continue to develop and mature applications that will live on the Growth Platform.
- Enterprise architecture ownership. You will contribute platform and application expertise and work with designated architects; architecture governance, standards ownership, and formal architectural approval remain with those roles.
- The primary relationship with Enterprise AI, IT, cybersecurity, or other enterprise organizations. You will provide technical analysis, support & recommendations as the technical lead; the Manager, Growth Systems & Analytics remains the primary interface.
- Unilateral deployment approval. You will make technical-readiness recommendations within the team's governance and prioritization process.
What Makes This Role Different:
- You will help determine what the platform should become and turn that vision into measurable capability.
- You will work across strategy, prototyping, architecture collaboration, development, deployment, operations, and continuous improvement - not just implementation.
- You will build selected applications directly while making the shared platform safer and easier for other developers to use.
- Innovation is distributed: you will help subject-matter experts develop and evaluate prototypes, work with architects on enterprise alignment, and help the team refine selected concepts into deployable applications.
- You will join a high-performing team whose members combine technical depth, business judgment, collaboration, and executive-ready communication.
We'll put all these as
allowed for section headings; we could still use inside? Not prohibited but likely they want only those headings. Safer to use Qualifications for both required and preferred, maybe separate with inside? Might be okay.
But we need to include Pay section with salary range.
We have no Benefits specific; skip.
Schedule: none.
Skills: we have "What Sets You Apart" which describes skills/attributes. Could put under Skills.
Thus sections:
- About the role (description)
- Responsibilities (detailed bullets)
- Requirements (maybe we can put Required Qualifications here)
- Qualifications (Preferred Qualifications)
- Skills (What Sets You Apart)
- Pay (salary range)
We must not include empty sections.
Let's extract content.
About the role: Use the first paragraph after "Responsibilities For This Position": "Turn the Enterprise Growth AI Platform vision into a secure, reliable enterprise capability. You will partner with Growth community subject-matter experts to develop prototypes and refine selected concepts into enterprise-scale applications. You will shape the technical roadmap, work with designated architects to define solutions that align with enterprise architecture, build and operate the shared platform, and guide safe deployment. This is a hands-on individual-contributor role for someone who can move from strategy to production code and communicate clearly with engineers, business partners, and senior executives."
That's good.
Responsibilities: Need to capture all bullet points under "What You'll Own:", "What You Won't Own:", "What Makes This Role Different:".
We'll create list items for each bullet.
Let's list them:
What You'll Own:
- Platform strategy and delivery. Translate the Growth Platform vision into a sequenced roadmap, investment options, measurable outcomes, and delivery plans, working with designated enterprise and solution architects to define the target architecture.
- Community prototyping and maturation. Work with Growth subject-matter experts to clarify business problems, develop and evaluate prototypes, and refine selected concepts into secure, supportable, enterprise-scale applications.
- AI-Driven Platform and application development. Build, test, deploy, document, and improve shared Python services, APIs, data and AI capabilities, developer tooling, and selected enterprise applications.
- Safe application onboarding. Assess applications developed by others against architectural patterns defined with architects and requirements for integration, dependencies, identity, security, data, reliability, observability, and support readiness before deployment.
- Platform operations. Monitor health, troubleshoot incidents, maintain operational procedures, manage technical debt and lifecycle needs, and improve the platform as demand grows.
- Technical standards and enablement. Create reusable patterns, reference implementations, automated delivery controls, and guidance that help other developers build and integrate applications effectively.
- Technical influence and storytelling. Explain choices, tradeoffs, risks, value, and progress in a way that enables decisions across technical, business, and executive audiences.
What You Won't Own:
- Every prototype-to-production effort. The Growth community originates ideas, subject-matter experts remain essential through discovery and validation, and multiple team members continue to develop and mature applications that will live on the Growth Platform.
- Enterprise architecture ownership. You will contribute platform and application expertise and work with designated architects; architecture governance, standards ownership, and formal architectural approval remain with those roles.
- The primary relationship with Enterprise AI, IT, cybersecurity, or other enterprise organizations. You will provide technical analysis, support & recommendations as the technical lead; the Manager, Growth Systems & Analytics remains the primary interface.
- Unilateral deployment approval. You will make technical-readiness recommendations within the team's governance and prioritization process.
What Makes This Role Different:
- You will help determine what the platform should become and turn that vision into measurable capability.
- You will work across strategy, prototyping, architecture collaboration, development, deployment, operations, and continuous improvement - not just implementation.
- You will build selected applications directly while making the shared platform safer and easier for other developers to use.
- Innovation is distributed: you will help subject-matter experts develop and evaluate prototypes, work with architects on enterprise alignment, and help the team refine selected concepts into deployable applications.
- You will join a high-performing team whose members combine technical depth, business judgment, collaboration, and executive-ready communication.
We'll put all these as
inside? Might be okay. But we need to include Pay section with salary range. We have no Benefits specific; skip. Schedule: none. Skills: we have "What Sets You Apart" which describes skills/attributes. Could put under Skills. Thus sections: - About the role (description) - Responsibilities (detailed bullets) - Requirements (maybe we can put Required Qualifications here) - Qualifications (Preferred Qualifications) - Skills (What Sets You Apart) - Pay (salary range) We must not include empty sections. Let's extract content. About the role: Use the first paragraph after "Responsibilities For This Position": "Turn the Enterprise Growth AI Platform vision into a secure, reliable enterprise capability. You will partner with Growth community subject-matter experts to develop prototypes and refine selected concepts into enterprise-scale applications. You will shape the technical roadmap, work with designated architects to define solutions that align with enterprise architecture, build and operate the shared platform, and guide safe deployment. This is a hands-on individual-contributor role for someone who can move from strategy to production code and communicate clearly with engineers, business partners, and senior executives." That's good. Responsibilities: Need to capture all bullet points under "What You'll Own:", "What You Won't Own:", "What Makes This Role Different:". We'll create list items for each bullet. Let's list them: What You'll Own: - Platform strategy and delivery. Translate the Growth Platform vision into a sequenced roadmap, investment options, measurable outcomes, and delivery plans, working with designated enterprise and solution architects to define the target architecture. - Community prototyping and maturation. Work with Growth subject-matter experts to clarify business problems, develop and evaluate prototypes, and refine selected concepts into secure, supportable, enterprise-scale applications. - AI-Driven Platform and application development. Build, test, deploy, document, and improve shared Python services, APIs, data and AI capabilities, developer tooling, and selected enterprise applications. - Safe application onboarding. Assess applications developed by others against architectural patterns defined with architects and requirements for integration, dependencies, identity, security, data, reliability, observability, and support readiness before deployment. - Platform operations. Monitor health, troubleshoot incidents, maintain operational procedures, manage technical debt and lifecycle needs, and improve the platform as demand grows. - Technical standards and enablement. Create reusable patterns, reference implementations, automated delivery controls, and guidance that help other developers build and integrate applications effectively. - Technical influence and storytelling. Explain choices, tradeoffs, risks, value, and progress in a way that enables decisions across technical, business, and executive audiences. What You Won't Own: - Every prototype-to-production effort. The Growth community originates ideas, subject-matter experts remain essential through discovery and validation, and multiple team members continue to develop and mature applications that will live on the Growth Platform. - Enterprise architecture ownership. You will contribute platform and application expertise and work with designated architects; architecture governance, standards ownership, and formal architectural approval remain with those roles. - The primary relationship with Enterprise AI, IT, cybersecurity, or other enterprise organizations. You will provide technical analysis, support & recommendations as the technical lead; the Manager, Growth Systems & Analytics remains the primary interface. - Unilateral deployment approval. You will make technical-readiness recommendations within the team's governance and prioritization process. What Makes This Role Different: - You will help determine what the platform should become and turn that vision into measurable capability. - You will work across strategy, prototyping, architecture collaboration, development, deployment, operations, and continuous improvement - not just implementation. - You will build selected applications directly while making the shared platform safer and easier for other developers to use. - Innovation is distributed: you will help subject-matter experts develop and evaluate prototypes, work with architects on enterprise alignment, and help the team refine selected concepts into deployable applications. - You will join a high-performing team whose members combine technical depth, business judgment, collaboration, and executive-ready communication. We'll put all these as
maybe. We must not include boilerplate like Company Overview, Equal Opportunity, etc. So we omit that. Now produce HTML fragment:
About the role
Turn the Enterprise Growth AI Platform vision into a secure, reliable enterprise capability. You will partner with Growth community subject-matter experts to develop prototypes and refine selected concepts into enterprise-scale applications. You will shape the technical roadmap, work with designated architects to define solutions that align with enterprise architecture, build and operate the shared platform, and guide safe deployment. This is a hands-on individual-contributor role for someone who can move from strategy to production code and communicate clearly with engineers, business partners, and senior executives.
Responsibilities
- Platform strategy and delivery. Translate the Growth Platform vision into a sequenced roadmap, investment options, measurable outcomes, and delivery plans, working with designated enterprise and solution architects to define the target architecture.
- Community prototyping and maturation. Work