What we’re building

We’re empowering small teams with technology that makes it easier to market and grow businesses. Our current focus is to help consumer brands shift from “workflow automation” to “agent management” within their marketing operations. Shadow is the AI coordination layer — providing shared AI memory, centralized agent control, and model orchestration for marketing teams.

Why join Shadow?

• Product Ownership You’ll ship production code daily and help steer key product and technical decisions.
• Shape the Engineering Culture You’ll influence how we work—tools, processes, standards, and hiring.
• Work with Challenger Consumer Brands Talk directly to customers (CEOs, CMOs, VP’s) of fast-growing consumer brands—some doing $80M–$500M in revenue.

The agency behind the product

Shadow is built alongside Darkroom — a performance marketing agency that’s been operating for 10 years, employs 100+ people, runs 100+ clients at a time, and has worked with over 1,000 consumer brands. The agency is both our proving ground and our first user, which means the data you build with is real marketing data at real volume from day one — not a synthetic demo.

This is a fully remote role supporting a team in the EST time zone (9 AM–5 PM EST).

The role

You’ll own features end-to-end at Shadow, from the first conversation with a user to the polished screen in production. You’ll design in Figma and in code, and ship it yourself.
You’ll work forward-deployed. You’ll sit with the subject-matter experts who use Shadow every day, like media buyers, strategists and creatives, to learn how they actually work and where they get stuck. Then you’ll turn what you learn into features that fix it.
You’ll also keep Shadow feeling like one product. As new features land, you’ll make sure every screen, from dashboards to agent conversations, follows the same system and meets the same bar.

Core Tech & Tools

• Languages & Frameworks: Python, Node.js, React (TypeScript)
• Datastore: PostgreSQL
• Cloud & Infra: Google Cloud Platform, Airflow, Terraform, Docker, Kubernetes
• ML/AI: LLMs, RAG, prompt engineering

What you’ll do

• Own features end-to-end: find the problem, shape the solution, then design, build and ship it.
• Embed with subject-matter experts to learn their workflows and challenges firsthand.
• Turn what you learn into product: agent conversations, performance and creative dashboards, the marketing calendar, and whatever comes next.
• Own UI/UX consistency across the whole app. Keep the design system current in Figma and React, and hold every new screen to it.
• Sweat the details, including type, spacing, motion, loading and empty states.
• Prototype fast, in code, in Figma or with AI tools, and put ideas in front of experts within days.
• Invent interaction patterns for agentic work. That means streaming answers, showing the agent’s reasoning, approving changes before they touch a live ad account, and admitting when data is missing.
• Turn dense, multi-channel data into screens a marketer can read in seconds.
• Bring the new Shadow brand into the product, working with our brand partners.

Must haves

• Shipped product UI you’re proud of, plus a portfolio or live work that shows both the design and the code.
• Strong React, TypeScript and CSS (Tailwind a plus). You can own a frontend codebase, not just individual components.
• Real visual and interaction design skill: typography, layout, color, motion and micro-interactions.
• Curiosity about how other people work. You can spend a day with a media buyer and come back with the real problem, not just a feature request.
• A systems mindset. You notice when two screens solve the same problem differently, and you fix it.
• Equal comfort in Figma and in your editor, and the judgment to know when to skip Figma.
• Taste for data-dense interfaces. Your dashboards, tables and charts stay calm under a lot of information.
• Daily use of AI tools like Cursor or Claude Code, with opinions on how AI products should feel.
• Comfort with ambiguity. You’d rather ship and learn than polish in private.
• Clear writing. You can explain the why behind a design to engineers, experts and non-designers.
• Most people who fit this have 5+ years across design and some experience with frontend engineering.

Nice to haves

• Forward-deployed, solutions or customer-facing work, or research with expert users.
• You’ve built a design system that ot…