Technical Requirements Analyst / Documentation Specialist (FedLine ART)

Technical Requirements Analyst / Documentation Specialist (FedLine ART)

**Engagement:** Contract (staff augmentation) |

**Location:** Remote, must reside in continental US |

**Duration:** Through end of 2026, potential extension into 2027

The position is remote , but will require at least one visit during the contract to travel to Richmond, VA ....my preference is to have someone in Virginia.

This is a fast-moving req and will need folks ASAP.

Engagement context

About the Role

Once documentation standards and templates exist, this role does the hands-on work: creating standardized requirements templates, training the ART teams that will maintain them, and directly authoring process-flow and requirements documentation for the highest-priority applications - those being replaced (not lifted-and-shifted) as part of the cloud migration, where missing documentation is a known blocker.

Key Responsibilities

- Create standardized requirements documentation templates covering data flows/sequence

diagrams, file specifications and data dictionaries, API contracts, error handling/exception scenarios, and SLA/performance requirements

- Train the ART resources who will maintain these templates going forward

- Using the finalized templates, produce process flow and detailed requirements documentation for the top 3 5 prioritized applications (as defined by the Product Owner) - prioritized because they are being replaced rather than lifted-and-shifted, e.g., an on-prem-to-cloud datawarehouse migration with multiple undocumented partner interfaces

- Elicit requirements directly from engineering and business stakeholders where documentation

doesn't currently exist

- Write clear user stories, acceptance criteria, and definitions of done where backlog gaps are

uncovered along the way

- Extract, organize, and maintain content in SharePoint, Confluence, and JIRA/JIRA Align consistent with the strategy defined in the parallel Documentation Strategy Lead role

Required Skills & Experience

- Strong **technical documentation** skills: PRDs, user flows, process maps

- Proficiency with **process mapping / diagramming tools** (Visio, Lucidchart, Miro) and knowledge of

**BPMN, swimlane diagrams, value stream mapping**

- Fluency in **SharePoint, Confluence, JIRA, JIRA Align** for both extracting and creating content

- Data analysis skills - able to write queries, extract insights, and validate assumptions with real data; advanced Excel (pivot tables, macros, VLOOKUP-level proficiency)

- Experience writing **user stories and acceptance criteria** and managing agile backlogs

- Working knowledge of **Agile/Scrum ceremonies** (sprint planning, refinement, retrospectives) and familiarity with scaled agile frameworks (SAFe)

- Basic understanding of **REST APIs, webhooks, and data flows** - enough to accurately document integrations, not build them

Soft Skills (explicitly weighted by the Bank)

- Stakeholder management - balancing competing priorities across engineering, business, and customer groups; comfortable managing up and influencing without authority

- Communication & translation - able to bridge technical and non-technical audiences

- Critical thinking - asks "why" to find root causes rather than documenting symptoms

- Adaptability & autonomy - able to ramp quickly with minimal onboarding and handle shifting priorities

Collaboration & facilitation - works well cross-functionally and can drive discussions to

consensus

Why This Role Is Challenging

- Will be documenting systems where the people who built the original integrations may no longer be available - requires real elicitation skill, not just transcription

- Undocumented interfaces (e.g., 10+ partner interfaces on a single application) mean discovering scope as you go, not working from a clean spec

- Documentation quality here directly feeds the shared service architecture team's design work for cloud migration - errors or gaps propagate downstream

- Must adopt and reinforce the templates/taxonomy from the Documentation Strategy Lead role rather than freelancing a personal approach, even under deadline pressure