Product & Business Analysis track

Product & Business Analyst Intern

Flocci Leads · product team

leads.flocci.in
Part-time InternshipRemote (India)2 months~20 hrs/week1 opening
Applications close
30 September 2026
Cohort
Next cohort begins October 2026
What you get
Certificate + merit bonus
How the two months run

What is the Product & Business Analyst Intern position on Flocci Leads?

A part-time, two-month on-job training position on Flocci Leads, our sales-operations cockpit. Roughly 20 hours a week alongside your semester. You start by testing the product against its current requirements, then you write the functional and non-functional requirements yourself — the documents the engineering and quality tracks work from.

The role

What this posting actually is

Flocci Leads answers one question for a salesperson every morning: who do I call next, and why. Behind that sit lead discovery, a scoring model, call queues, follow-up rules and a daily briefing. Almost every disagreement about this product is a requirements disagreement — what counts as a stale lead, whether a follow-up that was rescheduled twice should still be at the top of the queue, what the score is actually claiming.

That is the job. You start where everybody starts, on application testing: using Leads properly, checking it against the requirements as they exist today, and filing what does not match. Very quickly you find the more interesting failure, which is that a requirement was never written down at all, and two people have been assuming different things about it for months. Your work is to close that gap — in writing, precisely enough that an engineer can build from it and a tester can test against it.

You will write user stories with acceptance criteria a person could argue with. You will write the non-functional requirements too, which students almost never get taught: how fresh the call queue has to be, how fast a briefing must load before a rep stops using it, what happens to the product when one account imports far more leads than anyone planned for. And you will use SQL to answer your own questions with data instead of taking somebody’s word for how the product is used.

The product team

The product you would join: Flocci Leads

Flocci Leads is a B2B lead-intelligence and sales-operations cockpit — discovery, scoring, call queues and follow-ups that tell a rep who to call next and why.

Read the full Flocci Leads page

How the two months run

Testing first. Then a gate. Then the codebase.

Nobody is handed the codebase on day one, on any track. This is the arc for this posting specifically — the phases, the gate in week four, and what you produce in each.

  1. Phase 1Weeks 1–3

    Application testing — learn the product by holding it to its word

    Everyone starts here, including this track. You use Leads as a salesperson would for a full week before you criticise it, then test it against the requirements that exist. You file defects like everybody else, and separately you keep a list of every behaviour that no written requirement covers — which becomes your work for the rest of the two months.

    What you produce

    • Reproducible defect reports against the existing requirements for lead discovery, scoring and the call queue.
    • A gap list: every behaviour you found that no requirement describes, with the ambiguity spelled out.
    • A written walkthrough of the daily rhythm the product is trying to create for a sales rep, in your own words.
    • Your first non-functional requirement draft — freshness and load time for the call queue, stated as numbers.

  2. The gate — not everyone passes

    Phase 2Week 4

    The gate — defend a requirement you wrote

    You bring one requirement document to an engineer and a reviewer and they attack it: what does this not say, what would two developers build differently from this, which of these are functional and which non-functional, what happens at the boundary you did not mention. You also explain the architecture behind the feature — what happens between a click and a database write — because you cannot specify a system you cannot describe.

    What you produce

    • One user story with acceptance criteria, defended line by line under questioning.
    • A clean separation of the functional and non-functional requirements in your own document, with the reasoning.
    • An architectural walkthrough of the feature you specified, from the interface to the data it writes.
    • The track decision for month two: your requirements go into the backlog as written, or you continue documenting and testing against existing requirements with review.
  3. Phase 3Weeks 5–8

    Own a specification that gets built

    Your documents become inputs to the actual backlog. You sit with the engineers who build from them, you answer the questions your specification failed to anticipate, you record the decisions, and you write the release notes when it ships. Watching your own words become software — and finding out where they were not clear enough — is the fastest possible education in this discipline.

    What you produce

    • A specification in the backlog that an engineer built from, with your name on it.
    • A decision log for your area: what was chosen, what was rejected, and why.
    • Release notes and in-product help text for what shipped during your two months.
    • A written closing review of your two months.

The work

What you will actually do

  • Test Flocci Leads against its existing requirements — lead discovery, scoring, call queues, follow-ups, the daily briefing — and file both the defects and the places where no requirement exists to test against.
  • Write the functional requirements for one area as user stories with acceptance criteria specific enough that two engineers would build the same thing from them.
  • Write the non-functional requirements for the same area: freshness of the call queue, load time of the briefing, behaviour when a lead import is far larger than expected, what must never be lost when a call is logged offline.
  • Define, in writing, what the scoring model is actually claiming — what goes in, what it means for a lead to score highly, and what a rep is entitled to conclude from it.
  • Answer your own product questions with read-only SQL instead of asking someone for their impression, and put the query in the document so the number can be checked.
  • Turn a one-sentence request from the founder into a specification an engineer can pick up, including the questions it raised and the decisions taken.
  • Write the release notes and the in-product help text for what ships during your two months.

