Grand Baie, Mauritius
Some work happens at the surface. Some happens underneath, in the parts that keep everything steady. I’m drawn to that second kind of work: backend systems, data workflows, and delivery infrastructure that help teams operate with more confidence. My work sits across software engineering, analytics, DevOps, and technical writing, with a focus on making complex systems clearer and more dependable.
Backend systems, data pipelines, cloud operations, security-minded engineering, and writing that helps technical work make sense when it starts to feel abstract.
About
My background spans software engineering, distributed computing, DevOps, and data analysis across healthcare, education, and e-commerce. Most recently, I've been focused on backend-heavy work: implementing optimization algorithms, architecting services, improving reliability, building internal tools, shaping data flows, and making systems easier to run.
I also write about technology, work, and growth. Some pieces are technical, covering topics like distributed computing, security, or data. Others are more reflective. They all have one thing in common: trying to understand how things work, then finding a clear way to talk about them.
Backend: Python, FastAPI, Flask, Go, Java, APIs, and service design.
Data: SQL, MongoDB, ETL flows, reporting systems, dashboards, and analysis that supports decisions.
Platform: AWS, GCP, Docker, Ansible, CI/CD, shell automation, and cloud operations that make delivery smoother.
Security: An active interest in resilient systems, secure software development, and practical cybersecurity awareness.
How I Work
I’m an entrepreneur at heart, so I’m especially drawn to work that starts with ambiguity. Sometimes that looks like building a product from scratch. Sometimes it looks like shaping a feature when the brief is still rough and the direction is still forming. I enjoy being the person who helps turn that uncertainty into something useful, structured, and real.
I’m comfortable starting where not everything is fully defined yet. I like asking the right questions, understanding the constraints, and then turning a vague need into an actual product, workflow, or feature that people can use.
Whether the challenge is technical design, data flow, delivery, or implementation planning, I like creating the shape of the solution. I do not just work within clarity. I help create it.
Backend services, data workflows, internal tools, automation, and cloud infrastructure are where I often do that work. They may be less visible than the interface, but they are often what makes a product reliable, scalable, and worth trusting.
The best way to predict the future is to invent it. Alan Kay
Writing
A reflective essay on growth, gratitude, mentorship, and the seemingly small gestures that shape a career over time.
Read on MediumI publish on Medium about software engineering, distributed systems, cybersecurity, communication, and professional growth in tech. Sometimes the writing is technical. Sometimes it is reflective. Often, it is both.
Visit the full Medium archiveA practical piece on problem-solving complexity, judgment, and applying the right tools to the right problems.
Read articleAn educational look at live-site vulnerabilities and why security hygiene matters in the real world.
Read on MediumA writer’s introduction to distributed computing and the mindset shift behind modern computation at scale.
Read on MediumExperience
Building pricing systems, internal tooling, and performance improvements with an emphasis on practical impact and operational efficiency.
Led cloud migrations, designed dashboards, automated GCP jobs, and improved the reliability and testing discipline of data pipelines.
Designed system architecture and helped build a microtask-driven audio annotation platform across front and backend layers.
Organized community events, including a DevFest with more than 150 participants, while building a culture of writing, collaboration, and technical curiosity.
Journey
In Kinshasa, learning often meant waiting for cheaper nighttime data, downloading books and software, and teaching myself with whatever I could access. Before software engineering became a career path, it was already a habit. I was experimenting early, building, breaking, and discovering that code could turn curiosity into something practical.
At African Leadership Academy, I found myself in a foreign country, among ambitious young people from across Africa, learning English from scratch while the world around me widened quickly. I arrived known first as a violinist and left as the person people called when something technical needed to be built. I started building for real users, teaching programming to peers, and creating startups with friends.
Holberton School, and later African Leadership College and Glasgow Caledonian University, gave names, depth, and discipline to what had already become instinct: backend engineering, systems thinking, data, DevOps, and secure software development. What began through self-teaching and experimentation became more rigorous, more architectural, and more grounded in how reliable systems are designed and maintained.
Contact
I’m open to roles, collaborations, and conversations where robust systems, dependable data, and clear thinking matter. If that sounds like the kind of work you care about too, I’d be glad to hear from you.