We’re a fully remote design studio. We hire remote designers, work with founders across time zones and ship apps and websites without ever sharing an office. Here’s what we’ve learned about what the job really takes in 2026.
The job: decisions, not decoration
Product design starts long before Figma opens. The real work is figuring out what a product should do, for whom, and why someone would keep using it. Screens are just where those decisions become visible.
In practice, a product designer moves through the whole loop:
- Understand. Talk to users, study competitors, read the data, find the actual problem.
- Shape. Turn that problem into flows and structure before any pixel gets polished.
- Design. Build interfaces that are clear, consistent and pleasant to use.
- Ship. Work side by side with developers so what launches matches what was approved.
- Learn. Watch how people use it, then improve it.
The last two steps are where many designs quietly die. A beautiful mockup that turns into something nobody recognizes at launch is not a design win. That’s exactly why at OSAM design and development live under one roof.
What remote actually changes
Remote doesn’t make the job easier or harder. It removes the hallway, and everything the hallway used to fix. Three skills fill that gap.
- Writing is the new meeting. Nobody can lean over your desk and ask what you meant. A clear Loom, a well-named Figma page or a three-line comment explaining why a button moved saves a day of back-and-forth. Designers who explain their decisions in writing get faster feedback and fewer surprises.
- Async by default. When your developer is six hours ahead, the question you send at 6 pm gets answered while you sleep. Good remote designers plan for that: they share work early, ask specific questions and never leave a teammate blocked overnight.
- You own your day. No manager walks by to check on progress. You set priorities, protect focus time and show your work before anyone has to ask. At OSAM, clients see progress every week, so this rhythm isn’t optional. It’s the product.
AI: a power tool, not a pilot
AI can now draft copy, generate layout ideas, summarize interviews and even write front-end code. That’s great news for designers who know what they’re doing, and bad news for products built on autopilot.
We’ve redesigned apps that were clearly made by typing "build me an app" into a prompt and shipping the first result. The features were there. The thinking wasn’t. Everything looked like everything else, and users noticed.
The designers we want use AI to move faster on the boring parts, so they have more time for the parts that need taste:
- Exploring more directions in less time.
- Speeding up research synthesis and first drafts.
- Prototyping ideas before committing to them.
- Checking edge cases and states a human might miss.
What AI doesn’t do is decide. Choosing which direction is right, saying no to a feature or noticing that a flow feels off is still a human job. Use AI to go faster, never to stop thinking.
How to stand out (from people who read the portfolios)
Every application we get is reviewed by a real person. Here’s what makes us stop scrolling:
- Show the thinking, not just the shots. One case study that explains the problem, the options you considered and why you chose one beats ten polished mockups with no story.
- Pick fewer, better projects. Three strong cases say more than twelve average ones.
- Show what shipped. If your design made it to real users, say so, and show how it looked live.
- Be honest about AI. Tell us where and how you used it. A smart workflow is a plus, not something to hide.
- Write like you’d write to a teammate. Your portfolio text is a preview of how you’ll communicate when we’re in different time zones.
And one thing that has nothing to do with Figma: be someone people enjoy working with. Remote teams run on trust, and trust starts with the first message.