UX/UI Audit of Self-Serve AI Product: Playground (Paid, Ongoing Work Available)

We're a YC-backed startup building AI fraud and compliance tooling for banks and fintechs. Our newest product catches AI-generated and forged documents at customer onboarding. It's live, it's processed over a million documents, and it just launched publicly. We want a UX/UI designer to audit it with fresh eyes, both UI and UX. This is a paid trial. We're running the same task with a small group of designers, and we're looking for one person to work with on an ongoing basis afterward. You get paid either way. THE TASK Audit our product and tell us what's wrong with it. The attached PDF has everything you need: what the product does, who uses it, the specific path we'd like you to walk, and a glossary for the domain terms. Read it before you start. It takes about five minutes and it will make your two hours far more useful. THE DELIVERABLE A written audit. Format is up to you: PDF, Notion page, Google Doc, annotated Figma file, whatever you normally work in. We care about the thinking, not the packaging. What to include: • Findings, ranked. For each one: what you saw, where you saw it, why it's a problem for the user, and how badly it hurts. Worst first. • Your reasoning. Why that order. What you weighed against what. This tells us more about how you think than the findings themselves do. • Recommendations. What you'd change. Concrete beats abstract. Not asking for mockups, a clear sentence is fine. • Open questions. What you'd need to know before recommending anything bigger. Assumptions you had to make, things you'd want to test. • What you skipped. Anything you noticed but didn't have time to dig into. Six to ten findings is a good target, fewer if they go deep. We'd rather read five that are well argued than twenty-five that are listed. Length isn't the signal, prioritization is. Full detail on what makes a finding useful to us is in the PDF. SCOPE, TIME, AND HOW WE'LL WORK We expect this to take about 2 hours, and that's how we've priced it. Please don't spend more. We'd rather have 2 focused hours than 6 unpaid ones, and we're comparing everyone against the same scope. Turnaround is 2 days from when we start the contract. You'll work independently, but we're around the whole time and happy to answer questions. Please ask them. Understanding what we're actually trying to do is part of the work, and we'd rather answer a question than read an audit built on a wrong assumption. WHAT HAPPENS AFTER Once we've read the writeups, we'll set up a call with the strongest ones. You'll walk us through what you found and we'll dig in together: why you ranked things the way you did, where you're uncertain, what you'd do with more time. That conversation is the real screening step. From there we pick one person for ongoing UI/UX work with us, full time and remote. WHAT WE'RE LOOKING FOR • Experience designing complex internal tools or workflow software for professional users. Dashboards, admin panels, ops tooling, review queues, anything dense. • Ability to prioritize. Three findings that matter beat forty that don't. • Writing a non-designer can act on. Our engineers have to read this. • Comfort saying what's wrong. Background in fintech, risk, compliance, or security is a plus. It is not a requirement. We can teach the domain. We can't teach judgment. LOGISTICS • $120 fixed, funded in escrow before you start • 2 day turnaround, roughly 2 hours of work • We're in US Pacific. Latin America is ideal for overlap, but if you're strong and elsewhere, apply anyway • Everything you'll be auditing is public, so no NDA needed for this task • We'll share some additional test documents with you on starting • Individual hire, not an agency engagement. Whoever writes the proposal is who we expect to do the work and join the call TO APPLY Start your proposal with the word X-RAY so we know you read this. Then send us: 1. Your portfolio. We'd like to see some of the work you've done before. 2. A writing sample. A past audit, critique, teardown, or research writeup. Anything where you made an argument in prose. This is a writing-heavy role and portfolios don't show us that. 3. One complex tool you've designed for professional users, and one specific thing you changed about it. 4. Your availability over the next week.