Product Designer — Design Audit, RTL & Dev Handoff

Context A saudi based fintech platform for fundraising. Two dashboards — Company and Investor — across several products. Web app, desktop-first, mobile optimized for specific flows. The design is ~90% done. The Figma file has all major flows built out. What's missing is not creative direction — it's the last mile: consistency, polish, the handful of screens I left for someone better than me, bilingual support, and turning the file into something a developer can build from without guessing. Important: there is no formal design system — the file has color and text styles only. You are not being asked to invent a new visual language. You are being asked to work inside the existing look and feel, tighten it, and systematize it. Scope 1. Design audit (the biggest piece) Go through the app screen by screen, as if you were a user actually using it, and find what's broken: Inconsistent button sizes, padding, corner radii, spacing Broken or drifting layouts and page structure Missing states — empty, loading, error, success, disabled, zero-data Missing confirmations, success messages, toasts, validation copy Inconsistent components doing the same job in different places Anything that would make a developer stop and ask "what happens here?" Deliver findings as a written list first (grouped by severity), then apply the fixes once we've aligned. 2. Net-new design (small) A short list of screens I intentionally left for a stronger designer. Roughly 3–6 screens These need to feel designed, not assembled. Everything else already exists. 3. Arabic / RTL The platform ships in English and Arabic. I need you to own the RTL strategy, not just execute it. Specifically: A written RTL ruleset: what mirrors, what doesn't (numbers, currency, IBANs, phone numbers, charts, timelines, progress indicators, directional vs. non-directional icons), and how the language switch behaves An Arabic type scale that pairs with the existing English one RTL versions of the screens where mirroring is genuinely non-obvious — I do not expect a duplicated RTL copy of every screen in the file. Tell me which ones actually need it and why Arabic copy handling: text expansion/contraction, line-height, truncation risk If you have a better approach than the above, propose it, I want your opinion here, this is the part I know least about. 4. Developer handoff Turn the file into something a dev team can build from: Componentize repeated elements (variants, properties, auto-layout) Consistent, sane layer and component naming Tokenize colors, type, spacing, radii into proper styles/variables (incl. light/dark if applicable, and LTR/RTL where relevant) Annotate behavior where the frame alone doesn't explain it (interaction, transitions, conditional states) Clean file structure: pages, flows, and screens organized so a dev can find things What you get from me Full Figma access and full professional seat for your AI workflow enablement. Written product specs (behavior, business rules, lifecycle) — the logic is documented, you won't be guessing A walkthrough call, then async Fast decisions. I respond quickly and I don't sit on feedback. What I'm looking for Strong product/SaaS dashboard experience, dense data, tables, multi-step flows, financial UI. Not marketing sites, not mobile apps. Real Arabic + RTL experience in a shipped product (this is close to a hard requirement) Figma componentization and dev handoff you've actually done before, not just heard about Someone who can spot inconsistency without being told where to look We estimate it to be a 1 week to 2 week job. And we need someone that is available and works fast. Preferably when you apply: Link 1–2 dashboard/SaaS products you designed. Show me RTL work you've shipped. In 3–4 sentences: how would you handle RTL in a Figma file, duplicate every screen, or something else?