Product DesignerRemote

I design digital products. The hard part is figuring out what the product should actually do, what people need, and how all the pieces should work together.

Teams I’ve designed with

  • DTS Solution

Selected work

Case studies,
the way they happened.

The problems I found, the decisions I made, and what changed.

Who am I

A designer who started in code.

What I bring to a team, and the numbers behind it.

Brief

I’m Tanvir. I’ve spent the last 7+ years designing digital products across fintech, healthcare, education, SaaS, and consumer technology.

I actually started out in software engineering, so I’ve always been interested in what happens beyond the screen.

I like getting into the messy parts of a product — complicated workflows, too much information, inconsistent experiences, edge cases, and all the little things that make a product harder to use than it needs to be.

  • Complicated workflows
  • Too much information
  • Inconsistent experiences
  • Edge cases
  • The little things

Then I try to make sense of it.

  • years

  • projects

  • clients

Designing products across different industries, teams, and problem spaces.

The mess, then the product

I like messy problems

Give me a complicated workflow, an old product, five different user types, or a requirement nobody quite knows how to solve. That’s usually where I get interested.

I care about the details

The small things matter. A confusing label, a missing state, an unnecessary step, or a component that behaves differently in every part of the product can add up to a frustrating experience. I notice those things.

I don’t design in isolation

I want to hear from product, engineering, and the people who actually use the product. Sometimes that changes the design. That’s a good thing.

I like building systems

I’m interested in what happens after the first few screens: patterns, components, states, documentation, and the rules that help a product stay coherent as it grows.

Journey

From code to design

I started on the other side of the screen.

How it went

Before I became a designer, I was a software engineer. I still care about what happens underneath the interface — the logic, the edge cases, and whether it can actually be built.

So I don’t just ask what a screen should look like. I ask why it needs to exist, what happens when things go wrong, and whether we can build and maintain it.

The kind of team I’m looking for

I work best where designers help shape the problem, not just the final pixels — close to engineering, and free to say “I don’t think this is working.”

I’m looking for a remote Product / UX Design role where I can own the work from the messy start to the finished product.

  • Remote
  • Product thinking
  • Ownership

Employment

  1. MIADVG LLC2020—NowLead Product Designer
  2. Digitruck Ltd.2019—2020Product Designer
  3. Monstarlab2017Front-end Engineer Intern

Education

  1. BSc in Software Engineering2014—2018IIT, University of Dhaka

In their words

Recommendations, as they wrote them.

Kind words

From the people I built things with.

5 notes

“Working with Tanvir on the Alokito Teachers website was a seamless experience. He designed a platform that is both user-friendly and visually engaging, while carefully aligning with our vision of building a comprehensive ecosystem for developing, assessing, and placing teachers, as well as supporting education institutions. His ability to combine functionality with clean, attractive design significantly improved the user experience of our platform.”
Azwa NayeemEducator, Social Entrepreneur, and Founder · Alokito Teachers01

Azwa Nayeem