Skills

The stack, and what I actually use it for.

Tools are not the point — but you probably want to know what I reach for. Grouped by where it sits in a build rather than by how impressive it sounds.

01

Front end

Interfaces people use without thinking about them. Accessible markup first, framework second.

React & ReduxPrimary
Next.jsPrimary
Vue.jsProduction
JavaScript & TypeScriptDaily
HTML & CSS / SASSDaily
Bootstrap & MaterializeSupporting
UI/UX & FigmaDesign
02

Back end

The part that has to stay up. Sensible schemas, boring reliability, no clever tricks.

Django & PythonPrimary
Node.js & ExpressPrimary
SpringProduction
PostgreSQLPrimary
MySQLProduction
MongoDBProduction
Supabase & FirebaseProduction
03

Mobile

One codebase, two platforms, and the awkward native bits handled properly.

React NativePrimary
Google Maps & geolocationProduction
Stripe & mobile paymentsProduction
Socket.IO & real-timeProduction
Push notifications & i18nProduction
04

Cloud & pipelines

Getting it deployed, keeping it deployed, and knowing when it breaks.

AWS (S3, Redshift, EFS)Certified
KubernetesCertified
VercelDaily
GitLab CI & JenkinsProduction
Testing & QACertified
05

AI, and the rest

Applied rather than theoretical — narrow problems where a model beats a rule.

LangChain & agent designProduction
RAG & retrievalProduction
Machine learningApplied
Web3 & blockchainExploratory
Technical SEOProduction

How I work

The stack matters
less than the habits.

  • Small diffs, strong tests, and a deploy you can roll back
  • Accessible and fast by default, not as a later pass
  • Written down — so the next person is not stuck
  • Clear on what I do not know, early rather than late
  • Available after launch, because that is when things break
Start a project

Next

Seven certifications
behind the stack.

See certifications