Turn business intent into requirements that engineers can build and QA can test. This is hands‑on specification engineering. You report to the CEO and work with the CTO, QA, engineers and business counterparts. You own editorial precision. Changes to approved business meaning, scope or architecture go to the relevant business authority, the CEO or the CTO.
This is not a product‑owner or roadmap role. You will not own the roadmap, pricing or revenue targets. You will own the requirements: what the system must do, where each rule came from, who approved it, and how QA can prove it. Your first assignment is a fund management platform.
If you are a senior Business Analyst, System Analyst, Requirements Engineer or technical Product Owner, and you value precision more than slide decks, this role is for you.
What you will do
Discovery and user understanding
- Plan and run stakeholder interviews, workflow discovery and user research to find goals, constraints, exceptions and unmet needs.
- Turn findings into clear problem statements, user journeys and priorities. Validate proposed flows and usability with intended users before they become build commitments.
Requirements and decisions
- Write versioned requirements with an ID, source evidence, approval record, explicit dependencies and acceptance criteria that QA can turn into positive, negative and boundary cases.
- Turn ambiguity or contradiction into a decision request: the issue, the evidence, the decision owner, your proposed default and the requested action.
- Keep a decision ledger, so that no ruling stays informal. Keep scope, open questions and approved decisions visible to engineering and business stakeholders.
Product design and delivery alignment
- Shape user flows, interaction requirements and usability acceptance criteria with engineering and business counterparts.
- Keep module boundaries and traceability current after approved semantic changes. Make the implementation impact visible before a boundary changes.
QA and engineering handoff
- Give QA the exact approved revision, acceptance basis and dependencies before the affected build starts.
- Resolve or elevate the material testability gaps that QA returns. The affected build stays blocked until the gap is resolved or its approval owner excludes that scope.
AI-enabled practice
- Use AI to draft and reconcile specifications. Check every AI‑drafted clause against its source, and document your method.
- Improve the tools and templates that keep requirements, decisions and traceability easy to maintain, such as ID issuance, traceability and contradiction checks.
What you need
- 5+ years of business analysis, specification engineering or product experience, delivering enterprise transactional or approval‑driven systems from discovery through release.
- Strong user‑research skills: you plan interviews and workflow observations, separate evidence from assumptions, and turn findings into user journeys and requirements.
- Practical UX understanding: clear navigation, interaction states, error recovery and accessibility. You can assess wireframes or prototypes and validate usability with intended users.
- Precise requirement writing and decision discipline. QA can test your acceptance criteria without asking what you meant.
- You read data models, API contracts and tests with engineers, and you reason about delivery trade‑offs.
- Clear written and spoken Bahasa Indonesia and English, including facilitation of stakeholder reviews and decisions.
- Practical AI proficiency, with source verification and a documented method.
Nice to have
- 7+ years of relevant experience.
- Financial‑industry experience: fund management, custody, securities settlement, banking or payments.
- B2B delivery with a client‑side sign‑off chain.
- You have shipped a product built on a language model.