Bro.Nungu.
Experience mode turns on sound and richer motion. Continue for the quiet, professional view. You can switch at any time.
Taking on new builds
Bro. Nungu, Data Science Engineer
Data Science Engineer building software systems, intelligent applications, and digital products that solve real-world problems.
Nicholaus Nungu Warobi
Also known as Bro. Nungu
I am a Data Science Engineer and full-stack developer focused on building practical digital solutions for real-world problems.
I don't just write code. I understand problems, analyze data, design systems, architect solutions, build software, integrate AI, test, deploy, and keep improving what I ship.
An engineering foundation: structured thinking, systems, and solutions that have to work in the real world.
Bachelor of Engineering in Data Science, Mbeya University of Science and Technology (MUST).
Full-stack software: interfaces, APIs, databases and the infrastructure that runs them.
AI-powered features and complete digital products, taken from idea to deployment.
Ten disciplines, one practice: understanding a problem well enough to build the system that solves it.
Structured, maintainable software designed around real requirements rather than features for their own sake.
Cleaning, exploring and interpreting data so that decisions are grounded in evidence.
Statistical and analytical thinking from an engineering degree in Data Science, applied to products.
Integrating AI capabilities into products where they genuinely help the people using them.
End-to-end ownership, from the database schema and APIs to the interface people touch.
Android and iOS apps built from a single codebase, so both platforms carry the same features and behaviour.
Buyer, seller and administrator workflows connected in one ecosystem.
Learning, assessment, school and analytics platforms for students and teachers.
Sales, inventory, point of sale, staff and reporting tools for daily operations.
Turning a real-world problem into a product people can actually use.
Marketplaces, business systems and consumer platforms, each designed as a complete product rather than a feature.
Business management system
Business operations, synchronised.
A business management platform bringing sales, inventory, point of sale, services, customers, expenses, branches, staff, reports, assets and debt management into one operational system.
Marketplace ecosystem
A Tanzanian marketplace for new and used products.
A marketplace ecosystem for Tanzania that connects buyers and sellers of new and used products, with administration, commerce workflows, analytics, and infrastructure designed to scale.
Visitor concierge & marketplace
A digital concierge that meets visitors to Tanzania before they land.
A concierge and marketplace platform for international visitors to Tanzania. Visitors describe their trip before they fly, are matched with a vetted local guide (a winga), receive a quotation, pay once and are met at the airport. Hotels, transport, tour operators, translators, and investment and mining consultants offer their services as verified partners.
Restaurant ordering platform
Online ordering for a Dar es Salaam restaurant, from menu to delivery tracking.
A full-stack ordering platform for Empire Food Point, a restaurant in Dar es Salaam. Customers browse the full menu section by section, customise dishes, check out in five steps and track their order live, while staff run orders, the menu, promotions and analytics from an admin dashboard.
Agricultural marketplace
Buy crops directly from verified farmers.
An agricultural e-commerce marketplace for Tanzania that connects buyers with verified farmers and vendors of grains, cereals and other crops. It covers listings, cart and checkout, shipping quotes, promoted ads, chat and announcements, and bulk SMS, in English and Kiswahili.
Movie & series marketplace
Preview, buy and download movies and series.
A mobile-first marketplace for movies and series. Visitors browse a curated catalogue and watch free previews, then buy a title, a single episode or a whole season and download what they own through short-lived secure links. Staff manage the catalogue, uploads, orders and settings from an admin dashboard.
Eight stages, from understanding the problem to improving the product long after launch.
Start with the problem, not the code. Who is affected, what is broken, and what would success look like?
Study the data, the workflows and the existing tools. Separate assumptions from evidence.
Shape the experience: the flows, interfaces and interactions that make the solution feel obvious.
Model the domain, the data and the services so the system can grow without being rebuilt.
Implement in small, reviewable increments with typed, maintainable code across the stack.
Verify behaviour, edge cases, accessibility and performance before anyone depends on it.
Ship to reliable infrastructure with a repeatable release path and visibility into production.
Measure how the product is used, learn from it, and improve it continuously.
My degree is in Data Science. I treat data as part of the product: what to capture, how to structure it, and what it can reveal.
Raw observations
Weekly readings arrive with noise, missing weeks and a few anomalies. Nothing is trusted yet.
| Week | Value | Status | Trend / forecast |
|---|---|---|---|
| 1 | 24.6 | Clean | 26.2 |
| 2 | 32.9 | Clean | 27 |
| 3 | 31.5 | Clean | 27.8 |
| 4 | 26.3 | Clean | 28.6 |
| 5 | 32.8 | Clean | 29.4 |
| 6 | 37.7 | Clean | 30.2 |
| 7 | 30.4 | Clean | 31.1 |
| 8 | 36.6 | Clean | 31.9 |
| 9 | 57.6 | Flagged | 32.7 |
| 10 | 33.5 | Clean | 33.5 |
| 11 | 32 | Clean | 34.3 |
| 12 | 32.5 | Clean | 35.1 |
| 13 | 32 | Clean | 35.9 |
| 14 | 33.2 | Clean | 36.7 |
| 15 | — | Missing | 37.5 |
| 16 | 32.4 | Clean | 38.3 |
| 17 | 31.4 | Clean | 39.1 |
| 18 | 36.3 | Clean | 39.9 |
| 19 | 35.5 | Clean | 40.8 |
| 20 | 36.8 | Clean | 41.6 |
| 21 | 16.1 | Flagged | 42.4 |
| 22 | 48 | Clean | 43.2 |
| 23 | 45.8 | Clean | 44 |
| 24 | 53.1 | Clean | 44.8 |
| 25 | 46.9 | Clean | 45.6 |
| 26 | 47.2 | Clean | 46.4 |
| 27 | 53.4 | Clean | 47.2 |
| 28 | — | Missing | 48 |
| 29 | 55.1 | Clean | 48.8 |
| 30 | 53.3 | Clean | 49.6 |
| 31 | 48.3 | Clean | 50.5 |
| 32 | 47.4 | Clean | 51.3 |
| 33 | 71.1 | Flagged | 52.1 |
| 34 | 48.4 | Clean | 52.9 |
| 35 | 48.3 | Clean | 53.7 |
| 36 | 51.3 | Clean | 54.5 |
| 37 | 49.4 | Clean | 55.3 |
| 38 | 51.4 | Clean | 56.1 |
| 39 | 55.9 | Clean | 56.9 |
| 40 | 62 | Clean | 57.7 |
| 41 | 42.7 | Clean | 58.5 |
| 42 | 64.2 | Clean | 59.4 |
| 43 | 65.8 | Clean | 60.2 |
| 44 | 71.4 | Clean | 61 |
| 45 | 65.9 | Clean | 61.8 |
| 46 | 65.2 | Clean | 62.6 |
| 47 | 64.9 | Clean | 63.4 |
| 48 | 63.4 | Clean | 64.2 |
| 49 | — | Forecast | 65 (54.8–75.3) |
| 50 | — | Forecast | 65.8 (55.6–76.1) |
| 51 | — | Forecast | 66.6 (56.4–76.9) |
| 52 | — | Forecast | 67.4 (57.2–77.7) |
| 53 | — | Forecast | 68.2 (58–78.5) |
| 54 | — | Forecast | 69.1 (58.8–79.3) |
| 55 | — | Forecast | 69.9 (59.6–80.1) |
| 56 | — | Forecast | 70.7 (60.4–80.9) |
Data models and services that grow with usage instead of against it.
Fast on the devices and networks people really have, not just on a developer laptop.
Clear boundaries, typed code and simple structures the next engineer can understand.
Authentication, authorisation and data protection designed in, not patched on.
Interfaces composed for every screen, from small phones to ultrawide monitors.
Semantic, keyboard-friendly and readable for everyone who uses the product.
Confidence through verification. Behaviour is checked, not assumed.
Systems that explain themselves in production through logs, metrics and analytics.
Deliberate structure: the right responsibilities in the right places.
Every technical decision ultimately serves the person using the product.
A deliberate, modern stack. Everything listed reflects the work I actually do.
01 · Languages
02 · Frameworks
03 · IDEs
04 · Tools
05 · Databases
I'm interested in roles, collaborations and projects where software, data and AI come together to solve meaningful problems.
What's next?
Have an idea, product, problem, or opportunity? Let's build something meaningful.