Senior POS Designer for Existing Restaurant Platform

We are looking for a senior UI/UX/Product Designer who has previously designed a real restaurant POS system. Important — please read before applying Previous restaurant POS design experience is mandatory. Please do not apply if your experience is limited to: * generic SaaS dashboards * restaurant websites * food-delivery/customer ordering apps * booking/reservation apps * e-commerce checkout * conceptual Dribbble POS screens with no complete operational flow * general mobile/web UI without restaurant POS experience We are specifically looking for someone who understands restaurant operations and has previously designed meaningful parts of a system involving areas such as: table/floor management → order taking → modifiers → KOT → kitchen/KDS → running checks → split/settlement → payment → receipt You do not necessarily need experience with every module, but you must be able to show substantial restaurant POS work. About the project We have an existing, working offline-first commerce/POS platform, with restaurants as its first major vertical. The functionality and major workflows are already built. This is not a project where you need to invent the restaurant product from scratch. We are looking for a designer to review the existing experience and create a complete, coherent UI/UX direction across: * Restaurant POS / Cashier — tables/floors, order taking, modifiers, KOT, checks, discounts/voids, split bills, settlement, payments and receipts * KDS — kitchen tickets, stations, timers, item states, amendments and completed orders * Waiter / handheld — fast touch-first restaurant workflows * Driver / Delivery — operational delivery workflows * Back Office / Admin — menus, products, modifiers, tables/floors, staff/roles, customers, printers/devices, orders, reports and settings * Design system — typography, colours, spacing, iconography, controls, forms, tables, operational states, navigation, overlays and reusable components * Responsive behaviour across tills, tablets, handheld/mobile and web/admin * Light and dark themes where appropriate What we are trying to achieve We want the result to feel like a purpose-built operational POS, not a generic SaaS dashboard adapted to restaurants. The interface needs to achieve: high information density without visual noise very fast operation during restaurant rush hours minimal taps for common actions clear table/order/KDS states excellent touch usability strong hierarchy restrained and meaningful use of colour consistent interactions across POS, KDS, mobile and Back Office The result should be a design system, not a collection of unrelated screens. Our development team must be able to take an approved component/pattern and reuse it elsewhere without the product visually drifting. Design quality We have specific high-quality restaurant POS references that we will share with shortlisted candidates. We particularly value design thinking that produces: * dense but calm operational screens * hierarchy through typography, spacing, surfaces and dividers rather than excessive cards * compact but touch-friendly controls * clear separation between selection, identity and operational state * context remaining visible while the operator works * purpose-built payment, KDS, table and authorization interactions * consistency across different roles and device sizes We do not want another product copied. The final system should have its own recognisable identity. Existing product and design work The underlying product already exists. Shortlisted designers will receive: * access to the working development environment * existing restaurant workflows * previous product versions * our current internal design-system/V6 exploration * detailed product clarification Our existing design exploration is not something you are required to preserve. We expect a strong designer to tell us what should remain, what should change and what can be improved. Future platform direction Restaurants are the first major vertical, but the underlying product is a modular commerce platform intended to expand into additional niches. It is also India-first but intended for multiple countries. The design system therefore needs to scale across: * multiple business verticals * multiple currencies * languages and translated text lengths * different tax structures * market-specific payment methods * different roles * tills, tablets, handheld devices and web * market-specific operational requirements Restaurant-specific workflows should be able to extend the shared platform system without forcing every future vertical to look like a restaurant POS. Deliverables Expected scope includes: * UX review of the existing restaurant POS * complete restaurant POS UI/UX * table/floor workflows * order-taking and modifier workflows * KDS * waiter/handheld experience * payment/settlement flows * driver/delivery experience * Back Office/Admin * responsive designs * light/dark treatment where required * complete reusable Figma design system * component variants/states * key edge/error/offline states * prototypes for important flows * organised developer-ready Figma handoff Final scope can be agreed after reviewing the working product. Mandatory application requirements Do not send us only your general portfolio. Your proposal must include: 1. The restaurant POS system(s) you previously worked on. 2. Screens or a case study showing the actual POS—not only the customer ordering app. 3. Which parts you personally designed. 4. Whether it was a real client/product or a concept/exploration. 5. Which flows you designed: tables, ordering, modifiers, KDS, payment, Back Office, etc. 6. Whether you designed the complete system or worked as part of a team. 7. Your approximate fixed-price range for our scope. 8. Your estimated timeline. Private/NDA work is acceptable only if you are legally permitted to show us some evidence privately. Screening requirement Start your proposal with: RESTAURANT POS — [name of the restaurant POS you