Education Requirements:
Bachelor's degree in Computer Science or related field is required or equivalent combination of education and relevant work experience plus a minimum of 5 years of relevant experience; or Master's degree plus a minimum of 3 years of relevant experience. Experience capturing, analyzing, and translating business requirements, specifications, processes, and business cases desired. Proficient as a developer, systems integrator, systems engineer, solutions architect, or similar preferred. Proficiency in development languages, platforms, and tools preferred. Proficient knowledge of SQL queries for data transfer or business reporting preferred.
Clearance Requirements :
Ability to obtain a Department of Defense Secret security clearance is required at time of hire. Applicants selected will be subject to a U.S. Government security investigation and must meet eligibility requirements for access to classified information. Due to the nature of work performed within our facilities, U.S. citizenship is required.
What You'll Own
- Current-state process mapping. Document existing business processes end-to-end: tasks, roles, systems, handoffs, decision points, exceptions, and workarounds. Get the real process, not the documented one.
- Future-state design. Work with Domain SMEs and the engineering team to define target processes that leverage AI capabilities — automation, intelligent routing, predictive decision support — while preserving business rules that exist for a reason.
- Gap analysis. Identify what changes between current and future state — process changes, data requirements, training needs, compliance impacts. Make the implicit explicit.
- User workflow analysis. Understand who performs each task, what systems they touch, what their pain points are, and what adoption barriers exist. The best system in the world fails if people won't use it.
- Acceptance criteria. Define clear, testable criteria for whether the new system meets the business need. Work with the Product Owner to ensure the pod builds what the business actually requires.
What You Won't Own
- Technical implementation decisions — you define the what, the engineers define the how
- Backlog prioritization — that's the Product Owner's call
- Change management or training delivery — that's a matrix partner role
What Makes This Role Different
- Your analysis directly shapes what gets built. You are not writing requirements for a vendor to interpret — you are sitting next to the engineers who will build it.
- You are working on AI-native system replacement, not incremental improvement. The future state isn't a better version of the current system — it's a fundamentally different approach.