Built on engineering principles.
Technologies are grouped by what they are for. Each group links to the services, case studies and articles where it shows up in practice.
- EX-01
Backend Engineering
Services and APIs that stay correct under concurrency, retries and partial failure.
- Go
- NestJS
- Node.js
- Express
- gRPC
- REST APIs
- EX-02
Architecture
Boundaries, data flow and failure modes decided deliberately and written down.
- Microservices
- Event-driven architecture
- Distributed systems
- System design
- Clean code
- Testable architecture
- EX-03
Data
Schemas that match the domain, and queries that stay fast as data grows.
- PostgreSQL
- MongoDB
- MySQL
- Redis
- Google Datastore
- Database optimisation
- EX-04
Messaging & Infrastructure
Reliable messaging between services, reproducible environments and automated delivery.
- RabbitMQ
- Kafka
- Kubernetes
- Terraform
- Jenkins
- Git
- EX-05
Geospatial (GIS)
Spatial data done properly: storage, queries and analysis on PostGIS, backed by a GIS diploma and a geography degree.
- GIS
- PostGIS
- Spatial databases
- Spatial analysis
- EX-06
Engineering Practice
The habits that keep a codebase healthy after the first release.
- Technical leadership
- Automated testing
- Security
- Database management
- Shell scripting
- EX-07
AI Integration
LLM features and agents with real tools, guardrails and evaluation.
- LLM APIs
- AI agents
- Retrieval (RAG)
- Tool calling
- Human handoff
Fig. 4 — Engineering matrix. Listed technologies are ones used in professional work; depth varies by area.
Have a complex problem worth solving?
Tell me about the product, the architecture or the engineering challenge. I reply to every relevant inquiry.