Product Engineer (Remote)

Product Engineer ================

Location: Remote, Europe Preferred: Portugal

About the Role ---------------

At Maker, we build an AI-powered page builder for ecommerce teams who want to be on the forefront of technology. We package complex AI into tools that feel simple - so our customers can build high-converting pages without needing to understand the technology behind them.

Were looking for a product engineer. Not a frontend engineer. Not a backend engineer. Someone who owns features end-to-end from understanding the user problem to architecting the solution to shipping it and watching how people use it.

Youll work across the stack. Our codebase spans TypeScript and ReScript, React, and HTMX on the frontend, Node.js and serverless infrastructure (Vercel, AWS, Fastly, Cloudflare). You dont need to know all of it; you need to be the kind of engineer who picks things up fast and isnt boxed in by a specialization.

AI tools are part of how we work every day. Youll write less code and review more. Your judgment about what ships and what isnt good enough is what matters most.

What Working Here Looks Like -----------------------------

Youll own features from idea to production. No one hands you a spec and walks away. Youll shape product decisions not just implement them. We expect you to have opinions about what we should build and why.

Youll build interfaces that ecommerce store owners can understand without a tutorial. Youll make architectural calls that balance speed with long-term quality. Youll use AI to move fast but youll know when to slow down and think for yourself.

You might be a good fit if you:

• Have deep experience building production software and can point to products you shaped not just code you wrote
• Have built and scaled at least one product from zero to real usage 10x-100x growth
• Have strong React and Node.js experience with solid API design instincts
• Have worked at an early-stage product-focused startup and thrived in the ambiguity
• Think about the user before you think about the architecture
• Communicate clearly in English - in code, in docs, in conversation

Its an added plus if you:

• Were a founder, co-founder, or early employee first 10-20 hires at a startup
• Have worked on products in our space (page builders, design tools, visual editors, AI, creative tools, AI coding tools)
• Have built side projects or open source work youre proud of
• Have experience with HTMX, Alpine.js, or ReScript
• Can show us how you use AI tools pragmatically - when to lean on them and when not to

How We Hire -------------

Our process reflects how we actually work. No LeetCode. No whiteboard algorithms.

1. Intro conversation - We talk about your background, what drives you, and what youve built. We want to see how you think about product and technology together.
2. Real-world project - We give you an open-ended problem inspired by something were actually thinking about at Maker. Use any tools you want - AI agents, copilots, whatever makes you fast. We care about what you deliver, how you scope it, and whether you can explain your decisions.
3. Team session - A working conversation with the team. Were evaluating fit in both directions.

If this sounds like the kind of work you want to do, wed love to hear from you - even if you dont check every box. The best people weve hired surprised us.