Open to remote roles in iGaming & crypto
Ilkin Ibadov
Backend developer with over 5 years of experience. I build the systems where money moves — payments, wallets, crypto rails and event-driven services in Go and TypeScript.
Skills & stack
Backend first: the stack behind payment, wallet and event-driven systems.
Programming languages
Backend
Data & messaging
Payments & crypto
Infrastructure
Observability
AI / ML
Languages
- English — C2 — IELTS 8.5
- Russian — fluent
Rates by type of work
| Service | USD / hr |
|---|---|
| Support & maintenanceOn-call fixes, incident triage, dependency updates, monitoring | 35–50 |
| Backend services & APIsGo / NestJS services, gRPC, REST, WebSockets, auth and permissions | 50–70 |
| Payments & wallet systems — Core strengthDouble-entry ledgers, idempotent deposits and withdrawals, balance reconciliation | 60–85 |
| Crypto payment rails — Core strengthUSDT (TRC-20 / ERC-20), BTC, ETH: confirmations, reorg handling, hot/cold wallet flows, Fireblocks | 65–95 |
| Event-driven architectureKafka, RabbitMQ, NATS; CQRS, sagas, outbox pattern | 55–80 |
| Data & storagePostgreSQL, Redis, ClickHouse, MongoDB: schema, indexing, zero-downtime migrations, analytics | 50–70 |
| KYC/AML & third-party integrationsVerification and screening providers, signature-verified webhooks, retries and reconciliation | 50–70 |
| Infrastructure & DevOpsKubernetes, Docker, AWS, Terraform, ArgoCD, GitHub Actions | 50–75 |
| Observability & load testingPrometheus, Grafana, OpenTelemetry, Loki, Sentry; k6 load tests before peak traffic | 50–70 |
| Fraud, risk & AIFraud and risk scoring models, LLM integration (OpenAI, Anthropic), embeddings, RAG | 60–90 |
| Architecture & consultingSystem and security review, high-load design, scaling plans, code review | 75–110 |
★ — areas where my profile delivers the most client value.
Crypto payments preferred. Crypto is my preferred way to be paid, for hourly work and monthly engagements alike.
Engagement models
Full-time employment
$5,000–8,000 / mo
Full-time, full ownership of a domain. Below the hourly equivalent — that discount buys stability and long-term product ownership.
Part-time
from $3,000 / mo
20–25 hrs/week on fixed days. Fits when you need a strong engineer but not a full-time one.
Support retainer
from $1,200 / mo
Agreed hour bank, priority response, security updates. Unused hours roll over one month.
Fixed-price project
estimate +20%
Fixed price where scope is well defined. The premium covers uncertainty risk; hourly work carries none.
Modifiers & conditions
| Condition | Uplift | Why |
|---|---|---|
| Rush — start within 48 hours | +50% | Displaces already-committed work |
| Weekend / night work | +50–100% | Off-hours releases, incidents |
| On-call rotation | +15% of salary | Availability outside the schedule |
| Undocumented legacy code | +25% | Time goes to comprehension before change |
| Long engagement — 3 months+ | −10% | Predictable utilisation |
| Quarterly prepayment | −5% | Removes payment risk |
What the rate includes
Included
- Tests for new code, including retry and failure paths
- Meaningful commit messages and review turnaround
- Deployment, metrics and alerts for what I ship
- Fixing my own bugs — free for 30 days
- Handover: how it works and why it’s built that way
Billed separately
- Scope changes after sign-off
- Meetings beyond one hour per week
- Hosting, licences, third-party services
- Maintaining code I did not write
- Frontend, mobile and design work
Why me
- Money that adds up.Double-entry ledgers, idempotency keys and the outbox pattern: a retried request or a crashed consumer never credits a balance twice.
- Crypto rails end to end.USDT on TRC-20 and ERC-20, BTC and ETH — confirmation thresholds, reorg handling, hot/cold wallet flows and Fireblocks custody.
- Built for peak traffic.Event-driven services on Kafka, RabbitMQ and NATS, load-tested with k6 before a big match or a promo launch sends the traffic.
- Production, not just development.Kubernetes, Terraform and ArgoCD to ship; Prometheus, Grafana, OpenTelemetry and Loki to see what’s happening — the work doesn’t end at merge.
- Risk and compliance in the flow.Fraud and risk scoring and KYC/AML checks sit inside the payment path, not bolted on after launch.
- Fullstack roots.Years of frontend and mobile work mean APIs designed for the clients that consume them — and a back-office UI when the team needs one.
How to read these numbers. The lower bound is a well-defined task in a familiar stack. The upper bound is tight deadlines, unfamiliar code, or a high cost of failure. Rates are negotiable: scope, duration and predictability move them more than the category of work does.
Contact
Leave a message — I'll get back to you shortly