Skip to content

Roman Vašek — freelance full-stack developer

Eight years of building information systems, owning the whole path from design to deployment.

What I do

Information systems from scratch
From the first domain design to running in production.
Taking over and developing an existing system
I take over a system that is already running and move it forward without stopping it.
Backend and architecture
Data model, API, queues, integrations, and what happens under load.
Mobile and desktop
Applications in Expo and Electron that run unattended.
Integrations
Connections to payments, registers and third-party systems.

What I focus on

Usability
An interface where the work gets done faster than before.
Performance
Measured, not estimated.
Delivering the whole path
From design to deployment and operation, not just handing off code.
Transparency
At any point you know what I am working on and what it will cost.
Sustainability
Code that someone else can take over from me.

How we work together

  1. Consultation — what is needed and whether I can deliver it.
  2. Quote with scope and timeline.
  3. Order with an agreed date.
  4. Iterative development with progress shown along the way.
  5. Handover with an acceptance protocol.
  6. Support and further development.

References

  • Axman Lounge

    Problem
    Office bookings, payments and invoicing lived outside any system and were redone by hand each month.
    Solution
    I built the whole application alone: bookings, payments and automatic invoicing.
    Result
    The monthly close runs itself and a booking takes a minute.
  • Direct Fidoo

    Via Qest

    Problem
    A payment card platform needed its card issuer wired to internal services.
    Solution
    Thredd integrations and Azure services backed by CosmosDB.
    Result
    Cards and transactions are processed without manual steps.
  • OPT On Demand

    Via Qest

    Problem
    A shop-floor production terminal had to run unattended and update itself.
    Solution
    An Electron application with auto-update and a NestJS backend on GCP.
    Result
    Terminals update themselves, with no trip to the floor.
  • Aeqoom

    Via Qest

    Problem
    Field service technicians needed job tracking on a phone.
    Solution
    Two Expo applications over one backend, plus an experiment with AR glasses.
    Result
    Jobs are recorded in the field instead of after the drive back.
  • GlampingCZ

    Via Qest

    Problem
    A booking system built from nothing, including background order processing.
    Solution
    A NestJS backend on AWS with an SQS queue for orders.
    Result
    Bookings and payments have run as one flow from day one.
  • ČSOB

    Via Enimo

    Problem
    A bank's mobile application needed new services inside an existing microservice architecture.
    Solution
    Microservice development inside the vendor's team, under the bank's security rules.
    Result
    The services run in production in an application used by hundreds of thousands of people.

Stack

Frontend

  • React
  • Vue
  • TypeScript
  • Tailwind
  • Expo
  • Electron

Backend

  • Node
  • Bun
  • NestJS
  • Elysia
  • PostgreSQL
  • BullMQ
  • REST
  • GraphQL

Infrastructure

  • Docker
  • AWS
  • GCP
  • Azure
  • Sentry
  • CI/CD

Email me

Tell me what you need and by when.

Email: roman@vengex.com