Flying Bisons
UX/UI Designer (AI-Native Process)
About this role
This role doesn't exist yet at most companies. We're looking for designers who don't start in Figma. You start in Magic Patterns, v0, Cursor, Claude Code — whatever gets you to a working, clickable prototype fastest. You think "generate first." You talk to your tools. You ship rough, iterate fast, and hand off to our craft team for the final polish. At Flying Bisons, we're rebuilding our design process around a simple principle: interactive prototypes before static screens. Every project, every module. We need people who can take a brief and produce 70-80% of the design as a working prototype — fast — so our senior strategists can focus on what to build, and our craft designers can focus on making it beautiful. We call this the AI-First Designer role. You are the engine of production in our Pyramid framework: you sit between the people who define the product and the people who polish it to perfection. You generate the bulk of the work. Speed and iteration are your core skills. What you'll actually do You'll join project teams alongside Strategic & Senior UX Designers (who own strategy and scope) and Top UI Designers (who own visual direction and craft). Your job starts when the concept is approved and the scope is locked. In practice, your week looks like this: you get a module brief — "build the checkout flow for a B2B e-commerce platform, here are the user stories, here's the approved visual direction." You open your AI tool of choice, start prompting (probably talking, not typing), and within a couple of hours you have an interactive prototype with real interactions, real copy, and real edge cases. You share it with the team async. They give feedback. You iterate. When it's solid, you hand it to a UI designer who takes it to 100% in Figma — design system compliance, pixel perfection, all states, documentation. You'll also be involved in concept workshops, where you build rough interactive prototypes live during the session so the team can react to something real, not abstract sketches. And honestly — you'll be a bit of an evangelist. You'll be one of the first people in this role at Flying Bisons. Your work will set the standard for how the rest of the team thinks about AI-first design. What we're looking for You think in a different paradigm. When you hear "design a settings page," your instinct isn't to open Figma and start placing rectangles. Your instinct is to describe what the settings page should do, prompt an AI tool, get a working version, and start shaping it from there. Generation first, refinement second. You're fast. You can go from a text or voice brief to a clickable, multi-screen prototype in under 2 hours. You don't aim for perfection on the first pass — you aim for something real enough that people can click through it and give meaningful feedback. You're fluent in AI design tools. You work regularly with at least 2-3 of these: Magic Patterns, v0, Bolt, Lovable, Cursor, Claude Code, Figma Make. You know their strengths and weaknesses. You know when to switch tools. You understand front-end fundamentals. You don't need to be a developer, but you understand HTML structure, CSS layout, how components work, what's easy and what's hard to implement. This makes your prompts better and your prototypes more realistic. You have design sensibility. You're not a pixel-perfect UI specialist — that's a different role on the team. But you know when something looks wrong, when spacing is off, when a flow doesn't make sense. You care about the end experience, even at the 70% stage. You can hold product thinking. You understand user stories, flows, edge cases, empty states, error handling. When you generate a prototype, you think about what happens when the list is empty, when the user makes a mistake, when there are 3 items vs. 300. You don't just build the happy path. What we don't care about
- How many years you've spent in Figma
- Whether you have a traditional design degree
- Whether your portfolio is full of polished static screens
- Whether you've worked at a "name brand" company What we want to see instead Show us things you've built with AI tools. Prototypes, apps, experiments, side projects — anything that demonstrates you think "generate first. " A video of you going from brief to prototype in real-time is worth more than 10 Behance case studies. Show us speed. During the interview process, we'll give you a real brief and 45-60 minutes with your AI tool of choice. We want to see how you think, how you prompt, how you iterate, how many decisions you make per minute. Show us product thinking. When you build a prototype, do you think about edge cases without being told? Do you consider different user types? Do you ask "what happens when...?" before we do? The interview process No cover letters. No "tell me about a time when…" questions. We want to see how you think and what you build. The process has four steps: Step 1 — Video application (max 12 min) Record a single video in English with exactly 3 parts: Part 1: Show us a build (4-5 min). Pick one thing you've built with AI tools — a prototype, an app, an experiment, anything. Screen-record yourself walking through it. Show the final result AND your process: what tools you used, how you prompted, how many iterations it took, what decisions you made along the way. We want to see your thinking, not just the output. Narrate what worked and what didn't. Part 2: Your toolkit (2–3 min) Walk us through the AI tools you use daily. Open them, show us your actual workspace — projects, history, components. Which tool for which task? What have you tried and abandoned? We're lookingfor real daily usage, not a list of logos on a slide. Part 3: Your view on the future of work (2–3 min) Talk to us directly, no screen share needed. Answer this question: "What will a design team look like in 2 years, and what role will you play in it?" There's no right answer. We want to hear how you think about where this is all going. What NOT to include: