We run a high-end product design and development studio working with ambitious founders and fast-moving startups. We’re entering a new phase. Clients no longer want static design files. They want: • working prototypes • AI-assisted product builds • faster iteration cycles • fewer handoffs between design and engineering At the same time, internally, we’re building toward something much bigger: a self-operating, AI-augmented studio that can design, build, and launch products at extreme speed. We’re looking for someone exceptional to help us build that system. ⸻ What this role actually is This is not a typical “AI engineer” role. This is not a prompt engineer. This is not a pure frontend dev role. You are: an AI-native builder who can turn chaos into systems. You’ll work directly with the founder to: • design and implement internal AI workflows • connect tools into real, usable systems • build infrastructure that compounds over time • ship fast, iterate faster, and continuously improve Think: Design × Engineering × AI × Operations ⸻ What you’ll be responsible for 1. Design → Code Systems (Core Priority) Build our proprietary workflow to go from: Figma → AI → React (or similar) → working local prototypes This includes: • integrating Figma MCP with tools like Claude Code, Codex, Cursor, etc. • defining prompting systems and reusable patterns • building starter repos and component foundations • improving output quality and reliability over time • enabling designers to generate high-quality prototypes without becoming engineers ⸻ 2. Internal AI Infrastructure Help us build the internal “operating system” for the company. Examples: • AI-powered workflows for product, design, and engineering • internal tools that reduce manual work across the team • building an AI Chief of Staff layer for operations and decision-making • connecting tools like Perplexity, Claude, OpenAI, etc. into real workflows • experimenting with orchestration frameworks (open source or custom) ⸻ 3. Rapid Prototyping + Product Builds You’ll help us go from: idea → prototype → functional product This may include: • building internal tools • building client-facing prototypes • shipping MVPs quickly using AI-assisted development • working inside environments like Replit, local repos, or hybrid setups ⸻ 4. Experimentation with Emerging Tools We move fast and test aggressively. You’ll explore and implement tools like: • Claude Code / Codex / Cursor • Figma MCP + design system integrations • Perplexity workflows • open-source orchestration frameworks (e.g. Paperclip or similar) • NVIDIA NeMo / emerging AI infra where relevant • anything else that meaningfully increases speed or capability ⸻ 5. Turning Experiments into Systems Anyone can test tools. You will: • turn experiments into repeatable workflows • document processes • identify what works and what doesn’t • create leverage for the entire team ⸻ Who you are You are a builder first. You likely: • have strong frontend or full-stack experience (React preferred) • are deeply comfortable using AI tools to build real things • have experimented with agent-based workflows • are not intimidated by ambiguity or new tools • can debug when things break (and they will) • care about speed, but also about quality You might describe yourself as: • “AI-native engineer” • “product-minded builder” • “systems thinker” • “technical operator” ⸻ Must-have traits • Extremely resourceful • Moves fast without waiting for perfect specs • Comfortable figuring things out from scratch • Can connect multiple tools into a working system • Strong problem-solving ability when things break • Clear communicator (you can explain what you built and why) ⸻ Nice-to-have experience • Design systems / Figma → code workflows • Tailwind / component libraries (e.g. shadcn) • MCP or tool-connected AI workflows • Replit / cloud dev environments • building internal tools or automations • experience working with startups or fast-moving teams ⸻ What success looks like (first 60 days) • We have a working Figma → AI → prototype workflow • Designers can generate and test components/pages locally • We have at least 1–2 internal tools saving real time • Clear direction on which tools and workflows we’re standardizing on • You’ve shipped multiple experiments (not just talked about them) ⸻ Why this is exciting • You’ll help define how a modern product studio operates • You’ll work directly with the founder on high-impact systems • You’ll build things that are actually used immediately • You’ll be at the intersection of design, engineering, and AI • This is not maintenance work — this is 0 → 1 system building ⸻ Engagement • Starting as a high-impact contract (Upwork) • Potential for long-term / full-time if there’s strong alignment • Flexible, async-friendly, but high ownership expected ⸻ 🔴 How to apply Send: 1. Examples of things you’ve built using AI tools (real outputs, not just ideas) 2. A short explanation of how you would approach: “Figma → AI → working React prototype” 3. Tools you’ve been using recently (Claude, Codex, Cursor, etc.) 4. Anything you’ve built that connects multiple systems together ⸻ If you’re the type of person who sees where things are going and wants to build the system before everyone else catches up, we should talk. looking forward to seeing what you’ve built