Full-Stack Developer
frontend, backend,servers and deploys.
I design, build, ship and maintain business-critical, high-concurrency web systems: interfaces, backend, frontend, servers and operations.
Design
Context boundaries, API contracts and trade-offs settled up front.
Build
Strict typing, bounded transactions and idempotent writes.
Management
SLOs with error budgets, declarative IaC and rehearsed rollback.
Available for architecture and platform work
Pablo José Ascanio
Software engineer with 10 years building and operating production web systems. I cover the full cycle: from the domain model to the server that keeps it running.
I work the whole system: interface, API, data and the infrastructure that runs them. I administer Linux servers, TLS, reverse proxies, deployment pipelines and ongoing management.
- Nationality
- 🇻🇪 Venezuelan
- Based in
- Venezuela · UTC-4
- Working mode
- Remote, async-first
Frontend Backend Servers CI/CD Operations
Selected work
Systems built
Software running in production, built for clients who own the source. That is why nearly every repository is private: instead of code, you get the architecture, the stack, the engineering decisions holding each system up, and screenshots of the product at work.
e-IBS Core BankingScreenshot pending
Private repository e-IBS Core Banking
2026Modular modernisation of a legacy banking core
- Java 21
- Spring Boot
- Angular
- PostgreSQL
- Docker
Private repository 2 Electorium
2026Anonymous, verifiable electronic voting on a purpose-built blockchain
- Go
- Templ
- SQLite
- RSA · SHA-256
- Tailwind
Public repository ZIOM
2026Agent council that decides whether code should be written at all
- Go
- Multi-agente
- ADR
- MIT
EchoPressScreenshot pending
Private repository EchoPress
2026White-label editorial CMS built to replace WordPress
- React 19
- TanStack Start
- TypeScript
- PostgreSQL 16
- Docker
Private repository Sierrane
2026Sales and collections management on Laravel 12
- Laravel 12
- Livewire 4
- Flux UI
- PostgreSQL
- Tailwind
Private repository Safipuv
2026Church administration migrated off Filament
- Laravel 12
- Livewire 4
- Alpine.js
- PostgreSQL 15
- Pest 4
Private repository Iglesia Total
2026Records, treasury and audit rebuilt on TanStack Start
- TanStack Start
- Drizzle ORM
- PostgreSQL 17
- better-auth
- shadcn/ui
Private repository IPUV.org
2026Institutional portal running on the EchoPress platform
- React 19
- TanStack Start
- PostgreSQL
- Docker
Private repository Piano IPUV
2026Piano chord study app with an interactive keyboard
- React 19
- TanStack Start
- PostgreSQL
- Docker
Engineering Competencies
Technical Mastery Matrix
The language is chosen for the problem, not out of habit. Here is what I build each layer with — from transactional processing to the interface — and what each tool actually solves best.
Backend & Systems
Server-side languages: business domain, data, processing and APIs.
9 technologiesPHP
The workhorse for management systems: invoicing, inventory, collections and admin panels that run every single day.
- PHP 8
- Composer
- PSR-12
- Pest
Java
For systems where a bug costs money: banking cores, transactional processing and services expected to run for years without a rewrite.
- Java 21
- Spring Boot
- JPA
- Maven
Python
Where the job is moving and reshaping data: batch processing, reconciliation, automation and integrations between systems that do not talk.
- Python 3
- Django
- Pandas
- CLI
Rust
When performance and memory safety are non-negotiable: the compiler rejects entire classes of bugs before they ever reach production.
- Rust
- Cargo
- Tokio
- CLI
Go
Services that compile to a single binary and deploy with no dependencies: ideal for running on the client site, even with no network.
- Go
- Templ
- Goroutines
- SQLite
JavaScript
The one language that runs in the browser and on the server: a single data model and a single validation shared by both halves of the product.
- Node.js
- TypeScript
- ESM
- Vite
Backend frameworks
What keeps you from rewriting authentication, permissions, migrations and queues on every project.
Laravel
The framework that takes a management system from zero to production fastest: authentication, queues, permissions and admin panel already solved.
- Laravel 12
- Livewire 4
- Eloquent
- Pest
Django
When the system lives off its data: the admin panel is generated from the model, so back-office management exists from day one.
- Django
- DRF
- ORM
- PostgreSQL
Spring Boot
The banking and enterprise standard on the JVM: transactions, security and legacy integration with guarantees an auditor will accept.
- Spring Boot
- Spring Security
- JPA
- Maven
Frontend & UI Architecture
Platform fundamentals, language, tooling, state and quality.
13 technologiesHTML
The platform ships native dialogs, popovers and disclosures. Using them removes kilobytes of brittle JavaScript and the accessibility bugs every UI library dragged along.
- <dialog>
- Popover API
- ARIA
- Forms
CSS
Nesting, :has() and container queries made preprocessors obsolete. A component adapts to its container instead of the viewport, and @layer ends the specificity wars for good.
- :has()
- @container
- @layer
- Grid
TypeScript
Dynamic JavaScript accrues debt because nobody refactors blind with confidence. Strict typing turns the backend contract into something the compiler checks, rather than something you hope holds.
- TypeScript
- strict
- Zod
- Generics
Tailwind CSS
It kills bloated stylesheets full of dead code and the runtime cost of CSS-in-JS. Only the classes you use get compiled, so there are no global collisions and no CSS nobody dares delete.
- Tailwind v4
- Tokens
- Dark mode
- No runtime
Vite · Rolldown
Replaces Webpack and Babel pipelines that took minutes to boot and configs nobody wanted to touch. With the bundler rewritten in Rust, the edit-and-see cycle stops being a bottleneck.
- Vite
- Rolldown
- HMR
- ESM
TanStack Query
Fixes the anti-pattern of stuffing network responses into a global store. Loading states, errors, deduplication and revalidation stop being hundreds of race-prone lines.
- TanStack Query
- Caching
- SWR
- Optimistic UI
Playwright
Ends the flaky suites that depended on arbitrary waits. Auto-waiting and hermetic browser contexts make end-to-end tests something you can actually trust to block a deploy.
- Playwright
- E2E
- Tracing
- CI
Frontend frameworks
They decide where rendering happens and how reactivity is orchestrated. The stack above holds them up.
React
The base everything I build on TanStack Start runs on. With Server Components the heavy logic moves back to the server and the browser only receives what genuinely needs to interact.
- React 19
- TanStack Start
- RSC
- Hooks
Next.js
Server Components run data access on the server and ship zero JavaScript for every non-interactive component. No more megabytes just to paint a nearly static view.
- Next.js
- RSC
- SSR
- Streaming
Astro
Not every site needs to be an SPA. Islands architecture ships plain HTML and hydrates only what genuinely interacts, which is what keeps Core Web Vitals healthy.
- Astro
- Islands
- SSG
- Core Web Vitals
Livewire
Reactive UI without standing up a separate client app. State lives on the server, so there are no two data models to keep in sync and no intermediate API to maintain.
- Livewire 4
- Blade
- Alpine.js
- Flux UI
FilamentPHP
Stands up a full admin panel over Laravel in hours: resources, tables, forms and permissions already solved. The price is coupling your interface to the package release cycle, and that is a call to make deliberately.
- Filament
- Resources
- Tables
- Forms
Angular
A fully opinionated framework: dependency injection, routing, forms and HTTP all come decided. On large teams that stops every module from inventing its own architecture.
- Angular
- RxJS
- Angular Material
- DI
Databases
Engines, cache and data models: where state lives and under what guarantees.
6 technologiesMySQL
The engine already running in most of the legacy systems I inherit. Migrating away is rarely the answer: the answer is understanding the indexes and the queries someone left unoptimised.
- MySQL
- InnoDB
- Indexes
- EXPLAIN
PostgreSQL
My default when the data matters. Constraints, transactions and serious types let business rules live in the database instead of depending on every application remembering to enforce them.
- PostgreSQL 17
- PL/pgSQL
- CTEs
- Indexes
MongoDB
It fits when the schema changes often and each document is read whole: catalogues, events, logs. It stops fitting the moment you need to join collections or guarantee consistency across them.
- MongoDB
- Aggregation
- Documents
- Indexes
SQLite
A complete database inside one file, with no server to administer. It is what lets a system run on the client site with no network and no dependency on someone else’s infrastructure, as in Electorium.
- SQLite
- WAL
- Embedded
- Offline
Redis
It absorbs the repeated work that never needed to reach the database: sessions, cache, queues and rate limits. Used well, half a system’s slow queries simply stop running.
- Redis
- Cache
- Queues
- TTL
JSONB
PostgreSQL’s binary document type: it stores flexible structures and indexes them with GIN, without leaving SQL. It saves you from running a separate document store just because a few fields vary.
- JSONB
- GIN
- PostgreSQL
- Flexible schema
Working environment
Tools and platforms
What I work with every day and why each one is there. There is no commercial arrangement with any of them: these are working decisions, not sponsorships.
- Code and review
GitHub
Source of truth for the code and the history of every decision: branches, reviews and continuous integration actions.
- Containers and registry
Docker
The environment is declared once and runs the same on my machine, the client’s and the server. A deploy means pulling a tagged image, not rebuilding in production.
- DNS, CDN and edge
Cloudflare
DNS, certificates and caching in front of the origin server. It absorbs traffic and attacks before they reach the machine actually holding the application up.
- APIs and contracts
Postman
Where an API is exercised and documented before the frontend depends on it. Collections leave the contract written down and runnable, not buried in a chat.
- Development environment
JetBrains IDEs
PhpStorm, IntelliJ and GoLand understand the whole project, not just the open file: renaming a method across the codebase stops being search and replace.
- Knowledge base
Obsidian
Architecture decisions and incident notes are written to plain local files, linked to each other and dependent on nobody’s service.
- Network and privacy
Mullvad
Remote access to client infrastructure over WireGuard, from a provider that keeps no logs and requires no identity to operate.
Operating systems
Where it all runs
Desktop and server on the same system family: what compiles on the development machine behaves the same in production, and the differences are decisions rather than accidents.
Server OS
Where the system lives in production: long support and predictable change.
- Primary server
Ubuntu Server 24.04 LTS
Where the systems I administer actually run: supported to 2029, predictable repositories, and the base Docker, Nginx and the certificates sit on.
- Enterprise server
Red Hat Enterprise Linux
The standard when a client demands contracted support and certifications: banking, health and public bodies that need someone accountable on the other end of the line.
- RHEL pre-production
CentOS Stream 10
The branch that feeds RHEL: it lets you test against what the enterprise server will receive next cycle, before it reaches the client.
Desktop OS
Where it is written and tested: recent tooling and parity with the server.
- Development desktop
Ubuntu Desktop 26.04 LTS
The desktop counterpart to the server: the same library versions, so what compiles locally compiles the same way in production.
- Leading-edge desktop
Fedora Workstation 44
Recent kernel and toolchain, to try today what reaches RHEL two years from now. It is the Red Hat ecosystem test bench, not a long-term support system.
- Workstation
macOS 26
The machine I design, write and connect to infrastructure from. Unix underneath, so the same terminal tooling as on the server.
Infrastructure
Where it gets deployed
Every project ships where its load and its budget justify. These are the platforms I administer and the reasoning behind choosing between them.
Scalable cloud
Capacity that follows demand and is paid for by use.
- Per-instance cloud
AWS · EC2 y Lightsail
EC2 when the system needs to grow or shrink with demand, and Lightsail when a project just needs one predictable machine at a fixed price.
- Droplets and deployment
DigitalOcean
The middle ground between price and control: clean instances in minutes, without the configuration surface of an enterprise provider.
- European compute
Hetzner
The best resource-to-cost ratio on the market, with EU data centres. For sustained workloads the saving against the big clouds is an order of magnitude.
Dedicated servers
Fixed resources, full system control and predictable cost.
- Dedicated server
ArtiakCloud
A machine with fixed resources and full system access: no neighbours sharing CPU and no limits imposed by the provider panel.
- Managed hosting
Hostinger
For sites that do not justify running a whole server: domain, mail and deployment solved without weekly maintenance.
- Regional server
DonWeb
Infrastructure and domains in Latin America, with local support and billing. Lower latency for regional users and paperwork that does not cross borders.
Also on hand
Assets carry weight too
A fast site does not come from code alone: it comes from every image shipping in the right format, size and compression. I prepare the assets myself — SVG for vectors, WebP and AVIF for photography, WebM for video — instead of publishing whatever the designer sent.
- Vectors and SVG
Adobe Illustrator
Logos and icons exported as SVG: a few kilobytes, sharp on any display, and inheriting the theme colour instead of needing one light and one dark version.
- Imagery and optimisation
Adobe Photoshop
Cropping, retouching and export to WebP or AVIF at the exact size it renders. A badly exported photo can outweigh every line of code on the page.
- Identity and print
CorelDRAW
Many clients hand over their brand as legacy .cdr files from their print shop. Being able to open and convert them to web formats avoids rebuilding an identity from scratch.
Capabilities
The full cycle
From the first conversation to year-three maintenance. Every stage rests on the stack, the infrastructure and the systems shown above on this page: follow the link and check it.
-
Let’s talk
01It starts with a conversation, not a quote. Understanding the real problem, the constraints and what happens if it goes unsolved usually changes the solution before the first line is written.
- Descubrimiento
- Alcance
- Restricciones
- Riesgos
-
Architecture
02I model the domain and settle boundaries and contracts before any code. Decisions are written down with their trade-offs, so they can be argued and reversed without archaeology.
- Límites de contexto
- Contratos de API
- Modelado de dominio
-
Build
03Interface, API and data as one system typed end to end: bounded transactions, idempotent writes and queries that do not grow unchecked.
- TypeScript
- Laravel
- Go
- React
-
Data
04Business rules live in the database, not in the hope that every application honours them. Cache absorbs the repeated work so the engine only does what matters.
- PostgreSQL
- MySQL
- Redis
- JSONB
-
Delivery
05From container to domain: reproducible environments, TLS, reverse proxies and deploys that repeat identically and roll back without drama.
- Docker
- Nginx
- Cloudflare
- CI/CD
-
Management
06A delivered system is not a finished one. Administered servers, backups proven by restoring them, and evolutionary maintenance for as long as the product lives.
- Linux
- Observabilidad
- Respaldos
- Rollback
Testimonials
The people who use the systems
The people who open these systems every day to do their work. No scores and no stars: what they describe is what changed in their routine once the system went live.
-
We used to close the month going through notebooks and calling each collector one by one. Now I open the system and the balance is right there, with who paid and who did not. What I appreciate most is that when something does not add up, Pablo looks at it the same day.
Vilma Mejías Administration — Sierra Nevada Sierrane -
I asked for something simple so the kids could study chords without depending on me. It turned out better than I pictured: they go in, pick a note and see the keyboard. Several of them now practise on their own at home, and that never used to happen.
Teudis Hernández Music education — Piano IPUV Piano IPUV -
The weekly close used to take me a whole afternoon between spreadsheets. Today I do it in a while and the daily ledger balances. When we asked for a change in the accounting codes, we did not have to explain twice what it was for.
Brenda Camacho Treasury — IPUV Cordero Central Iglesia Total -
We came from a system where every update broke something. Pablo rebuilt it and since then we have worked without worry. It is not just that it works: it is that you ask a question and someone answers who understands the problem.
Oswald Rondón Administrative coordination — Safipuv Safipuv -
The trial went perfectly. The terminals ran with no internet all day and at closing we had the results with their backup. Being able to show that every vote was recorded and that nobody knows who voted for what — that is what convinced people.
Juan Colmenares Electoral process coordination Electorium
Contact
Let’s talk architecture and product
If you need to sort out an architecture, build a product or stabilise a platform already running in production, tell me the problem. You get an honest read back: whether I can solve it, what I would do first, and how long it takes.
- pabloascanio.dev@gmail.com
Email
For proposals, scope and anything worth putting in writing.
- +58 424 730 5392
WhatsApp
For a short conversation about something specific.
- pabloascanio-dev
LinkedIn
Track record, recommendations and professional contact.
- @pascaniodeb
GitHub
Public repositories and open source.