IMMOTIC
A property platform where every listing lives on a map, not just a list.
- Django
- Django REST Framework
- Next.js
- TypeScript
Read the case study
Software Engineer · Full Stack & DevOps
Software Engineer
I build modern web applications, scalable APIs and reliable software infrastructure from the data model through to the deployment pipeline.
UTC+1 - overlaps most of the working day with Europe, mornings with the Americas. I reply within a day.
Act I
The journey of a request
01
A request starts here: a browser rendering React and Next.js, built on data models rather than routes.
02
Before it reaches any application code, it crosses a network and a pipeline that already tested and shipped whatever it's about to run.
03
A Django REST Framework core resolves it: authentication, business logic, a contract that existed before the endpoint did.
04
Most of what I build has a location at its center. PostGIS turns coordinates into queries; GeoServer turns queries into a map someone can actually read.
05
Zoom out, and the whole journey ran inside containers, replicated and scheduled the part that decides whether any of this survives real traffic.
Act II
I'm based in Yaoundé, Cameroon (UTC+1). That's not a constraint to plan around it's a timezone that overlaps the entire European working day and the American morning.
Yaoundé, Cameroon
European and US offsets shift by up to an hour with daylight saving; Yaoundé itself never observes it, so the numbers below are the winter/standard-time figures.
Benin
On-site infrastructure deployment at a national datacenter, for GIZ's digital-observatory programme
Douala
Architecture and technical leadership for a regional urban-planning authority (anonymised)
Act III
Real systems, real dates from developer to lead to architect.
5+
Years shipping production software
6
Government & institutional programmes delivered
2
Countries with on-site delivery
40+
Tools and technologies across the stack
Full Stack Developer
A property platform where every listing lives on a map, not just a list.
Junior Solutions Architect · DevOps
The architecture and the infrastructure behind a national real-estate platform, not just the app.
Lead Developer
Taking a national observatory from running software to a production system with a datacenter behind it.
Technical Lead
Two systems, one shared question: where does this data actually live, geographically.
Technical Lead
Centralising how a city collects and tracks what it's owed.
Developer
Turning raw regional statistics into something a visitor can actually read.
Creator & Solo Developer
The immigration math, done once, correctly, in the open.
That's the path so far. See every project in detail, or start a conversation.
Ready now
Six areas I can own end to end, starting now.
01
Django and DRF APIs designed as contracts before the endpoints exist: authentication, business logic and data modelling, built to be maintained by someone who isn't me.
02
PostGIS, GeoServer, Elasticsearch and mapping APIs - turning location data into search, mapping and reporting people actually use, across five production systems.
03
Docker, Kubernetes and GitLab CI/CD from preproduction through production, including standing up infrastructure on-site in a national datacenter, not just a managed cloud.
04
Production-ready applications in React and Next.js: polished interfaces, authentication, dashboards and forms, built on real data models and wired to solid APIs.
05
Fast, responsive, search-friendly websites in Next.js or WordPress: from design hand-off to going live, with the documentation that keeps the client self-sufficient.
06
Cross-platform apps in Flutter or React Native, connected to your API: one codebase for iOS and Android, when the product genuinely needs to live in a pocket.
What I build
Five kinds of work, all of which end in production.
System thinking
A generic shape, not a specific project the layers I reason in before writing any code.
Each layer names what it does, never which framework does it. The framework is the part most likely to change.
Work
Real systems delivered for real clients: from a public map-based marketplace to a government datacenter deployment.
A property platform where every listing lives on a map, not just a list.
Read the case study
The immigration math, done once, correctly, in the open.
Read the case study
Taking a national observatory from running software to a production system with a datacenter behind it.
Read the case study
The architecture and the infrastructure behind a national real-estate platform, not just the app.
Read the case study
Tools
Not everything I have touched what I actually reach for, in the order I reach for it.
How I work
Five rules that decide the arguments before they start.
01
Solve the real problem before adding complexity. Most features are a symptom of a question nobody asked properly.
02
Clear architecture and readable code outlive clever code. The next person to open the file is the actual user.
03
Repetitive work belongs in tooling, not in someone's day. If it happens twice, it gets a script.
04
Systems should be observable, testable and boring in production. Excitement at 2 a.m. is a design failure.
05
Software gets good through feedback, not through planning. A deployed guess beats a perfect document.
Credentials
Recent and verifiable.
DevOps & Cloud
Udemy
Aug 2025
DevOps & Cloud
SkillUp / Simplilearn
May 2026
DevOps & Cloud
SkillUp / Simplilearn
May 2026
DevOps & Cloud
Udemy
Aug 2025
Web & Software Development
Alison
Feb 2025
Web & Software Development
Udemy
Apr 2025
Web & Software Development
Udemy
Mar 2025
Web & Software Development
Udemy
Apr 2025
Web & Software Development
CodeSignal
Feb 2025
Web & Software Development
Udemy
Apr 2025
Web & Software Development
Learn IT University
2025
Methodology & Management
SCRUMstudy
Sept 2025
Methodology & Management
SMstudy
Sept 2025
01 / 13
Contact
I'm interested in engineering problems worth solving, products that need building properly, and teams where an engineer is trusted to own a feature end to end.
I answer within a day.