← Back to work

Case study 02 / Fynd · PixelBin.io

Building PixelBin from day one

Joined at the beginning and helped build the frontend foundation behind PixelBin.io, Erase.bg, Upscale.media, and WatermarkRemover.io.

RoleFounding Frontend Engineer
TimelineJun 2021 – Dec 2024
FocusTeam leadership · SSR & Core Web Vitals · Experimentation
4AI-media product surfaces
5frontend engineers led
SSRand Core Web Vitals work
01 / Context

From the first product surface to a four-product suite.

I joined PixelBin from its earliest stage and helped build the frontend foundations as the suite expanded into PixelBin.io, Erase.bg, Upscale.media, and WatermarkRemover.io. Each product served a distinct media workflow while sharing the same expectations for speed, clarity, and reliability.

02 / What I did

Scaling architecture and delivery together.

I led and mentored five frontend engineers, owned sprint planning and technical direction, and helped build the suite with React, Next.js, and Electron. We improved Core Web Vitals through server-side rendering and performance optimization, introduced feature flags and A/B testing with PostHog, and established testing standards with Jest and React Testing Library.

03 / Decisions

The choices behind the product.

01

Use server rendering and Core Web Vitals work to support product scale.

02

Build feature flags and experimentation into the release process.

03

Raise consistency with shared testing standards across the suite.

04 / Outcome

Performance connected to product outcomes.

Shared frontend direction made complex media workflows easier to evolve across products. Server-side rendering and Core Web Vitals work improved performance, experimentation enabled safer releases, and common testing standards reduced regressions across the codebase.

Start a conversation

What can we build?

Prefer your inbox?
Open mail app
gamparth@gmail.com