Who this is for

What you need, and what simply helps

Requirements

  • You are in your 2nd, 3rd or 4th year of an engineering or business-technology degree and can commit roughly 20 hours a week for two continuous months.
  • You write well in English. This posting is largely a writing job, and vague sentences cause real defects downstream.
  • You are willing to learn enough SQL to answer a question with a SELECT and a GROUP BY. We will teach you; you have to want it.
  • You can be told your document is ambiguous without taking it personally, and rewrite it the same day.
  • You are comfortable using a product properly and at length before forming an opinion about it.
  • A schedule you can actually keep alongside classes, agreed in writing before you start.

Nice to have

  • You have written documentation, a report or a proposal that somebody else had to act on.
  • You have sold anything, run a college event, or done cold outreach — you will understand the user faster.
  • Any SQL at all.
  • You have used a CRM or a sales tool, even a spreadsheet somebody called a CRM.
  • You have drawn a flow diagram to explain a process to somebody who was confused.

The stack

What you would be working with

  • Flocci Leads itself — discovery, scoring, call queues, follow-ups and the daily briefing
  • Read-only psql against the staging PostgreSQL database, for answering your own questions
  • Postman or curl to read the API and understand what the interface is really working with
  • Flocci Library for the specifications, and Flocci Projects for the backlog they feed
  • Flocci Pulse to run a short structured survey when you need input rather than opinion
  • Markdown, and diagrams when a sentence will not do it

What you leave with

What you will learn that college does not teach

  • How to write a functional requirement that cannot be built two different ways, and why that is harder than it sounds.
  • What non-functional requirements are for, stated in numbers rather than adjectives — the thing almost no student is taught to write.
  • How to move from an opinion to evidence: define the question, get the data, state the answer with its query attached.
  • How engineering actually consumes a specification, because you will watch your own document be built from and see what it failed to say.
  • How a product decision gets made and recorded, including the option that was rejected and why.

Eligibility

Before you apply, check these

  • Enrolled in a full-time engineering or business-technology programme at an Indian institution.
  • Available for roughly 20 hours a week across two continuous months, on a fixed agreed schedule.
  • Remote from anywhere in India, with a connection stable enough for regular video calls — this track involves more conversation than the others.
  • Your own laptop.
  • If this is a college-mandated OJT, your institution must accept an unpaid, part-time, remote industrial-training placement — check this before applying, since some colleges require full-time hours.

Selection

How we decide

Five steps, in this order. The written answers carry more weight than the resume.

  1. Apply with your resume, a link to anything you have written that someone else had to act on, and the two written answers below. The writing is the portfolio here.
  2. A 20-minute screening call, including agreeing the weekly schedule that fits around your classes.
  3. A practical exercise: we describe a feature in three sentences and ask you to write the requirement and list every question the three sentences left open.
  4. A conversation with the engineer who owns Leads, who will push back on your exercise the way they would on a colleague’s.
  5. Offer and joining letter, with the college paperwork attached.

Compensation

Certificate + merit bonus

A certificate of completion for every intern who finishes the programme.

Interns whose work clears an exceptional bar are considered for a completion bonus at the end of the two months. It is earned, not scheduled.

This is an unpaid industrial-training position

The programme

What we provide, and what we expect back

Identical on every posting — this is one programme with several tracks.

What we provide

  • A real product, not a sandbox: a live Flocci surface with real customers, its requirement notes, and a staging environment of your own to break.
  • A certificate of completion for every intern who finishes the two months, on either track.
  • Code review from the engineers who own the service — on your commits, and on your defect reports before that.
  • Access to the tooling that matters: the repositories, staging environments, the issue tracker, and read access to the databases you are testing against.
  • A weekly one-to-one where you are told plainly how you are doing, including when it is not going well.
  • A written closing review, and consideration for a completion bonus if your work clears an exceptional bar.

What we expect

  • Roughly 40 hours a week on the full-time track and roughly 20 on the part-time track, on a schedule agreed in writing before you start.
  • A daily written update: what you did, what you found, what is blocking you. Three lines is enough. Silence is not.
  • Defect reports another person can follow without asking you a single question.
  • That you use the product properly before you judge it, and read the requirement before you call something a bug.
  • Confidentiality. You will see customer data structures and unreleased work; it stays inside.
  • Honesty about what you do not know. It is the single fastest thing you can do for yourself here.

