Order
Menus, location, cart, checkout, delivery, catering
Avenga · Senior Frontend Engineer — React + Next.js
Frontend ownership for products that cannot afford to feel slow.
I am a frontend engineer based in İzmir with six years of experience across customer-facing web products. I combine recent React and Next.js work with performance, architecture, API contributions, CI-backed automated testing, and cross-functional delivery.
- Recent commercial experience across React and Next.js.
- High-traffic B2C product and performance work.
- Vitest and Playwright running through CI pipelines.
- Comfortable collaborating across product, UX, backend, and US time zones.
The product system
A restaurant transaction is never only a checkout screen.
The visible journey sits across identity, integrations, payment state, delivery, operator workflows, and guest data. That is where frontend architecture and product quality become the same conversation.
Pay
Payment state, trust, fraud protection, reconciliation
Engage
Identity, guest data, loyalty, campaigns, retention
Relevant product work
Evidence from transactional, high-traffic, and integration-heavy products
eSIM.io · Teknasyon
Visit productMy current product context is a B2C purchase journey where acquisition intent, checkout clarity, SEO, performance, and reliable delivery meet. It is my most recent commercial Next.js experience.
- Work with Next.js, TypeScript, and Tailwind CSS in production.
- Reviewed server–client flow, state ownership, and frontend logic boundaries.
- Contributed to PageSpeed, SEO, image loading, and perceived performance.
- Built lightweight Next.js endpoints and contributed CRUD endpoints to backend projects.
Nesine.com
Visit productA high-traffic React product where performance regressions are user-facing product problems. I worked inside a frontend monorepo while legacy .NET surfaces moved toward a React SPA.
- Used React Profiler and component update analysis to investigate rendering behavior.
- Worked with virtual-list patterns and production performance constraints.
- Shipped within established monorepo conventions and shared product patterns.
- Learned to treat rendering, loading, and regressions as product quality signals.
Petal Maps Studio · Huawei
Visit productAn enterprise map-customization product with complex UI state, map-engine communication, and heavy perceived-performance constraints.
- Connected interface selections with map-engine behavior.
- Solved state-management problems across complex map interactions.
- Worked in an international team and a large enterprise codebase.
- Used UX techniques to make long-running engine responses feel clearer to users.
Rockads · Teknasyon
Visit productAn evolving advertising-management product built around third-party platform behavior, data visualisation, and a Vue 2 to Vue 3 migration.
- Integrated with external advertising platforms and their management surfaces.
- Worked extensively with charts and dashboard-style data presentation.
- Contributed through a framework migration while the product direction evolved.
- Strengthened documentation reading and integration-boundary reasoning.
Engineering practice
The role asks for end-to-end frontend ownership; this is the working baseline I bring
Feature lifecycle
01Frame
02Build
03Test
04Ship
05Support
Performance
Architecture
Quality
Recent React and Next.js delivery
My current commercial work is in Next.js and TypeScript; immediately before it, I spent roughly a year and a half in a high-traffic React product. Both are recent production contexts, not portfolio-only exposure.
Architecture, state, and maintainability
I have worked across server–client boundaries, state ownership, SPA migration, monorepo conventions, complex map interactions, and framework migrations. I am comfortable reasoning beyond an isolated component.
APIs and reusable UI
I have contributed CRUD endpoints to backend projects, built lightweight endpoints in Next.js, consumed third-party platform APIs, and added components to shared libraries. I have not yet owned a production SDK, so I would treat that as a concrete growth edge rather than an invented claim.
Automated quality in CI
I use an AI-assisted test-driven workflow with Vitest and Playwright. The tests run in CI, and I remain responsible for scenarios, review, failures, and whether the test protects the intended behavior.
Performance as product quality
My experience spans React profiling, render analysis, virtual lists, Core Web Vitals, PageSpeed, image loading, SEO, and perceived-performance decisions. I have also spoken publicly about measuring web quality.
Cross-functional technical communication
I work across frontend, backend, product, analytics, and international-team boundaries. Public technical talks are an additional signal that I can make a decision and its trade-offs understandable to other people.
Avenga × Olo
My reading of the product environment behind the role
Public-source research, kept separate from claims about internal teams or data.
01
Avenga describes Olo as a strategic technology partner relationship—not a short, anonymous delivery engagement.
The public partnership story grew from legacy-platform modernization into product engineering, hundreds of integrations, technical advisory, and infrastructure planning. That suggests room for durable product context and meaningful engineering ownership.
Avenga company presentation02
Olo connects Order, Pay, and Engage across more than 800 restaurant brands, roughly 90,000 locations, and 400+ integration partners.
The frontend sits inside a transactional system: menus, location, cart, checkout, payment, delivery, identity, operations, and guest data all influence one another. Reliability and clear state are commercial requirements.
Olo enterprise platform03
Olo's 2026 releases join online and in-store journeys through Serve, loyalty, guest intelligence, payment operations, and AI-supported workflows.
This creates the kind of frontend work I find valuable: responsive customer journeys alongside operator tools, where new features still have to respect permissions, failure states, integrations, and existing product behavior.
Olo 2026 product release04
The advertised role combines feature ownership with code review, stakeholder updates, engineering advocacy, performance work, and an L2 support rotation.
I read this as a senior individual-contributor role where shipping is not the finish line. The expected ownership includes maintainability, production behavior, feedback, and the consequences of a technical decision.
Role descriptionCommunication proof
Technical depth is more useful when it can be shared clearly
I have given public talks on web performance, Next.js, JavaScript internals, and data structures. They are practical evidence of preparation, technical curiosity, and explaining trade-offs to an audience.