AOS
The digital platform of SRM’s employee association: a member portal and a back-office, two connected apps on one backend.
- role
- tech lead · product, architecture, security, delivery
- timeline
- 2026
- delivered
- through UDAT
- stack
- React · TypeScript · Bun · Oracle · Redis
the challenge
AOS is the employee association of SRM. Members asked for its benefits on paper, then waited, with no way to see where their request stood.
Behind each request, several departments sign off in turn before anything is paid. Money and members’ personal data move through every step, so each action has to be checked, traced and limited to the people whose role allows it.
what i built
Two connected apps on one shared backend: MyAOS, where members file and follow their requests, and a back-office where staff run every case file from filing to payment.
Members on one side, staff on the other
Two apps with separate accounts and permissions, on one shared backend. A request filed by a member becomes a real case for staff without anyone retyping it.
From a phone to a payment, no paper chase
Members file online with their documents, eligibility is checked up front, and they follow the request live up to payment. Partner forms are bilingual, Arabic and Latin.
Admins design the approval circuits
Each department signs off in turn, with deadlines in business hours. Circuits are built without code, versioned and simulated before they go live.
One workspace to run the association
Ten back-office modules: case files, member requests, the member registry, budget, cash registers with monthly closing, analytics, the circuit designer, reference data, users and roles, and the audit journal.
Members' money and data, built like it
Email one-time-code login on both apps, four layers of access checks on every action, personal data masked in logs and an append-only audit journal.
results
next
Moving a paper process with sign-offs and money online?