01
Risk and product engineering
Policy engines, pre-trade checks, sizing, permissions, audit trails, and a user experience making governance usable.
MADO / WORK WITH US
We do not add people to make the team look larger. We add leverage that makes the company faster, the product stronger, or trust deeper.
MADO is in a focused founding stage. MADO Risk is the first commercial product, and the five arms define the capabilities we will build around it. There is no broad hiring wave today; there are high-value problems looking for exceptional owners.
WHERE CAN YOU CREATE LEVERAGE?
Five technical domains — plus two paths separating a good product from a global company.
02
Market data and execution
Tick-data quality, streaming infrastructure, microstructure, simulation, slippage measurement, and reliable broker integrations.
03
Intelligence and quantitative research
Anomaly detection, uncertainty, explainability, rigorous testing, and controls against leakage and bias.
04
Security, reliability, and compliance
Isolation, access control, observability, incident response, privacy, and retention fit for a scaling financial product.
05
Capital and analytics
Risk budgets, allocation, attribution, stress scenarios, and reporting that moves decisions from opinion to accountability.
06
Distribution, sales, and partnerships
B2B and B2C sales, prop and broker channels, repeatable offers, and partnerships compressing go-to-market cost.
07
Design and communication
Calm financial interfaces, clear product narrative, content explaining value without noise, and a bilingual experience ready for multiple markets.
CURRENT REALITY
We build the team around constraints, not the org chart we imagine five years from now.
The company priority is making MADO Risk a product customers buy, activate, and retain. Roles closest to that outcome come first. The other arms attract early researchers, partners, and advisors before they require full teams.
01
A role accelerating revenue, activation, or retention.
02
A role reducing material security or operating risk.
03
A role opening an integration or distribution channel we cannot open alone.
04
A role turning a research hypothesis into repeatable evidence.
HOW WE WORK
Outputs matter more than presence. Evidence matters more than confidence.
01
Begin with the decision
Define who will make a better decision because of your work, not the technology name you plan to use.
02
Shrink scope, increase clarity
We prefer a small experiment with a metric over a large project nobody can define.
03
Write boundaries before success
We know what a product will not do before advertising what it does.
04
Expose error early
There is no place for hiding model failure or system defects until they become expensive.
05
Build for Arabic and English
The company begins in the region but is not architected to remain confined to it.
06
Own the outcome
The task is not delivering a file or code. It is moving a metric, removing a risk, or opening a capability.
WHAT SHOULD YOU SEND?
Do not begin with the résumé. Begin with the strongest evidence that you can remove a real constraint.
Send a link or document showing: what was the problem, what did you build, sell, or analyze, what were the constraints, what changed, and what would you do differently now? Do not send passwords, client secrets, or sensitive data.
- 01A repository, product, or case study.
- 02A technical memo or repeatable research result.
- 03Distribution or sales numbers with context.
- 04A security review or system design you completed.
- 05A specific proposal for a constraint inside MADO you can remove.
No suitable role is posted? Send a contribution that cannot be ignored.
The best message is not: I want to work with you. It is: I saw this constraint, here is my evidence, and here is the smallest experiment proving I can remove it.