Текст заказа
About the role
We are not hiring a traditional marketer, and we are not hiring a traditional software engineer.
We are hiring an Architectural Operator: someone who designs systems that produce software (and the motion around it), not someone who writes one-off campaigns or one-off code.
With AI, generation is no longer the constraint. The bottleneck is making what gets produced correct, reproducible, and architecturally sound.
Your job is to define systems that rapidly generate high-quality software whose outcome is marketing: community, distribution, events, and repeatable go-to-market motion.
You will build and evolve agent-driven systems that build and evolve agent-driven systems that execute real marketing functions.
This seat is scoped to marketing operations. The agents you ship must produce marketing outcomes we can run: meetup and community operations, content and distribution systems, candidate and community funnels, event coverage, and the operating system for building our own meetup circuit in-market. If it doesn't create or run a marketing system, it doesn't count.
This month the company is on the ground in San Francisco (meetups, coverage, hackathons). This role exists so that motion becomes a system, not a heroic calendar.
What you'll do on the team
\- Design reusable systems for marketing work, so campaigns, events, and community operations like meetups and calendars don't get rebuilt from scratch each time.
\- Build data-first systems that track people, events, content, and where each lead stands. Use graphs and events where they help, and make it easy to see what actually changed.
\- Build and improve agents that run marketing work, like finding and covering meetups, turning conversations into follow-ups, creating content to share, and running a community calendar.
\- Replace manual go-to-market work in Slack messages and spreadsheets with systems.
\- Work fast in the San Francisco office, with AI as your default tool.
Marketing outcomes we care about: a system that can stand up and run community and meetup operations, keep coverage across events without one person doing hero ops, and turn "we showed up" into a repeatable machine.
Who fits
You think in systems. You would rather manufacture a community/GTM machine than "do marketing." You use AI as a core tool. You care about structure. You want fewer heroics, not more campaigns to babysit.
Technical environment
\- AWS Lambda, Step Functions, EventBridge, SQS, SNS, and DynamoDB
\- Serverless-first, event-driven systems built on AWS
\- Graph databases like Neo4j, plus pipelines and observability
\- Marketing tools: email, calendar, social, CRM, and tasks
The first step
To qualify for an interview, you must build and submit an agent system. This is not theoretical.
After you apply on LinkedIn, we will send a set of use cases. You pick one.
Example use case (illustrative):
\- Monitor Gmail and identify work-related emails
\- Convert emails into structured tasks
\- Use Asana as the system of record
\- Suggest or generate responses
\- Maintain state across systems and workflows
For this role, pick a use case that produces a marketing outcome. For example, ingest inbound interest, turn it into a campaign or event workflow, keep state across CRM/calendar/content tools, and generate the next action (invite, follow-up, recap, distribution).
What we evaluate (all four at once)
1\. Speed: Build with AI tools like Cursor and record it on video. We measure calendar days and the time you actually spend building with agents.
2\. Architecture first: Consistent patterns, event-driven flows, and defined data movement. Include a short architecture overview, diagram or written, as the agent's skill.
3\. Runnable and deployed: Clean, runnable, and deployed. We run the whole system end to end ourselves, with no babysitting from you.
4\. Reproducibility: On video, change something real, like a list, channel, or account, and regenerate. We will also try to break or adapt it ourselves.
Evaluation and outcome
Same bar as every Operational Architect seat: architecture, speed, reproducibility, and practical usefulness. We score it as a marketing system, not a brochure.
If selected: interview. If exceptional and usable: offer + signing bonus for the submitted system.
Principles
\- Code is disposable. Architecture is permanent.
\- Reproducibility > reusability
\- Speed without structure creates failure
\- If it can be done twice, systematize it
\- The best system is one you never need to fix
Compensation
Candidates may be remote or in person in the San Francisco Bay Area.
\- In person: up to $250k
\- Remote: up to $150k
Starting salary is decided based on your skill at the beginning of hiring, and it can go up based on performance within the cap.
Project participation
For each project, Prism puts 20% of collected project revenue into a project participation pool. The pool is paid on cash collected, not on signed contract value.
\- 3%: Attributed to Sales Lead
\- 3%: Attributed to Account lead
\- 14%: Attribution split across Architect team
If three strong operators using agents can deliver a project, the 14% Operational Architect pool is split among three people. If the same project takes ten operators, the same 14% is split among ten.
Why this role exists
We are building software manufacturing for the whole company, including distribution. Marketing should be performed by agents, generated by agents. Architecture is the asset. If you can build systems that build marketing systems, apply on LinkedIn.