Senior Product Designer

Experience is the value

This is not another health app. The difference between a member ignoring their lab results and a member changing behavior is almost always the quality of the interface, the moment, the language, and the interaction.

As Senior Product Designer, you will own the experience that turns complex health data into simple, motivating, behavior-changing product moments. From onboarding and lab booking to results reveal, plan execution, weekly review, and retesting.

You will make biomarkers understandable to someone with zero medical background. You will make the plan feel active, directive, and human, not like a PDF, a dashboard, or a generic wellness feed.

About atheal

Atheal is a personal health intelligence platform built for Saudi Arabia and the GCC. We combine comprehensive biomarker testing, deep medical expertise, and consumer-grade product design to help people understand their health before problems emerge.

The product challenge is hard: health is emotional, data-heavy, bilingual, and high-trust. That is exactly why design matters. We are not optimizing a lab portal. We are rethinking what a personal health product can be.

Backed by Sanabil Studio by Redesign Health.

What you will own

• Behavior-driven product design. Design experiences that guide people toward healthier decisions instead of simply displaying data. Make taking action feel natural, not overwhelming.
• Core member flows. First app open and onboarding, health profile and sensitive-question flows, lab booking and prep, waiting-for-results, first-time results reveal, returning and retest reveal, plans and supplement and lifestyle action detail, home as a daily touchpoint, weekly rewind, companion entry points, referral and gifting moments.
• Interaction and interface excellence. Hierarchy, spacing, typography, motion, transitions, and micro-interactions. Define what happens on tap, press, loading, success, failure, empty, error, partial, and returning-user states.
• Complex information made simple. Translate biomarkers, wearable metrics, scores, and trends into “what does this mean for me?” and “what should I do?” without spreadsheet energy or generic dashboard patterns.
• Arabic and English product design. Create RTL-ready designs that work natively in both languages. Treat Arabic parity as a product quality requirement, not a localization pass at the end.
• Design system and dev-ready handoff. Build and maintain tokens, components, variants, accessibility, and state matrices. Deliver production-ready specs that engineers can implement with confidence.
• Research, iteration, and measurement. Plan and run discovery interviews, usability tests, and comprehension testing with real users in Saudi Arabia. Iterate quickly while preserving a high bar for experience quality.

What strong looks like here

We are hiring for this role because our product is design-constrained. The right designer brings craft, process, and product judgment in equal measure.

• Systems thinking and feedback generalization. When a note lands on one screen — about hierarchy, tone, spacing, CTA clarity, state handling, or trust language — you proactively assess where else that issue exists and apply the fix consistently. You translate specific feedback into reusable principles, not local patches. Consistency is trust: members feel fragmentation between onboarding, results, and plans even when they cannot articulate it.
• End-to-end journey thinking. You see the whole member journey, not isolated screens. You ask what happens before and after, what if a member is new or returning or anxious, what if they have no data yet, and what is the one primary action right now.
• State and edge-case discipline. Empty, waiting, error, no-show, first-time, returning-user, Arabic, long-copy, and partial-data states are not polish. They are the product.
• Interaction design, not static screens. You think in flows, transitions, progressive disclosure, feedback loops, and daily-use patterns, not just beautiful frames.
• Dev-ready handoff. Clean Figma structure, named layers and components, state matrices, token usage, annotated interactions, motion and haptic notes, Arabic RTL screens, accessibility notes, and acceptance criteria. Engineering can build without guessing.
• Health-specific judgment. Tone, hierarchy, and timing are clinical product decisions, not copy polish. Words like “failing,” “poor,” or “non-adherent” can break trust. A biomarker out of range needs careful framing.
• Process and feedback closure. You make work visible. When feedback is given, you track it. When a decision is made, you document it. When something is unresolved, you flag it. Strong design without strong process will not work here.

You may be a good fit if you

• Have 3 to 7+ years of end-to-end product design experience, ideally in consumer health, wellness, fintech, education, or another complex, data-heavy consumer product.
• Have shipped iOS, Android, or responsive web products where the experience itself drove user value.
• Can show portfolio work where complex information became simple, motivating, and usable.
• Are excellent in Figma: Auto Layout, variables and tokens, components, variants, prototyping, Dev Mode, and file hygiene.
• Have strong interaction design instincts: timing, feedback, affordances, hierarchy, motion, and progressive disclosure.
• Care deeply about details: spacing, typography, edge cases, accessibility, touch targets, state coverage, and polish.
• Can translate ambiguous product strategy into concrete flows, prototypes, and production-ready specs.
• Are comfortable pushing back when shortcuts compromise user trust, comprehension, or product quality.
• Are excited by the challenge of making health feel approachable, personal, and empowering.

Strong plus: Arabic fluency or bilingual product experience, prior RTL design, health-tech or longevity or diagnostics or quantified-self experience, behavior-change loops or coaching products or AI-assisted experiences, design systems built 0 to 1, light front-end literacy (SwiftUI, React, Webflow, Framer), and pre-seed or seed startup experience.

What success looks like

By 30 days, you understand atheal’s member journey, product vision, design system, and known design gaps. You have audited the current experience and identified the highest-leverage fixes. You have produced or refined a clear standard for state coverage, handoff, Arabic parity, and health-language safety. One contained flow or component set is closed into dev-ready specs.

By 60 days, one major member flow is redesigned or materially improved and ready for engineering. Figma files are clean, structured, and easy for engineering to use. Empty, error, loading, and returning-user states are no longer afterthoughts. You have run or supported user testing for at least one high-risk product moment.

By 90 days, atheal has a stronger, more coherent end-to-end member journey. The results reveal, plan, or daily home experience has moved from concept to shippable product quality. The design system is more complete and production-aligned. Engineering can build from your specs with fewer clarification loops.

The real test: a member opens atheal, understands their health better, and takes the next right action without needing someone to explain the product to them.

What this isn’t

• Not a clinical role. You will not make clinical decisions or prescribe treatment.
• Not generic dashboard work. We are not building a portal that exposes data.
• Not Arabic as a translation pass. RTL is a product quality requirement, not a final step.
• Not visual polish without journey clarity. We will not optimize gloss while the core flow is confusing.
• Not static screens over the wall. Handoff includes states, behaviors, and implementation clarity.

How we hire

The process is built to be a scalable filter, not theatre. Each stage has clear milestones; we can cut early at any of them if the work indicates this is not the right fit.

1. Application. Send your portfolio, CV or LinkedIn, example Figma files, and a short note on why this mission speaks to you.
2. Portfolio review. We look for complex information made simple, shipped product judgment, interaction craft, design systems thinking, and clear process.
3. Paid trial task. A focused 2 to 4 hour exercise on a realistic atheal moment, like results reveal, waiting state, plan action detail, or retest progress. We use this as a scalable design interview — it lets us learn how you think, structure, simplify, and communicate before committing more of your time and ours. AI tools are welcome and encouraged. We work AI-natively here; we want to see how you use the tools, not have you avoid them. We test specifically for systems thinking and feedback generalization (turning notes on one screen into reusable principles across the journey), end-to-end thinking, state and edge-case discipline, communication, and health-specific judgment.
4. Design conversation. A working session with product, clinical, and engineering leads, anchored on the work you submitted in the trial task. We discuss health UX tradeoffs, behavior change, handoff, RTL, how you approach ambiguity, and how you would translate trial-task feedback into broader product principles.
5. Final conversation. Meet the founders. Ask anything. We align on role shape, working style, compensation, and expectations for a high-commitment, remote-friendly contract.