06:12sunrise

I build systemsthat hold upunder load.

Full Stack Engineer, MERN and MEAN. Five years of Node.js microservices, Kafka streams and Socket.io real-time, with React and Next.js dashboards on top. Currently leading backend architecture at A4Next GmbH in Kiel.

Full Stack Engineer — MERN / MEANKiel, Germany

Scroll — the sun moves with you

09:40morning

Half of the job is the part nobody sees.

I design and build the backends that everything else leans on — Node.js microservices, REST and GraphQL APIs, Kafka event streams, Redis clusters, Socket.io pushing state to whoever is watching. Then I build the React and Next.js dashboards that make all of it legible to the people who actually use it.

Most of my work has been taking something manual and making it a system: paper workflows turned into a company-wide ERP, a thrift marketplace turned into a platform with its own mobile app. I care about services that fail in ways you can reason about — clear boundaries, real health checks, Docker and Kubernetes underneath, Prometheus and Grafana telling the truth about what is happening.

I live in Kiel with a Niederlassungserlaubnis, so no sponsorship required anywhere in the EU. German at B1 and climbing. Away from the keyboard it is coffee, long reading, and trains going somewhere I have not been.

Years shipping
5+
Primary stack
Node · React · Next · MongoDB
Based in
Kiel, Germany — CET
Work authorization
Niederlassungserlaubnis (EU)
Languages
English C2 · German B1
Open to
Full-time & contract
12:40midday

The stack, as paper talismans.

Nine emblems, hung on a line. The same ones that float through the scenes on this page.
Node.jsMicroservices & APIs
React · Next.jsDashboards & SSR
TypeScriptTyped end to end
JavaScriptReact Native too
MongoDB · MySQLSchemas & indexes
AWSEC2, S3, Nginx, PM2
Kafka · Socket.ioEvents & real-time
Docker · K8sSwarm, YAML, CI/CD
TailwindWith Framer Motion
15:10afternoon
Odoo ERP · Implementation, customization & rescue

Odoo ERP implementation that actually ships.

Messy spreadsheets and broken rollouts, turned into one clean Odoo system a team actually runs the business on. Every engagement starts with your operations — scoped tightly, delivered incrementally, supported long after go-live.
50+
Projects delivered
8+
Countries served
100%
Client retention
Your operations, unified. From CRM to accounting, connected and configured around your team rather than a generic template.
CRMPipeline & leads
SalesQuotes & orders
AccountingFinancials & reports
InventoryStock & logistics
PurchaseProcurement
ManufacturingProduction flows
ProjectTasks & timesheets
HelpdeskSupport tickets

Implementation, customization, and custom software under one roof.

Odoo Implementation

Full-cycle deployment for businesses replacing spreadsheets or legacy systems. Scoped around your operations, then delivered as a system your team trusts.

  • Needs analysis & tight scoping
  • Module config & clean data migration
  • User training & go-live support

Odoo Customization

Custom modules, automations, validations and reports that fit how the business actually runs, instead of forcing a team into generic templates.

  • Custom modules & logic
  • Workflow automation
  • Reports built around real decisions

Odoo Integrations

Maintained connections to payment gateways, shipping APIs, e-commerce platforms and internal systems, so Odoo stays the single source of truth.

  • REST & token-authenticated APIs
  • E-commerce and payment links
  • Scheduled sync jobs

Odoo Support & Rescue

Ongoing support, optimization, and rescue work for stalled, broken or underperforming Odoo implementations inherited from another vendor.

  • Failed-rollout recovery
  • Monthly development capacity
  • Odoo.sh releases & maintenance

Portals, APIs & Custom Systems

Operations dashboards, customer portals, approval workflows and purpose-built internal tools for teams that need software shaped around how they work.

  • Operations dashboards
  • Approval & handoff workflows
  • Customer and dealer portals

Take Odoo live without rollout guesswork.

A clear rollout plan, working demos, clean data migration and team training — before Odoo becomes business critical.

01

ClarifyStart with the right scope

Map today's workflows, spot the gaps, and agree the first Odoo release before configuration begins.

Release scoped

02

PlanPlan the launch path

Milestones, owners, data needs and risks up front, so decisions do not slow the project later.

Risks covered

03

ValidateApprove real workflows

Configure, migrate, test and train against real scenarios, so the team signs off each workflow with confidence.

Flows approved

04

LaunchGo live with support ready

Support the cutover, document the handover, monitor adoption, and plan the next improvements after launch.

Launch supported

What sets this apart from a generic agency rollout.

Odoo plus custom software

ERP implementation and custom internal tools from the same hands, so your systems work together instead of around each other.

Workflow-first, not module-first

Every project starts with your actual operations, not a module checklist. How the team works gets mapped before a line of config is written.

Remote delivery that stays in sync

Written handovers, documented decisions and real overlap hours, so distance never becomes the reason a rollout stalls.

Built for real complexity

