Job description

🎨 About OpenArt OpenArt is an AI storytelling and visual creation platform used by millions of creators worldwide. We're building the next generation of creative tools powered by cutting-edge AI — enabling anyone to create videos, visuals, characters, and stories with unprecedented speed and imagination. We believe the future of creativity is AI-native, and we're shaping that future. 🚀 Why Join OpenArt - Brand-new function, real mandate — enterprise and team customers are one of our biggest growth levers, and most of the infrastructure behind them hasn't been built yet. You'll be in on the ground floor. - Small team, massive surface area — engineers own real systems end to end, not slices. - Real scale, real stakes — OpenArt serves millions of creators, and enterprise deals will close (or not) on what you ship. - Founder-led engineering culture — both founders are technical and deeply involved in product and architecture. - AI-native product — you'll help decide how cutting-edge models get packaged, governed, and sold to teams and enterprises. - High ownership, low process — we value judgment, clarity, and speed over bureaucracy. 🎯 About the Role We're hiring engineers to build the product and infrastructure that lets OpenArt serve teams and enterprises, not just individual creators. That spans the full surface: workspaces and team management, roles and permissions, usage-based billing and procurement-friendly invoicing, audit logs, and the security posture — SSO, data controls, compliance groundwork — that larger customers expect before they'll sign. This is a full-stack role on a brand-new team. You'll move between customer-facing product (admin consoles, billing UI, workspace settings) and the backend underneath it (access control, usage metering, payment integrations). You'll work closely with the founders and the enterprise team to figure out what "enterprise-ready" means for an AI-native creative platform — and then build it. 🛠 What You'll Do - Build core enterprise primitives: organizations/workspaces, roles and permissions (RBAC), SSO/SAML, and audit logging. - Implement usage-based billing, invoicing, and payment flows that support both self-serve and enterprise procurement (e.g. Stripe). - Contribute to platform security and reliability work — access control, data isolation, and groundwork for compliance certifications (e.g. SOC 2). - Build and maintain backend services and APIs that support multi-tenant, team-based usage patterns. - Build clean, polished frontend experiences (React/Next.js) for admin, billing, and workspace management. - Work with founders, sales, and customers to turn real requirements into shipped features. - Take on increasing ownership as the enterprise platform and team grow. ⚙ What We're Looking For Core Requirements - 2+ years of full-stack engineering experience shipping production software. - Solid fundamentals in system design and data modeling — you can reason about APIs, permission models, and how data should be structured and isolated. - Comfortable across the stack: React/Next.js on the front end, Node.js/TypeScript or Python on the back end, and a relational database in between. - A strong AI-assisted coding practice — you use tools like Claude Code, Codex, or Cursor as a core part of how you build, and have real opinions about what makes them work well. - Product sense — you care about what makes an admin console feel trustworthy and a workspace feel effortless, not just whether it works. - Clear communication — you can explain what you built, why, and what the trade-offs were to teammates who aren't engineers. Nice to Have - Exposure to payments or billing systems (e.g. Stripe): subscriptions, usage-based billing, invoicing. - Exposure to auth, security, or compliance work: SSO/SAML, RBAC, audit logging, SOC 2 / GDPR. - Experience with cloud infrastructure (GCP/AWS), observability, or reliability work. - Startup experience, or having built something 0 to 1 (side projects count). 💰 Compensation - $300k+ total compensation including base salary, bonus, equity. - Equity — meaningful ownership in what you build. - High autonomy, high growth environment. 🌍 Work Setup - Bay Area preferred (hybrid available). - Visa sponsorship available. 🎯 What Success Looks Like in 3–6 Months - You've shipped meaningful pieces of workspaces, permissions, or billing into production, and paying teams are using them. - You own at least one enterprise surface end to end — e.g. the admin console, audit logs, or invoicing — and are the go-to person for it. - You've sat in a customer or sales conversation and turned what you heard into a shipped feature. - You're proposing improvements and catching problems early, not just executing on specs. - You've grown into more scope than the role started with. If you want to help build the platform that turns a consumer AI product into an enterprise business — and grow fast while doing it — we'd love to talk.

Requirements

Must-haves

Build core enterprise primitives: organizations/workspaces, roles and permissions (RBAC), SSO/SAML, and audit logging.
Implement usage-based billing, invoicing, and payment flows that support both self-serve and enterprise procurement (e.g. Stripe).
Contribute to platform security and reliability work — access control, data isolation, and groundwork for compliance certifications (e.g. SOC 2).
Build and maintain backend services and APIs that support multi-tenant, team-based usage patterns.
Build clean, polished frontend experiences (React/Next.js) for admin, billing, and workspace management.
Work with founders, sales, and customers to turn real requirements into shipped features.
Take on increasing ownership as the enterprise platform and team grow.
2+ years of full-stack engineering experience shipping production software.
Solid fundamentals in system design and data modeling — you can reason about APIs, permission models, and how data should be structured and isolated.
Comfortable across the stack: React/Next.js on the front end, Node.js/TypeScript or Python on the back end, and a relational database in between.
A strong AI-assisted coding practice — you use tools like Claude Code, Codex, or Cursor as a core part of how you build, and have real opinions about what makes them work well.
Product sense — you care about what makes an admin console feel trustworthy and a workspace feel effortless, not just whether it works.
Clear communication — you can explain what you built, why, and what the trade-offs were to teammates who aren't engineers.

Nice-to-haves

Exposure to payments or billing systems (e.g. Stripe): subscriptions, usage-based billing, invoicing.
Exposure to auth, security, or compliance work: SSO/SAML, RBAC, audit logging, SOC 2 / GDPR.
Experience with cloud infrastructure (GCP/AWS), observability, or reliability work.
Startup experience, or having built something 0 to 1 (side projects count).

Application prep

Use the role’s language and application details while tailoring your materials.

Keywords to mirror

aireactnext.jsnode.jstypescriptpythongcpawsgo

Platform: ashby
Effort: quick