About the role

You'll own the LottieFiles Platform our SaaS DAM where teams store, organize, review, and ship creative assets. It's a product used by teams at Google, TikTok, Disney, and thousands of others. It's also technically dense: GraphQL underneath, a permissions system that has to get every edge case right, workspace and account models, auth flows, and a dozen sub-systems that have to play nicely together.

You don't need to be an engineer. You do need to think like one when the situation calls for it.

What you'll do

• Own the roadmap for Platform like workspaces, collaboration, asset management, sharing, search, and the surfaces customers touch every day
• Work directly in GraphQL schemas, permission models, and system diagrams when shaping a feature. Specs that ignore the data model get rewritten by engineers
• Make the right tradeoffs between shipping fast and not breaking the systems other products depend on (Creator, Workflow, integrations all sit on top of Platform)
• Drive enterprise-grade work: SSO, SCIM, RBAC, audit logs, admin controls, compliance like the things that close six-figure deals
• Talk to customers. The DAM is a product people live in for hours a day; you need to understand how their teams actually work
• Define and track the metrics that matter: activation, retention, expansion, time-to-value for new workspaces
• Partner with GTM, design, and engineering to ship launches that land
• Be the person leadership trusts when they need a straight answer about what's possible, what it'll cost, and what it'll break
  
  

What we're looking for

• 5+ years in product, with meaningful time on SaaS products that have real technical depth
• Comfort reading and reasoning about GraphQL schemas, RPC, REST APIs, auth flows (OAuth, SSO, SAML), and permission models (RBAC, sharing semantics, inheritance)
• Comfortable working across cloud providers (AWS, GCP), CI/CD pipelines, and relational databases, Postgresql preferred.
• Working knowledge of the AI stack like LLMs, embeddings, vector databases (pgvector, Pinecone, or similar), and RAG patterns.
• You've shipped collaboration or workspace features and know why they're harder than they look
• You write specs that handle the edge cases like permission conflicts, billing transitions, migration paths without hand-waving
• Strong product instincts. Technical depth is a tool, not the job. The job is shipping things customers love
• Clear writer. Specs, RFCs, launch notes, customer communications.
• Bonus: DAM, creative tools, or design platform experience; multi-tenant SaaS at scale; experience deprecating or migrating customer-facing systems without breaking trust