Senior Product Engineer (NextJS/TypeScript) - barcelona
hace 9 horas
Barcelona
Senior Product Engineer (AI native) You'll ship features used by developer marketing teams at companies inc Vercel, Supabase, n8n. We're looking for a senior product engineer, AI-native, with startup experience, who wants to own features end-to-end and help us shape what Plug.Dev looks like for the next five years. Salary: Competitive salary + performance bonus (company + individual) Remote: 100% (Spain/Europe preferred) 🛸 Bootstrapped & profitable · 🤖 AI-first · ⚡ Async-first · 🛠️ End-to-end ownership · 🎯 Real impact We're Plug.dev, the creator partnership platform for devtools. We help companies like Vercel, Supabase, n8n and more run programs with the YouTubers, educators, and dev influencers their developers actually watch. We're nearly three years old, bootstrapped, profitable, and growing. If you want to own features end-to-end, ship to real customers next week, and build internal AI tooling that makes the team faster, keep reading. What you'll do Where we are. We're rebuilding the platform from scratch on a modern stack. You'll be working on new code, not maintaining legacy. You'll be writing the code that defines what the next 5 years of Plug looks like. The technical challenge. Two things at once: • Build the new platform. Design and ship the new Plug.dev application with scalability, performance, and maintainability built in from the start. This is the product our customers and creators rely on every day., • Build Plug AI-native internally. You'll build internal tools that help the team move faster, using AI workflows, agents, MCPs, and skills, without losing the quality our customers expect. You'll move between both depending on the week. Your responsibilities • Own features end-to-end. From shaping the requirement with the team to writing the code, deploying it, monitoring it, and iterating on what customers actually do with it. No handoffs., • Build the new platform. Next.js, TypeScript, Postgres, Prisma. You'll write code that defines the foundation., • Build internal AI tooling. Workflows, agents, MCPs, skills, CLIs, RAG, whatever shape makes the team faster without sacrificing quality., • Make architectural calls. When to extract a service, when to keep it a workflow, when shadcn is enough vs. when it isn't. We trust you to balance speed, scale, and simplicity., • Keep the lights on. We're a small team with no dedicated DevOps. Everyone owns infra, monitoring, and incident response at the level a senior dev needs to. You don't need to be an SRE, but you can't be helpless when something breaks., • Talk to customers. You'll join calls, watch sessions, read support threads. Product instincts come from contact, not from specs. In your first month You'll get a working setup on day one, pair with Pablo or Jaume on the new codebase, and ship something small to production in week one. We believe onboarding happens through real PRs, not documentation marathons. By the end of week four you'll have owned at least one user-facing feature and built one piece of internal tooling that makes someone's week measurably better. How you'll do it The stack: • Frontend: TypeScript, Next.js, React, Zustand, shadcn/ui, Tailwind, • Backend: TypeScript, Next.js, PostgreSQL, Prisma, n8n, • AI: OpenRouter, Claude, Gemini., • Integrations: Clerk (auth), Stripe (payments), Resend (email), Dub (links and attribution), Trigger.dev (orchestration), Browserbase (browser agents), Reddit Ads, Slack and more., • Infra & ops: GitHub, Railway, PostHog, Sentry, • Tooling we lean on: Linear, Slack, Google Workspace, Loom, Figma We use a lot of tools. You don't need to know all of them on day one. You'll pick up what you don't know as you go, that's how the rest of us got here. AI-native is not a buzzword here. We expect you to use Claude Code, Cursor, or whatever assistant works for you as a default part of how you write code and become a better engineer, but more than that: we want someone who has gone deeper than the defaults. Built their own AI-assisted dev workflow. Wrote their own skills, MCPs, or CLI helpers. Has opinions on context engineering, prompt structure, and orchestration. The interesting problems aren't the syntax, they're how you build the system around the model. When and where you'll work 100% remote, Spain/Europe preferred. We're a distributed team across different countries with the same async rhythm. We meet in person 1 to 2 times a year for offsites. They're useful, fun, and historically end with wine. Beyond that, you organize your own time. The product engineering team is small and senior. You'll work directly with: • Pablo Martín Junquera, Tech Lead. Runs engineering and product. He'll be your closest collaborator on architecture, scope, and shipping. https://www.linkedin.com/in/pablo-martin-junquera/, • Jaume Gelabert, Senior Engineer. Currently building the bulk of the Plug application and internal tooling. Your day-to-day pair. https://www.linkedin.com/in/jaumegelabert/, • Neill Gernon, Founder. Sets product direction, talks to customers daily, and wrote the why of the company if you want a deeper read. https://www.linkedin.com/in/neillgernon/, https://plug.dev/blog/ourwhy We're an 8-person team total. Strong shared GIF taste. The wine-at-offsites tradition is real. What we're looking for We're hiring against three pillars. 1. Startup DNA You've built things in small teams before. You've shipped MVPs and POCs and watched some of them die. You're comfortable with ambiguity, you take ownership end-to-end, and you don't wait for someone to write you a ticket. 5+ years building software, ideally most of it in startups or high-ownership roles. 1. Product sense You think about why before how. You're proactive about product: you push back on features that don't make sense, propose ideas before being asked, and you ask whether a feature should exist before you ask how to build it. You care about UX and polish, but you also know when shipping the ugly version teaches us more. We're not asking you to be a PM, we're asking you not to need one over your shoulder for every decision. 1. AI engineering You've shipped real things with LLMs in production. Not just a demo, not just a chatbot. Agents, RAG pipelines, MCPs, skills, CLIs, workflows, integrations: you've built or shipped at least a few of these. You understand context engineering, prompt design, evaluation, and the difference between an AI feature that works in the demo and one that works at scale. Stack expectations Strong: TypeScript, Next.js, React, PostgreSQL, Prisma, Claude Code, AI/agent SDKs, Tailwind, working with third-party APIs (Stripe and Clerk-style integrations). Comfortable: Infra and DevOps at the level a small-team senior needs. Deploying, monitoring, debugging production, managing the basics of Railway or equivalent. We don't need an SRE, we need someone who isn't helpless when Sentry lights up. Nice to have: shadcn/ui, n8n, Trigger.dev experience. OSS or side projects we can look at. Languages English, fluent. Async-first means our written communication is in English all day. What we offer • Competitive salary plus performance bonus tied to both company and individual performance. We hit our numbers, we share the upside, and we have so far., • Autonomo long-term contract, • 100% remote with Europe-friendly hours, • Vacation, common-sense approval, • 1 to 2 in-person offsites per year in Europe, • Real ownership. You'll shape what the new platform looks like, not implement someone else's plan., • Profitable, bootstrapped, growing. No investor pressure. Selection process We keep it simple, fast, and focused on real work. • Apply. Send your CV or portfolio plus one product, side project, or OSS repo you've shipped. We read these., • Intro call (30 min) with Neill (Founder). About you, your work, and what you've built., • Tech call (60 min) with one of our engineers. Real conversation about your stack experience and how you've solved hard problems., • Follow-up (if needed). Short Loom walkthrough or a second call for deeper context., • Offer. If we're aligned, we'll share a written proposal with the specifics: start date, contract details, compensation breakdown, ... Total: usually 2 to 3 weeks.