WeSearch

Flick (YC F25) Is Hiring Front End Engineer to Build Figma for AI Filmmaking

·1 min read · 0 reactions · 0 comments · 31 views
Flick (YC F25) Is Hiring Front End Engineer to Build Figma for AI Filmmaking
TL;DR · WeSearch summary

Flick is seeking a front-end engineer to develop a platform for AI filmmaking, akin to Figma. The role involves leading the creation of the user interface and collaborating with various teams to enhance user experience. Candidates should have experience in high-performance web applications and a passion for creative interfaces.

Key facts
About this source

Hacker News (Front Page) files mainly under programming. We currently carry 1,007 of its stories. Top-voted stories on Hacker News.

Original article
Y Combinator
Read full at Y Combinator →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherY Combinator
Canonical URLhttps://www.ycombinator.com/companies/flick/jobs/Tdu6FH6-senior-frontend-engineer
Publication timeSun, 24 May 2026 17:00:46 +0000
Retrieval time2026-05-24T17:07:33.664Z
Last seen2026-05-24T17:07:33.664Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterzbMZ2XtSDFR4
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

About Us Flick is defining the future interface for AI native filmmaking. Think Figma and Cursor, but for creating AI films. Founded by Engineer who built Instagram Stories + Award winning filmmaker, we are a team of Tech + Artist. Well-funded by top VCs. Checkout our recent launch post Award-winning AI Films created using Flick The Role As our founding front-end engineer, you’ll lead the development of the core experience of Flick — our canvas, timeline, and creative tooling. You will work directly with the founders, and have the opportunity to shape the future interface for AI visual storytelling. What you’ll do Lead the architecture and development of our editor UI from the ground up (canvas, timeline, node graph, playback).

Excerpt limited to ~120 words for fair-use compliance. The full article is at Y Combinator.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Y Combinator