Here’s a practical map of what I reach for most often — not an exhaustive résumé keyword list. Recent day jobs lean Rails + Postgres at Skylab / Symphony, with TypeScript and Next.js on the product side in my current role.
| Area | Tools |
|---|---|
| Backend | Ruby on Rails, PostgreSQL, MySQL, Redis, Solid Queue, Solid Cache (also Sidekiq) |
| Streaming & data | Apache Kafka, Debezium (CDC), ClickHouse, Apache Solr |
| Frontend | HTML5, CSS, JavaScript, TypeScript, React, Next.js, StimulusJS; Redux / Redux-Saga |
| Testing | RSpec (unit and integration tests) |
| Infrastructure | Docker, Kubernetes, Nginx, Puma, GCP, GitHub Actions (CI/CD), Capistrano; Ansible / DigitalOcean / Proxmox in my homelab |
| Monitoring | New Relic, Monit, logrotate |
| AI / tooling | Claude Code, Cursor |
| Leadership | Team leading, mentoring, project management |
How this maps to employers
- LIFULL Tech Vietnam — TypeScript, Ruby, Next.js
- Skylab — Rails, Solid Queue / Solid Cache, PostgreSQL, Docker, Debezium, Kafka, ClickHouse
- Symphony Creative Solutions — Rails, Sidekiq, PostgreSQL, RSpec, Docker
- ZIGExN VeNtura — Rails, Sidekiq, MySQL, Solr, React, Redis, Nginx, GCP
- NUS Technology — Rails, Sidekiq, RSpec, AngularJS, EmberJS, Capistrano
- Vinova — Rails, Sidekiq, Spree
I pick tools to match the problem: Rails for fast, maintainable backends; React / Next.js when the UI needs rich client state; streaming pipelines when usage or billing events need to move reliably between systems.
This site and my interactive CV are examples of the React + TypeScript side; most of my day jobs have been Rails-first, with a growing TypeScript / Next.js footprint in the current role.
Public comments are closed, but I love hearing from readers. Feel free to contact me with your thoughts.