Business Analyst

QualityWorks Consulting Group

Business Analyst Job Description Focus: Domain Context & Requirements Analysis Department: Technology Location: United States – Remote Experience Level: Mid-Level Security Requirement: Must be a U.S. Citizen and eligible to obtain and maintain the required Public Trust determination and DoD system access. About the Role We are seeking a Mid-Level Business System Analyst to collect and analyze domain-specific context for each system in scope on a government client engagement. The primary responsibility of this role is to serve as the accuracy layer between business stakeholders and the delivery team. The Business System Analyst elicits requirements, business rules, and workflows directly from stakeholders; translates them into structured, validated documentation; and ensures that context is accurate, complete, and consistently understood by developers, the test team, and any AI/automation components that depend on it. The role requires strong requirements-elicitation judgment, disciplined documentation practice, and the ability to work within controlled government engagement environments. This is a mid-level analyst role, not a senior/lead architecture position — the emphasis is on thorough, well-validated analysis rather than independent system design. What You'll Do Collect and analyze domain-specific context for each system in scope, working directly with business stakeholders to capture requirements, business rules, and workflows. Develop and maintain requirements, business-rule, and domain-context documentation that serves as a source of truth for downstream teams. Coordinate with business stakeholders, developers, and the test team to confirm domain context is accurate, complete, and consistently understood across the delivery team. Identify, document, and track gaps, assumptions, and open questions in the domain context, driving them to resolution with the appropriate stakeholder. Monitor changes to domain context, requirements, and business rules over time, and communicate their impact to appropriate stakeholders. Maintain clear visibility into context accuracy and completeness, flagging areas of low confidence before they become downstream defects. Facilitate stakeholder meetings and working sessions to elicit domain knowledge, resolve ambiguities, and validate understanding. Collaborate with technical leadership, program leadership, and stakeholders to support successful delivery of project objectives.

What We're Looking For Bachelor's degree in Business Administration, Information Systems, Information Technology, Computer Science, Business Analytics, or a related field — or equivalent practical experience. 3–5 years of experience as a business analyst, business systems analyst, or similar requirements-focused role on a software delivery team. Demonstrated experience eliciting requirements and domain knowledge directly from business stakeholders (interviews, workshops, document review) and translating it into structured, usable documentation. Experience working cross-functionally with both business stakeholders and technical teams (developers and QA), acting as the accuracy check between what the business needs and what's being built and tested. Strong written documentation skills — able to produce requirements/business-rule documentation clear enough for a developer or tester to work from without re-interviewing the business. Experience identifying gaps, ambiguities, or conflicting requirements and driving them to resolution rather than passing them downstream unresolved. Familiarity with Agile/Scrum delivery (backlog grooming, sprint reviews, acceptance criteria definition). Ability to work independently within a remote and security-conscious engagement environment.

Nice to Have (not required) IIBA certification (CBAP, CCBA, or ECBA) or PMI-PBA, reflecting formal training in business analysis practice. IIBA Agile Analysis Certification (AAC) or equivalent, given the Agile delivery context. Prior experience on a government-client or public-sector engagement, including familiarity with SOW/CDRL-style deliverable schedules and Government Furnished Information (GFI) handling. Experience preparing structured domain/requirements artifacts intended as input for AI or automation components (e.g., model training data, rules engines), not just traditional software requirements. Familiarity with requirements/traceability tooling (e.g., JIRA, Confluence, or a dedicated requirements management tool). Experience building or maintaining a living knowledge base that multiple teams rely on as a source of truth. What We Offer Competitive salary commensurate with competence and experience Referral bonus in accordance with existing referral programme A collaborative team environment working alongside developers, QA, and program leadership on a government client engagement Security & Eligibility Requirements This position involves direct engagement with business stakeholders on the client side and receipt/handling of Government Furnished Information (GFI) and other business-sensitive material. Candidates must: Be based in the United States. Be legally authorized to work in the United States. Be able to complete required background/vetting paperwork (e.g., SAAR-N, DD Form 2875 – System Authorization Access Request (SAAR), or Public Trust processes) within the standard post-award window. Complete any required security awareness training within the standard post-award window. Comply with applicable organizational and contractual rules governing handling of Government Furnished Information (GFI) and other business-sensitive content. Maintain continued eligibility for the assigned engagement's access requirements throughout employment. What Success Looks Like Success in this role means the domain context captured is accurate, complete, and trusted enough that developers can build against it and the test team can validate against it without re-interviewing the business. The Business System Analyst provides the judgment necessary to determine whether requirements are fully understood, gaps and assumptions are surfaced before they become downstream defects, and the domain context stays current as the system and business rules evolve. The analyst also maintains the documentation discipline and stakeholder trust expected when serving as the source of truth for a multi-team delivery effort.