Herycklys Gonçalves
EN / PT

Based in Brazil · Working with US & EU teams

Backend systems that are fast, correct, and boring to operate.

I’m a senior backend engineer with 10+ years in fintech, HR tech, media and e-commerce. My focus is correctness at scale — systems where a quiet bug means lost money or trust, not a cosmetic defect.

Production systems at Deel · Nubank · Imgur · eBay · CVC

SERVICES

You bring the problem. I’ve solved it before.

Every engagement starts with your problem, not a tech stack. Here’s what I take on, and where I learned to do it.

01 · PAYMENTS

Money-movement you can trust

Refunds, settlement and balances that finance has stopped trusting.

I build payment backends that are correct first and auditable by default — idempotent, reconciled, and safe to retry across asynchronous, distributed services.

For: Fintechs, marketplaces, SaaS billing

02 · DATA AT SCALE

Pipelines over billions of rows

Your data outgrew the job that processes it.

I design pipelines that stay fast and correct as volume grows — real-time processing, safe re-runs, and changes validated in production before they replace what works.

For: Data-heavy products & platforms

03 · INTEGRATIONS

Connecting to the systems customers already run

Every new customer needs another integration, and each one breaks differently.

I build integration layers with clear contracts between your platform and third-party systems, so onboarding a customer stops being a custom project.

For: B2B SaaS & platforms

04 · MODERNIZATION

Legacy migrations without the drama

The old stack is expensive to run and scary to change.

I move services to a better language or infrastructure piece by piece, with production traffic flowing the whole time — and the cost savings to show for it.

For: Teams carrying legacy code or infra

ABOUT

Ten years of systems where failure is expensive.

I’m Herycklys, a backend engineer from São Paulo, Brazil. I’ve spent my career on the parts of big products that have to be right: payments, trust and safety, integrations and the infrastructure underneath them.

Outside of work: reading, long runs, and occasionally shipping personal projects that scratch an itch.

GoClojureTypeScriptKubernetesPostgreSQLKafkaElasticsearchDatadogAWS
  1. Deel · Senior Back End Developer 2026 — Now
    The integrations layer of a global HR platform

    Integrations, the marketplace app and its migration to new infrastructure; now on AI evaluation tooling.

    HR Tech · Integrations · AI

  2. Nubank · Senior Software Engineer 2025 — 2026
    Payments that have to be right

    Refund and settlement flows on NuPay for 200+ merchants, the merchant KYC onboarding service, and internal AI tooling.

    Fintech · Payments · Clojure

  3. Imgur · Senior Software Engineer 2022 — 2025
    Trust and scale for 3M+ daily users

    Real-time trust-and-safety pipelines, media transcoding at 10TB+/day, sitemaps over 6B+ entries, and the move from PHP to Go and EC2 to Kubernetes.

    Media · Go · Kubernetes

  4. Avenue Code → eBay · Software Engineer 2020 — 2021
    SEO tooling for millions of product pages

    Internal SEO tooling that cut operational errors, and the team that grew to own eBay’s SEO tooling experience.

    E-commerce · SEO

  5. CVC Corp · Software Engineer 2019 — 2020
    Checkout for Latin America’s largest travel company

    New checkout and the BFF to the internal payment provider, as part of a redesign that improved conversion.

    Travel · Checkout · Next.js

2015 — 2019 · Earlier: technical lead at SourcerDigital, plus full-stack roles at Kenoby, Sciensa, Aktie Now and Docpix.

HOW I WORK

Small engagements, clear outcomes

  1. Step 1 · Free · 30 min

    Discovery call

    You describe the problem; I tell you honestly whether I’m the right person for it.

  2. Step 2 · Fixed scope

    Diagnosis & plan

    I dig into the system and come back with the target outcome, the approach and a fixed price.

  3. Step 3 · Ship safely

    Build, verify, hand over

    Run old and new side by side before cutover, leave documentation your team can own, and show the before/after.

READY TO START?

Not sure where the problem is? That’s usually where we start.

LinkedIn · GitHub