Choosing your trackاختيار المسار

There are five career tracks in FinTech: engineering, data, operations, compliance and product. They are not departments on a chart. They are five different questions five people ask about the same incident.

A fair question first: how do I pick a track in a field I have not entered yet?

The objection is reasonable, because choosing before knowing looks backwards. But what you are picking now is not a job or a university major. You are picking the chair you sit in while you read this roadmap. You can change it any week and lose nothing.

Five people and one incident

The fastest way to see the five tracks is to watch them in a single moment, rather than reading five definitions side by side.

Picture a shop in Riyadh on a Thursday night. A customer taps a mada card and the screen says "transaction declined". They try again and it declines again. A queue is forming behind them, and the shop owner picks up the phone.

At the FinTech company running that terminal, five people hear the same news at the same moment. Each one asks a completely different question:

• Did the decline come from our system or from the card's issuing bank?
• How many other shops were hit in the last hour, or is it just this one?
• Who do we call at the acquirer right now, and when do we tell the other shops?
• Does this outage cross the threshold that requires reporting to SAMA?
• Why does the screen only say "declined" and leave the customer standing there with no idea what to do?

Those five questions are the five tracks. They are not levels of one profession, and none of them ranks above the others. They are five angles on the same incident, and each angle takes a different skill and draws people from a different background.

The first question: engineering

The person asking the first question is an engineer. Their work is building systems where money moves without going missing or happening twice. Mistakes here cost money directly: a payment sent twice, a balance that disagrees with the ledger, an outage during settlement.

People usually arrive here from software, and the market titles are backend engineer and payments engineer. In this roadmap you will read about ledgers, idempotency keys and message queues.

You can test this angle today with one question: if step three of any operation fails, what happens to the money? If you find that question enjoyable rather than exhausting, that tells you something.

The second question: data

Asking how many shops were affected is a data question. This track measures fraud, credit and behaviour, and doubts its own numbers before anyone else does.

Take a case that repeats often. Approval rates on mada payments at an online shop went up this month, because the team switched off a fraud rule that was declining a lot of traffic. The number genuinely improved, and the loss shows up two months later as chargebacks. The data person's job is to refuse to present that improvement without naming what changed in the rules.

People come into this track from statistics, mathematics or accounting, and the titles are data analyst, fraud analyst and data scientist.

The third question: operations and partnerships

The person asking who to call is the least visible of the five in headlines and the most decisive in whether the service survives. They open the ticket with the acquirer, chase the partner bank until the settlement file arrives on time, and review the fee schedule with finance.

This work runs on persistence, organisation, and following one thread through weeks of dull detail. Without it, engineering looks fine on paper while shops go unpaid.

Many people enter it from customer service or from bank jobs, and the titles are operations specialist and partnerships manager. It is the widest door in for anyone without a technical background.

The fourth question: compliance and risk

The reporting question is a compliance question. This track sets what is allowed, what must be proven before launch, and what stops the product when something breaks.

Its day is reading regulatory text and turning it into an executable step. It reads SAMA circulars, works out when a payments licence is enough and when a partner bank is required, and designs the know-your-customer and anti-money-laundering procedures.

The job is not blocking innovation. It is making innovation defensible in front of a regulator or an auditor. Good compliance shortens launch arguments instead of stretching them, because it draws the line before the team builds on sand.

People arrive from law, sharia, audit or from inside the banks, and the titles are compliance officer and money laundering reporting officer. It demands precision in language and patience with detail far more than it demands a technical background.

The fifth question: product

The one asking about the customer stranded at the screen works in product. They decide what gets built, for whom and why now, living between customer desire, licence limits and engineering capacity.

Take a "pay later" button on a shop screen. The product person asks whether the button lifts completed purchases enough to justify the fees the partner bank charges and the friction that Nafath verification adds. The answer is not a marketing slogan. It is a measurement on a real sample, and an honest kill if the effect is weak.

People enter from marketing, design, analysis, or any job where they dealt with real customers. The titles are product manager and UX designer.

Which one is actually closest to you?

Three questions are enough, and they take under ten minutes.

First: which of those five questions stopped you as you read the scene above? An honest answer here beats any personality test.

Second: which skill do you already have? If you write code, engineering is nearest. If you write and proofread, compliance is nearest. If you finish what you start and chase detail, operations is nearest.

Third: where are people scarcest in your market? Do not guess this one, because you can measure it yourself. Open one job site, search the five titles above restricted to your city, and count the listings. You will get a clearer picture than any article about "the jobs of the future".

If you are torn between two close tracks, pick the one nearest to this month's work rather than a distant dream. Reading the roadmap while you fix a real signup flow goes deeper than reading while you postpone the choice until you "have time".

What changes once you pick

Once you choose, write one sentence on paper: "I read this roadmap as a …". Reread it before every new phase.

The sentence turns every topic into an answer to a question you are already carrying. If you chose product, ask at every topic: where does the customer get confused? If you chose compliance, ask: what must be proven to SAMA or the partner bank? If you chose engineering, ask: where can money be lost or duplicated? If you chose data, ask: which number here can lie? If you chose operations, ask: who calls whom when this link breaks at two in the morning?

If a topic falls outside your track, read it for context and do not stop to master it. Breadth comes after you hold one angle steady, not before.

Do not wait for a job title that matches letter for letter. Many small FinTech teams mix engineering with operations, or mix product decisions with compliance. Nobody in this industry knows all of it, including the people who sound like they do in interviews.