10000 akin-oz (Akin Oztorun) · GitHub
[go: up one dir, main page]

Skip to content
View akin-oz's full-sized avatar
  • Remote

Block or report akin-oz

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don't include any personal information such as legal names or email addresses. Markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
akin-oz/README.md

Akın Oztorun

Senior Frontend / Product Engineer · TypeScript · React · API-first · Reliability

I design and build vertical slices: clear domains, strong contracts, and frontends that behave well in production.
Not “pixel pusher”, not “just the UI”. Think product, systems, and teams.


What I do

  • Frontend platforms & product engineering

    • TypeScript, React, Next.js, GraphQL, modern tooling.
    • Shared UI systems, design-system-minded components.
    • Contracts-first: align APIs with how clients actually use data.
  • Quality & reliability

    • CI/CD, testing strategy (unit / integration / E2E), static analysis.
    • Observability basics: logging, tracing, error tracking.
    • Performance, accessibility, and safe rollout habits.
  • Collaboration

    • Work closely with product, design, and backend.
    • Turn vague requirements into concrete, measurable changes.
    • Mentor devs, document decisions, reduce heroics.

Selected work

Energy Portfolio Slice
Vertical slice showing how I approach Staff-level product engineering from a frontend seat:

  • Domain modeling: Customer → Project → EnergyAsset.
  • GraphQL API as the contract (pagination, filters, typed errors).
  • React client wired to the real API, not mocks.
  • Structure ready for auth, logging, events, and multi-tenant growth.

Repo: energy-portfolio-slice


Next.js SWR Quality Demo
A focused demo on safe, observable data fetching in Next.js:

  • Uses SWR to handle caching, revalidation, and error states.
  • Shows loading, fallback, and failure UX that respects real users.
  • Highlights patterns for API boundaries, typing, and testability.

Repo: next-swr-quality-demo


How I work

  • Start from the problem and domain, not from components.
  • Design API and data contracts early with backend.
  • Keep the frontend lean and predictable, backed by tests.
  • Treat internal teams as customers: docs, DX, and guardrails matter.
  • Own the lifecycle: idea → implementation → rollout → monitoring → iteration.

Currently focused on

Senior / Staff-track roles where:

  • Engineers own a slice end to end.
  • API-first, cloud-native, product-led culture is real.
  • Reliability and UX both matter.

If that sounds like your environment and you’d like to talk,
reach out via LinkedIn or open a discussion here.

Pinned Loading

  1. next-swr-quality-demo next-swr-quality-demo Public

    Next.js + SWR demo focused on data consistency, caching, and error handling.

    TypeScript

  2. energy-portfolio-slice energy-portfolio-slice Public

    Vertical slice for an energy portfolio platform – TypeScript, GraphQL, React, contracts-first, testable.

    TypeScript

0