Open Data Jobs is seeking a Business Analyst to translate stakeholder needs into clear requirements, map current and future processes, and document decisions and exceptions to guide delivery teams. The role can sit near software, data, operations, policy, or all four, and involves interviewing users and subject-matter experts, mapping current and future workflows, maintaining traceability as requirements evolve, and helping ensure the delivered solution solves the original problem as work moves between mission and technical teams. Location: Washington, United States. Work arrangement: Hybrid.

What you'll build - Current-state and future-state process maps that reveal decisions, handoffs, delays, exceptions, and control points. - Business requirements, functional requirements, user stories, business rules, and acceptance criteria that delivery teams can act on. - Requirements traceability that connects mission needs to designs, releases, tests, and implemented outcomes. - User acceptance testing plans, scenarios, and evidence that demonstrate whether the solution works as intended. - Decision records, data definitions, and operating documentation that remain useful after implementation.

Who you are You are curious about how work really happens, listen carefully, ask the question behind the first answer, and write with enough precision that ambiguity becomes a decision instead of a defect. You enjoy being the bridge without becoming a messenger, you understand the substance, challenge assumptions on both sides, and help the team reach a shared, testable understanding.

What

Open Data Jobs is seeking a Business Analyst to translate stakeholder needs into clear requirements, map current and future processes, and document decisions and exceptions to guide delivery teams. The role can sit near software, data, operations, policy, or all four, and involves interviewing users and subject-matter experts, mapping current and future workflows, maintaining traceability as requirements evolve, and helping ensure the delivered solution solves the original problem as work moves between mission and technical teams. Location: Washington, United States. Work arrangement: Hybrid.

What you'll build - Current-state and future-state process maps that reveal decisions, handoffs, delays, exceptions, and control points. - Business requirements, functional requirements, user stories, business rules, and acceptance criteria that delivery teams can act on. - Requirements traceability that connects mission needs to designs, releases, tests, and implemented outcomes. - User acceptance testing plans, scenarios, and evidence that demonstrate whether the solution works as intended. - Decision records, data definitions, and operating documentation that remain useful after implementation.

Who you are You are curious about how work really happens, listen carefully, ask the question behind the first answer, and write with enough precision that ambiguity becomes a decision instead of a defect. You enjoy being the bridge without becoming a messenger, you understand the substance, challenge assumptions on both sides, and help the team reach a shared, testable understanding.

What