The deploy is not dependable
Releases fail, environments drift, or the team cannot say what is running where. I trace the path from code to running service and remove the fragile parts.
Emergency technical triage
When the system is stuck, I get it moving again.
I diagnose the software problems other developers have put down: failing deployments, fragile infrastructure, tangled integrations, and AI-generated apps nobody can safely maintain.
Based in Spain (CET). Working remotely with teams worldwide.
Production debuggingDeployment recoveryPodman and Linux systemsMaintainable handover
The call comes after
Something important stopped being straightforward.
You do not need a polished brief. You need someone who can enter an unfamiliar system, separate symptoms from causes, and make useful progress without making the situation worse.
The infrastructure grew without a design
Networks, containers, proxies, secrets, and storage have become coupled by accident. I rebuild boundaries so the system is legible and safe to operate.
The AI-built app is now a liability
It appeared quickly, but nobody can change it with confidence. I map the codebase, isolate risk, and turn the next changes into normal engineering work.
How I work
A way through complicated technical problems.
When an application, deployment, or infrastructure setup has become difficult to change safely, I help make sense of it. I work across the code and the systems around it to identify what matters, fix what is urgent, and leave a clearer path forward.
- A failing deployment, a repository, or a short description of the issue is enough to begin.
- I investigate across the application, containers, networking, and deployment setup rather than treating them as separate problems.
- You get a practical view of the risk, the options, and the work worth doing next.
- Whether I implement the changes or hand them to your team, the aim is a system that is easier to run and change.
Technical ground
I work across the boundary between application and operations.
Runtime and isolation
Systems that have edges
Isolated Podman environments, container networking, reverse proxies, service boundaries, permissions, persistent data, and backup paths.
Delivery and operations
Deployments you can reason about
Linux hosts, CI/CD, release workflows, observability, recovery procedures, configuration discipline, and calm operational handover.
Application recovery
Code that can be changed again
TypeScript and Node applications, APIs, integrations, frontend state, testing seams, dependency cleanup, and targeted refactoring.
Good fit
You have a real system and a real constraint.
Good fits include a launch or deployment that is blocked, an app that is failing under real use, a self-hosted stack that needs hardening, or a rushed codebase that needs to become maintainable.
I am not the right fit for speculative builds with no technical owner, indefinite on-call coverage, or a request to conceal avoidable risk. The goal is a system your team understands better when I leave.
Open for triage
Send the messy version of the problem.
Include what stopped working, the deadline or impact, the stack, and what access is possible. A short message is enough to start.
Email hello@hirejorge.com
Use the subject: Emergency triage request