An application made for this job — a tailored resume and cover letter that speak straight to the posting.
Kavaliro is seeking a Technical Business Analyst to bridge business stakeholders and software development, documenting requirements, user stories, and acceptance criteria with traceability from scope to release. The role supports process mapping, data integration, and BI reporting across multiple departments, ensuring quality and adoption of new solutions.
Responsibilities include interviewing stakeholders, creating functional specs, validating data integrity, and coordinating testing and
The Technical Business Analyst role is critical to properly defining requirements and connecting the technical aspects between business stakeholders and the software development team. The role documents new ideas to define product requirements in documented, testable, and traceable requirements — including process maps, functional specifications, user stories, acceptance criteria, data mappings, and integration definitions, so development work begins with defined scope and measurable success criteria. This position will assist with setting product vision, roadmap priority, or architectural standards, and will assist in writing, reviewing, merging, or deploying production code. Additionally, the TBA will serve as a technical resource among the operators and technicians supporting basic IT needs from computers, printers, network and basic communication applications to further support and manage communication with our IT managed service provider (I.e. IT VOICE). The Technical Business Analyst is accountable for requirement quality, documentation accuracy, data integrity analysis, user acceptance validation, and adoption support across Sales, Dispatch, Operations, Warehouse, Accounting, and Customer Service. Pay: $60,000.00 - $70,000.00 /annually
Conduct interviews, job shadowing, and working sessions with front-line and administrative stakeholders to capture current-state workflows, business rules, and pain points. Author (document) business requirements documents, functional specifications, user stories, and acceptance criteria that satisfy the agreed Definition of Ready. Maintain a requirements traceability matrix linking each business need to its user story, test case, and release. Record assumptions, constraints, dependencies, and out-of-scope items in writing, and obtain documented stakeholder approval before development begins. Escalate conflicting, ambiguous, or non-compliant requirements to leadership rather than resolving scope unilaterally.
Produce current-state and future-state process maps, swim-lane diagrams, and data flow diagrams for intake, estimating, dispatch, receiving, inventory, installation, billing, and claims. Perform gap analysis between written SOPs and actual system behavior; quantify manual effort, rework, error rates, and cycle time. Identify regulatory, contractual, insurance, and records-retention obligations affecting a workflow and document them as explicit, testable requirements. Recommend automation, validation rules, and exception handling supported by effort, risk, and benefit analysis.
Analyze interfaces between Cervus 2.0 and CRM, accounting, dispatch, telematics, and third-party partner systems; document field-level data mappings, transformation rules, and error handling. Review APIs, file transfers, and interface specifications for completeness; flag data-quality, duplication, and reconciliation risks before implementation. Define role-based access, permission, and data-retention requirements, including handling of customer, employee, and payment-adjacent personal information consistent with Company policy and applicable privacy law. Write and run queries to validate data integrity, migration accuracy, and post-release system behavior.
Gather reporting requirements and specify dashboards, metric definitions, calculation logic, data sources, and refresh frequency. Establish one documented definition for each shared metric to prevent conflicting figures across departments. Perform ad hoc analysis of operational and financial data to size problems before build and to measure realized benefit after release.
Write test cases and user acceptance scripts from documented acceptance criteria; coordinate business-user testing schedules, environments, and test data. Log, reproduce, and track defects to closure with QA, and verify fixes at the business-requirement level. Confirm release readiness, including completed acceptance criteria, documented sign-off, training materials, back-out considerations, and stakeholder communication. Conduct post-implementation reviews and document results against the original business case.
Produce user guides, quick-reference materials, release notes, and configuration documentation in plain language. Deliver end-user training and on-site support during rollouts; capture adoption barriers and return them to leadership as prioritized input. Facilitate requirement reviews, demonstrations, and cross-departmental working sessions across markets.
Kavaliro provides Equal Employment Opportunities to all employees and applicants. All qualified applicants will receive consideration for employment without regard to race, color, religion, age, sex, national origin, disability status, genetics, protected veteran status, sexual orientation, gender identity or expression, or any other characteristic protected by federal, state, or local laws. Kavaliro is committed to the full inclusion of all qualified individuals. In keeping with our commitment, Kavaliro will take the steps to assure that people with disabilities are provided reasonable accommodations. Accordingly, if reasonable accommodation is required to fully participate in the job application or interview process, to perform the essential functions of the position, and/or to receive all other benefits and privileges of employment, please respond to this posting to connect with a company representative.