01
Payments arrive. Access doesn't.
Implement and repair billing workflows, webhook handling and account provisioning.
Work directly with Josué Barros
Senior engineering for your existing product.
I implement backend features, repair integrations and improve reliability. Monthly engineering capacity, written updates, and direct collaboration through your issue tracker.
Submit your project for review →No introductory call required. No payment to submit a brief.
Move the engineering backlog forward.
02
Your systems disagree.
Build and maintain API integrations, data synchronization and reliable background jobs.
03
The AI demo worked. Production doesn't.
Improve retrieval, response times and usage controls in an existing AI feature.
Best fit: SaaS teams and agencies with an existing product, a prioritized backlog and recurring engineering work.
MONTHLY ENGINEERING
An engineer who stays with the product.
Work directly with me on your backlog: implementation, tests, pull requests and handover. We agree on priorities and available hours, then track progress in your existing tools.
Start with a paid implementation trial: one bounded task, a written scope and acceptance criteria. The trial has a separate quote agreed before work begins. Continue monthly if the collaboration fits.
Monthly engineering engagement
$10,000 USD / month
- Up to 80 engineering hours per month
- Implementation, tests, code review and documentation
- Written progress updates and tracked delivery hours
- Direct collaboration in your repository and issue tracker
Availability and start date are confirmed before payment. Planning, project communication and any agreed meetings count toward the 80 hours. Additional hours require written approval and a separate quote. Renewal, cancellation and unused-hour terms are agreed in the contract. No unlimited workload or 24/7 support.
From a written brief to working code.
1. Share your backlog
Describe the product, stack and first task. I reply by email with questions and availability; we arrange repository or task review if needed.
2. Start with a paid task
We agree on a bounded implementation trial, price, access and acceptance criteria. You receive code, tests and a written handover.
3. Continue monthly
If the collaboration fits, reserve monthly engineering capacity. Priorities, progress and decisions stay visible in tickets and pull requests.
Inspect the engineering.
Background & experience →Public engineering projects, not client case studies or promised business results.
Production RAG ↗
Retrieval, grounding checks and usage budgets for an AI application.
Read the source
Webhook incident lab ↗
Signed webhooks, delivery retries and observability in Go.
Read the source
Warehouse service ↗
An exploration of outbox/inbox patterns and consistency across services.
Read the source
Before you send a brief
Do I need to get on a sales call?
No introductory call is required. We qualify the work and agree on scope in writing. Day-to-day coordination happens through tickets, pull requests and written updates. Any useful technical meeting is arranged in advance.
What does the paid trial include?
One agreed implementation task with acceptance criteria, tests and a written handover. Its price and deadline are quoted separately before work starts. The trial is not a consulting report or a promise to complete an unspecified backlog.
What does the monthly fee cover?
Up to 80 hours of scheduled engineering work, including implementation, tests, review, documentation and project coordination. We prioritize the backlog together. The fee reserves capacity; it does not guarantee that every requested feature fits into one month.
Can I start with a single project?
Yes. Send a concrete task or project for review. I can quote a bounded implementation separately; a monthly engagement is optional.
Can you respond to an emergency?
This is scheduled engineering work, not a 24/7 incident-response service. Availability, response expectations and any meetings are agreed before the engagement starts.
FIRST STEP
What would you like me to build or fix?
I’ll review your brief and reply by email. Please share a high-level description only—no passwords, API keys, customer records or confidential code.