UX Designer Remote, Austin, Texas; Hybrid View

About PressW

Press

W is where some of the world's most ambitious companies come to actually ship AI.

We're redefining how businesses harness AI by building real systems for real clients, not just selling slides about what's possible. We're a team of three exited AI founders and a group of Applied AI Engineers based in Austin, and we've been heads‑down for the last few years building this firm into something we're proud of: more than 70 production AI solutions shipped, 40+ clients across seven industries, and over $50M in measurable profit gains delivered.

We work on the bleeding edge of what AI can do, guide our clients to the right solutions for their business, and ship the infrastructure they run on.

We sell across three divisions.
Managed AI is our MSP, purpose‑built for institutional investors: private equity firms, venture capital funds, asset managers, and capital markets clients. We map how a firm actually works, deploy custom agents into the workflows that consume deal teams' time (reading deal documents, drafting IC memos, scoring targets, triaging inbound, structuring offers, monitoring portfolio companies), and keep evolving those systems as models and firm needs change.

AI Engineering embeds our teams directly with clients to build and harden production AI systems.
AI Transformation handles roadmap and readiness work, helping leaders figure out what to build, in what order, and how to prepare for it.

You will own the user experience for Press

W's healthcare scheduling platform rebuild (codename Phoenix), reporting to Engineering Leadership. The platform serves hundreds of thousands of workers across mobile and web, plus an admin interface used by 1,000+ healthcare facilities. Every user‑facing surface is being rebuilt from scratch, and you are the person who determines what the new experience looks and feels like.

This role starts before any frontend code is written. Your first months are research: auditing the existing platform's workflows, understanding where users struggle (template management is the #1 pain point and the top churn driver), and conducting customer research with the client's product and CS teams. That research directly informs the API design for each service group and the frontend architecture.

By the time frontend engineering begins (~week 20-24), you have months of research behind the design system and component library you're handing off.

• Lead internal platform audit and customer research (Phases 0-2). Map existing workflows, pain points, and user patterns. Work directly with the client's product and customer success teams to understand what needs to change and why.

• Provide API design input during backend service group migrations (Phase
  3). The REST API shapes should reflect how users actually work, not just how the database is structured.

• Design the complete user experience across two frontend batches: worker‑facing (schedule viewing, shift pickup, messaging, push notifications) and admin‑facing (template management, schedule building, reporting, compliance). The admin batch is where the platform's NPS moves.

• Build and maintain the design system and component library. Establish patterns for accessibility (WCAG 2.1 AA target), responsive design, and consistency across web and mobile.

• Create wireframes, prototypes, and high‑fidelity designs. Conduct usability testing to validate decisions before and during rollout.

• Participate in frontend rollout feedback: usability testing with real users during wave rollouts, synthesizing feedback, and iterating on the design.

• Present research findings and design decisions in weekly UX reviews with the Frontend Lead and client product team.

• Strong UX design experience with both web and mobile applications.

• Experience conducting user research and translating findings into product design decisions.

• Experience designing for complex, workflow‑heavy applications (scheduling, operations, admin tooling, or similar).

• Experience with legacy system transformation: understanding existing workflows well enough to redesign them without losing what works.

• Ability to design for systems involving APIs and data…