Between banking systems and offline mobile

At Arolitec I build banking web applications end to end. I set the application architecture — frontend, backend, database — and model the PostgreSQL relational schema before any business logic gets written. Then come the REST and GraphQL APIs in Node.js and NestJS, wired into internal applications and third-party services, and the business and back-office interfaces in Angular, React and Remix, mapped to how the operational processes actually run. In a bank the question is never only “does it work”, it is “who is allowed to do what”: I design and implement the user profiles and role-based access control that govern every screen and every endpoint.

Alongside that, I publish my own apps on Google Play under the name Codeur d'Ivoire: Background Eraser, Currency Converter Offline and Simpli Code, all built with React Native, Expo and TypeScript. All three are offline-first, and that is an engineering decision rather than a preference: here, mobile data is prepaid, coverage changes from one neighbourhood to the next, and Mobile Money is everyday infrastructure rather than a payment option. So I treated offline as a constraint to solve rather than route around: the AI cutout runs entirely on the device, the converter keeps more than 170 currencies in local storage and syncs later when the signal returns, and the USSD manager chains the steps of Orange, MTN and Moov codes on the right SIM.

I am finishing a Master's in Software Engineering at Groupe EDHEG-Abidjan, after a Licence 3 in the same field and a BTS in application development. What I consolidate there gets used at work the next day: modelling, application security, industrialisation. Day to day I work in Agile with product teams and business stakeholders: settle the business rule before coding it, run code reviews and have my own code reviewed, write unit and integration tests, and document whatever someone else will inherit.