Product designer
פורסם אתמול · 32 מועמדים
התפקיד במילים פשוטות
התפקיד כולל עיצוב תהליכים ומוצרים שלמים מותאמים למובייל, תוך תמיכה במצב כהה ועיצוב דו-כיווני (RTL ו-LTR). העבודה דורשת הרחבה ותחזוקה של מערכת ה-Design System הקיימת, כתיבת מיקרו-קופי, ומחקר משתמשים ישיר מול בעלי עסקים כדי לדייק את המסכים גם לאחר ההשקה.
- Three years or more of product design, and at least one product carried from nothing to people using it
- Figma to a standard other people can build from: components, states, and edge cases
- Fluency with right-to-left (RTL) layout and design
- Dark mode design using semantic tokens and light-dark palettes
- Accessibility standards (contrast, focus, target size, reduced motion, screen readers)
- Experience maintaining design systems
- Arabic or Russian language proficiency in product contexts
- Tailwind or utility CSS systems
- Self-run user research (recruiting, interviewing, synthesis)
חולץ מתיאור המשרה · מתעדכן אוטומטית
למי זה מתאים
התפקיד מתאים למעצבי מוצר עם לפחות 3 שנות ניסיון, שליטה מעמיקה ב-Figma ו-RTL, ורקע טכני בסיסי ב-HTML/CSS ונגישות. פחות יתאים למי שמחפש לעצב בלבד ללא כתיבת טקסטים או ללא התחשבות במגבלות פיתוח ומערכות עיצוב קיימות.
תיאור המשרה המלא
המשרה המקורית · נשמר לעיוןAll roles
Product designer
Product Tel Aviv Full-time
A design system that already exists, two writing directions, and screens people use one-handed on a bus.
About The Role
Every screen in Torim serves two people: somebody booking a haircut in thirty seconds, and somebody whose whole working day is that diary. The design system is written down — tokens and components — and the hard part of this role is keeping it one system while it grows.
What you would do
• Design whole flows — in both directions, in light and dark, on a phone first.
• Extend the design system rather than route around it, and say for each addition why it is not a duplicate of something already there.
• Sit with business owners and watch what they actually do, which is almost never what the wireframe assumed.
• Write the words as well as draw the boxes — the label, the empty state, and the sentence that explains a refusal.
• Stay with a screen after it ships: watch it being used, and change it.
What we are looking for
• Three years or more of product design, and at least one product you carried from nothing to people using it — show a screen you changed twice and why.
• Figma to a standard other people can build from: components, states, and the awkward cases drawn rather than described.
• Fluent with right-to-left layout. Two of the four languages here are RTL, and Arabic is what catches a design that only ever meant Hebrew.
• Dark mode as one palette rather than two — this system is semantic tokens and `light-dark()`, and there is not a single `dark:` variant in the tree.
• Accessibility as a floor and not a phase — contrast, focus, target size, reduced motion, and a screen reader you have actually used.
• HTML and CSS well enough to argue with an engineer about what is expensive: logical properties, grid, and why a hardcoded colour breaks a theme.
• Hebrew at native level, English at working level.
Nice to have, not required
None of these is a condition. If you have none of them, apply anyway.
• Design systems you have maintained rather than only started.
• Arabic or Russian, in a product rather than at a dinner table.
• Tailwind, or a utility system you kept coherent while it grew.
• Research you ran yourself — recruiting, interviewing, and writing up what you got wrong.
Apply
Attach a CV, give a LinkedIn profile, or both. One of the two is required.
Website
Name Email address Phone
• optional LinkedIn profile For example linkedin.com/in/your-name CV Drop a file here, or tap to choose one PDF or an image, up to 5MB. Anything we should know
• optional A few lines about you, or a link to work you are proud of.
Your details and CV are kept for up to a year, then deleted.
שאלות על המשרה
- המשרה לא ציינה שכר. אנחנו מציגים שכר רק כשהמעסיק מפרסם אותו.
- Three years or more of product design, and at least one product carried from nothing to people using it, Figma to a standard other people can build from: components, states, and edge cases, Fluency with right-to-left (RTL) layout and design, Dark mode design using semantic tokens and light-dark palettes, Accessibility standards (contrast, focus, target size, reduced motion, screen readers)