Senior engineer · Istanbul · booking Q3 projects
Software engineer. Spent years on backend — now I build products.
Right now that's HookSense, a webhook reliability + MCP tool. Alongside it I build and run products for writers, like Yayınlıyor and Cordy. Backend depth, shipped as real things people use.
8+ years backend · AWS Community Builder (Serverless) · 6 products live
What I do
I take things from idea to running in production — and I stay for the unglamorous part.
Build the MVP
Fast, but not throwaway — the data model and the failure cases are right from day one.
Harden it
Retries, idempotency, dead-letter handling — the stuff that decides whether it survives real load.
Scale and fix
When it grows or breaks, I'm the one on the pager.
Started in QA, moved to backend, now building my own products. The QA part never left — I design from the failure case inward.
Selected work
Four products, all live. Two things I'm good at: deep backend infra, and getting products in front of real readers.
Infra & devtools
HookSense
hooksense.comA webhook reliability tool. Spin up your own endpoint, send requests to it, and inspect every one in detail — verify signatures, replay the failures, keep a history that doesn't vanish. There's an MCP server too, so you can drive it straight from AI.
Live · free tier + paid · open-source MCP server
SelfInbox
selfinbox.ozersubasi.comSelf-hosted transactional email on AWS SES, with the SPF/DKIM/DMARC setup automated so you don't fight DNS for a week. I open-sourced it instead of turning it into a SaaS — owning other people's deliverability as a solo operator is a risk I didn't want.
Open source · MIT · runs on your own AWS
Products with readers
Yayınlıyor
yayinliyor.comMy own serialized-fiction platform. Writers publish chapter by chapter, readers follow along. Built it, run it, grew it to 259K+ reads and ~2K readers.
Live · 259K+ reads · solo-built and operated
Cordy
cordy.isilsugultekin.comA mobile app I build and maintain for author Işılsu Gültekin. Her readers get her printed and new work chapter by chapter, and can interact with her directly. Growing steadily.
Live · iOS/Android · client product, actively maintained
How I build
I build AI-native, with agents doing the heavy lifting and me owning the decisions that matter.
Parallel agents on separate git worktrees, orchestrated through CLAUDE.md and AGENTS.md files — one on the API, one on the jobs, a UI pass alongside. It's fast, but the architecture, the data model, the failure semantics and the taste are mine. The agents write a lot of the code; they don't decide how the system should fail.
- wt/apiagent · retries + idempotency✓ merged
- wt/jobsagent · dead-letter handler✓ merged
- wt/uiagent · status page passrunning
Writing
Notes on what I'm building and what I've learned — reliability, webhooks, serverless, shipping solo.
Work with me
I mostly build my own products now, but I'm open to the right backend and product work. If you've got a backend that needs hardening, an MVP that needs shipping, or something that grew faster than its architecture — that's exactly what I've spent my career doing.
Free scope + roadmap within 48 hours. Average reply: same day.