Product & Business Analyst Intern

About the Role

• A part-time, two-month on-job training position on Flocci Leads, Flocci's sales-operations cockpit.
• Roughly 20 hours per week alongside your semester.
• You will start by testing the product against its current requirements, then write the functional and non-functional requirements yourself.

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.

Key Responsibilities

• Test Flocci Leads against its existing requirements (lead discovery, scoring, call queues, follow-ups, daily briefing) and file defects and identify areas where no requirement exists.
• Write functional requirements for one area as user stories with acceptance criteria specific enough for two engineers to build the same thing.
• Write non-functional requirements for the same area, including:
• Freshness of the call queue.
• Load time of the briefing.
• Behavior when a lead import is far larger than expected.
• Data that must never be lost when a call is logged offline.
• Define, in writing, what the scoring model is actually claiming (inputs, meaning of a high score, conclusions a rep can draw).
• Answer product questions using read-only SQL instead of asking others for their impressions.
• Turn a one-sentence request from the founder into a specification an engineer can pick up, including raised questions and decisions taken.
• Write release notes and in-product help text for features shipped during your two months.

The Process

• Phase 1 (Weeks 1-3): Application Testing
• Use Leads as a salesperson would and test it against existing requirements.
• File defects and keep a list of behaviors with no written requirement.
• Produce: Reproducible defect reports, a gap list, a walkthrough of the product's daily rhythm, and a first non-functional requirement draft.
• Gate (Week 4): Defend a Requirement
• Defend one requirement document to an engineer and reviewer.
• Explain the architecture behind the feature.
• Produce: One user story with acceptance criteria, separated functional and non-functional requirements, and an architectural walkthrough.
• Decision on whether requirements go into the backlog or further documentation and testing is needed.
• Phase 3 (Weeks 5-8): Own a Specification
• Your documents become inputs to the backlog.
• Sit with engineers building from your specifications, answer questions, and record decisions.
• Produce: A specification that was built from, a decision log, release notes, in-product help text, and a closing review.

Requirements & Tech Stack

Requirements

• Enrollment in your 2nd, 3rd, or 4th year of an engineering or business-technology degree.
• Ability to commit roughly 20 hours a week for two continuous months.
• Excellent written English.
• Willingness to learn enough SQL for basic queries (SELECT, GROUP BY).
• Ability to accept constructive criticism on documents and rewrite them.
• Comfort using a product thoroughly before forming an opinion.
• A reliable schedule that can be maintained alongside classes.

Nice to Have

• Experience writing documentation, reports, or proposals that required action from others.
• Experience in sales, event management, or cold outreach.
• Any prior SQL experience.
• Experience using a CRM or sales tool.
• Experience drawing flow diagrams to explain processes.

Tech Stack

• Flocci Leads (discovery, scoring, call queues, follow-ups, daily briefing).
• Read-only query access to a staging database.
• Postman or curl for API interaction.
• Flocci Library for specifications.
• Flocci Projects for the backlog.
• Flocci Pulse for structured surveys.
• Markdown.
• Diagrams.

What You Will Learn

• How to write functional requirements that cannot be built in multiple ways.
• What non-functional requirements are for, expressed in numbers.
• How to move from opinion to evidence using data and queries.
• How engineering consumes specifications.
• How product decisions are made and recorded.

Eligibility

• Enrolled in a full-time engineering or business-technology program at an Indian institution.
• Available for roughly 20 hours a week across two continuous months on a fixed schedule.
• Remote from anywhere in India with a stable internet connection.
• Own laptop.
• College must accept an unpaid, part-time, remote industrial-training placement.

Compensation

• Certificate of completion.
• Merit bonus for exceptional work.
• This is an unpaid industrial-training position.