Backend + Mobile Engineer

I build the systems your app can't afford to have fail.

Production-grade APIs and cross-platform mobile apps for teams that need to ship fast and stay up — Django backends, Flutter apps, and the RAG pipelines that turn documents into real answers.

Systems in production 3 / 3 operational
SSGI FIX Flutter · Field maintenance reporting
Offline sync < 5s
Report time -70%
OPERATIONAL
LexiAI Django · RAG document intelligence
Avg query ~380ms
Grounded retrieval-first
OPERATIONAL
Kech Delivery Flutter · Real-time logistics tracking
Live tracking real-time
Network-resilient auto-retry
OPERATIONAL
3production systems shipped
2platforms — iOS & Android
1engineer owning phone → server
0tolerance for silent failures
Case Studies

Selected systems, not screenshots

Every project below shipped to real users. Expand for the architecture behind it.

A field maintenance reporting app for technicians at remote satellite sites, built to turn a maintenance issue into a digital report that reaches every technician and manager on the job instantly.

The Challenge

Field technicians logged maintenance issues on paper or disconnected spreadsheets. Reports were slow to file, easy to lose, and impossible to track once submitted — especially in areas with unreliable signal.

Architecture

A Flutter app for iOS and Android with a local-first data layer: reports are captured and queued on-device, then synced automatically the moment connectivity returns. Predictable state management keeps the UI consistent through connectivity drops, with structured photo capture and role-based workflows for field agents vs. supervisors.

Solution & Impact

Technicians file a complete report in seconds, with or without signal. Supervisors get a live queue instead of a paper backlog. The result: faster repair turnaround, an auditable history of every report, and effectively zero lost submissions.

FlutterDartOffline-first syncLocal persistenceRESTRole-based accessFirebase

A retrieval-augmented legal assistant that answers questions on Ethiopian law — grounding every response in real legal documents and citing its sources, instead of relying on generic model recall.

The Challenge

Ethiopian legal information is scattered across sources with no central place to search it — and even when you find the right document, it rarely comes with an explanation. Lawyers lose hours preparing for court cases, researchers struggle to locate the right material, and everyday citizens have no easy way to understand what the law actually means for them.

Architecture

Django and Django REST Framework power an ingestion pipeline that indexes Ethiopian legal texts — codes, proclamations, and case materials — for retrieval. When a lawyer, student, or citizen asks a question, the system pulls the relevant passages first and passes them to the Mistral API to generate a plain-language answer with the source cited, so nothing is stated without a document behind it. A React frontend delivers the query/response experience, with caching and rate-limit handling to keep answers fast under load.

Solution & Impact

Instead of digging through scattered legal texts, users ask a question in plain language and get an answer grounded in the actual law — with a citation attached. Lawyers cut down research and case-prep time, students and researchers find relevant material in seconds, and everyday citizens get a plain-language explanation of laws that affect them.

PythonDjangoDRFPostgreSQLVector retrievalMistral APIReact

A role-based Android delivery marketplace connecting customers, drivers, and admins — from browsing a restaurant's menu to placing an order, approving a driver, and navigating a live delivery to the door.

The Challenge

Restaurants needed a reliable way to reach customers online, drivers needed a clear path from signup to earning, and the business needed to manage both sides — verifying driver documents, approving vehicles, tracking every order — without juggling disconnected spreadsheets and phone calls.

Architecture

A Flutter Android app with role-based access control powering two distinct experiences: customers browse registered restaurants and menus, place orders, and pay directly in-app; drivers submit documents and vehicle details for approval, then view, accept, or decline available orders and navigate deliveries on the map. Behind the app, an admin platform manages driver approvals, restaurant listings, and order oversight, with a separate sales agent web platform handling onboarding — all running against the same backend.

Solution & Impact

Customers get an on-demand ordering experience, from menu to doorstep, with payment built in. Drivers get a clear, self-serve path: apply, get approved, and start accepting orders on their own schedule. Admins and sales agents get dedicated tools to run the marketplace instead of managing it by hand.

FlutterDartPostgreSQLReal-time locationReconnect/retry logicRESTDjango
Competency Matrix

One engineer, both ends of the wire

The server your data lives on, and the app your users actually touch.

Backend

APIs, data, and infrastructure built to stay up.

Languages & Frameworks
PythonDjangoDjango REST Framework
Data
PostgreSQLQuery optimizationVector search / RAGRedis
Systems
REST API designAuth & permissionsDockerCI/CD

Mobile

Cross-platform apps that hold up outside the demo.

Core
FlutterDartClean Architecture
State & Data
State managementOffline-first storageBackground sync
Delivery
iOS & Android deploymentApp Store / Play StorePerformance profiling
One request, full ownership: from the Flutter client to the Django API to the database it reads from — no handoffs, no gaps.
How We'd Work Together

From scope call to shipped system

01

Scope call

A short call to understand the problem, constraints, and what "done" actually means for your team.

02

Architecture proposal

A concrete plan — stack, data model, milestones — before a line of production code gets written.

03

Build in sprints

Working software delivered in short cycles, with demos so you're never guessing what's been built.

04

Ship & support

Deployed, documented, and handed off cleanly — with support after launch, not radio silence.

Start Here

Tell me what you're building

Two minutes now saves a week of back-and-forth email later.

Scope summary