Role Overview
Maya Mobile is a global B2C travel eSIM business serving millions of international travelers across 165+ countries. Design is not a support function here. It is the primary lever that determines whether a traveler finds the right plan, trusts us enough to buy, activates without help, and comes back the next trip.
We are hiring a Senior Product Designer to own the end-to-end design practice across our mobile apps and responsive web. This is not a role where you receive specs and produce screens. You will define how millions of customers experience Maya: the flows, the conversion surfaces, the design system, and the feedback loops that connect real user behavior to continuous improvement.
You will walk into an environment where design has been functional but not yet expert-led. We need someone who already knows what world-class B2C product design looks like, who can assess where Maya is today, articulate what needs to change, and personally drive the transformation while building the foundation for a design team over time.
Key Responsibilities
Design Strategy and Standards
- Conduct an end-to-end audit of the current customer experience across app and web. Identify the highest-impact UX and conversion problems and create a prioritized design roadmap.
- Establish the design principles, quality bar, and review process that all customer-facing surfaces must meet before shipping.
- Build and maintain a production-grade design system (component library, tokens, patterns, documentation) that ensures consistency across app, web, email, and campaign surfaces while enabling engineering to ship faster.
- Define the UX research and insight practice: what data sources are used, how insights are captured, how they feed into the design cycle, and how design impact is measured.
Product Design and Conversion
- Own the complete design of core product flows: discovery, plan selection, purchase, eSIM activation, account management, and support. Accountable for usability, task completion, and conversion at each step.
- Own the design of high-conversion landing pages, lifecycle emails, and campaign surfaces. Apply layout hierarchy, progressive disclosure, and friction-reduction techniques grounded in evidence rather than opinion.
- Develop a structured experimentation practice: define hypotheses, design test variants, partner with engineering and analytics to run tests, and use results to inform subsequent design decisions.
- Ensure every design accounts for real-world constraints: device diversity, connectivity conditions during travel, localization, accessibility (WCAG), and platform conventions (iOS and Android).
Insight, Analytics, and Continuous Improvement
- Use quantitative data (funnel analytics, heatmaps, session recordings, conversion metrics) and qualitative data (support tickets, reviews, user feedback) to diagnose problems and prioritize design work.
- Partner with Customer Operations to build a systematic feedback loop: understand where users get stuck, what generates support contacts, and what drives complaints, then translate that into measurable design improvements.
- Establish clear design KPIs (task success rate, funnel conversion, time-to-activation, support contact rate on redesigned flows) and report on them regularly.
- Evaluate how AI and modern tooling (generative design, automated QA, personalization) can accelerate design output and improve quality.
Cross-Functional Leadership
- Partner closely with Product and Engineering on prioritization, feasibility, handoff, and shipped quality. Design intent should survive implementation; gaps between design and production are treated as defects.
- Collaborate with Marketing on brand consistency, ad-to-landing-page alignment, and campaign creative standards.
- Communicate design rationale, trade-offs, and results clearly to senior leadership. Be the voice of the customer experience in strategic discussions.
- As the company scales, scope, hire, and develop a small design team. Define roles, standards, and workflows that maintain quality as volume increases.
What Success Looks Like (First 6-12 Months)
- Completed a full UX audit and delivered a prioritized design roadmap that leadership has bought into and that is actively being executed.
- Redesigned the highest-friction flows (purchase and activation are likely candidates) with measurable improvement in conversion or task completion.
- Shipped a functioning, documented design system that engineering actively uses and that has reduced visual inconsistency across surfaces.
- Established a running experimentation cadence: tests are being designed, run, and fed back into the product cycle, not treated as one-off projects.
- Built a systematic feedback loop with Customer Operations so that recurring UX issues surface in design prioritization rather than only in support queues.
- Design quality is visibly higher. Stakeholders, engineers, and customers can see and feel the difference.
- Provided a clear, evidence-based recommendation on whether, when, and what type of design hire(s) Maya needs next.
Experience and Qualifications
Required
- 7+ years designing consumer digital products with meaningful time spent in a product design (not purely visual or brand) capacity.
- A portfolio of shipped work across mobile app (iOS and Android) and responsive web, demonstrating end-to-end ownership from problem framing through final UI rather than just polished screens.
- Demonstrated experience improving conversion, activation, or retention through design. You can point to specific flows you redesigned and the business impact that resulted.
- Expert-level Figma proficiency. Non-negotiable.
- Hands-on experience building or significantly evolving a design system used in production.
- Strong analytical instinct: you regularly use funnel data, heatmaps, session recordings, and experiment results to diagnose problems and validate solutions rather than relying on intuition alone.
- Experience designing for real-world complexity: localization, accessibility (ADA/WCAG), device fragmentation, and variable connectivity.
- Experience designing responsive email templates in Klaviyo or a comparable ESP.
- Clear, direct communication skills. You can present a design rationale to a non-design audience, defend decisions with evidence, and accept challenge without defensiveness.
- Must be based in and work EST, CST, or PST hours. This is a hard requirement.
Strong Advantages
- Experience at a high-growth B2C technology, travel, subscription, marketplace, or e-commerce company where design directly influenced commercial outcomes.
- Hands-on CRO experience: you have personally designed, run, and analyzed A/B or multivariate tests.
- Copywriting ability or strong content design instinct: you draft the words in your own designs rather than waiting on copy.
- Motion design, micro-interaction, or animation skills.
- Front-end literacy sufficient to have productive technical conversations, review implementation quality, and understand engineering constraints.
- Experience with AI-assisted design tools and an informed view on where they do and do not add value.
- Experience in a multi-language or multi-market product environment.
- Experience hiring, mentoring, or managing other designers.
Ideal Candidate Profile
You are a senior product designer (or strong #2 at a more established company) who has already built or materially upgraded the design function at a consumer technology business. You think in outcomes, not deliverables. You are as comfortable digging into funnel data and session recordings as you are polishing a screen. You have strong opinions about what great product design looks like and you back them with evidence. You want ownership of an entire customer experience rather than a queue of tickets, and you are energized by building something from a strong base rather than optimizing an already-mature system.
You are not looking for a role where someone else sets the vision and you execute it. You want to be the person who walks in, assesses the landscape, says "here is what needs to change and here is why," and then does the work to make it happen.
Key Changes From the Original Job Description
• Title: UX/UI Designer to Senior Product Designer. "UX/UI Designer" undersells the scope and signals a mid-level execution role. "Senior Product Designer" reflects end-to-end ownership of product experience and conversion, which is what the role actually demands.
• From activity list to ownership model. The original listed tasks ("design end-to-end flows," "build a component library"). The rewrite frames each area around what the person is accountable for achieving and the outcomes they must produce.
• Added design strategy and audit responsibility. The original assumed the person would slot into existing workflows. The rewrite expects them to assess the current state, define what good looks like, and build the roadmap themselves.
• Elevated analytical requirements. The original mentioned heatmaps and session recordings as a plus. The rewrite makes data-driven diagnosis, experimentation, and KPI ownership core to the role.
• Added experimentation ownership. A/B testing was a "strong plus" in the original. In the rewrite, establishing and running a structured experimentation practice is a primary responsibility.
• Added customer feedback loop. The original mentioned working with support. The rewrite requires building a systematic, recurring insight loop between Customer Operations and design.
• Added team-building trajectory. The original was a pure individual contributor role. The rewrite includes scoping the team and eventually hiring as the company scales.
• Added AI and modern tooling expectation. Not present in the original. The rewrite asks the candidate to evaluate where AI and automation can improve design velocity and quality.
• Sharpened success metrics. The original listed general statements ("conversion improves"). The rewrite specifies concrete 6-12 month deliverables: completed audit, redesigned flows with measured improvement, shipped design system, running experimentation cadence, and a team-build recommendation.
• Removed generic language. Phrases like "give and take feedback without ego" and "design for real constraints, not ideal cases" were replaced with specific, measurable expectations.