Job Details

Fractional Product Systems Designer (Web + iOS) Location: Remote (U.S.-based)Job Type: 2030 hours/month Why This Role ExistsWe build internal business applications at speed using:v0 for prototypingAngular + PrimeNG for implementationNative iOS apps that must feel like iOS, not web-on-a-phoneAs our velocity increased, traditional screen-based design became unnecessary. What did become necessary is system-level UX ownership. This role exists to ensure our products remain:PredictableConsistentNative to their platformsEasy to learn and hard to misuseYou will not be designing every screen. You will be designing how the product behaves over time.Who You AreRequiredSenior-level product or systems designerExperience with internal or enterprise applicationsStrong systems thinking; comfortable defining rules and constraintsDeep familiarity with iOS as a platform (not just mobile UI)Comfortable challenging PMs and saying dont ship thatPragmatic, opinionated, and not precious about visualsStrong PlusExperience cleaning up inconsistent productsFamiliarity with component-based design systemsExperience working with engineers directlyPrior fractional or advisory rolesRed Flags (for us)Portfolio-first, system-light backgroundStrong preference for redesigns over convergenceFocus on delight over clarity and predictabilityReliance on Figma as the primary outputEngagement DetailsCompetitive hourly rate (senior, fractional)Long-term engagement if mutually successfulWhat Youll Be Responsible ForProduct-wide UX coherenceOwn interaction patterns across the productEnsure similar problems are solved the same wayReduce inconsistency as new modules are addedPrevent UX drift as multiple PMs and teams ship in parallelWorking within existing productsAudit current applications and patternsIdentify what already works and should be preservedDrive convergence not redesign-for-the-sake-of-redesignRespect user muscle memoryWeb UX (Angular + PrimeNG)Define how PrimeNG components are used (tables, forms, filters, modals)Establish behavioral standards:StatesErrorsPermissionsProgressive disclosurePrevent almost-the-same component variantsiOS UX (Native-first)Ensure strict alignment with Apple Human Interface GuidelinesCatch web/Android patterns leaking into iOSEnforce native navigation, gestures, and control usagePrioritize platform correctness over internal consistency when they conflictPartnering with PMsReview v0 prototypes and early implementationsProvide fast, opinionated feedbackHelp PMs reason through UX tradeoffsEstablish clear guardrails PMs can confidently operate withinWhat You Will Not Be DoingPixel-perfect mock productionDesigning every feature or screenMaintaining Figma parity with codeVisual branding or marketing designCreating handoff artifacts for engineersIf your default output is screens, this is not the right role.What Success Looks LikeUX feels consistent across modules and platformsPMs move fast without inventing new patternsFewer usability questions from usersFaster onboarding with less trainingNo why does this work differently over here? momentsNo large-scale UX rewrites six months laterHow Youll WorkFractional, 2030 hours per monthReview-heavy, not production-heavyEmbedded early in feature thinking, not late-stage polishPrefer rules, patterns, and written guidance over visualsUse Figma only when a concept cannot be expressed clearly in text or prototypesCode and prototypes are the source of truth.
recblid ecwl7qnjp9jh6p1z6y64cqr72f7awt