Story · ストーリー

Arpan Debnath

Designer by training. Systems-builder by compulsion. Currently mid-argument with an AI about grammar.

Now: Webflow Developer & Web Designer at Remedo
Building: A J.TEST-style Japanese-learning app, and an MBTI community app on the side
Based: India · UTC+5:30 · open to relocating to Japan, Singapore, Malaysia or within India

the path

How I ended up here

2023
Graphic design at Remedo
I never sat down and decided to become “a designer who also builds AI pipelines.” It happened one repetitive Tuesday at a time. I started at Remedo, a healthcare-tech platform, making social graphics and motion loops, and the throughline ever since has been the same instinct: get closer to the whole pipeline, not just the slice with my name on it.
2023–2025
Design to deployment, one person
That's how graphic design turned into UI/UX, and how UI/UX turned into owning design-to-deployment end to end: wireframes and high-fidelity design in Figma, production builds directly in Webflow, no developer handoff in between. I ship what I design, and it matches pixel-for-pixel, because the same person is doing both halves.
2025–
Building the tools
The automation habit came from exactly the same place. Once you're responsible for the whole pipeline, the boring, repetitive parts of it become impossible to ignore, so instead of doing them faster by hand, I started building tools that do them instead. Grammar QA that used to eat half a workday now takes less time than a coffee break. It's less a philosophy than a pattern: hit the same wall enough times, and eventually you build a door.

A few things I actually believe

Ship it yourself, or don't design it that way.
If a design can't survive contact with a real build, it isn't finished; it's a suggestion. Zero-handoff isn't a productivity flex, it's the only way I trust the output.
If you're doing it a third time, build a tool instead.
Every automation system I've shipped started as the same manual task, done enough times to become unbearable: the QA passes, the SEO/ADA audits, the data checks. None of them were clever ideas. They were me refusing to do the same thing a fourth time.
A system should outlive the person who built it.
The Figma taxonomy, the QC framework, the audit pipelines: none of them need me personally to keep running. That's the actual test of whether something's a system, or just a habit with my name on it.

michi · the path

The Japan of it all

I've been chipping away at Japanese for a while (JLPT N5 down, N4 in progress) and the honest long-term goal is a career in Japan's design industry. Something about the precision and restraint in how design gets made there lines up with how I already like to work, which is what made the studying stick instead of fading out like most New Year's resolutions.

That said, I'm not gatekeeping this whole site around it. If a good, English-speaking team wanted to hire me tomorrow, in Japan or anywhere else, I'd take the call. Japan is the direction I'm walking, not a condition I'm attaching to saying yes.

the work

The work, one line each

Every number and the full write-up live in the case studies.

All case studiesProblem, approach and every number.履歴書 · ResumeThe trajectory with real dates and titles.

That's the story so far

If the next chapter looks like your team, a role or a project that needs design and build without a handoff, I'd like to hear about it.

Connect

Arpan Debnath

How I ended up here

Graphic design at Remedo

Design to deployment, one person

Building the tools

A few things I actually believe

Ship it yourself, or don't design it that way.

If you're doing it a third time, build a tool instead.

A system should outlive the person who built it.

The Japan of it all

The work, one line each

That's the story so far