Job Requirements
Job Description
FEDITC, LLC is a fast-growing business supporting DoD and other intelligence agencies worldwide. FEDITC develops mission critical national security systems throughout the world directly supporting the Warfighter, DoD Leadership, & the country. We are proud & honored to provide these services.
Overview of position:
FEDITC is seeking an experienced Technical Business Analyst / Product Analyst to support the Cybersecurity and Infrastructure Security Agency (CISA) in designing and delivering new digital, data, and AI-enabled capabilities.
This is not a traditional requirements-documentation Business Analyst position.
We are looking for an analyst who can take an ambiguous mission or business problem and independently drive it toward a solution that an Agile technical team can build. The successful candidate must be able to discover how a business process actually operates, model the current and future state, identify systems and data dependencies, decompose complex needs into functional and technical requirements, and translate those requirements into development-ready backlog items.
The analyst will work directly with government stakeholders, Product Owners, solution and enterprise architects, developers, data engineers, database engineers, testers, Scrum Masters, and program leadership.
The ideal candidate understands enough about modern application development, enterprise data platforms, data pipelines, APIs, AI/ML-enabled solutions, and system architecture to ask technically meaningful questions and bridge the gap between mission stakeholders and engineering teams. The analyst is not expected to serve as the software developer, data engineer, or solution architect, but must be technically fluent enough to work effectively with each of them.
Success in this position requires much more than taking meeting notes and converting them into requirements. The successful candidate must be comfortable challenging assumptions, identifying missing requirements, modeling complex processes and system interactions, analyzing data needs, and continuing discovery until the development team has a clear and testable definition of what must be built.
A United States Citizenship is required for this position. Candidates must be able to obtain and maintain DHS suitability and access to government systems and information as required. Personnel will support a DHS environment containing Controlled Unclassified Information (CUI).
Responsibilities:
- Lead structured discovery sessions, stakeholder interviews, requirements workshops, and technical discussions to understand mission problems, business processes, user needs, constraints, and desired outcomes.
- Take ambiguous or high-level business needs and decompose them into specific business, functional, nonfunctional, technical, data, integration, and security requirements.
- Ask probing questions to uncover requirements that stakeholders may not initially recognize or articulate.
- Identify assumptions, constraints, dependencies, exceptions, business rules, edge cases, risks, and unanswered questions before requirements enter development.
- Distinguish between a stakeholder's requested solution and the underlying business or mission problem, and help the team determine what capability actually needs to be built.
- Independently analyze requirements for completeness, consistency, feasibility, traceability, and technical impact.
Business and Systems Modeling
- Analyze and document current-state and future-state business processes, including users, systems, decision points, data movement, integrations, handoffs, exceptions, and business rules.
- Develop structured visual models rather than relying solely on narrative documentation or simple flowcharts.
- Apply modeling techniques such as Business Process Model and Notation (BPMN), Unified Modeling Language (UML), use-case modeling, activity diagrams, sequence diagrams, context diagrams, data-flow diagrams, entity-relationship models, and system/interface diagrams, as appropriate to the problem.
- Work with solution and enterprise architects to ensure business-process models align with the proposed technical architecture.
- Perform gap analysis and identify process, system, information, and capability changes necessary to move from current state to future state.
Data Requirements and Data-Centric Solutions
- Define data requirements at a level sufficient for data engineers, database engineers, developers, and architects to design and implement the solution.
- Identify and document:
- authoritative data sources;
- source and target systems;
- data owners and consumers;
- data entities and attributes;
- business definitions and business rules;
- source-to-target mappings;
- ingestion requirements;
- transformation and enrichment rules;
- data quality and validation rules;
- metadata requirements;
- lineage and traceability;
- access and security requirements;
- retention and lifecycle requirements; and
- reporting, analytics, and downstream-consumption requirements.
- Work with engineering teams to identify incomplete, unavailable, conflicting, or poor-quality data that could prevent successful implementation.
- Support solutions using Databricks or comparable modern data platforms, data warehouses/lakehouses, relational databases, APIs, and enterprise analytics environments.
AI/ML-Enabled Solutions
- Support discovery and requirements development for AI/ML-enabled applications and business processes.
- Translate business use cases into specific requirements for AI-enabled capabilities rather than simply identifying that "AI" should be used.
- Define requirements associated with:
- inputs and authoritative data;
- expected outputs;
- accuracy and quality expectations;
- human review and approval;
- exception handling;
- explainability and traceability;
- access and security;
- auditability;
- operational workflow integration; and
- acceptance and validation of AI-generated results.
- Work with technical teams and stakeholders to determine where AI/ML can appropriately improve a business process and where deterministic automation, traditional application logic, or human decision-making is more appropriate.
- Help establish testable acceptance criteria for AI-enabled functionality whose results may not behave like traditional deterministic software.
Product and Agile Delivery
- Translate discovered requirements and solution designs into development-ready epics, features, user stories, acceptance criteria, use cases, and supporting specifications.
- Develop acceptance criteria that are clear, measurable, testable, and tied to the intended business outcome.
- Work alongside Product Owners to create, refine, sequence, and prioritize the product backlog.
- Participate actively in backlog refinement, sprint planning, sprint reviews, retrospectives, and other Agile/SAFe ceremonies.
- Identify stories that are too large, ambiguous, technically incomplete, or dependent on unresolved data or architecture decisions and drive those issues to resolution before development.
- Maintain requirements traceability from mission/business objectives through epics, features, stories, development, testing, UAT, and delivered capabilities.
- Support Product Owners with refinement and product decision-making without requiring the analyst to be the formal Product Owner.
Validation and Acceptance
- Develop comprehensive UAT strategies, test scenarios, test cases, and expected results based on documented requirements and acceptance criteria.
- Work with developers, testers, and stakeholders to determine whether defects arise from implementation, requirements, data, configuration, or changed user expectations.
- Validate that delivered functionality satisfies both the documented requirement and the underlying mission/business need.
- Manage requirement clarifications and changes throughout the delivery lifecycle.
Stakeholder and Technical Communication
- Explain complex business requirements to engineers and technical concepts to nontechnical government stakeholders.
- Communicate requirements using diagrams, models, data definitions, examples, prototypes, specifications, and user stories rather than relying solely on meeting notes or narrative documents.
- Facilitate discussions between stakeholders who may have conflicting objectives or different understandings of the problem.
- Prepare findings, recommendations, decision materials, technical/business briefings, SOPs, user guides, and other documentation for government stakeholders and program leaders