Skip to contentOLI.DEV

/ career

Career

I want to keep owning backend systems and the production path around them — APIs, data, auth, realtime where it is justified, and Linux-based deploys — while still shipping full-stack surfaces in TypeScript when that is the product.

Direction

Backend / Full-Stack Software Developer

Roles I am targeting

  • Backend engineer (Node.js / NestJS / TypeScript)
  • Full-stack engineer with a backend bias (Next.js + Node APIs)
  • Roles that include production infrastructure: VPS, Nginx, Docker, CI/CD — not title-only DevOps

Technologies I want to work with

Same stack I already ship in — not a wishlist of frameworks I have never used.

  • TypeScript
  • Node.js
  • NestJS
  • Express.js
  • React
  • Next.js
  • MongoDB
  • PostgreSQL
  • MySQL
  • Prisma
  • Redis
  • WebSocket / Socket.IO
  • Linux
  • Docker
  • Nginx
  • GitHub Actions

Engineering interests

  • API and backend architecture
  • Multi-tenant product dashboards
  • Automation and data pipelines
  • Realtime systems
  • Secure APIs and RBAC
  • Production Linux / VPS operations
  • Developer tooling and npm packages
  • AI-assisted automation in product workflows

Problems that are worth the hours

  • Turning messy operational workflows into APIs and dashboards other people can run.
  • Keeping production deploys boring: proxy, process manager, TLS, backups, CI.
  • Integrations (payments, social APIs) that have to survive real provider constraints.
  • Reporting and aggregations that stay correct as the data grows.

Currently exploring

  • Low-level / OS-related experiments and CLI tooling (hobby, not a job claim).
  • Packaging reusable data and developer libraries (for example BD Geo).
  • TODO: System Design.

Experience and projects are the evidence. See experience, projects, and contact.