Backend troubleshooting
Unexpected errors, failing jobs, or behavior that’s difficult to reproduce. Trace the cause, agree on a fix, and verify the result.
Independent software engineer · Florida
Get your backend
back on track.
PHP and Laravel troubleshooting, API integrations, and focused fixes for agencies and small teams. I help you understand what’s failing and get it working.
A clear scope, an agreed price, and a documented handoff.
10 years of software engineering experiencePHP / Laravel / Vue / WordPress / MySQL / AWS
01 / How I can help
Focused help for the
problem in front of you.
API integrations
Connect systems and make failures easier to recover from, with validation, useful error reporting, and safe retries where needed.
Scoped improvements
A specific issue in an existing PHP or Laravel application. Get a bounded piece of work delivered with notes your team can use.
02 / Selected work
A failed delivery.
A safe way forward.
Order Delivery Monitor is an independent Laravel and Vue demonstration of a common integration problem: an order needs to reach another system, even when requests fail.
Try the live demoPortfolio demonstration, not client work. All customer and order data is fictional. The fulfillment API is simulated. Each browser gets a temporary workspace, and inactive orders expire after about 24 hours.
The problem
A request can fail before an order is accepted—or the response can disappear after it’s accepted. Retrying blindly risks duplicate fulfillment.
The approach
Queue deliveries, record each attempt, and expose failures in an operator dashboard. Reuse an order’s idempotency key so the receiver recognizes repeat deliveries.
The verified behavior
Temporary failures recover automatically. An operator can retry after an outage. Lost acknowledgements and repeat requests leave one fulfillment record.
The walkthrough
The receiver stores an order but returns a simulated timeout. The automatic retry retrieves the original record. Sending one more duplicate delivery produces the same result: three requests received, one fulfillment record.
Inside the demonstration
Three requests. One fulfillment.
03 / Working together
Clear from the first step.
Start with the problem.
Tell me what should happen, what happens instead, and the technology involved. We’ll establish whether I’m a fit.
Define scope and price.
We’ll agree on the deliverable, boundaries, price, and timing before work begins.
Leave a useful handoff.
Receive the change, a summary of what was verified, and notes on remaining limitations or next steps.
Let’s talk
What’s holding
your project up?
I’m Benjamin, an independent software engineer based in Florida. Send a short description of the issue and we can take it from there.
A useful first email includes:
- What you’re trying to get working
- Your stack and the symptoms you’re seeing
- Any timing or scope constraints