Senior Technical Functional Analyst
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. The job title is Senior Technical Functional Analyst. Not to use as heading.
We need to include sections: About the role (intro paragraph), Responsibilities, Requirements, Qualifications, Skills (maybe combine required and preferred?), Work Environment maybe as its own? But allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also add Work Environment? Not in list; but we could incorporate into About the role or maybe as part of Qualifications? Better to stick to allowed headings. Could treat work environment as part of About the role or maybe as a separate section not allowed? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should use those headings only if content exists. We have content for About the role (intro), Responsibilities, Requirements, Qualifications, Skills (maybe combine required and preferred as skills), Schedule (travel). No Benefits, Pay.
We need to preserve all substantive information. So we need to include details from description, responsibilities bullet list, required qualifications list, preferred qualifications list, work environment details (maybe incorporate into About the role or Schedule? Travel info is schedule). Work environment details like dress code, sitting/standing, use of hands, occasional movement, ability to travel up to 10% (we already have travel). Could include those in About the role or maybe a separate section not allowed; but we could incorporate into About the role as prose.
We must not include boilerplate like EEO, equal opportunity, etc. Remove those.
We must not include application instructions.
We need to output only HTML fragment.
Let's craft:
About the role
ITility is seeking a Senior Technical Functional Analyst to support a mission-critical enterprise modernization contract with the Department of Defense (DoD). This role supports mission-critical, AWS-hosted enterprise applications that enable the secure processing of recruit candidates entering the U.S. Armed Forces across geographically dispersed sites. This is a remote position with occasional travel up to 10%, which may include occasional visits to client sites or government installations. The position operates at the intersection of mission operations, cloud architecture, and Agile DevSecOps delivery. The Senior Technical Functional Analyst serves as a senior liaison between Government stakeholders and cloud development teams, translating operational requirements into secure, scalable, and technically sound solutions within a modern AWS cloud environment. The ideal candidate combines deep functional analysis expertise with technical fluency in cloud-native architectures and federal compliance frameworks.
Then Responsibilities: list bullet points from "Key Responsibilities:" sections.
We need to break into sub-sections? The responsibilities have categories: Requirements & Functional Leadership, Cloud & Technical Collaboration, Security, Compliance & Risk Management, Agile Product & Delivery Support, Stakeholder Engagement. We could keep as a single list with subheadings? But we cannot add extra headings beyond allowed? Could use for subheadings? Probably okay to keep as list items with the category bolded? But we must not invent headings. Safer to just list all responsibilities as
- items, preserving the detail.
Let's extract each bullet:
- Lead complex requirements elicitation sessions with Government stakeholders, subject matter experts, and executive leadership.
- Translate business, operational, and compliance needs into structured functional and non-functional requirements.
- Own the end-to-end requirements lifecycle from discovery through production deployment.
- Decompose system capabilities into epics, features, and detailed user stories aligned to Agile delivery practices.
- Maintain bidirectional traceability between requirements, design artifacts, test cases, and release deliverables.
- Partner with AWS cloud development teams supporting Ruby on Rails backend services, React front-end applications, PostgreSQL databases, and GraphQL APIs.
- Provide functional guidance on data modeling, database design considerations, and API schema structures.
- Support integration patterns leveraging AWS services such as CloudWatch, SQS, and SNS.
- Contribute to architecture and design reviews to ensure alignment with mission scalability and performance requirements.
- Collaborate within a DevSecOps pipeline supporting CI/CD, automated testing, and secure release management.
- Ensure requirements incorporate DoD security controls, role-based access controls, and least-privilege models.
- Support RMF documentation updates and control validation activities in coordination with cybersecurity teams.
- Identify functional risks, integration gaps, and system impacts; recommend mitigation strategies.
- Contribute to audit readiness and ATO sustainment activities.
- Participate in sprint planning, backlog refinement, release planning, and user acceptance testing.
- Support Product Owner in backlog prioritization aligned to mission value and operational impact.
- Analyze user feedback and system performance metrics to inform feature enhancements and continuous improvement.
- Develop clear, concise technical documentation, training materials, and executive-level briefings.
- Serve as a trusted advisor to Government leadership, technical teams, and cross-functional stakeholders.
- Deliver functional briefings and training sessions to both technical and non-technical audiences.
- Promote transparent communication and collaborative problem-solving across distributed teams.
Now Required Qualifications: list bullet points.
- U.S. Citizenship required; active DoD Secret clearance preferred.
- Minimum of eight (8) years of progressive experience in functional analysis, business systems analysis, or requirements engineering supporting federal IT systems.
- Demonstrated experience supporting AWS cloud-native application development environments.
- Experience operating within Agile or DevSecOps delivery environments.
- Demonstrated experience constructing workflow diagrams, data flow diagrams, interface specifications, and requirements traceability matrices.
- Strong analytical and systems-thinking mindset with exceptional attention to detail.
- Excellent written and verbal communication skills, including experience briefing executive-level stakeholders.
- Bachelor’s degree in Computer Science, Information Systems, or related field (or equivalent professional experience).
Preferred Qualifications: list bullet points.
- Experience supporting DoD or federal acquisition programs.
- Experience supporting systems operating under DoD RMF and cybersecurity compliance frameworks.
- Experience supporting applications built on Ruby on Rails, React, PostgreSQL, and GraphQL.
- Working knowledge of AWS services including CloudWatch, SQS, and SNS.
- Experience working in AWS GovCloud environments.
- Familiarity with role-based access control models and entitlement management.
- Experience supporting enterprise modernization or large-scale digital transformation initiatives.
- Agile certification (CSM, SAFe, or equivalent).
Work Environment: details: dress appropriately, sit/stand extended periods, sustained use of hands/fingers, frequent verbal communication, active listening, visual acuity, occasional movement around office including climbing stairs, ability to travel up to 10% (already covered). We could incorporate into About the role or maybe a separate section not allowed. Since we have Schedule heading for travel, we could put travel info there. Work environment details could go into About the role as prose.
Schedule: we have remote position with occasional travel up to 10%, occasional visits to client sites or government installations. So schedule section:
Remote position with occasional travel up to 10%, which may include occasional visits to client sites or government installations.
Now we need to ensure we don't include boilerplate like "Why ITility?" and EEO statements. Remove those.
Now produce HTML fragment with sections in order: About the role, Responsibilities, Requirements, Qualifications, Skills, Schedule. Should we include Skills? We could combine Required and Preferred qualifications into Skills? But we already have Requirements and Qualifications sections. The instruction list includes Skills as a possible heading. We could put combined skills (technical skills) under Skills. But we already have Requirements (maybe for required qualifications) and Qualifications (maybe for preferred?). However they'd be similar. Better to follow: Requirements = required qualifications, Qualifications = preferred qualifications, Skills = technical skills (like AWS, Ruby on Rails, etc). But we already have those in required and preferred. To avoid duplication, we could treat Requirements as required qualifications, Qualifications as preferred qualifications, and omit Skills (or combine some). But we need to include all substantive info; we can't omit required or preferred. So we need both sections. Use headings Requirements and Qualifications. That's fine.
Now Skills heading maybe not needed if we already covered skills in those sections. But we could still include Skills heading with a list of technical skills (AWS, Ruby on Rails, React, PostgreSQL, GraphQL, CloudWatch, SQS, SNS, DevSecOps, CI/CD, etc). However that would duplicate content from required/preferred. The instruction: "Prefer a few substantive sections over many thin ones." So maybe better to not add Skills if we already have Requirements and Qualifications covering skills. So we will omit Skills.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Schedule.
Check that we didn't miss any substantive info: The "Why ITility?" paragraph about mission impact, equal opportunity employer, etc. We removed EEO and equal opportunity lines. The "Why ITility?" includes mission impact statement: "Your work will directly contribute to enterprise modernization efforts supporting national defense readiness." That's substantive; we should keep that. It's not boilerplate; it's about the role's impact. So we should include that in About the role maybe as a separate paragraph.
Also "ITility is a Service-Disabled Veteran-Owned Business dedicated to delivering secure, innovative technology solutions that protect and defend our nation. We empower our teams to think beyond perceived limits and deliver mission-focused solutions that matter." That's also substantive about company. Should we include? It's not boilerplate; it's company description. Could include in About the role.
Thus About the role paragraph(s) can include multiple elements.
We must not include the EEO statement lines (the long paragraph about non-discrimination). Remove those.
Now produce final HTML.
Let's craft:
About the role
ITility is seeking a Senior Technical Functional Analyst to support a mission-critical enterprise modernization contract with the Department of Defense (DoD). This role supports mission-critical, AWS-hosted enterprise applications that enable the secure processing of recruit candidates entering the U.S. Armed Forces across geographically dispersed sites.
ITility is a Service-Disabled Veteran-Owned Business dedicated to delivering secure, innovative technology solutions that protect and defend our nation. We empower our teams to think beyond perceived limits and deliver mission-focused solutions that matter.
This is a remote position with occasional travel up to 10%, which may include occasional visits to client sites or government installations. The position operates at the intersection of mission operations, cloud architecture, and Agile DevSecOps delivery. The Senior Technical Functional Analyst serves as a senior liaison between Government stakeholders and cloud development teams, translating operational requirements into secure, scalable, and technically sound solutions within a modern AWS cloud environment. The ideal candidate combines deep functional analysis expertise with technical fluency in cloud-native architectures and federal
for prose. We must not repeat job title as heading. The job title is Senior Technical Functional Analyst. Not to use as heading. We need to include sections: About the role (intro paragraph), Responsibilities, Requirements, Qualifications, Skills (maybe combine required and preferred?), Work Environment maybe as its own? But allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also add Work Environment? Not in list; but we could incorporate into About the role or maybe as part of Qualifications? Better to stick to allowed headings. Could treat work environment as part of About the role or maybe as a separate section not allowed? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should use those headings only if content exists. We have content for About the role (intro), Responsibilities, Requirements, Qualifications, Skills (maybe combine required and preferred as skills), Schedule (travel). No Benefits, Pay.
We need to preserve all substantive information. So we need to include details from description, responsibilities bullet list, required qualifications list, preferred qualifications list, work environment details (maybe incorporate into About the role or Schedule? Travel info is schedule). Work environment details like dress code, sitting/standing, use of hands, occasional movement, ability to travel up to 10% (we already have travel). Could include those in About the role or maybe a separate section not allowed; but we could incorporate into About the role as prose.
We must not include boilerplate like EEO, equal opportunity, etc. Remove those.
We must not include application instructions.
We need to output only HTML fragment.
Let's craft:
About the role
About the role
ITility is seeking a Senior Technical Functional Analyst to support a mission-critical enterprise modernization contract with the Department of Defense (DoD). This role supports mission-critical, AWS-hosted enterprise applications that enable the secure processing of recruit candidates entering the U.S. Armed Forces across geographically dispersed sites. This is a remote position with occasional travel up to 10%, which may include occasional visits to client sites or government installations. The position operates at the intersection of mission operations, cloud architecture, and Agile DevSecOps delivery. The Senior Technical Functional Analyst serves as a senior liaison between Government stakeholders and cloud development teams, translating operational requirements into secure, scalable, and technically sound solutions within a modern AWS cloud environment. The ideal candidate combines deep functional analysis expertise with technical fluency in cloud-native architectures and federal compliance frameworks.
Then Responsibilities: list bullet points from "Key Responsibilities:" sections. We need to break into sub-sections? The responsibilities have categories: Requirements & Functional Leadership, Cloud & Technical Collaboration, Security, Compliance & Risk Management, Agile Product & Delivery Support, Stakeholder Engagement. We could keep as a single list with subheadings? But we cannot add extra headings beyond allowed? Could usefor subheadings? Probably okay to keep as list items with the category bolded? But we must not invent headings. Safer to just list all responsibilities as
Remote position with occasional travel up to 10%, which may include occasional visits to client sites or government installations.
Now we need to ensure we don't include boilerplate like "Why ITility?" and EEO statements. Remove those. Now produce HTML fragment with sections in order: About the role, Responsibilities, Requirements, Qualifications, Skills, Schedule. Should we include Skills? We could combine Required and Preferred qualifications into Skills? But we already have Requirements and Qualifications sections. The instruction list includes Skills as a possible heading. We could put combined skills (technical skills) under Skills. But we already have Requirements (maybe for required qualifications) and Qualifications (maybe for preferred?). However they'd be similar. Better to follow: Requirements = required qualifications, Qualifications = preferred qualifications, Skills = technical skills (like AWS, Ruby on Rails, etc). But we already have those in required and preferred. To avoid duplication, we could treat Requirements as required qualifications, Qualifications as preferred qualifications, and omit Skills (or combine some). But we need to include all substantive info; we can't omit required or preferred. So we need both sections. Use headings Requirements and Qualifications. That's fine. Now Skills heading maybe not needed if we already covered skills in those sections. But we could still include Skills heading with a list of technical skills (AWS, Ruby on Rails, React, PostgreSQL, GraphQL, CloudWatch, SQS, SNS, DevSecOps, CI/CD, etc). However that would duplicate content from required/preferred. The instruction: "Prefer a few substantive sections over many thin ones." So maybe better to not add Skills if we already have Requirements and Qualifications covering skills. So we will omit Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Schedule. Check that we didn't miss any substantive info: The "Why ITility?" paragraph about mission impact, equal opportunity employer, etc. We removed EEO and equal opportunity lines. The "Why ITility?" includes mission impact statement: "Your work will directly contribute to enterprise modernization efforts supporting national defense readiness." That's substantive; we should keep that. It's not boilerplate; it's about the role's impact. So we should include that in About the role maybe as a separate paragraph. Also "ITility is a Service-Disabled Veteran-Owned Business dedicated to delivering secure, innovative technology solutions that protect and defend our nation. We empower our teams to think beyond perceived limits and deliver mission-focused solutions that matter." That's also substantive about company. Should we include? It's not boilerplate; it's company description. Could include in About the role. Thus About the role paragraph(s) can include multipleelements. We must not include the EEO statement lines (the long paragraph about non-discrimination). Remove those. Now produce final HTML. Let's craft:
About the role
ITility is seeking a Senior Technical Functional Analyst to support a mission-critical enterprise modernization contract with the Department of Defense (DoD). This role supports mission-critical, AWS-hosted enterprise applications that enable the secure processing of recruit candidates entering the U.S. Armed Forces across geographically dispersed sites.
ITility is a Service-Disabled Veteran-Owned Business dedicated to delivering secure, innovative technology solutions that protect and defend our nation. We empower our teams to think beyond perceived limits and deliver mission-focused solutions that matter.
This is a remote position with occasional travel up to 10%, which may include occasional visits to client sites or government installations. The position operates at the intersection of mission operations, cloud architecture, and Agile DevSecOps delivery. The Senior Technical Functional Analyst serves as a senior liaison between Government stakeholders and cloud development teams, translating operational requirements into secure, scalable, and technically sound solutions within a modern AWS cloud environment. The ideal candidate combines deep functional analysis expertise with technical fluency in cloud-native architectures and federal