Technical Business Analyst (Compliance and Integrations Platform)

Technical Business Analyst (Remote – Sri Lanka)

Full-Time | Remote | Sri Lanka-based candidates only

Salary: LKR ~125,000 – 250,000 per month (approx; fixed in LKR at start date, no monthly FX adjustments).

Role Overview

We are building a compliance and integrations platform that connects eCommerce systems (such as Shopify, Amazon, and eBay) to internal reporting and downstream accounting and compliance tools.

We are hiring a Technical Business Analyst (TBA) to turn business and compliance requirements into clear, structured, execution-ready documentation that engineering teams can build from and test against.

This role supports delivery end-to-end, from early analysis through UAT and production readiness.

It does not own architecture, engineering decisions, or delivery management.

This is a hands-on, execution-focused role, suited to someone who enjoys clarity, documentation, and working within a disciplined delivery model.

The Team You Will Work With

You will work as part of a small, structured team:

• Business owners and operators providing non-technical requirements and compliance logic
• A Full-Stack Developer responsible for implementation
• A Quality Gate Advisor (part-time consultant) reviewing work for quality, security, and reliability
• You, as the Technical Business Analyst, responsible for documentation clarity and traceability

Responsibilities are intentionally separated to avoid role confusion.

What You Will Do (Day-to-Day)

1. Requirements gathering & analysis

• Gather and clarify requirements from business owners, operators, and compliance inputs
• Break down high-level needs into clear, structured requirements, including:
• scope and non-scope
• assumptions and constraints
• functional behaviour
• key edge cases and exceptions
• Analyse existing systems, processes, and data flows to identify dependencies and risks
• Translate business requirements into technical-ready specifications developers can execute without guesswork

2. Documentation & artefact creation (core responsibility)

Produce and maintain clear, structured artefacts such as:

• process maps and user flows
• logical system and data flow diagrams
• user stories and acceptance criteria
• data models and mapping tables (source → internal → destination)
• conceptual interface definitions (API-level)
• assumptions and decision logs

Documentation must be concise, unambiguous, and aligned with what is actually being built.

3. Integration & data analysis

• Analyse and document integrations between systems, including APIs, data synchronisation, and reconciliation logic
• Define expected data behaviour, reconciliation rules, and known failure scenarios
• Support debugging and issue analysis by tracing data flows and documenting findings clearly
• Engineering owns fixes; you own analysis clarity

4. Functional prototype maintenance

• Maintain a functional, clickable prototype (e.g. Figma) that reflects:
• onboarding and setup flows
• integration connection screens
• dashboards and reporting views
• reconciliation and exception handling flows
• Ensure prototypes show correct system states (success, error, empty, disconnected)
• Use prototypes to validate understanding and reduce ambiguity

This is a clarity tool, not a visual design role.

5. Delivery support & collaboration

• Work closely with the Full-Stack Developer and Quality Gate Advisor
• Participate in structured discovery sessions or walkthroughs when required
• Provide analytical input to support solution discussions and risk identification

You support delivery but do not manage delivery or make final solution decisions.

6. UAT preparation & support

• Create and maintain UAT test cases aligned to requirements and acceptance criteria
• Prepare UAT packs for features and integrations
• Support UAT execution by guiding scenarios, logging defects, and validating fixes
• Maintain a simple regression checklist for critical workflows

7. Reporting & visibility (non-negotiable)

Daily (end-of-day):

• Short written update covering:
• what was worked on
• what was completed (with links)
• open questions or blockers
• next steps

Weekly:

• Summary of documentation packs completed
• Highlight open decisions or risks
• Confirm UAT readiness status

Written communication is the system of record.

What This Role Is NOT

This role does not:

• own system architecture
• write production code
• manage developers
• act as a product owner or project manager
• make final engineering or solution decisions

Required Experience

• 3–6 years of full-time experience as a Technical Business Analyst (or equivalent Business Analyst / Systems Analyst role) on software delivery projects
• Proven ability to produce execution-ready documentation developers can build from (user stories + acceptance criteria, flows, mapping tables)
• Comfortable with API-based systems, integrations, and data flows (sync logic, error cases, basic reconciliation concepts)
• Strong analytical thinking: able to break down workflows, data, and edge cases methodically
• Strong written English (daily written updates are mandatory); spoken English sufficient for calls

Working Requirements

• Based in Sri Lanka
• Reliable personal laptop or desktop suitable for full-time remote work
• Stable internet suitable for regular video calls and screen sharing
• Comfortable working fully remote with structured written communication in English

How We Work

• Clarity before code
• Documentation before development
• Quality gated reviews
• Decisions recorded, not implied

Predictability and correctness matter more than speed.

Final Note

This role has a clearly defined scope and salary band. If you enjoy analysis, documentation, and supporting real systems within a structured team, this role will suit you well.