Requirements

• 3–6 years experience in product design (mobile and web), owning features end-to-end in a cross-functional team.
  
• Strong interaction design fundamentals: flows, states, edge cases, information architecture, and usability.
  
• Strong visual craft and UI execution (spacing, hierarchy, layout, typography), with comfort working within a design system.
  
• Proficiency with Figma (components, variants, auto-layout, prototyping).
  
• Experience working iteratively (Agile-style), shipping in increments, and improving based on feedback and data.
  
• Ability to translate messy real-world requirements into clear, buildable specs—without over-designing.
  
• Clear communicator: can explain trade-offs, align stakeholders, and collaborate tightly with engineers and QA.
  

Nice to have

• Experience designing for offline/low-bandwidth environments or emerging-market contexts.
  
• Experience designing for operational tools (logistics, inventory, field ops, admin dashboards).
  
• Familiarity with accessibility standards (WCAG) and designing inclusive experiences.
  
• Comfort running lightweight usability tests or field discovery
  

• Own end-to-end feature design from problem framing → flows → interaction/visual design → prototyping → handoff → iteration in production.
  
• Work cross-functionally with Product, Engineering, QA, Data, and Operations to define the right solution and ship it in iterative modules (Agile delivery, frequent releases).
  
• Design for multiple user personas (e.g., parents, tappers, school admins, kitchen teams, internal ops) and ensure role-based clarity.
  
• Design for operational constraints: offline-first or low-connectivity patterns, queue-speed interactions, device realities (older Androids), and high-stakes accuracy.
  
• Prototype to learn fast, use clickable prototypes to validate workflows and de-risk engineering before build.
  
• Contribute to the design system, pushing consistency across all our digital solutions.
  
• Continuous UX research, participate in/lead usability testing and incorporate findings into iterations, with a bias toward measurable improvements on critical flows.
  
• Communicate clearly, present rationale, trade-offs, and decisions in reviews, and keep stakeholders aligned without drama.
  
• Maintain strong handoff discipline: clean files, component reuse, accessibility notes, and developer-friendly specs.