Engineering track

Software Engineering Intern

Flocci Pulse · product team

pulse.flocci.in
InternshipRanchi, Jharkhand (Hybrid)2 months~40 hrs/week2 openings
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 Software Engineering Intern position on Flocci Pulse?

A two-month on-job training position on Flocci Pulse, our live audience-engagement platform. You begin on application testing — the six response formats, the share links, the live result stream — and once you can explain how a response travels from a browser to a database row and back out to every open screen, you move onto the codebase.

The role

What this posting actually is

Pulse is how a lot of people meet Flocci for the first time. Somebody puts a question on a screen at a workshop, a hundred phones scan a QR code, and the answers have to appear on the projector while the room is still watching. Six response formats sit behind that — polls, quizzes, surveys, forms, word clouds and petitions — and every one of them has to agree with the others about what a valid response is.

Your first three weeks are spent finding the places where it does not. What happens when two people submit in the same second? What does a link do if it was opened before the poll closed and submitted after? Does the word cloud treat "Ranchi" and "Ranchi " as the same word? Does the number on the analytics screen match the count of rows in the table? You will not be guessing — you get the requirements, a staging environment and read access to the database.

Clear the gate in week four and the second month looks different: small, reviewed pull requests against the real Pulse repositories. A validation rule that was missing. A result query fetching more than it needs. A broadcast that updates one screen and forgets another. Nothing large, nothing unreviewed, and nothing you cannot explain in a sentence.

The product team

The product you would join: Flocci Pulse

Flocci Pulse is a live audience-engagement platform for polls, quizzes, surveys, forms, word clouds and petitions, with analytics that explain a result instead of only counting it.

Read the full Flocci Pulse 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

    Break Pulse on purpose

    You get a staging Pulse, the requirement notes for the response formats, and read access to the database behind it. You run every format the way a real host would, then the way a bored respondent would. You write down everything that disagrees with the requirement — and everything the requirement forgot to say.

    What you produce

    • A test charter covering two response formats end to end, stating what you are deliberately leaving out.
    • Reproducible defect reports with steps, expected vs actual, browser and device, and a screenshot or network capture.
    • A reconciliation note comparing the on-screen analytics for one poll against the raw response rows.
    • A written list of the non-functional requirements a live result screen must meet, and how you tested each.

  2. The gate — not everyone passes

    Phase 2Week 4

    The gate — explain the response path

    You sit with the engineer who owns Pulse and walk the path a response takes, out loud: the submit event, the API call, validation, the insert, the broadcast, the re-render. Then you take three of your own defects and classify each as violating a functional or a non-functional requirement, and defend the classification.

    What you produce

    • A whiteboard-level walkthrough of one submission, from the tap on a phone to the pixel that changes on the projector.
    • Three of your defects mapped to the exact requirement each one violates.
    • Your prediction of what fails first when a single poll receives responses far faster than usual, and why.
    • The track decision for month two, told to you directly with reasons.
  3. Phase 3Weeks 5–8

    Commits on the live product

    On the codebase track you take real Pulse issues and ship them in small reviewed pull requests. On the testing track you own a response format: its test plan, its regression list and its release sign-off. Either way your name is on work that ships.

    What you produce

    • Merged pull requests on the Pulse repositories, in conventional-commit form, reviewed by the engineer who owns the service.
    • Or a test plan for one response format that runs against every release.
    • A regression list for your area that the team keeps using after you leave.
    • A written closing review of your two months.

The work

What you will actually do

  • Test all six Pulse response formats and find the places where they disagree with each other about validation, limits or closing behaviour when they should not.
  • Trace a single response end to end: the submit click in the browser, the API call, the validation layer, the row written to PostgreSQL, and the Socket.io broadcast that updates every open result screen.
  • Hunt the edge cases that only appear in the wild — a link opened after a poll has closed, two submissions in the same second, a repeat vote from the same device, a QR code scanned on a phone with a weak connection.
  • Reconcile the live analytics against the raw rows and report every place the number on screen disagrees with the number in the table.
  • After the gate: fix real defects in the Pulse UI or API in small reviewed pull requests — a validation rule, a misleading empty state, a result query doing more work than it needs to.
  • Write the migration and the seed data for any schema change you make, so the next person can run it without asking you.
  • Keep the regression list for your area current and run it before each release.

Who this is for

What you need, and what simply helps

Requirements

  • You are in your 2nd, 3rd or 4th year of an engineering degree and can commit two continuous months.
  • You can read JavaScript or TypeScript and follow what a React component is doing, even if you have not written much of either yourself.
  • You know what an HTTP request is, what a database row is, and roughly what sits between them.
  • Git basics: clone, branch, commit, push, open a pull request.
  • You can write clearly in English — a defect report and a commit message are both writing tasks before they are technical ones.
  • You are willing to spend the first three weeks testing before touching the codebase. That is the programme, not a formality.

Nice to have

  • You have used a live polling or quiz tool in a class or event and formed an opinion about it.
  • You have seen a WebSocket or Socket.io connection before, even only in a tutorial.
  • Enough SQL to write a SELECT with a WHERE and a GROUP BY.
  • You have opened the browser DevTools Network tab on purpose at least once.

The stack

What you would be working with

  • React 18 + TypeScript (Vite)
  • Node.js + Express
  • PostgreSQL
  • Socket.io for live results
  • Zod request validation
  • Flocci Identity for sign-in, Flocci Payments for credit metering
  • Git with conventional commits, deployed to an OVHcloud VPS behind nginx and pm2

What you leave with

What you will learn that college does not teach

  • What realtime actually costs — why a live result screen is a harder problem than a page you refresh.
  • How to write a defect report an engineer can act on without a single follow-up question.
  • The difference between a functional requirement (a poll must reject a second vote from the same respondent) and a non-functional one (the result screen must update within a second of the response landing).
  • How a change ships here: branch, small commit, review, migration, deploy, then watch it in production.
  • How to read a codebase you did not write without panicking — the skill college does not teach.

Eligibility

Before you apply, check these

  • Enrolled in a full-time engineering programme at an Indian institution (B.E./B.Tech/M.Tech or an equivalent diploma).
  • Available for two continuous months from the cohort start, roughly 40 hours a week.
  • Able to be in Ranchi, Jharkhand for the agreed in-office days — this is a hybrid position.
  • Your own laptop and a usable internet connection.
  • If this is a college-mandated OJT, your institution must accept an unpaid industrial-training placement.

Selection

How we decide

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

  1. Apply with your resume, a GitHub link or any link to something you have built, and the two written answers below. The answers carry more weight than the resume.
  2. A 20-minute screening call about how you think, not what you have memorised.
  3. A practical exercise: we point you at a live Pulse screen and ask you to find three things wrong with it and say which requirement each one violates.
  4. A conversation with the engineer who owns Pulse about your exercise and about how the two months will run.
  5. Offer and joining letter, with the paperwork your college needs 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 Software Engineering Intern position on Flocci Pulse

2 openings · Ranchi, Jharkhand (Hybrid) · Next cohort begins October 2026. Applications close 30 September 2026.

Elsewhere in the cohort

Other open roles

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

Software Engineering Intern

Flocci Pulse · closes 30 September 2026