DESK: DESIGN + FRONTEND
HANDOFF: NOT REQUIRED
STATUS: OPEN TO OFFERS + FREELANCE
THURSDAY, 3 SEPTEMBER 2026
EDITION: WEB
EDITORIAL · THE LONG VERSION
The designer behind this broadsheet — Tamal Biswas, UI/UX and frontend, currently SDE-I at Medecro.ai, where he designs interfaces and ships the production code that renders them.
I am a self-taught designer who learned to code, which turns out to be the useful order to do it in. Design taught me what the screen should be; code taught me which of my ideas were fantasies. Most of what I know about interfaces I learned by having to implement my own worst decisions.
I started at Legabyte Innovations in late 2023, building responsive frontends in HTML, CSS, JavaScript and React. I joined Medecro.ai as a UI/UX design intern in July 2024 and became SDE-I on the frontend team in April 2025 — which meant the design work and the implementation work landed on the same desk, on purpose.
What I build at work is not mine to publish — the screens and the system belong to the company that owns them, so you will not find them here, and I would be a poor bet for your team if I treated that differently. What is here is work I own outright: Budget Bliss, a budgeting app I designed and shipped end to end because I wanted a product where every decision on screen was mine to defend, and interface work across desktop, iOS and web in Section B.
I design in component states and real tokens rather than in finished pictures, because a picture cannot tell you what happens when the data is empty, the name is forty characters long, or the request times out. Then I build it, which is where I find out whether I was right. The loop between intent and running software is measured in hours rather than sprints — that is the whole argument for one person holding both halves.
A product team where design decisions get made once and where the review cycle is fast. I care far more about the product being real and used than about the company being large. Remote is where I do my best work — a home setup built for long uninterrupted stretches of thinking, and hours that already overlap US, UK and EU. Remote or hybrid only.
Designing and shipping frontend at Medecro.ai. Reading about criminal psychology and detective casework, which is less of a detour than it sounds — both are the practice of reasoning from what people actually did rather than what they said they would do, and that is most of what user research is.
2023
Started in December, building responsive, user-friendly web interfaces in HTML, CSS, JavaScript and React. Built reusable components, worked on cross-browser consistency, and integrated frontends with REST APIs — the year the fundamentals got put in properly.
2024
Joined in July. Designed interfaces, wireframes and high-fidelity prototypes in Figma for web-based healthcare products, and started the design system that later work would be built on. Worked directly with the developers who had to implement it, which shaped how I design more than any book did.
2025
Moved into the engineering team in April while keeping design ownership. Built and maintained the frontend in a Next.js and TypeScript monorepo, shipped accessible pixel-accurate components from my own Figma files, integrated REST APIs, and extended the design work to native mobile.
2026
Designing and building frontend at Medecro.ai, building a design system of my own on the side, and open to the next thing — a team where design and engineering are not two departments with a ticket queue between them.
The constraint that improved my work most was requiring every value to be expressible as a real token. It kills the one-off 13px gap and the shadow nobody can reproduce — the small things that quietly make engineers stop opening the design file.
Every field somebody asks for is individually defensible, and nobody is accountable for the total. In a clinical dashboard that arithmetic is the whole difference between a doctor reading a screen and searching it.
Dividers, boxes and borders are usually white space somebody gave up on. If the spacing scale is doing its job most of those lines are redundant — this page has almost none, and every one it has is a single pixel.
It simply cannot be found from the design side. How a thing feels belongs to whoever is responsible for how it feels, which means interaction performance is a design concern — and a good reason for the designer to be able to open a profiler.
Q. Designer or developer?
A.Designer first, and one who ships the production frontend. I own the UX for the product I work on and I write the Next.js that renders it. The point is not being equally good at both — it is that nothing gets lost between them.
Q. Can you work inside an existing design system?
A.That is easier than building one. I have built a design system more than one product depends on, so I know exactly why yours has the constraints it has, and I will not spend my first month arguing with them.
Q. Why isn't your day-job work on this site?
A.Because it isn't mine to publish. I design and build the frontend of a healthcare product full time; the screens, the values and the internals belong to the company that owns them. What is here instead is work I own outright — and the specimen sheet on the front page documents this site's own system, top to bottom, which is the same job done in public.
Q. Are you actually available?
A.Yes — open to product design, UI/UX, frontend, and design-engineer roles, remote or hybrid. The press kit is one click away and the inbox is genuinely monitored.