Product Software Engineer

Required Qualifications

• Devtool DX, end to end. You think about developer experience holistically, not just the frontend. That means the web IDE (script, flow, app, raw app, pipeline editors), but also the CLI (wmill), the VS Code extension, the local dev workflow, the sync between local files and the Windmill server, the API surface (what's exposed, how it's shaped, how it composes), the SDKs. You have strong opinions on what makes a developer tool good across all of these surfaces (Linear, Raycast, Cursor, Figma, Replit, Vercel, Supabase, your own tools, take your pick) and the patience to get the details right. TypeScript is a must. Svelte a plus. Comfort reading Rust to understand and shape what the backend exposes is a plus too.
• AI product engineering. You've built and shipped real LLM-based systems, not just demos. You understand agent loops, tool use, skills, evals, streaming, retrieval. You have taste for what makes these experiences good versus terrible. You also think about the AI experience across the full Windmill surface: developers don't just live in the web IDE, they sync to local files, work in VS Code, run things from the CLI. The agent has to be useful wherever they are, with a consistent mental model across surfaces. Bonus if you've also owned the UI around them, because at Windmill the model and the interface are the same product.
• Workflow & data infrastructure depth. You've built or deeply used the systems in our space: data pipeline builders (Airflow, Dagster, Prefect), workflow engines (Temporal, n8n, Inngest), execution runtimes and schedulers, observability and monitoring stacks. You have strong opinions on what makes these tools fast, operable, and a joy to debug. You want to build the best version of one of them inside Windmill, whether that's the pipeline editor, the runtime, the worker layer, the monitoring UI, or something we haven't shipped yet.
• Full-stack / systems range. You can read and contribute to a Rust backend, and you care about latency, correctness, and how the frontend and backend fit together. You see infrastructure as part of the product.