Product Intern

Duration: 6 months, with a path to full-time

Reports to: Shubham Shrivastava, Head of Product

Neoflo is building an AI-native agentic platform that automates high-volume back-office operations for the enterprise. We are ~40 people, backed by Lightspeed and Peak XV, with customers across the US and Southeast Asia.

This page is long on purpose. If you skim it and fire off a resume, you'll get auto-rejected. If you read it and still want to apply, you're probably the kind of person we're looking for.

What you'll actually do

You will not shadow meetings and write summaries. You will not be assigned to "learn about the product" for three weeks before touching anything real.

You will own things. Small things at first — a feature spec, a user research synthesis, a customer-facing doc, a competitive teardown. Then bigger things. You'll sit in on enterprise customer calls, watch real users navigate real workflows, and translate that into product decisions. You'll write PRDs that engineers build from. You'll get feedback that will sometimes sting.

Six months in, if you're good, you'll have shipped features that real enterprise teams use every day. You'll understand how to build AI products for people who can't afford to be wrong. You'll have a portfolio no bootcamp can give you.

Who this is for

You are probably a fit if:

• You've built or shipped something publicly — a side project, a blog, a community, a product teardown, a tool people use. Not a college group assignment. Something you started because nobody told you to.

• You have a point of view about products you use. You can defend it.

• You can reason about AI products without buzzwords.

• You're okay being wrong in public and changing your mind fast.

You are probably not a fit if:

• You want a structured curriculum and clear weekly deliverables handed to you.

• You're doing this for the brand name or the stipend line on your resume.

• You've never built anything outside of what was assigned.

• You need a manager who explains things twice.

Both are valid — just not for this role.

The five questions

Your application lives or dies here. Put your answers in a single document — Google Doc, PDF, or Notion page.

Use AI however you want — but the thinking and the effort have to be yours.

1. The teardown (300 words max)

Pick any product you use often. Not Neoflo. Tell us: what's one thing about this product you would change, and why? What would you measure to know if your change worked? What would you not change, even if your manager asked you to?

That last question is the one we care about most.

2. The thing you built (one paragraph + link + numbers)

Tell us about one thing you've built, shipped, written, or run — publicly. Link to it. Include the date you started, the date you shipped (or launched, or first published), and one number that tells us its scale (users, readers, subscribers, attendees — whatever fits). If you can't name one thing, this role isn't for you yet.

3. The rabbit hole (250 words max)

Tell us about something you learned recently that you didn't have to. Not for school, not for work. Something you went deep on because you wanted to. What was it? How did you go about learning it? What do you know now that you didn't three months ago?

4. The why (150 words max)

Why this role, at this company, right now? "I want to learn product management" is not an answer.

5. One question for us

One question you'd want us to answer, if we offered you the role tomorrow. Just the question. No setup needed.

How to apply

No cover letter. No "I'm excited about the opportunity to..." The five questions and the screen recording are what actually decide this.

The form will ask you for:

1. Your resume — link to Google Drive, Dropbox, or any URL we can open.

2. Your portfolio — personal website, GitHub, Behance, or wherever your work lives. This is not your LinkedIn — it's proof of what you've built, written, or shipped.

3. Your application document — one document with your answers to all five questions above. Make sure the link is accessible.

4. A screen recording — walk us through your answers in your own words. Don't read the doc out loud — talk to us like you're presenting it. At the end, tell us how many hours you spent on this application and one thing at Neoflo you're curious about. Keep it under 5 minutes. Use Loom, QuickTime, OBS — whatever works.

We read the doc first. If it stands out, we watch the recording, then look at the resume and portfolio for context. The thinking is what gets you in the door.

What happens next

• If your application stands out, you'll meet me for a 1-hour video call.

• If that goes well, you'll meet one of the founders.

This role is in-person in Bengaluru, Monday to Friday, for all 6 months. If you're not here, you'll need to relocate. We'll help with the logistics.

We're setting this bar deliberately high because product interns who clear it tend to become product managers we want to keep. If any of this felt like too much, that's good information. If it felt like a challenge you want to take on, we want to hear from you.

Shubham, Head of Product, Neoflo