Available for remote contracts

Emre Erkorkmaz · Senior Frontend / Fullstack Engineer

Senior TypeScript engineer for frontend platforms, fullstack features and AI product features.

Since 2021 I have built production React and TypeScript products: the order flow of a PWA handling millions of daily orders, the Node.js endpoints it depends on and real-time finance UIs. Now extending that into LLM-powered product features, on remote contracts with UK, EU and US teams.

shipping to production since
2021
daily orders on systems I worked on
M+
overlap with UK and EU working hours
UTC+3

Selected work

Production work at real scale.

Brand names are withheld for confidentiality; details and references on request.

  1. 01Quick-commerce platform

    The order flow of a PWA handling millions of daily orders

    Client-side core and order life cycle of the PWA restaurants run their orders on, shipped inside the native apps through webviews.

    Need, solution, impact

    Need

    A business-critical order flow under high traffic, with web releases blocked by the mobile apps’ code freezes.

    Solution

    Owned the order life-cycle flow: a REST snapshot on load, WebSocket events for new orders and status changes, and a connection-state indicator with manual refetch instead of polling. Integrated the PWA into native webviews and exposed native capabilities such as push notifications to the web layer. Built the REST API endpoints the frontend depended on with Node.js and Express, and added a generic proxy endpoint to the Node.js BFF.

    Impact

    Web releases ship independently of mobile code freezes; business partners receive push notifications from the web layer; new gateway endpoints no longer need BFF code changes or a separate deploy.

    • React
    • TypeScript
    • PWA
    • WebSockets
    • Native webviews
    • Node.js
    M+daily orders
  2. 02Fintech

    Real-time finance UIs without pagination

    Multilingual B2B and B2C trading apps in React and Angular that render large, live market data without paging, plus a config-driven form layer.

    Need, solution, impact

    Need

    Following large, constantly streaming data sets without interruption across multilingual B2B and B2C interfaces.

    Solution

    React and Angular interfaces that render real-time, large-scale data without frontend pagination; a config-driven form layer (Formik, Yup, Material UI) that let backend-focused developers ship validated form pages with dependent fields from a typed config; a reusable app template with React, Material UI, Redux and Redux Saga; unit tests with React Testing Library and Mock Service Worker, end-to-end tests with Cypress.

    Impact

    Large live data sets stay browsable in a single view; backend-focused developers ship complex form pages from config; new projects start from a ready template.

    • React
    • Angular
    • TypeScript
    • Redux Saga
    • Material UI
    • Cypress
    Livereal-time data
  3. 03E-commerce

    A multilingual, server-rendered storefront on Next.js

    A multilingual e-commerce app with server-side rendering on Next.js, TypeScript and Redux, and a React + GraphQL survey product in the same period.

    Need, solution, impact

    Need

    Product pages that rank in search and load fast across several markets.

    Solution

    A multilingual e-commerce app with server-side rendering on Next.js, TypeScript and Redux; a survey product built with React and GraphQL; responsive designs turned into semantic HTML.

    Impact

    Product pages render on the server in every language, so they are indexable and fast on first load.

    • Next.js
    • TypeScript
    • SSR
    • Redux
    • GraphQL
    • i18n
    SSRmultilingual storefront

Capabilities

Frontend depth, full-stack reach.

Ownership of UI architecture and performance, the APIs a feature needs, and safe delivery through automated tests.

  • Frontend & performance

    Maintainable UI architecture for high-traffic products: PWAs, SSR and real-time data, with pages that stay fast and secure.

    EcosystemTypeScript · React · Next.js · Angular · Redux · Tailwind CSS · Storybook

  • Backend & APIs

    The APIs and services a feature depends on, designed together with the interface that consumes them.

    EcosystemNode.js · Express · GraphQL · REST · WebSockets · PostgreSQL

  • Testing & delivery

    Unit, integration and end-to-end tests wired into the pipeline, so changes ship with confidence.

    EcosystemPlaywright · Cypress · React Testing Library · Docker · Git

Ways of working

  • Code review
  • Automated testing
  • Documentation
  • AI-assisted development
  • Remote, async collaboration
  • Agile / Scrum

How I work

From first call to steady delivery.

  1. Intro call

    We go through the codebase, the team and what needs to ship. You get a straight answer on fit before anything is signed.

  2. Onboarding

    Local setup, then a map of the architecture and release path. Questions come early and in writing; the codebase’s existing conventions are followed.

  3. First change

    A small, reviewed change goes to production early, proving the setup and building trust before larger work.

  4. Steady delivery

    Small pull requests with tests, async progress updates, and documentation that stays with the team when the contract ends.

Engagement

Contract terms, kept simple.

  • Remote contract

    Hourly or daily, fully remote. The contract setup is agreed per engagement.

  • Rates

    On request, based on scope and duration.

  • Working hours

    UTC+3, no daylight saving. A working day that overlaps UK and EU hours, with partial overlap on US East Coast mornings.

  • References

    References from previous roles are available on request.

Remote
Yalova, Türkiye · UTC+3
Languages
English (C2) · Turkish (native)

FAQ

Questions teams ask first

What is your timezone overlap?

I work from Türkiye (UTC+3, no daylight saving). My working day overlaps UK and EU hours, and US East Coast mornings. Stand-ups and reviews are planned into that overlap.

How do you onboard into an existing codebase?

Local setup first, then a map of the architecture and release path, then a small, reviewed change to production early. Questions come early and in writing, and the conventions already in the codebase are followed rather than replaced.

How quickly can you start?

Start dates are agreed on the intro call, based on current commitments. The status badge at the top of this page shows whether I am taking on new work.

How is the contract structured?

Fully remote, billed hourly or daily. The details are agreed per engagement to fit your procurement process.

What are your rates?

Shared on request, based on scope, duration and weekly hours.

Frontend only, or full stack?

Frontend-led and full-stack capable: UI architecture and performance on the frontend; REST and GraphQL APIs with Node.js and Express on the backend.

Can you provide references?

Yes, references from previous roles are available on request.

Contact

Need an extra senior engineer?

Send a few lines about the role, the stack and the timeline, and we can set up a short intro call.