Multi-entity structures, cross-border logistics, custom approvals. The build assumes complexity rather than fighting it.

A partner, not a vendor

Engagement continues through support, iteration and new requirements, so systems keep improving instead of drifting back to manual work.

The work goes deepest where operations are genuinely tangled — stock, production, approvals and money all moving at once.
  • Manufacturing & maintenance
  • Wholesale, retail & distribution
  • Food, beverage & catering
  • Packaging, printing & paper
  • Architecture & design studios
  • Digital & professional services
17:30golden hour

Four things I built and still stand behind.

20:10nightfall

Real projects, real operational outcomes.

From a rescued rollout to a multi-dealer platform, here is the shape of the work: what was broken, what got built, and what changed afterwards.

Odoo Rescue · Digital organizing · United States

Tidy Haus

A failed rollout, rescued into a working operation

A US home-and-digital organizing company inherited a failed Odoo implementation from another vendor. Client workflows, invoicing and project management were broken, and the CRM ran on default stages that had nothing to do with how bookings actually moved.

What got built

  • CRM restructured around the real customer journey
  • Custom pipeline stages for booking readiness
  • Inquiry → booking → follow-up connected in one flow
  • Lead and opportunity records reorganized for daily use
  • Recurring friction points resolved as they surfaced
  • Ongoing monthly Odoo development and support

What changed

  • Live again within weeks of taking the project over
  • A pipeline the team can read without guessing
  • Less confusion between inquiry, booking and follow-up
  • Technical capacity on tap as requirements change
  • Odoo CRM
  • Project
  • Invoicing
  • Custom logic

Odoo + Mobile · Coffee & retail · Saudi Arabia

Hjeen Coffee Roasters

A secure REST API layer between a mobile app and Odoo

Hjeen already ran POS, Sales, Purchase and Inventory on Odoo. Its customer mobile app needed a reliable way to talk to that backend — exposing selected workflows without disturbing daily retail operations, and without spawning a second, disconnected source of truth.

What got built

  • Custom Odoo controllers exposing controlled REST endpoints
  • Endpoints mapped onto existing Odoo business models
  • Custom user management for mobile account flows
  • Two-factor authentication on sensitive access paths
  • Integration across POS, Sales, Purchase and Inventory
  • Deployment, staging and production support on Odoo.sh

What changed

  • Mobile app talking to Odoo through a defined API contract
  • Odoo kept as the operational system of record
  • Password-only access replaced with a second factor
  • Controlled, repeatable releases through Odoo.sh
  • Odoo.sh
  • REST APIs
  • 2FA
  • POS
  • Inventory

Custom platform · B2B2C · Odoo v18

Priminer

A multi-dealer connector across separate Odoo environments

Priminer ran its own Odoo, and each dealer ran a separate one. Dealers needed current catalogs and their own contracted prices, and a dealer sale needed to trigger supplier-side procurement automatically — across system boundaries, with no duplicate data entry.

What got built

  • Product catalog sync: SKUs, structure, content and images
  • Dealer-specific pricelist mapping from contract rules
  • Token-authenticated REST layer between environments
  • Scheduled cron sync keeping both sides current
  • RFQ automation from dealer demand
  • Supplier sales order creation and inventory flow alignment

What changed

  • One catalog as the source of truth across every dealer
  • Repetitive cross-company data entry removed
  • Faster fulfillment from dealer demand to supplier response
  • Pricing that stays accurate, and room to add dealers
  • Odoo v18
  • Custom connector
  • REST API
  • Pricelists
  • Cron
very capable of solving the worst of the challenges with Odoo
DavidFounder & Chief Organizer, Tidy Haus

Need Odoo implemented properly?

Whether it is a new implementation, a recovery from a failed one, or custom internal systems — start with a short conversation and get a practical next step.

  • Free consultation
  • No obligation
  • Reply within 1 business day
21:05night

Where the work happened.

2024 — now

A4Next GmbH — Kiel, Germany

Senior Full Stack Engineer

Backend architecture for a custom ERP: Node microservices, Kafka, AWS, Nginx, and the Next.js dashboards on top.

2023 — 2024

Jumppace

Senior Full Stack Engineer

Directed the microservices split — REST and GraphQL APIs, Socket.io real-time, Docker Swarm and Kubernetes orchestration.

2022 — 2023

Swag Kicks — Karachi, Pakistan

Full Stack Engineer

Thrift ERP from concept to deployment, a full e-commerce launch, a React Native app and custom Shopify apps.

2021 — 2022

iEDGE — Karachi, Pakistan

Full Stack Engineer

In-house CRM and accounts management, plus an audience-interactive game built on JavaScript and Node.

23:47midnight

Tell me what you are building.

I read everything. If it is interesting I answer within a day.
abdulwasayahmed19@gmail.com
Scenes painted with Nano Banana Pro and Seedance. Type set in Zen Old Mincho and Klee One, with JetBrains Mono for the numbers. Built with Next.js.