Taste is building the AI for creative work.

Today’s AI is great at logic and code, but when it comes to anything visual, brand, or aesthetic, it produces slop. Generic fonts, cluttered layouts, off-brand colors, soulless compositions. The models don’t understand taste.

We’re changing that. We’re building the creativity layer for AI: the models, evaluators, and data pipelines that teach AI what “great” actually looks like, so that every company building with AI can ship work that feels crafted, on-brand, and beautiful.

We recently closed a $16M seed round co-led by Amplify and CRV. We’re working with customers like Anthropic, Flint, and leading AI labs, powering the design intelligence behind their products. The team today is small, senior, and hungry. We care deeply about quality, move fast, and love the problem.

If you think AI-generated work feels soulless right now, and you want to be part of the team fixing that, we’d love to meet you.

What you'd own

You're building and running community as an operating system.

The talent funnel from application to active project. ~1,500 experts in flight at any time. You own the systems, metrics, and process improvements that get more of them activated and keep them active.

This is supply chain operations for a curated expert network. Not community management. Not recruiting. The expert community is the company's compounding asset, and your job is to make that true in practice. The supply graph is your product. The activation workflow is your product. Onboarding, calibration, and bridging between projects are your product.

This is an execute and build role. Most of the infrastructure doesn't exist yet. You'll join work already underway and build the structure as you run it.

Day to day

• You own the weekly funnel dashboard. Five numbers, every Monday: apps → portfolio yes → tested → passed → contracted → staffed. You publish, the team reacts.

• You collapse the nine-plus-step onboarding into fewer steps. You find the single-person bottlenecks and eliminate them.

• You make Airtable the source of truth for every stage. Retire the side spreadsheets and Notions where possible, or sync them in.

• You build and run the activation model. The bench is full of vetted experts who never made it to a project. Getting them activated is the job.

• You run reactivation campaigns. Send the sequences, track replies and bookings, route conversations to the right person, report what converted.

What you walk into

1,000+ vetted experts across design styles and specialties. A working but partial supply graph. A pod lead model in development. An ops team that has built real infrastructure and is building more. A clear thesis: community is a compounding asset, quality is institutionalized, and retention is structural rather than transactional.

You're not starting from zero. You're not inheriting something finished either. You're joining mid-build.

What we screen for

Running vs doing.

When you say you "owned" a funnel: what were you allowed to decide without asking permission? What did you change, and what moved because of it? You know what cohort analysis means and you've actually built one. We are hiring people who have built systems other people use, not people who have executed inside systems someone else built. The story we want is the funnel you rebuilt that kept converting after you stopped touching it.

Where your ego sits.

Ego in “my function” produces silos. Ego in “the mission” produces interfaces, documented handoffs, and data the next person can trust. We are hiring for the second.

Comfort in ambiguity.

The workflows you execute this month are being designed this month. If you need the playbook finished before you can move, this is not the seat.

The taste question.

We'll ask whether you have taste in something. Not whether your taste matches ours. Whether you have the muscle at all. Because the people you're emailing, scheduling, and tracking are people who have it, and they can tell when the person on the other end doesn't care.

Where you might be coming from

We are intentionally open. A handful of profiles match the shape of this work, none of which are obvious by title.

• Product growth or lifecycle leads at marketplaces or networks where supply was the product

• Revops or growth ops people who owned a funnel end to end and built the reporting themselves

• Marketplace supply ops where activation mattered more than acquisition

• Growth generalists at fast companies who built the workflow everyone ended up using

• Operators at Scale, Mercor, or Surge who pushed quality against the volume model and want to build a network that compounds rather than churns

• Early-stage founders whose company didn't work out, especially marketplace, network, or community-driven

What disqualifies

• You think of community management as content programming: events, newsletters, swag

• You can't distinguish between “building a community” and “building a guild”

• Your background is volume recruiting: fill rate over fit

• You need someone to chase you for the Monday numbers

• You produce polished work but slowly. Polished alone is not the bar.

What you get

End-to-end ownership of the supply funnel. A vendor budget to buy tools instead of building them where it makes sense. A network of working designers who will know you by name. If the seat grows, you grow with it.

How the loop runs

Screen, then founding team member to screen for operating tempo and systems thinking, then a culture and commitment conversation. References at the end.