Download CV

Stack  ·  27 entries, with depth stated

A skill list is worthless without a depth next to it

Everything here carries how deep it goes and how long I have used it. Four means I have taken it apart under load and know where it breaks. Two means I am productive in it and would not architect a system on that alone.

4 · load-tested, debugged in production
3 · shipped real systems on it
2 · productive, not authoritative

Languages

6  ·  what I write in

JavaScript / Node.js

3 years

Python

2 years

C++

2 years

PHP

1 year

Lua

1 year

Bash

2 years

Frameworks

7  ·  what I build on

Express

3 years

React

2 years

Vue.js

2 years

Next.js

1 year

Django / FastAPI

1 year

Laravel

1 year

Socket.IO / WebSockets

2 years

Data

3  ·  where state lives

MongoDB

3 years

Redis

2 years

SQL (MySQL / PostgreSQL / SQLite)

2 years

Infrastructure

4  ·  where it runs

AWS

2 years

Cloudflare R2

1 year

Docker

1 year

Firebase / Vercel / Hostinger

2 years

Security & networks

3  ·  the attacker's side

Penetration testing (eJPT)

1 year

OWASP API security

1 year

Network engineering (CCNA-level)

2 years

Practice

4  ·  the part that is not a library

System design & architecture

2 years

API design (REST, 178-request scale)

3 years

Payment integration (Stripe, Qcard, Zain Cash, SindiPay)

2 years

Team leadership & mentoring

1 year

What I went and learned next

9 areas

The deliberate list, worked through in order rather than picked up incidentally. Each area has a goal and the specific things it covers, so it can be checked in an interview rather than taken on faith.

01

Distributed systems fundamentals

worked through

The vocabulary of why systems fail: the theory behind every architecture decision.

CAP theoremConsistency modelsIdempotencyOutbox patternSaga pattern2-phase commitDelivery guaranteesBackpressure

02

Event-driven architecture with Kafka

worked through

Beyond sockets into durable, replayable event streams.

Topics & partitionsPartition keys & orderingConsumer groupsOffsetsDead-letter queuesReplay & retention

03

Container orchestration: Docker → Kubernetes

worked through

From "it works on my machine" to declarative, self-healing deployments.

Multi-stage Dockerfilesdocker-composeDeployments & ServicesIngressConfigMaps & SecretsHPA autoscaling

04

Observability

worked through

Logs, metrics and traces as one debugging workflow, not three dashboards.

Structured logging & correlation IDsPrometheus & percentilesOpenTelemetry tracingJaeger

05

API design at scale

worked through

Beyond REST: contracts, versioning and transport chosen deliberately.

gRPC & protobufVersioning & backward compatibilityOpenAPI-firstGraphQL federationRate limiting algorithmsAPI gateways

06

CI/CD done properly

worked through

Every commit proves itself before it ships.

Pipeline stages & quality gatesGitHub ActionsImage tagging by SHARolling / blue-green / canaryRollbackSecrets in pipelines

07

Testing maturity & reliability

worked through

The testing pyramid as practice, not diagram.

Unit & mocksTestcontainersContract testing (Pact)Load testing (k6)Chaos engineeringSLI / SLO / error budgets

08

AWS cloud architecture depth

worked through

From using AWS to architecting on it.

VPC & subnetsIAM least-privilegeECS / EKS / LambdaSQS / SNS / KinesisRDS vs DynamoDBCloudFront & Auto ScalingCost optimization

09

Security engineering

worked through

The eJPT foundation, weaponized for defense at the architecture level.

OWASP API Top 10 (BOLA)OAuth2 + PKCEOIDCJWT validationVault dynamic secretsmTLS & zero-trustSAST/DAST in CI

Where each of these was actually used

Kafka, outbox relays, optimistic concurrency and connection-pool arithmetic are on this list because a system broke and taught them. The systems index says which one, and the decisions index says what each choice cost.