Available for backend opportunities

I build systems that stay reliable when things get busy.

I’m Ebube Chika, a backend engineer focused on scalable APIs, payments, multi-tenant systems, queues, data workflows, and the infrastructure behind modern web products.

View selected work Get in touch ↗

profile.json

{
  "role": "Backend Engineer",
  "experience": "7+ years",
  "stack": [
    "Node.js", "NestJS",
    "PostgreSQL", "Redis",
    "AWS"
  ],
  "focus": "Reliable systems"
}
SCROLL

Selected work

Products and systems I’ve worked on.

01 Hospitality · SaaS

Orbitverse

A multi-tenant hotel operations platform covering bookings, rooms, guest-facing hotel websites, payments, reporting, staff workflows, and operational action items.

  • NestJS
  • PostgreSQL
  • Redis
  • Paystack
  • AWS S3
↗
02 Survey · SaaS

SurveyBuddy

A visual survey builder with node-based flows, access controls, publishing validation, analytics, themes, and multiple response experiences.

  • Next.js
  • NestJS
  • React Flow
  • Redis
  • Clerk
↗
03 Fintech · Infrastructure

Hydrogen

Backend and platform work across fintech products, API proxying, permissions, deployment environments, payment-adjacent workflows, and production debugging.

  • Node.js
  • Next.js
  • Azure
  • TypeScript
  • APIs
↗

About

I care about what happens after “it works.”

My work sits mostly behind the interface: APIs, data models, background jobs, payments, permissions, caching, webhooks, event-driven workflows, and the boring-but-important details that keep software dependable in production.

01

Backend

Node.js, NestJS, TypeScript, REST APIs, WebSockets

02

Data & async

PostgreSQL, Redis, Bull queues, events, webhooks

03

Cloud & delivery

AWS, Azure, Docker, CI/CD, S3, production debugging

04

Product engineering

Multi-tenancy, payments, permissions, SaaS architecture

Contact

Have a backend problem worth solving?

I’m open to backend engineering roles, product collaborations, and interesting technical conversations.

Email me GitHub ↗ LinkedIn ↗

Replace the email, GitHub and LinkedIn links in index.html before publishing.