Full-stack engineer, 8 years. TypeScript, Go, Postgres. I pick products up at “we have an idea and a Figma file” and take them to production with CI, monitoring and docs.
02 / About
I’m Pablo Velázquez — 37, full-stack engineer based in Seville. Eight years building products that survive contact with real traffic: fintech back offices, logistics consoles, analytics clients host themselves. I work in TypeScript and Go, live in Postgres, and would rather delete a service than add one.
Seville, Spain
UTC+1
Spanish · English
Available for new projects
03 / By the numbers
Numbers I can defend in a call
1.2M
MAU on the busiest product
99.95%
uptime on services I own
8 yrs
shipping commercial software
24
projects taken to release
04 / Selected work
Projects I owned end to end
05 / Stack by layer
The stack I actually run in production
Frontend
01
React, Next.js (App Router), TypeScript, Zustand, TanStack Query, Tailwind, Vitest, Playwright
Backend
02
Node.js (Fastify, NestJS), Go, tRPC / REST / gRPC, queues: BullMQ, NATS, Kafka
Data
03
PostgreSQL (partitioning, indexing, reading EXPLAIN), Redis, ClickHouse, Prisma / Drizzle, zero-downtime migrations
Infrastructure
04
Docker, Kubernetes, Terraform, AWS (ECS / RDS / S3 / CloudFront), GitHub Actions, Grafana + Loki + OpenTelemetry
06 / Experience
Eight years, four companies, one direction
— Built the payment gateway in Go, 4k RPS at peak
— Introduced trunk-based development and preview environments; release cycle from 2 weeks to 1 day
— Hired and grew two mid-level engineers into seniors
07 / Open source
Two tools I maintain in the open
Audit-log plugin for Drizzle ORM. Tracks row-level changes with zero schema boilerplate.
1.4k ★
40k downloads / mo
GitHub Action that spins up a per-PR preview environment and tears it down on merge.
620 ★
used in 90+ repos
08 / How I work
Four steps, no three-month branches
01
Audit
I read the code and the metrics before proposing anything. Output is a written document: risks, estimate, plan.
02
Skeleton
Data schema, API contracts, module boundaries. Agreed before the first line of UI.
03
Ship
Weekly slices to production behind a flag. No three-month branches.
04
Handover
README, ADRs, dashboards, on-call runbook. I leave so the team does not have to call.
09 / What they say
What the people who paid say
“He took over a payments stack nobody could reconcile and made it predictable within a quarter. Explains technical decisions in a way the CFO follows.”
ANA Wotstak · CTO, Ledgerly
“Rare case where one person does the frontend and the backend and both are good.”
Mark Qiubert · Head of Product, Northwind
Available for new projects
Two days a week are already booked. Talk early if the timeline matters.
10 / FAQ
Questions I get before the first call
If yours is not here, write — I answer within a day.
Both. Solo, I take products up to roughly four months of work; on teams I usually lead an area or own one hard piece.