• Support a large-scale government agency initiative to modernize a complex, interdependent system of systems migrating from legacy on-premises platforms to AWS Cloud Native architectures. • Conduct structured discovery sessions to understand legacy on-prem systems, workflows, data dependencies, and integration points. • Document current-state (As-Is) and target-state (To-Be) capabilities supporting AWS Cloud Native migration. • Support development of phased migration plans (e.g., refactor vs. lift-and-shift decisions). • Identify cross-system dependencies that must be sequenced to prevent downstream rework or hybrid thrashing. • Collaborate with architects to ensure requirements align to target cloud-native design principles. • Develop modernization EPICs aligned to cloud-native re-architecture, data ingestion modernization, integration redesign, automation of manual workflow gates, DevSecOps enablement. • Decompose EPICs into features and refined user stories with clear acceptance criteria, testable outcomes, and defined dependencies. • Establish initial product backlog in collaboration with Product Owners. • Ensure traceability from high-level modernization objectives to sprint-ready user stories. • Collaborate with Requirements Engineers in other workstreams to coordinate interdependent user stories, align sequencing of integration capabilities, prevent duplication of effort, and manage shared components. • Maintain visibility of system-of-systems impacts when new requirements are introduced. • Support integrated release planning across workstreams. • Participate in Agile Scrum ceremonies (Sprint Planning, Backlog Refinement, Daily Standups, Reviews & Retrospectives). • Work closely with Product Owners to prioritize backlog items, groom stories for sprint readiness, and ensure stories meet INVEST principles. • Define and document Definition of Done (DoD) criteria including code complete, automated tests implemented, documentation updated, security checks passed. • Support incremental delivery aligned to modernization milestones. • Develop requirements artifacts supporting architecture review board submissions, interface control documentation, security authorization processes. • Maintain end-to-end Requirements Traceability Matrix (RTM), ensuring requirements are testable and align with validation frameworks. • Define requirements for high-volume data processing systems, event-driven and serverless architectures, API-based integration patterns, and database modernization (e.g., Postgres/Aurora migration).