Akın Öztorun · Senior Frontend Engineer

Contracts, slices, and calm releases.

I help product teams ship thin vertical slices that match real data, not guesses. Contract first, clear quality checks, and UI that fits the rest of the system.

What I do best

  • API first frontend work
  • Vertical slices
  • Quality in CI
  • Performance and reliability

Best fit: product teams in EU time zones that care about contracts, tests, and clear ownership.

Selected projects

Small but complete slices that show how I work.

Energy portfolio slice

Full stack

GraphQL and React slice for an energy portfolio domain. Models customers, projects, and assets with a typed contract and a thin UI on top.

TypeScriptGraphQLReactNode

Next SWR quality demo

Frontend

Next.js app that shows how I handle data fetching, caching, loading states, and error paths with SWR and a clear quality setup.

Next.jsSWRTypeScriptTesting

Writing

Short, practical pieces for engineers who want more ownership.

Clarify Before You Code

Newsletter

A series on contracts, slices, and small habits that make teams calmer and faster. The focus is on real tickets, not theory.

  • Issue 1: Do not start vague tickets
  • Issue 2: Contracts first, screens second

How I work

What it is like to ship a slice together.

1

Contracts first

Agree on the API and data shapes before building screens. Generate types, mock early, and keep a simple contract check in CI.

2

Vertical slices

Own one slice end to end, from user goal to contract, UI states, monitoring, and a calm rollout plan.

3

Quality in the pipeline

Linting, tests, code checks, and basic performance checks live in CI so they run on every change, not only before big releases.

4

Clear collaboration

Ask precise questions, write short docs, and make trade offs visible so others can decide with you, not after you.

Contact

For roles, slices, or just to talk about product engineering.

Best fit: product companies in EU time zones that care about contracts, tests, and clear ownership.