I’m Zoha, a product engineer.
Most recently, I delivered LineupBridge, a booking marketplace for DJs, shaping an open brief into an MVP as the only product, design and engineering person.
What interests me is how a product stays close to its users as it grows. These days, I’m exploring how we can use LLMs to build leaner systems, leaving more bandwidth for reshaping the product and crafting its interface.
Thirty-something and finally moving to Berlin. In my spare time, I’m giving some love to my older project, an English translation of the Yoga Sutra.
Tools
- Product discovery, user flows, prototyping
- Experiments, feature flags, PostHog
- React, Next.js, TypeScript, GraphQL, server-side rendering
- Design systems, design tokens, Storybook, Tailwind CSS, Figma
- Accessibility, Jest, React Testing Library
- Monorepos, performance
- Claude Code, agentic development
Education
- Software Engineering Immersive
General Assembly - Master of Architecture
University of Newcastle - Bachelor of Architecture
UNSW
Timeline
- 2026 — NowProduct Engineer
LineupBridgeProduct EngineerA booking marketplace for DJs, from an open brief to a first release, as the only product, design and engineering person.
A DJ booking marketplace. An event organiser sends a DJ an offer, both sides can counter, and the DJ accepts; the booking is paid through the platform.
- Product
- The brief was open, so I started by talking with event organisers, DJs and the founder about how bookings are agreed today. What they told us changed the core flow, and the founder and I agreed what the first release would do.
- Design engineering
- Defined the brand identity with the founder, then the user flows and the interface. Started with a light design system, documented in the code and kept in step with the design file, so it can keep changing as user data and the product evolve.
- Engineering
- Chose an existing marketplace foundation, so the custom work went into the booking model: an offer that both sides can counter before payment. Built with Claude Code from rules and specs kept in the repository, with reviewer agents checking each change.
- 2025 — 2026Frontend Engineer
Digistore24Frontend EngineerAn established application and a large team: consistency first, then releases driven by what users say and do.
- Product
- Set up event tracking and experiments so that UI and feature releases came from what users say and do. Took the onboarding from prototype to build to release.
- Design engineering
- With a large team and an existing design system, the fastest improvement was rules, not a rebuild: layout rules and usage guidelines that brought consistency straight away. The new navigation was designed in code, from experiment results and how the frontend uses its data.
- Engineering
- Defined and owned an internal platform in a monorepo, linked to the main application, that automates operational workflows for customers and support teams. Owned releases end to end, including fixes on the frontend and backend in production.
- 2023 — 2025Frontend Engineer
GotphotoFrontend EngineerA high-traffic application on a modern frontend, with a design system shaped by the code and by user data.
- Product
- Worked with product, design and data on user journeys, iterating from analytics, which contributed to fewer drop-offs on targeted flows.
- Design engineering
- The component library lived in the code and defined the tokens and components in the design file. What went into it came from how the application handled data and from user data. Raised its test coverage to 80%.
- Engineering
- Moved a high-traffic legacy application to React, TypeScript and Next.js step by step, without disrupting production, and later to the App Router.
- 2021 — 2022Software Engineer
ProppsSoftware EngineerAn early-stage startup: the foundation other applications were built on, from the GraphQL schema to the design system.
- Product
- Worked with product and design to turn changing requirements into responsive interfaces from the product’s early stages.
- Design engineering
- Built and owned the design system: a typed, tested component library published from a monorepo and used by every application.
- Engineering
- Built the Next.js application and wrote the schema of its GraphQL API, shaping the frontend architecture from the start.