Skip to content

Joining · Three steps

How to join Product Circle.

How to join Product Circle in three steps: fill in a short form, a person reads it, and you're added to the group. Every question on the form, and how to answer it.

Last updated

To join Product Circle, you fill in a short application form: your details, your role and experience, one product decision you're proud of and what you want from the community. Product managers at any level are welcome to apply, from APM to CPO. What matters is how you think about products, not your title. A person on the team reads every application, and new members are added in small batches.

Apply to join Product Circle

By applying, you agree to how we handle your details as set out in our privacy notice. Questions? Email team@productcircle.club.

How to join Product Circle in three steps

1. Fill in the application

It's a short Google Form, and every question on it is required. Most of it is quick details; the one answer worth thinking about is a product decision you're proud of. Every question is listed below.

2. A person reads it

Every application is read personally by the team behind Product Circle, which is the team behind Mehman. No automated filter decides whether you get in. That's also why it isn't instant: someone has to actually read it, and new members are added in small batches to keep the room high-signal.

3. You're added to the group

If you're selected, the WhatsApp number you gave on the form is added to the member group, and you're introduced to the circle. From there, you have access to everything on the membership page.

What the application form asks

The form has ten questions. Eight are quick details, and two are where you tell us how you think.

Your details

QuestionWhat to put
Full nameYour name as you'd like members to see it
EmailAn address you check
WhatsApp numberWith country code. If you're selected, this is the number added to the group
Current role / titleAny level, APM to CPO
CompanyWhere you work now
Years in product0–2, 2–5, 5–10 or 10+
CityWhere you're based
LinkedIn profile URLYour full profile link

What's one product decision you're proud of, and why?

This is the main thing we read. Two or three lines is plenty. Pick one real decision you made or shaped, say what you chose, and say why it was right. It doesn't need to be a big launch: a feature you cut, a metric you changed, a trade-off you argued for all count.

What do you want from this community?

Tick whichever apply:

  • Live events
  • Workshops
  • Get-togethers and meetups
  • Knowledge sharing and discussions
  • Career and hiring
  • Finding collaborators and mentors
  • Other (write your own)

There's no right combination. It tells the team what you're hoping to get, so tick what's true rather than everything.

How to write a strong product decision answer

There's no checklist of titles or years of experience. Your role, company and years in product give the team context; the product decision answer shows how you think. This is practical advice, not a scoring rubric.

Pick one decision, not a career summary

"I've led growth across three products" is a summary. "I removed the sign-up wall from our app's first screen" is a decision. One specific choice gives a person something to read.

Say why, in plain words

The "why" is the part that shows your thinking. What did you know, what did you trade off, and what happened? A good structure: what you chose, what you gave up, and what changed as a result. Our guide on product prioritisation frameworks covers the trade-offs behind most of these calls.

Keep it to two or three lines

The form says two or three lines is plenty, and it means it. A short, specific answer reads better than a long one. If your decision needs a paragraph of setup, pick a simpler example.

Early in your career? Use what you've done

At 0–2 years, a small decision explained well is better than a big one you were near. A bug you chose to fix before a feature, a question you added to customer interviews, or a spec you rewrote after feedback all show product judgment. Our customer interviews guide and how to write a PRD are good places to find examples from your own work.

Weak and strong answers, side by side

These are illustrative examples, not real applications.

QuestionWeaker answerStronger answer
One product decision you're proud ofLed a big redesign that users lovedCut KYC from five screens to two by deferring PAN until first payout; drop-off at onboarding fell by a third
One product decision you're proud ofPrioritised the roadmap using dataKilled a feature our biggest client asked for, because it served one account and slowed setup for every other one
One product decision you're proud of (APM)Worked on many features as an APMPushed to fix a search bug before shipping filters; support tickets about "can't find it" halved in a month

The stronger answers aren't longer. They name one decision and say why it was right.

What happens after you apply

  1. Your application is read by a person. We don't publish a fixed turnaround, and new members are added in small batches.
  2. If you're selected, you're added to the member group on the WhatsApp number you gave on the form, and introduced to the circle.
  3. You get the details members get: schedules for the weekly AMA and product teardowns, the chai meetup, the jobs board and office hours.

Practical details that aren't published here, including any membership cost, are covered in the application process.

Your first two weeks as a member

Some suggestions to get value quickly:

  • Introduce yourself. A one-line tagline works well; the member intros page has tips and examples.
  • Read the other intros. Find three members whose work overlaps with yours and say hello.
  • Bring one question to the next AMA. Our guide on how to ask good questions in an AMA helps you frame it.
  • Join a teardown. Use the product beforehand and arrive with one note each under "Works", "Doesn't" and "Steal this".
  • Check the board. Even if you're not looking, you may know someone who is.

Frequently asked questions

What does the Product Circle application ask?

Your full name, email, WhatsApp number, current role or title, company, years in product, city and LinkedIn profile URL. Then two questions: what's one product decision you're proud of and why, and what you want from the community. Every question is required.

How long should my product decision answer be?

Two or three lines is plenty. It's the main thing the team reads, so one specific decision and the reason behind it does more than a long paragraph.

Who can apply to Product Circle?

Product managers at any level, from APM to CPO. What matters is how you think about products, not your title. If you're a founder doing the product job yourself, put that as your role and answer the product decision question the same way.

Why does the form ask for my WhatsApp number?

If you're selected, that's the number added to the member group. Include your country code.

Can I save the form and finish it later?

The form is a Google Form. If you sign in to Google, it saves your progress so you can come back to it.

What happens if I'm selected?

Your WhatsApp number is added to the member group and you're introduced to the circle. From there you have access to all six parts of membership.

Apply now

If you've got this far, you probably already have a product decision in mind. Write it down in two or three lines, say why, and send it. A person will read it.

Apply to join Product Circle

Related guides