Technical Business Analyst

The Technical Business Analyst is the bridge between ambiguous business intent and deterministic, buildable specifications for AvantoDev's data and agentic projects. Our platform turns Standard Operating Procedures into executable agent logic ("Code = SOP"), and that translation starts with you. You deconstruct messy business processes — quote-to-install workflows, document-processing pipelines, master-data validation rules — into precise requirements that data engineers and AI engineers can implement and test.

This is not a "write user stories in Jira" role. You will own Spec-Driven Development (SDD) artifacts end-to-end: EARS-formatted requirements, Gherkin acceptance scenarios that define "Definition of Done" for probabilistic agents, data dictionaries and schema specifications, source-to-target mappings, and the business-rule catalogs that become guardrails. You sit at the center of high-entropy data work — defining what "correct" means for a PO, an ACK, an invoice, or a tenant-specific discount rule — and you make sure the rest of the team builds the right thing.

You'll work closely with the Head PM (Carlos Cedeño), the Head Product Manager (Rey Ramirez), data and AI engineers, and stakeholders across the business, translating in both directions: business → spec, and technical complexity → stakeholder-friendly explanation.

What You'll Own

Requirements & Spec-Driven Development

• Deconstruct complex business processes and user stories into EARS-formatted requirements (Easy Approach to Requirements Syntax) that are unambiguous, testable, and traceable.
• Author Gherkin scenarios (Given/When/Then) that define the "Definition of Done" — including for non-deterministic agent behavior, where you specify the logic path, not just the output.
• Maintain the Master Contextual Package (MCP) traceability: every requirement maps to a business need and to the agent/pipeline logic that implements it.

Data Specification & Analysis

• Build and maintain data dictionaries, schema specifications, and source-to-target mappings for the Bronze → Silver → Gold pipeline and the PostgreSQL schema registry.
• Define field-level validation rules, tolerances, and alias dictionaries (e.g., "Qty Shipped" → quantity) that drive the Schema Matching and validation MCP servers.
• Profile source data, quantify data-quality issues, and write the acceptance criteria for data-quality gates and cross-field validation (e.g., line items sum to total).

Business-Rule & Guardrail Catalogs

• Translate business policy into structured, machine-consumable business-rule definitions (discount limits, tax rules, workflow steps) and the guardrail specs that enforce them ("Block discount > 20%").
• Maintain the knowledge-pack catalogs (business rules, guardrails, knowledge base) as living, versioned specifications.

Process & Workflow Modeling

• Map current-state and future-state quote-to-install and document-processing workflows, identifying automation opportunities, HITL (Human-in-the-Loop) decision points, and exceptionpaths.
• Define confidence-based routing rules with stakeholders (≥90% auto-approve, 60–89% review, <60% Expert-in-the-Loop) and the SLAs around them.

Stakeholder Translation & Acceptance

• Run requirements workshops and translate technical complexity (why an automation is risky, costly, or non-deterministic) into language non-technical stakeholders canact on.
• Own UAT planning and acceptance: build test cases from the Gherkin specs, coordinate sign-off, and verify delivered work matches the spec.
• Produce operational reporting specs — defining the metrics (throughput, accuracy, cost-per-document, net savings) and dashboards the businessneeds.

What You'll Do Day-to-Day

Analysis & Specification

• Run discovery sessions with business stakeholders and engineers; produce EARS requirements, Gherkin acceptance criteria, and datamappings.
• Write SQL queries to profile and validate data, quantify edge cases, and back requirements with evidence (not assumptions).
• Maintain the requirements backlog and traceability matrix in Jira (project SDB) and Notion.

Cross-Functional Coordination

• Partner with Data Engineers on schema/registry specs and source-to-target mappings.
• Partner with AI Engineers to define agent behavior, tool contracts, and the "Definition of Done" for probabilistic outputs.
• Work with the PM team to scope sprints, estimate, and sequence delivery.

Quality & Acceptance

• Build and execute UAT test cases from the specs; document defects with clear reproduction steps.
• Validate that delivered pipelines and agents meet acceptance criteria before release.
• Maintain decision logs and ADR-style records of requirement changes.

Minimum Qualifications

• 5+ years as a Business Analyst / Technical BA, with 3+ years on data-intensive projects (data platforms, integrations, analytics, or document/IDP processing).
• Strong SQL — able to independently profile data, validate hypotheses, and write moderately complex queries against PostgreSQL or similar.
• Demonstrated requirements engineering skill — user-story decomposition, acceptance criteria, and at least one formal technique (EARS, BDD/Gherkin, use cases, or equivalent).
• Data modeling literacy — able to read and contribute to data dictionaries, schema specs, ER diagrams, and source-to-target mappings. Understands normalized vs. denormalized models conceptually.
• Process modeling — BPMN or equivalent; mapping current/future-state workflows and identifying automation and exception paths.
• Familiarity with the modern data & AI stack — understands what RAG, vector databases, APIs/microservices, and LLM-based automation are and where they fit (you don't have to build them, but you must spec for them).
• Tooling — Jira, Confluence/Notion, and diagramming tools; comfortable maintaining traceability matrices and living documentation.
• English proficiency: B2+ required (C1 preferred). You'll facilitate workshops, write specs, and translate between business and technical audiences daily.

Nice to Have

• Experience specifying agentic / LLM-driven systems — defining "Definition of Done" for non-deterministic outputs and writing guardrail/policy requirements.
• Hands-on with document/IDP projects — POs, ACKs, Invoices, schema/alias matching, confidence scoring, and HITL review workflows.
• Familiarity with Spec-Driven Development (SDD) and the Model Context Protoc
• ol (MCP) concept.
• Experience writing YAML/JSON business-rule definitions or configuration-as-spec.
• Light scripting (Python) for data profiling and analysis.
• BI/reporting spec experience (QuickSight, Power BI, Metabase).
• Background in commercial furniture, logistics, distribution, or manufacturing operations.
• Domain exposure to quote-to-install / order management processes.