Kitestring Technical Services is seeking a Senior Business Analyst to serve as the primary requirements owner for the Elera Fuel Module. The role involves translating discovery findings into structured specifications, collaborating with architects and developers, and producing comprehensive requirements and documentation for various fuel capability areas.
Responsibilities:
- Author functional requirements for all in-scope Elera Fuel features across all 13 capability areas
- Write development-ready user stories and use case narratives for all primary transaction flows: pre-pay, post-pay, fleet, drive-off, refund, pump test, manual fuel sale, and more
- Define data models for each service domain (fuel grades, transactions, pricing, loyalty, inventory, etc.)
- Document service boundary definitions and microservice interaction contracts (APIs, events, message formats)
- Produce integration specifications for Allied ANDI protocol, payment processor interface, loyalty engine, car wash controller, and third-party monitoring systems
- Capture non-functional requirements: PCI DSS compliance architecture, offline/degraded mode behavior, performance expectations, auditability
- Develop POS UI screen-level requirements for all in-scope cashier and admin UI flows
- Document out-of-scope items with clear, auditable rationale
- Collaborate with the Lead Architect (Vicente) to ensure requirements traceability into ARB submission artifacts
- Contribute to the ARB Submission Package: fuel service architecture blueprint and supporting documentation
- Assist in drafting the Technology & Integration Decisions Log and Development Readiness Assessment
- Support iterative ARB review cycles with Toshiba architects, tracking feedback and incorporating changes
- Attend and facilitate clarification sessions with Toshiba stakeholders (Morgan, Joe Fraser, Paul Lindsay, David Zhou, and relevant SMEs)
- Manage requirements review cycles with Toshiba, targeting 5-business-day feedback windows per deliverable batch
- Maintain traceability between Toshiba’s Feature List, discovery outputs, and finalized requirements
- Flag scope change requests and support change order documentation as needed
- Own Elera Fuel Module Requirements Specification — full document, all 13 capability areas
- User Story Backlog — all in-scope features expressed as development-ready user stories
- Data Model Reference — entity definitions, relationships, and domain ownership
- API Contract Specifications — interface definitions for all service boundaries
- Integration Requirements Documents: ANDI/Allied, Payment Processor, Loyalty Engine, Car Wash Controller
- POS UI Requirements Summary — screen-level requirements for all cashier and admin UI flows
- Non-Functional Requirements Document — security, compliance, performance, resilience
Requirements:
- Hands-on experience with fuel/forecourt systems is required — candidates without this background will not be considered
- Demonstrated experience with at least one of: Allied/ANDI protocol, Gilbarco, Wayne, or equivalent fuel controller systems
- Working knowledge of pump transaction lifecycle: pre-authorization, hold management, final capture, reversal, and settlement
- Familiarity with pre-pay and post-pay fuel transaction flows at the POS level
- Understanding of fuel tax handling, wet stock reconciliation, and end-of-day fuel reporting
- Experience with OPT (outdoor payment terminal) transaction flows and card processing in the forecourt context
- 5+ years of BA experience on enterprise software or platform delivery engagements
- Proven ability to write functional requirements and user stories at a level of detail sufficient for developer consumption
- Experience producing API contract specifications or service boundary definitions
- Strong data modeling skills — ability to define entities, relationships, and domain ownership
- Comfortable working in a microservices / event-driven architecture context
- Ability to produce non-functional requirements across security, compliance, and performance dimensions
- Working knowledge of PCI DSS compliance requirements in a payments context
- Familiarity with payment authorization flows: pre-auth, hold modification, final capture, void, and reversal
- Experience with credit/debit, mobile wallet, fleet card, and cash tender types
- Demonstrated ability to lead requirements review sessions with technical and non-technical stakeholders
- Experience managing iterative review cycles and incorporating structured feedback into living documents
- Strong written communication — your deliverables will be consumed directly by senior architects and development teams
- Comfortable working in a lean, senior team without extensive coordination overhead