Product Designer

Entermotion builds software that real people depend on every day to do their jobs. Our flagship product, Atlas EMR, is a Direct Primary Care platform that clinics use to run their practice end to end: scheduling, messaging, clinical notes, billing and patient-facing mobile apps. We also build across education platforms and interactive entertainment, so the surface area is wide and the problems are varied.

We are a small dispersed team that ships a lot. We prefer builders over specialists. We prefer people who can move across the full design stack, from wireframe to pixel, from flow to system, from product thinking to shipped interface. We care less about where you trained and more about what you have built.

Design at Entermotion is not a handoff stage. It is part of product thinking, part of engineering collaboration, part of the product's voice. We want someone who wants to operate that way.

As a Product Designer at Entermotion, you are accountable for outcomes, not just artifacts. You partner with product leads, engineers and other designers to define the right problems, explore solutions, ship them and stay involved through iteration.

The craft of product design is changing quickly. The tools, the workflows and the expectations around what a designer can do in a day are all shifting. Our team works with LLMs such as Claude in the daily flow, and we expect the designer we hire to already be shaping their own process in similar ways. Figma is still where systems and polish live, but the thinking starts earlier and the prototyping gets closer to code than it used to.

You will work inside mature applications. Atlas EMR is used every day by real clinics, and small decisions compound. That means respecting what already works, understanding why it works and improving things without disrupting the people whose livelihoods run on the product. Shipping new features is part of the job. So is quiet, thoughtful refinement of what is already there.

• Own product work end to end: Partner with product and engineering to define problems, explore solutions, validate direction and ship. Stay involved past launch.
• Design across surfaces: Web apps, native mobile (iOS and Android), embeddable widgets and user portals. Most weeks you will touch more than one.
• Operate the design system: Own and evolve our Figma libraries. Keep components, autolayout and variables in a state where other designers and engineers can move fast inside them.
• Prototype closer to code: Move past static mocks where it helps. Use whatever tooling gets you to a real, testable artifact fastest.
• Communicate clearly async: Feature decks, recorded walkthroughs, written specs, Figma comments. We collaborate over text far more than over Zoom.
• Work close to engineering: Review builds, flag drift, and know when to fight for pixel fidelity vs. when to let something ship.
• Manage your own priorities: Multiple product areas, multiple moving pieces, light oversight. You keep the work moving.

• 3+ years designing product, ideally in SaaS or application-heavy environments
• Fluent in Figma: components, autolayout, variables, prototyping, dev mode
• Comfortable on both ends of the craft spectrum: rough flow mapping and pixel-level UI
• Strong product instinct. You can tell when a feature is pointed in the wrong direction before the mockups go bad.
• Comfortable designing for data-dense desktop web and for native mobile
• Working understanding of responsive design, accessibility and common patterns for complex applications
• Strong async writing. You can run a design review through text without losing signal.
• Self-directed. You do not need close supervision to ship.
• Tuned to how the profession is evolving. You are already adapting your process to the tools and expectations of the current moment, not waiting to be told how.

• Strong typography: pairing, scale, rhythm, hierarchy
• Confident with color, grid and layout across breakpoints and devices
• Sharp instinct for visual hierarchy. Knows when to stop.
• Comfortable with iconography and illustration, and can judge when to use libraries vs. custom
• Taste-aware. Can feel when something is off and explain why, not just flag it.
• Systems-minded. Prefers clean documented structure over endless open-ended exploration.

Full-time, remote. We work as a dispersed team and a lot happens over text, so you need to be comfortable there. Schedule is flexible, but at least 4 hours of overlap with your core team is mandatory.