We're hiring a Remote Product Designer, full-time, $98,000 a year, open to anyone regardless of location. This is a design role that sits close to the product itself, not off to the side making things look nice after decisions are already made.
The Work
- Talking to users early enough to understand a problem before sketching a single screen
- Turning that understanding into wireframes and clickable prototypes that get put in front of people, not shipped straight to engineering untested
- Sitting in on planning and build conversations with the PM and engineering team so the design holds up once it's actually built
Here's a real version of how that plays out. A team wants to add a bulk-edit feature to a dashboard. You'd start by talking to a handful of users who currently do that work one row at a time, figure out where the pain actually lives, sketch a few directions, then sit down with an engineer to work out what's realistic to build this quarter versus what's a longer-term bet. The wireframe is maybe a third of the way through that process. The rest is conversation and tradeoffs.
Some weeks that balance tips heavily toward research and discovery, especially early in a project when almost nothing has been decided yet. Other weeks, it's mostly refinement: adjusting spacing, fixing an interaction that felt off in testing, and tightening up a flow that mostly works but has one confusing step left. Both count as real progress, even though only one of them produces something visually impressive to show off.
Skills That Matter Here
Figma is the daily tool, full stop. Beyond that, you need real user research chops, comfort building wireframes and prototypes fast, and a solid handle on interaction design, meaning how things actually move and respond, not just how they look frozen in a static frame.
Design systems experience counts for a lot too. Products at this stage tend to have some kind of component library already in place, and knowing how to work within one, extend it thoughtfully, and flag when something new is genuinely needed rather than just convenient saves everyone time. Collaboration with engineers isn't a soft skill tacked onto the list here; it's a core part of the job, since a design that can't get built on schedule isn't much of a design yet.
Who We're Looking For
A bachelor's degree is required, typically in design, human-computer interaction, or a related field. Thirty months of hands-on product design experience is the bar, and the portfolio needs to show full end-to-end work: research through shipped (or at least fully specced) product, not a folder of isolated screens with no context around them.
Proficiency with modern design tools is assumed. What matters more at this level is judgment: knowing when a quick low-fidelity sketch settles a question faster than a polished mockup, and when the opposite is true.
Prior experience in a specific industry isn't required. What tends to matter more than industry background is whether you've worked on a product that shipped and then changed based on how people actually used it, since that loop of shipping, watching, and adjusting is most of what this job is about.
Pay and Benefits
$98,000 a year; however, your employer structures full-time compensation. Health coverage, paid time off, and 401(k) matching are all part of the package, and remote flexibility is baked in since the role has no fixed location to begin with.
- Health coverage
- Paid time off
- 401(k) matching
- Remote-work flexibility
Some employers hiring for roles like this one add tuition reimbursement or a learning stipend on top, particularly the larger ones. Naukri Mitra sees that pattern show up often enough in this space that it's worth checking for on the specific listing you're applying to, since it varies by employer rather than being guaranteed across the board.
Remote Reality
No office, no fixed hours beyond whatever your team sets for overlap. Most design reviews and critiques happen on video, most day-to-day questions get resolved in chat, and you'll need to be comfortable making a case for a design decision in writing when a live conversation isn't practical. That last part trips up some designers who are used to walking over to someone's desk to hash things out in person. Here, you write it down, share your screen, or record a quick video walkthrough instead.
A decent home setup helps: a second monitor makes reviewing prototypes and reference material side by side much easier, and a quiet space matters when you're on back-to-back calls with users or teammates in different time zones.
Async habits matter as much as any tool here. Writing up a research finding clearly enough that someone in a different time zone can read it and act on it the next morning is its own skill, separate from the design work itself, and it's one that takes most new hires a few weeks to build.
Experience Level and Growth
Thirty months lands you past entry-level territory but short of a senior title. Expect solid ownership over individual features rather than company-wide product strategy, at least at first. Designers who spend a couple of years here and build strong design-system instincts tend to move toward senior product designer roles, sometimes taking on a specialty such as systems design or research leadership, depending on where their interests lie.
Pay at this level for a remote product designer role is competitive without being an outlier, sitting comfortably above entry salaries once the 401(k) match and any learning stipend get factored in alongside the base number.
The path from here usually branches. Some designers push deeper into the systems side, ending up owning the component library and the standards other designers work within. Others move toward research leadership, spending more time framing the questions a team should ask and less time in Figma day-to-day. Which branch fits better tends to show up fairly early, often within the first year.
How to Apply
Send a resume and a portfolio link. The portfolio needs at least one project walked through end-to-end: the research question, what you tried, what got cut, and what shipped. Skip the temptation to include ten thin projects instead of two or three deep ones.
Interviews typically include a portfolio review, a working session where you'll sketch through a sample problem live, and a conversation with someone from the engineering side about how you handle tradeoffs when a design idea runs into a technical constraint. Plan on two to three weeks from application to a decision, give or take scheduling on both ends.
