Technical Business Analyst

Commence is at the forefront of data-centric transformation in healthcare, aiming to improve health outcomes through innovative solutions. The Technical Business Analyst will facilitate projects by bridging the gap between stakeholders and the engineering team, ensuring clear requirements and documentation throughout the project lifecycle.

Responsibilities:

• Leads requirements gathering through structured sessions with stakeholders, engineering, and customer-facing teams -- translating discovery into a baseline that Engineering can build from
• Produces and maintains the requirements baseline document for projects: functional requirements, non-functional requirements, acceptance criteria, assumptions, constraints, and a traceability index
• Maintains traceability between requirements and delivery outputs
• Runs stakeholder sign-off processes and communicates baseline changes to all relevant parties when scope evolves
• Acts as a liaison between product owners and the engineering team; assists stakeholders in transforming customer needs into effective functional and non-functional requirements
• Supports the Platform Team's feature fit and reusability analysis by documenting requirements patterns across programs, identifying where similar needs are being solved differently across verticals, and surfacing duplication risks early
• Assists in testing and user validation of solutions prior to implementation
• Maintains working knowledge of SDLC, project management, change control, and configuration management procedures
• Participates in software development and delivery management meetings
• Helps maintain operating approaches

Requirements:

• Bachelor's degree in information systems or a related field required
• 3 to 5 years of experience in a business analysis, requirements management, or technical delivery support role, preferably in federal health IT or a comparable regulated environment
• Demonstrated ability to produce and maintain structured requirements documentation in a delivery context, not just gathering notes, but owning a living baseline that Engineering references throughout a build
• Sufficient technical fluency to translate between what stakeholders ask for and what Engineering can build: understands what a sprint, a data model, and an API integration mean in practice. Code writing not required
• Experience working on or adjacent to federal programs (CMS, VA, DHA, or similar): understands what a SOW and QASP are, and why the difference between an internal scope change and a contractual modification matters
• Experience in an Agile/Scrum software development environment required
• Strong written communication: requirements documents, change logs, and stakeholder summaries are primary work products and must be clear, precise, and defensible
• Must be eligible to obtain and maintain appropriate Security Clearance for work being performed
• Proven analytical skills with the ability to identify root causes of issues and implement timely solutions in SaaS/federal delivery environments
• Self-directed; capable of working effectively in a fast-moving, lean environment with significant individual responsibility
• Able to facilitate independent meetings; comfortable working with all levels of the organization and communicating technical issues clearly to both technical and non-technical stakeholders
• Strong organizational and time management skills; able to multitask efficiently without sacrificing quality
• Ability to lead and influence diverse teams of internal and external stakeholders to achieve milestones and delivery objectives
• Ability to engage stakeholders to discuss, formulate, and obtain: technical inputs, business requirements, schedules, issue resolution, and resource identification
• Experience with federal contract vehicles -- IDIQ task orders, OTAs, T&M programs -- and the delivery dynamics they create
• Familiarity with health data interoperability standards -- HL7 FHIR, X12 EDI, or HL7 v2
• Background in health IT platforms: claims processing, care quality, prior authorization, dispute resolution, or similar
• Experience supporting platform-level product thinking: feature reusability, modular capability design, or shared service identification
• Familiarity with Jira, Confluence, or similar delivery tooling for requirements tracking and documentation
• Knowledge of healthcare IT systems and the healthcare software market