Business Analyst

Goodman Masson Oman; Muscat; On-site; OMR 12,000 - 24,000; Full time

Job summary

Goodman Masson Oman is establishing a hands‑on Business Analyst role in Muscat to support a greenfield financial markets infrastructure project. The BA will own documentation standards, design documents, and runbooks, while leveraging Claude as a productivity tool and ensuring human accountability for accuracy and domain interpretation.

The role requires at least three years in a documentation-heavy or process-analyst role, with strong English, process-mapping skills, and the ability to

Qualifications

• Three+ years in a business analyst or documentation-heavy role, ideally in financial services or regulated industry.
• Strong process mapping and documentation skills with ability to translate verbal discussion into structured output.
• Greenfield opportunity requiring ability to whiteboard from scratch.
• Fluent in English and fast learner with tech savviness in AI tools.

Responsibilities

• Produce, structure, and maintain programme delivery documentation (process maps, workflows, design docs, logs, runbooks, training materials).
• Drive consistency of documentation across the programme (templates, terminology, structure, version control).
• Operate as a skilled Claude user: prompt effectively, iterate, refine outputs as first drafts.
• Identify opportunities to use AI to compress effort (e.g., generate test plans from design docs or training material from runbooks).
• Map target-state processes across the operating model with Product Owner and other business owners.
• Maintain RAID log; support Project Manager with plan maintenance, dependency tracking, status reporting.
• Generate test artefacts from upstream design docs: test plans, test cases, test data requirements, traceability matrices.
• Absorb domain knowledge on CSD, settlement, registry, corporate actions, and regulator requirements.

Skills

Process mapping

Documentation

Microsoft Office

Visio

Lucidchart

Miro

English fluency

Claude experience

AI adoption

Tools

Visio

Lucidchart

Miro

Claude

Job description

A new financial markets infrastructure venture is being established in Oman, backed by prominent institutional investors and operating under an international common law framework. The platform is being built from scratch, to go-live in 2027, and is designed to operate as a regulated financial market infrastructure from day one.

We are hiring two Business Analysts to sit at the engine room of the programme. A regulated financial market infrastructure being built from a blank sheet generates an enormous volume of design, process, and operational documentation that needs to be produced, standardised, kept current, and used to drive downstream artefacts including test plans, training materials, runbooks, and regulatory submissions.

This programme operates as a highly AI‑leveraged programme office, with Claude adopted as the standard productivity tool. The Business Analyst is the human who knows the business, knows the documentation standards, prompts Claude well, and rigorously checks and refines its output. The principle is clear: AI is the servant, never the master. Human accountability for accuracy, judgement, and domain interpretation is non‑negotiable.

What the role covers

• Producing, structuring, and maintaining the programme's delivery documentation: process maps, workflow diagrams, design documents, decision logs, operational procedures, runbook drafts, training materials, and papers
• Driving consistency of documentation across the programme: common templates, terminology, structure, and version control
• Operating as a skilled user of Claude: prompting effectively, iterating, refining, and treating AI output as a first draft to be improved, never as a finished product
• Identifying opportunities to use AI to compress effort across the programme, for example generating test plans from design documents or training material from runbooks
• Mapping target‑state processes across the operating model in collaboration with the Product Owner, Operations Lead, Head of Operations Control, and other business owners. There is no as is or current state as this is greenfield
• Maintaining the programme RAID log; supporting the Project Manager on plan maintenance, dependency tracking, and status reporting
• Generating test artefacts from upstream design documentation: test plans, test cases, test data requirements, and traceability matrices
• Absorbing domain knowledge actively: how a CSD works, how settlement happens, how registry is maintained, how corporate actions flow, and what the regulator requires

Who we are looking for

At least three years in a business analyst, process analyst, or documentation‑heavy role, ideally in financial services or another regulated industry. Strong process mapping and documentation skills: able to translate verbal discussion into clear, structured written output. This is a greenfield opportunity so you must be prepared to whiteboard from scratch

Fast learner: able to absorb new domain knowledge quickly and use it accurately. High proficiency in Microsoft Office and standard process‑mapping tools (Visio, Lucidchart, Miro, or equivalent). Fluent in English.

Demonstrable, hands‑on fluency with Claude or equivalent large language models as a productivity multiplier in real work is required. Candidates should be able to describe specific examples. Candidates without prior Claude experience but with strong evidence of fast AI adoption will be considered. AI is used as a tool to aid the human here not replace so you must be using to amplify your skills

Exposure to financial market infrastructure or capital markets and post‑trade processes is an advantage. So is experience producing documentation subject to regulatory inspection or external audit.

What this is

This is a hands‑on, productive role for fast learners who want to operate at the frontier of how a modern programme office works. The post‑holder will not be a passive note‑taker. They will be expected to absorb domain knowledge quickly, drive their own work, and continuously raise the standard and consistency of programme documentation. If that is the way you work and you have the AI fluency and documentation discipline to back it up, this is worth a conversation.