PYTHON
Language
Software & data architecture
Preparing the details
Software & Data Architect
I help teams build reliable software, make sense of their data, and put AI to practical use.
Rooted in Nairobi, Kenya.
Building for teams everywhere.
Bringing the island into view…
An interactive map of my work
Every building tells a project story.
Take a little detour. Drag to roam, zoom in for a closer look, and select a building for the story behind it.
Centralized platform with structured academic workflows: content access, engagement, and school operations in one place.
Supported centralized academic communication and learning workflows.
One centralized workflow model: publish, receive, review, process — with reporting-ready data structures from day one.
Designed a single workflow model for publishing, intake, review, and processing.
Two-tier architecture: high-frequency ingest feeding live views, validated history replicating centrally. The pipeline monitors itself.
Improved visibility into drilling operations and data quality.
Security-sensitive UX patterns balanced against rapid-response workflows — usability as a safety feature.
Supported safer communication patterns for high-risk users.
End-to-end ownership from gap analysis to handover: deployment, training, documentation, and stabilization treated as one workflow.
Moved product delivery from implementation planning into stabilized operational use.
Language
Language
Language
Database
Observability
Framework
I like getting close to the real problem before reaching for a clever solution. We’ll make the trade-offs clear, build something dependable, and leave the team able to run it without a decoder ring or a midnight rescue.
Off the clock, you’ll find me at a tech meetup, on a run, or on a badminton court, where my enthusiasm still outruns my footwork. I’m happiest swapping ideas, learning from people, and building things that make their workday easier.
Between a good idea and a working product, there’s usually a knot or two. I help teams untie them.
Some tasks deserve a shorter stay on your to-do list. I build AI into everyday workflows, with people in charge of the important calls.
The part your users never see, but definitely notice when it breaks. I build backends and APIs that keep the whole thing connected.
Three reports. Three different answers. Sound familiar? I bring your data together so the next decision starts with numbers you can trust.
Getting it live is the beginning. I build cloud infrastructure with monitoring and recovery built in, so your team has a plan beyond “try restarting it”.
From desktop support to software architecture, these are the roles that shaped how I build today.
Partner with founders from first conversation to launch, shaping real problems into clear product plans and useful SaaS features.
Bring product, design, and engineering together, then use feedback from real users to improve what ships.
Architected insurance platforms across claims, underwriting, and policy management, guiding delivery from integrations through rollout.
Integrated claims tools and underwriting APIs, helping cut average policy approval time from 6 hours to 4.6 hours.
Built client web and mobile apps, working across the interface, backend services, databases, and third-party APIs.
Delivered a rapid-response app with C# services and React Native for secure coordination in high-risk settings.
Developed internal applications for secure reporting, employee wellbeing, and day-to-day operations.
Turned stakeholder needs into features for whistleblower and mental wellness applications.
Kept operational software running: fixed backend issues, improved database performance, and supported releases.
Created SQL Server Reporting Services reports and added PHP features to the CodeIgniter application.
Helped colleagues get back to work by setting up devices, configuring software, and solving everyday IT issues.
Prepared workstations, installed updates, and recorded fixes to make recurring problems easier to solve.
We had data in a few different places and no easy way to trust the numbers. Eric helped us agree on what mattered, connect the sources, and shape a dashboard the team could use without calling engineering every time.
Eric didn’t just hand us a technical plan and disappear. He asked how teachers actually use the product, then helped us simplify the parts getting in their way. The rollout felt calmer because someone was thinking about the whole journey.
He was patient with our questions and honest about the trade-offs. We shipped in steps, fixed the rough edges quickly, and ended up with a system our team could use on a busy day without a manual beside them.
Then you're in the right place. Get the best designs you're
looking for. Just reach out and let me know!
