Skip to content
open for freelance work

$ whoami

Hüseyin Akbaş

I build B2B marketplaces, realtime products and the teams behind them.

Ankara, Turkeygithub
neofetch — h4kbas
Portrait of Hüseyin Akbaş

h4kbas@portfolio

uid=1(h4kbas) gid=1(dev)

OS
·Ankara, Turkey / Europe/Istanbul
Kernel
·15+ years shipping software
Shell
·typescript, sql
Focus
·marketplaces, realtime, scale
Languages
·Turkish, English, Italian
Coffee
·████████░░ 82%

50+

Projects shipped

48,600+

Working hours

1,945+

Cups of coffee

[01]$ cat about.md

Engineer, operator, problem solver

I care about systems that survive contact with real users, and teams that keep shipping after the launch postmortem.

Experienced in building and scaling B2B marketplaces, with a strong background in B2B e-commerce, chat applications and startup operations.

Skilled in team management, hiring and streamlining processes. I keep up with tech trends but take a pragmatic approach, opting for custom solutions when necessary.

Highly autonomous and results-driven. I set high standards and focus on execution. Direct and goal-oriented — working with me isn't always easy, but the focus is always on achieving success.

  • Based inAnkara, Turkey
  • LanguagesTurkish, English, Italian
  • Emailh4kbas@gmail.com
  • AvailabilityFreelance / consulting

currently

Building products for clients who need senior judgement, not a body in a standup.

$ git commit -m "ship"

[main 4f2a1c9] availability: open

Direct, high standard, low ceremony. I would rather tell you a hard truth early than discover it in production.

B2B marketplaces & e-commerce

End-to-end marketplace platforms: catalog, pricing, quoting, ordering, fulfillment and the back office nobody wants to build but everybody needs.

  • →Multi-vendor catalog & RFQ flows
  • →Order, invoice & logistics pipelines
  • →Payments, wallets and reconciliation

Realtime & chat systems

Presence, messaging, notifications and live collaboration that stays correct under load.

  • →WebSocket / SSE architecture
  • →Fan-out, delivery guarantees, history
  • →Mobile + web clients on one protocol

Product engineering & scale

From a blank repo to production: domain modelling, APIs, infrastructure, observability and the boring reliability work that keeps it alive.

  • →API design & service boundaries
  • →CI/CD, containers, observability
  • →Performance and cost tuning

Fractional CTO & team building

Hiring, onboarding, process and technical direction for founders who need senior judgement without a full-time seat.

  • →Hiring loops that filter for signal
  • →Roadmaps and delivery cadence
  • →Code review culture & mentoring
[02]$ ls -la ./stack

Tools I reach for, and why

Pragmatic defaults, not dogma. Pick boring technology for the core, sharp tools at the edges.

TypeScript◆C#◆Node.js◆React◆Next.js◆PostgreSQL◆Redis◆Docker◆AWS◆Linux◆GitLab CI◆GitHub Actions◆Nginx◆Vercel◆TypeScript◆C#◆Node.js◆React◆Next.js◆PostgreSQL◆Redis◆Docker◆AWS◆Linux◆GitLab CI◆GitHub Actions◆Nginx◆Vercel◆
04

Languages

  • TypeScripteveryday
  • C#.NET
  • SQLPostgres / MSSQL
  • Bashglue
04

Backend

  • Node.js
  • .NET
  • PostgreSQL
  • Redis
04

Frontend

  • React
  • Next.js
  • Tailwind CSS
  • Vite
07

Platform & ops

  • Docker
  • AWS
  • Linux
  • Nginx
  • GitHub Actions
  • GitLab CI
  • Vercel
05

Practice

  • Domain-driven design
  • Event-driven systems
  • Observability
  • Technical hiring
  • Delivery management
[03]$ git remote -v

Pinned builds and public work

A mix of product code, experiments and open source. Live metadata pulled from GitHub.

GitHub

synced from pinnedall repos →
hint: press ⌘K to jump anywhere|repos refresh daily via ISR
[04]$ tail -f activity.log

Always shipping something

Contribution graph and recent public events from GitHub.

853 contributions in the last year

lessmore
OctNovDecJanFebMarAprMayJunJulAugSepOct

853

contributions

607

commits

203

pull requests

14

issues

27

public repos

36

followers

[05]$ ./start-project --interactive

Tell me about your project

Fill this in and it composes a structured brief for you. Nothing is stored, nothing is sent behind your back — it opens in your own mail client.

add a name, a valid email and a few words about the problem

$ cat brief.txt
NEW PROJECT BRIEF
=================
from      : - <->
company   : -
type      : Web application
budget    : Not sure yet
timeline  : Within a month
links     : -
nda       : not required

THE PROBLEM
-----------
-

--
sent from h4kbas.me project brief

what happens next

  1. 01You send the brief from your own mail client.
  2. 02I reply within one business day with questions or a call slot.
  3. 03We scope it, agree on a shape and I give you a written estimate.
or just email h4kbas@gmail.com
[06]$ curl medium.com/@hakbas

Writing about what I build

Long-form notes on marketplaces, realtime systems and running product teams. Mirrored from Medium.

read everything on Medium

from the timeline

@h4kbas
loading timeline...