podk1dish

I work on Go backend systems where reliability matters: APIs, payment workflows, transaction processing, and integrations that need to survive failures.
I can help you troubleshoot an existing service, fix recurring bugs, improve test coverage, or build a backend component with clear behavior and reliable recovery.

What I can help with:
- Go backend development: REST APIs, microservices, PostgreSQL, Redis, message queues, and third-party integrations.
- Debugging and maintenance: production issues, refactoring, unreliable tests, and problems that only appear under specific conditions.
- Payment and transaction workflows: idempotency, retries, state transitions, durable processing, and recovery after failures.
- Blockchain integrations: EVM transactions, RPC handling, event indexing, confirmation tracking, and chain reorganizations.
- Testing and delivery: integration tests, Docker, CI/CD, and reproducible local development environments.

My engineering portfolio
My public GitHub includes five technical demonstration projects exploring real backend reliability problems:
- Transaction Orchestrator: transaction submission, nonce management, and recovery after RPC failures.
- SettleKit: ERC-20 escrow payments, confirmation tracking, and signed webhooks.
- ReorgGuard: blockchain event indexing and reorganization recovery.
- BridgeWatch: cross-chain message monitoring and delivery reconciliation.
- Gasless Policy Engine: ERC-4337 transaction sponsorship, authorization policies, and budget controls.

How I approach projects
I prefer understanding the existing system before changing it. I focus on clear requirements, reproducible failures, targeted changes, and tests that demonstrate the expected behavior.

If you have a Go service that needs debugging, a payment workflow that needs to become more reliable, or a blockchain integration that needs careful implementation, I'd be happy to discuss the problem and identify a practical next step.