Software engineer focused on backend systems, distributed architecture, and product engineering.
I enjoy building software that is reliable in production, understandable to other engineers, and genuinely useful to the people using it. Most of my best work sits at the intersection of application development, systems design, APIs, developer experience, and operations.
- Portfolio: horacenjoroge.netlify.app
- LinkedIn: linkedin.com/in/horacenjoroge
- GitHub: github.com/horacenjoroge
- Email: horacenjorge@gmail.com
I mainly work on:
- Backend platforms, APIs, and application architecture across different stacks depending on the problem
- Distributed and event-driven systems with queues, workers, caching, and async processing
- Production-ready products with Docker, CI/CD, observability, and deployment workflows
- Full-stack applications where strong backend architecture matters as much as user experience
The tools change from project to project, and I’m comfortable learning what a product or client actually needs instead of forcing every solution into the same stack.
My engineering style leans toward:
- Clear architecture and strong documentation
- Secure authentication and authorization flows
- Reliability under real usage, not just local demos
- Systems that are easy to extend, test, and operate
AI-powered job search and application platform.
Cvelo helps users move from job discovery to application with resume tailoring, cover letter generation, ATS scoring, application tracking, browser autofill, billing, notifications, and a multi-surface product experience.
Highlights
- Full-stack architecture spanning React, TypeScript, FastAPI, PostgreSQL, Redis, background workers, and a Chrome extension
- Product features that go beyond CRUD: AI-assisted document workflows, subscription billing, push notifications, and external-job autofill
- Production-minded setup with health checks, metrics, structured configuration, Docker workflows, and observability
Links
- Repo: horacenjoroge/Cvelo
- Live: cveloapp.com
Backend-first voting platform built for reliability and operational clarity.
Provote showcases idempotent vote handling, documented APIs, architecture diagrams, load testing, backup and restore workflows, and a strong operations story around a Django-based service stack.
Highlights
- Built with Django, Django REST Framework, PostgreSQL, Redis, Celery, Docker, Gunicorn, and Nginx
- Focus on backend engineering quality: safe retries, API contracts, system documentation, and performance validation
- Strong repository maturity through OpenAPI artifacts, architecture docs, and deployment-oriented scripts
Links
- Repo: horacenjoroge/provote
Graph-first SME intelligence platform inspired by data-intensive systems thinking.
AfricGraph models business relationships and operational data using a graph-driven architecture supported by Neo4j, PostgreSQL, Redis, RabbitMQ, Elasticsearch, FastAPI, React, and Celery.
Highlights
- Combines graph and relational models for different access patterns and workflows
- Includes REST and GraphQL surfaces, monitoring assets, seed data, deployment tooling, and architecture documentation
- Reflects strong systems-design thinking around data movement, service boundaries, and observability
Links
- Repo: horacenjoroge/AfricGraph
Distributed systems project inspired by Kafka- and Pulsar-style log architecture.
This project explores storage internals, replication ideas, benchmarks, monitoring, and distributed systems concepts through a runnable event-log platform.
Highlights
- Built with Python, gRPC, asyncio, Docker, and Raft-inspired coordination ideas
- Focused on systems thinking, internal mechanics, and deep technical exploration
- Good example of the kind of infrastructure and architecture problems I enjoy working on
Links
Languages
- TypeScript
- JavaScript
- Python
Frontend
- React
- Next.js
- Svelte
- React Native
- HTML
- CSS
Backend
- Node.js
- Express.js
- NestJS
- Django
- FastAPI
- REST APIs
- GraphQL
- Microservices and event-driven services
Data and Infrastructure
- PostgreSQL
- MongoDB
- Redis
- Neo4j
- RabbitMQ
- Elasticsearch
- Docker
- Kubernetes
- AWS
- Azure
Observability and Quality
- CI/CD pipelines
- Prometheus
- Grafana
- Jest
- API documentation
- Architecture documentation
- I do not just build features. I pay attention to architecture, failure modes, deployment, and maintainability.
- I enjoy hard backend problems: concurrency, async workflows, distributed coordination, and system reliability.
- I document my projects well so other engineers, hiring teams, and collaborators can understand how the systems work.
- I am comfortable shipping complete products, but my strongest edge is turning complex backend ideas into structured, usable systems.
Right now I’m focused on growing in:
- Distributed systems design
- Advanced backend architecture
- Kubernetes and cloud infrastructure
- Graph and data-intensive applications
- Building AI-enabled products with solid engineering foundations
- Reading Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable Systems by Martin Kleppmann
- Continuously learning new concepts, languages, and tools that help me design better systems and ship better products
- Backend engineering roles
- Software engineering roles with strong systems or platform work
- Freelance or contract work involving APIs, architecture, or full-stack product delivery
- Collaborations on ambitious products, developer tools, and infrastructure-focused projects
If you’re a client, recruiter, or engineering team reviewing my profile, the best way to understand my work is through the project repositories above. I care about code quality, architecture clarity, continuous learning, and shipping software that holds up beyond the demo stage.