Work with me

Senior backend engineer for fintech, payments and crypto.

I design and build the money-moving backends regulated companies run on, and I lead the teams that ship them. Available for contract work, fractional tech lead roles and full-time remote positions.

Tell me about your project →Download CVDubai, UAE · remote worldwide · contact@amahkudi.dev
01

Who I work with

Fintech and payments teams

Card programs, wallets, crypto-to-fiat rails, ledgers and reconciliation. Systems where a silent drift is a compliance incident.

Crypto exchanges and custody providers

Custodial wallets, multi-chain integration (EVM, Tron, Bitcoin), provider-agnostic custody (Fireblocks, Liminal) and withdrawal pipelines in regulated environments such as VARA.

Founders with a product to ship

Greenfield backends built right the first time: Clean Architecture, event-driven where it pays off, deployed to AWS with CI/CD from day one.

Teams that need a lead

Roadmap, backlog, sprints, code review and turning regulatory obligations into shippable specs. I have led teams of six through a legacy-to-microservices rewrite.

02

Ways to engage

Typically 4–16 weeks

Project contract

A scoped build or integration with a fixed deliverable: a payment backend, a custody integration, a migration off a monolith. Fixed-scope or day rate, agreed after the intro call.

Monthly, 3-month minimum

Fractional tech lead

Two to three days a week owning architecture, reviews and delivery for a team that has engineers but no senior backend owner.

Permanent

Full-time remote

Senior backend or team lead roles with companies building in fintech, payments or crypto. Dubai-based, remote worldwide.

03

How a project runs

  1. / 01

    Intro call

    30 minutes on what you are building, the constraints and what done looks like. No charge.

  2. / 02

    Written proposal

    Scope, architecture outline, milestones, risks and price within a few days of the call.

  3. / 03

    Build in the open

    Two-week sprints with a demo at the end of each, a shared board and code in your repository from the first commit.

  4. / 04

    Handover that holds

    Runbooks, architecture notes, tests and a recorded walkthrough so your team owns it after I leave.

04

Recent work

All projects →
05

Questions people ask

What do you charge?
Project work is quoted as a fixed price for a defined scope or as a day rate for open-ended work. Fractional lead roles are a monthly retainer. I send a written quote after the intro call, once I understand the scope and constraints.
Are you available now?
I take on a limited number of engagements alongside my current role so each one gets real attention. Send a few lines about the project and I usually reply within two working days with my earliest start date.
Which time zones do you work with?
I am based in Dubai (GMT+4), which overlaps the full working day in Europe and Africa and the morning in East Asia. For US teams I keep East Coast morning hours for meetings.
Do you work remotely?
Yes. Most of my work is remote with companies in the UAE, Europe and Africa. I am also open to on-site and hybrid work in Dubai.
What stack do you work in?
Node.js with NestJS and TypeScript, ASP.NET Core with C#, and Python. PostgreSQL, MongoDB and Redis for data. AWS (ECS, Lambda, RDS, S3), Docker, Kubernetes and Terraform for infrastructure. React, Next.js and React Native when the project needs a front end.
Can you integrate crypto custody or blockchain rails?
Yes. I have integrated EVM chains, Tron and Bitcoin, built custodial wallet infrastructure, and worked with Fireblocks and Liminal behind a provider-agnostic custody layer for a VARA-regulated exchange.
Will you sign an NDA?
Yes. Much of my past work is under NDA, which is why some case studies on this site describe the architecture without naming the client.
How do we start?
Use the form below or email contact@amahkudi.dev with what you are building, your timeline and the stack. I will reply with a few questions and propose a 30-minute call.
06

Tell me what you're building.

A few lines about the product, the timeline and the stack is enough to start. I reply with questions and a proposed call.