Architecture must earn its keep
A framework is only successful when it makes the product faster to change, easier to understand, or measurably better for customers.
Senior Software Engineer · Picnic Technologies
Frontend & mobile architectureplatformsmigrations for products used by millions.
/01
The work I enjoy most is a transition — templates to typed components, two apps to one codebase, a product to a platform.
Today I work on Picnic’s React Native customer app, where I designed the TypeScript framework behind its server-driven Page Platform and am evolving it toward server-side rendering with React Server Components.
Earlier, I grew from frontend engineer to tech lead at Digikala, hired and led a 20-person team, and helped modernize web and mobile products used by millions. I later built a five-person frontend team at DFreight before relocating to the Netherlands.
A framework is only successful when it makes the product faster to change, easier to understand, or measurably better for customers.
I lead through design and code. Working at platform level should sharpen product judgment—not replace it with abstraction.
Documentation, workshops, and clear APIs turn individual technical work into capability that a whole team can own.
Off the timeline
Based in Amsterdam. B.S. in Information Technology Engineering from the University of Tehran. Native Persian speaker; professional English. Technical speaker since 2019.
/02
Three systems: the constraint, the architectural move, and the evidence it mattered.
Picnic’s customer app needed server-driven screens without giving up the composability and developer experience of modern frontend engineering.
My contribution
I led the architecture and implementation of an async TSX framework with data resolvers, replacing Handlebars templates. I built its local development and testing toolchain, then evolved the platform toward React Native SSR with React Server Components—and taught teams how to extend it.
Separate native applications duplicated delivery effort at one of the Middle East’s largest e-commerce platforms.
My contribution
I architected and contributed hands-on to a ground-up React Native rebuild. The shared codebase aligned Android and iOS delivery while keeping the app ready for a large consumer audience.
The storefront was rebuilt twice without slowing product delivery: from a legacy stack to Supernova's PHP/Twig frontend, then to Next.js.
My contribution
I first helped build Supernova's customer-facing frontend, then oversaw its migration to Next.js after promotion to tech lead. Alongside the architecture, I hired and led the 20-person frontend team responsible for delivering it.
/03
Interfaces, then platforms, then the teams that build them.
Amsterdam, NL
Evolving the Page Platform toward React Native SSR with React Server Components; driving adoption through workshops, knowledge-sharing sessions, and technical direction.
PromotionDesigned the async TSX framework and its Vite/Vitest tooling, shipped customer-experience features that reduced demand on customer service, and improved runtime performance through state architecture work.
Dubai, UAE · remote
Built and led a five-person frontend team delivering the Next.js customer portal and operations back office, plus a React Native shipment-tracking app.
Tehran, IR
Hired and led 20 frontend engineers, directed two cross-functional teams, and guided web, mobile, SEO, and advertising-platform initiatives at large consumer scale.
PromotionBuilt Digikala’s customer-facing frontend from the ground up as part of Supernova, establishing reusable components and shared libraries before promotion to Frontend Tech Lead.
Tehran, IR
Built the React passenger PWA for roughly 10,000 daily users and migrated snapp.ir to React on a ride-hailing platform handling more than 2M rides per month.
Tehran, IR
Built a real-time React messenger with Protobuf and WebSocket, and helped implement the Televizak video-on-demand platform.
/04
The clearest test of an idea is whether you can explain it. I share the architecture behind the work—not just the polished outcome.
Speaking since 2019Picnic’s server-driven Page Platform, why server-side rendering matters in a native app, and where React Server Components take the architecture next.
Talks on React, React Native, and frontend architecture for Iran’s largest React community.
A co-authored account of moving an application server’s UI layer from Handlebars templates to type-safe asynchronous TypeScript components.
/05
Tools change. These are the problems I have repeatedly learned how to solve—and the technologies I know deeply enough to solve them with.
Server-driven UI, SSR, React Server Components, framework APIs, state architecture, and the boundaries between server and client.
Incremental migrations, shared mobile architectures, performance work, testing strategy, and developer tooling that supports daily delivery.
Architecture decisions, hiring and mentoring, cross-functional delivery, workshops, and helping engineers become contributors to the platform.