Job description

What You'll Do - Lead JAD (Joint Application Development/Configuration) sessions to identify required functionality and use cases - Elicit, document, and validate business and functional requirements across program, legal, IT, and fiscal stakeholder groups - Draft and maintain Business Requirements Documents (BRDs), Functional Requirements Documents (FRDs), and user acceptance criteria - Translate high-level program policies into field-level configuration rules, workflow logic, and compliance validations - Map out and revise As-Is and To-Be business processes with clients, identifying pain points and automation opportunities - Serve as a customer-facing subject matter expert for specific grants lifecycle workflows and funding logic - Create and manage traceability matrices linking requirements to system configuration and test coverage - Collaborate with development and configuration teams to align on functional design and validate system behavior - Coordinate UAT cycles and guide clients through test script execution and results validation What You'll Bring - 3–5 years in SaaS implementation, business analysis, or public sector consulting - Proven success facilitating discovery sessions and requirements workshops (e.g., JAD) - Experience drafting BRDs, FRDs, and traceability matrices used in successful implementations - Strong familiarity with government workflows (grant application intake, program compliance, fiscal reporting) - Demonstrated ability to translate policy or regulatory guidance into system logic and business rules - Experience partnering with QA or config teams to co-author test cases and validation scripts - Adept in business process mapping (As-Is/To-Be) and helping customers evaluate what to automate, eliminate, or streamline - Strong documentation and stakeholder communication skills - Experience with our Tech Stack Tools: Azure DevOps, Lucidchart/Visio, Microsoft Office Suite What Success Looks Like - All business and functional requirements are traceable, testable, and documented by the end of the discovery phase - Configuration and development teams report fewer than 10% scope revisions post-discovery - Stakeholders from multiple departments feel understood, aligned, and clear on what’s being built - UAT test plans and results are directly tied to your requirements, resulting in faster client sign-off

Requirements