Flick is Building the ‘Figma for AI Filmmaking’ as it Recruits for Founding Engineering Roles
Table of Contents
Moving Beyond the Prompt Box
For the past year, the primary interface for AI video generation has been a simple text box. Whether using Runway, Luma Dream Machine, or Kling, the workflow is largely linear: type a prompt, wait for a render, and hope the seed matches your vision. If it doesn’t, you tweak a word and try again. It is a process of lottery, not direction.
Flick, a new startup emerging from the Y Combinator F25 cohort, believes this is the wrong way to build a movie. Instead of treating AI as a vending machine for clips, Flick is building a spatial, collaborative environment designed specifically for AI-native filmmaking. The company describes its vision as a “Figma for AI filmmaking,” suggesting a shift toward a canvas-based workflow where directors can manipulate scenes, characters, and timelines with the precision of a graphic designer or a software engineer.
The ‘Cursor’ Moment for Video
The comparison to Figma isn’t just about collaboration; it’s about the transition from static tools to dynamic, intelligent systems. By citing Cursor—the AI-powered code editor that has rapidly gained traction by integrating LLMs directly into the development environment—Flick is signaling a move toward “agentic” editing. In this model, the tool doesn’t just execute a command; it understands the context of the entire project.
For a filmmaker, this could mean a timeline that doesn’t just store clips, but manages consistent character identities across different shots or suggests lighting adjustments based on the emotional arc of a scene. The goal is to remove the friction between a director’s intent and the final pixel, turning the AI from a generator into a sophisticated production assistant.
Building the Foundational Stack
To realize this, Flick is currently in the aggressive hiring phase typical of YC companies, specifically hunting for a founding front-end engineer. The role is critical because the “canvas” is the product. Creating a high-performance timeline and a flexible creative workspace that can handle the heavy data loads of AI video—without the lag that plagues traditional browser-based editors—is a significant technical hurdle.
The founding engineer will be tasked with developing the core experience: the canvas where assets are arranged, the timeline where temporal logic is applied, and the creative tooling that allows users to “paint” or “direct” AI generation in real-time. It is a bet that the next great leap in AI cinema won’t come from a better model, but from a better user interface.
The Shift Toward AI-Native Production
Flick enters a crowded but fragmented market. While Adobe is integrating Firefly into Premiere and DaVinci Resolve continues to lean into neural engine masking, these are largely legacy tools with AI bolted on. Flick is taking the opposite approach, building from the ground up for a world where the “footage” doesn’t exist until the moment it is generated.
This approach mirrors the shift seen in software development. Just as engineers moved from basic text editors to IDEs and now to AI-native editors like Cursor, filmmakers are likely to move away from the traditional NLE (Non-Linear Editor) toward something more fluid. If Flick can solve the interface problem, they may move the AI filmmaking process from a series of lucky guesses to a repeatable, professional craft.