The bar

  • Show up. Two months is eight weeks and eight weeks is short. If you cannot make a day, say so before it starts, not after it has passed.
  • Reproduce it before you report it. A bug you saw once and cannot make happen again is a note to yourself, not a defect report.
  • Read first, then ask. The requirement, the existing code and the error message answer most questions. Ask once you have read all three and it still does not make sense — then ask immediately, not on Friday.
  • Do not ship code you cannot explain. If you cannot say why a line is there, it does not go in. Pasting a fix you do not understand is worse than saying you are stuck.
  • Write in plain sentences. Half of this work is being understood — in a defect report, a commit message, a stand-up note. Nobody here is impressed by long words.

For colleges

If this is your college's on-job training requirement

  • We issue the paperwork colleges normally ask for: a joining letter at the start of the two months and a completion certificate at the end, stating the dates, the track, the product worked on and the weekly hours.
  • Attendance and progress are recorded weekly. A college mentor or TPO can be named on the application — they will receive the joining confirmation, a mid-programme note and the completion certificate, and can write to us directly at workshop@flocci.in. If your institution needs a periodic report or a signed logbook in its own format, tell us in the application and we will keep our records in that shape.
  • The part-time track exists for exactly this situation: if your training window runs alongside a semester, send us your college schedule and the two months are structured around it.
  • What we will not do: promise a placement, backdate a certificate, or certify hours that were not worked. These are unpaid industrial-training positions — if your college requires a paid placement for the training to count, please check that before you apply.

The company

About Flocci Technologies

Flocci Technologies is an India-based, AI-native software company founded in 2023 and built in Ranchi, Jharkhand. It publishes a connected estate of software: 20 product surfaces — audience engagement, AI support, recruiting, sales, meetings, work apps — plus 8 full ERP and POS systems for hotels, schools, garages, libraries, marts, pharmacies and restaurants. It is priced in rupees, billed through PayU, and designed around how Indian businesses actually operate rather than translated from a US product.

The idea holding it together is called One Flocci: every product runs on the same shared layer instead of reinventing it. Identity handles sign-in, organisations, teams and roles once, for everything. Payments holds a single credit wallet you top up once and spend in any product. Intelligence is the shared, metered AI layer every app calls, so AI behaves and bills the same way everywhere. Graph is the cross-app event spine, carrying counts and metadata but never your content. Notifications is one delivery pipe for transactional email and one-time codes, and Gateway is the only public door in — it resolves the app, verifies the session and strips untrusted identity headers before anything reaches a service.

Flocci was founded by MD Afsar Hussain, who spent 10+ years as a senior engineer at SAP Labs India across S/4HANA, ABAP, Fiori and BTP before building this platform. He studied at BIT Mesra (B.Tech) and BITS Pilani (M.Tech), mentors 30+ startups and runs AI and coding workshops across India. That enterprise background shows up in how the estate is built — shared services, auditable rails, systems meant to survive being depended on — and it is why an internship here is run as engineering rather than as a workshop.

What that means for you as an intern: you will touch production code and production data structures used by real customers, not a training sandbox built for interns. The product you are assigned is live while you are testing it. When your commit merges, it gets deployed and somebody uses it. That is the appeal and it is also the reason for the gate in week four — real code carries real consequences, so we make sure you understand the system before you change it.

The facts

Company
Flocci Technologies — an India-based, AI-native software company
Founded
2023
Headquarters
Ranchi, Jharkhand, India
Founder
MD Afsar Hussain, Founder & CEO — 10+ years as a senior engineer at SAP Labs India
Scale
20 product surfaces and 8 ERP/POS systems on one shared platform
Platform
One account, one credit wallet and one AI layer across every product
Contact
workshop@flocci.in

The stack, across the estate

Frontend
Vite + React + TypeScript single-page apps, Tailwind and shadcn components
Backend
Node.js and Express services, with some Python/FastAPI
Database
PostgreSQL
Realtime
Socket.io — Flocci content features are realtime by default
AI
DeepSeek through the OpenAI SDK behind a provider abstraction, or through the shared Intelligence service
Payments
PayU, metered per action against one credit wallet
Infrastructure
Self-hosted OVHcloud VPS with nginx and pm2; sibling -ui and -srv repositories per product, conventional commits

Questions

Questions about this posting

Apply for the Product & Business Analyst Intern position on Flocci Leads

1 opening · Remote (India) · Next cohort begins October 2026. Applications close 30 September 2026.

Elsewhere in the cohort

Other open roles

EngineeringSoftware Engineering InternFlocci Pulse · Ranchi, Jharkhand (Hybrid)View roleEngineeringSoftware Engineering InternFlocci Talent Suite · Remote (India)View roleEngineeringSoftware Engineering InternFlocci Schools Suite · Ranchi, Jharkhand (Hybrid)View role
See all 8 postings and how the programme works

Product & Business Analyst Intern

Flocci Leads · closes 30 September 2026