Product Builder, Founder's Office Swym

Remote-first · Full-time · Bengaluru-based team. Sits within the Founder's Office, working closely with the Product Team across every function.

Every day, millions of shoppers save products they want but are not ready to buy. Most brands never know it happened. Swym fixes that.

We capture what shoppers want at the earliest and most specific point in their journey, and we make that signal usable across every channel a brand has, until the purchase completes. 48,000 brands use Swym today. The infrastructure works. The data moat is real and widening. What this role exists to do is make the product sharper, faster, and more compellingly valuable, by staying close to merchants, close to the market, and close to the decisions that shape what gets built next.

We are a lean team that runs on AI and GitHub. No wiki. If it matters, it is in the repo or it does not exist.

When a merchant ticket arrives, AI drafts the first response. When a brief needs writing, AI writes the first version. When we need competitive context, AI pulls it. When we write code, AI writes the first version. Humans drive strategy, apply judgment, and own the outcome. That is the model across every function.

We build on GitHub. We work across a range of LLMs. We are actively building toward a model where agents handle tasks that at most companies consume entire teams. We are already partway there, and this hire is expected to push that further.

In your first 90 days: Assessment and intent.

Arrive, look at the AI tooling environment honestly, identify what is sanctioned, what is missing, and what is creating drag. Produce a recommendation, not a report. In parallel, build your own working AI stack for your role: ticket handling, merchant prep, internal synthesis. Be operating at full personal fluency within whatever constraints exist by the end of this period.

The milestone is simple: do you have a clear point of view on what needs to change, and are you already acting on it. From day one you are inside the AI model, using the same tools and workflows as the rest of the team. You will leave this period able to make Swym's value immediately obvious to any merchant or partner you speak with.

At six months: Early organisational reach.

The bar here shifts from personal fluency to visible impact beyond yourself. Two things mark this milestone.

First, at least one AI workflow you built is being used by someone else on the team. Not because you were asked to build it. Because you identified a drag point, built something to address it, and it got adopted.

Second, you have contributed meaningfully to at least one product decision grounded in merchant or data insight you gathered yourself. Not owning direction yet. Demonstrating the instinct that will own it.

Own the relationship loops with merchants and partners. The goal is not opens or responses. It is merchants getting more value from Swym because of how you showed up.

If your AI fluency is still contained within your own output at six months, something is wrong with either the hire or the environment.

At twelve months: Structural change.

At twelve months, the things that were emerging at six months should now be structural.

Features shipped from idea to market. Connective tissue established across product, growth, and CX, the person who drives decisions rather than waits for them. AI workflows the team depends on that did not exist before you joined. A point of view on where Swym goes next that people listen to.

The question at twelve months is not what you built. It is what is different about Swym because you were here. Would Swym's AI posture look the same if you had not joined. If yes, the hire underdelivered.

Not shipped some features. Build something that compounds.

On success metrics.

You get handed real problems, not tasks. The expectation is that you figure out why it matters, what good looks like, and how to get there. The team is with you. The thinking is yours. Your output will be reviewed by the Head of Product, which means you have real support and real accountability from the start, not unsupervised autonomy.

Specific success metrics are set with your manager in the first 30 days. The categories are merchant activation, workflow adoption, and product outcome attribution. Numbers are not pulled from the air. They are set consultatively, grounded in where Swym is when you join and what you are working on.

One honest note on the milestones. The six and twelve-month milestones are only reachable if Swym's environment supports them: sanctioned tools, accessible data, documentation in queryable shape, role autonomy. We are committing to building that environment as much as we are expecting you to perform within it. The twelve-month milestone is partly a commitment from Swym, not just an expectation of the candidate.

You are the kind of person who identifies what matters and moves on it before being asked. You have shipped something real from zero. Not contributed to. Not managed. Shipped.

You think like a product person and build like an engineer. In practice, not in theory. You prototype. You do not write the doc and hand it off.

Ambiguity does not slow you down. The problems here do not arrive with clear definitions. Part of your job is figuring out what the right question is before you answer it.

You operate across product, strategy, compliance, and commercial without being defensive of a narrow lane. The role demands it. The team expects it.

You are already using AI to multiply your output. Not experimenting with it. Using it as a default. This is assessed during the process, not assumed on your word.

Three to six years of experience. A generalist who has gone deep on product. Pure engineering profiles are not the fit. Neither are pure PMs who have never built.

Most product roles will not let you operate this way for years. The scope will be too narrow, the AI too peripheral, the decisions too far from where you sit.

Here, you are in it from day one. Real intent data. Real merchant activation at scale. A team that means what it says about building differently.

The scope is wide. The trust is high. The learning curve is steep in the best possible way.

If your idea of a good year is: I shaped something that mattered, I got dramatically better at building with AI, and I can point to the revenue that moved because of decisions I was part of, you will be happy here.

We are strong where it counts: capturing shopper intent with precision, anonymously and without requiring login. Deep integration across the merchant marketing and sales stack. Privacy-compliant capture even in the most restricted environments.

We are openly working on the harder problems: making our value immediately obvious to merchants without making them hunt for it. Building experiences that become operationally indispensable. Going deeper on verticalized solutions for specific merchant categories. And on the AI tooling side too: our workflows are good and getting better, but we are not yet at the ceiling of what we know is possible. This hire is part of how we get there.

If those open problems sound like the interesting part rather than a warning, that is a good sign.

How we work, what we value, and what we expect from each other: http://getswym.com/careers

Compensation: Competitive cash and meaningful equity. Stock options for everyone on the team. We will talk specifics early.

Please apply directly through this LinkedIn job post. Be sure to attach your CV and include a link to something you have built.

If you are shortlisted, here is what happens next. We will reach out within a week. You will receive a 90-minute build assignment: a real dataset, an open brief, no predetermined answer. Use whatever AI tools you normally use. We evaluate thinking and judgment, not just polish. Where you get to in 90 minutes, and what you chose to prioritise, is part of the signal.

Before you apply, have something real in mind that you have built. A product, a feature, a tool, a side project. We will ask about it.

What happens to what you send us: if you do not advance, your CV and any work you share will not be used beyond this process. We will not retain it beyond 90 days.

If the process sounds interesting, we should talk.