Technical Business Analyst

Description

At Commence, we’re the start of a new age of data‑centric transformation, elevating health outcomes and powering better, more efficient process to program and patient health. We combine quality data‑driven solutions that fuel answers, technology that advances performance, and clinical expertise that builds trust to create a more efficient path to quality care.

With human‑centered, healthcare‑relevant, and value‑based solutions, we create new possibilities with data. We provide proof beyond the concept and performance beyond the scope with a focus on efficiencies that transform the lives of those we serve. With a culture driven by purpose, straightforward communication and clinical domain expertise, Commence cuts straight to better care.

The Business Analyst facilitates assigned projects by serving as the requirements authority between stakeholders and the engineering team. This is not a liaison or note‑taking function. The BA at Commence sits at the center of how we define, document, and protect what gets built – working directly alongside Technical Delivery Managers to own the requirements baseline from initiation through closure on programs that directly affect outcomes.

This role requires demonstrated requirements development and traceability skills, strong written communication, and the ability to operate where the contract, the customer, and the engineering team converge.

• 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.

• 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.

• 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…