Engineering track

Software Engineering Intern

Flocci Schools Suite · product team

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 Schools Suite?

A two-month on-job training position on Flocci Schools Suite, the ERP that carries admissions, fees, attendance, examinations and the parent portal for Indian schools. You start on application testing, where money and marks make the stakes obvious, and after the gate you write reviewed code inside a system a school runs its day on.

The role

What this posting actually is

Schools Suite is not a consumer app you can redesign on a whim. A school runs its admissions, its fee collection, its attendance registers, its examinations and its parent communication on it, and every one of those has a paper equivalent somebody will compare it against. A receipt number that repeats is not a cosmetic bug; it is an accounting problem with a person standing at a counter holding the printout.

That is why this is one of the best products to learn on. The requirements are unusually concrete — a concession applies before or after tax, an academic year rolls over on a date, a parent may see their own child and nobody else’s — so the distinction between "the software is wrong" and "I misunderstood the rule" is sharp and teachable. In three weeks of testing you will learn to read a requirement properly, because here it is the only thing that settles an argument.

After the gate you work on the code with the same care: a fee calculation, a grade computation, a register query that gets slower as a school adds sections. Small, reviewed, explainable. On a system where somebody’s child’s marks are the output, that is the only acceptable way to work.

The product team

The product you would join: Flocci Schools Suite

Flocci Schools Suite carries the full school lifecycle — admissions, academics, attendance, fees, examinations and parent communication — on one platform, so a fee receipt, an attendance record and an exam result all describe the same student file.

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

    Test where the money and the marks are

    You get a staging school with seeded students, fee structures and an exam cycle. You test the fee lifecycle and the examination path against the written rules, and you record both what failed and what you verified. On this product, evidence that something is correct is worth as much as a defect.

    What you produce

    • A fee-scenario matrix — partial payment, concession, late fee, cancellation, double payment — each with expected and actual outcomes.
    • Defect reports for any receipt-numbering, rounding or total mismatch, with the exact figures attached.
    • A parent-portal access test, including direct-URL attempts against another student’s records.
    • A written list of the non-functional requirements a school ERP carries — auditability, data retention, response time on a register — and how you tested them.
  2. The gate — not everyone passes

    Phase 2Week 4

    The gate — explain a receipt from click to row

    You walk an engineer through what happens when an accountant records a fee payment: the validation, the transaction boundary, the receipt number, the rows written, the PDF produced, and what the system does if the request is submitted twice. Then you classify your defects as functional or non-functional and defend each one.

    What you produce

    • A full account of a single fee payment, including where the transaction begins and ends.
    • Your defects classified, with the requirement each violates named.
    • Your prediction of what breaks first when the school runs a fee collection drive and a hundred receipts are issued in an hour.
    • The track decision for month two, told to you directly with reasons.
  3. Phase 3Weeks 5–8

    Change code a school depends on

    On the codebase track you take real defects in the fee, exam or attendance modules — small and reviewed, with the calculation reasoning written into the pull request. On the testing track you own the fee and examination test plan and run it before every release, which on this product is the higher-stakes half of the job.

    What you produce

    • Merged, reviewed commits on the Schools Suite repositories, with the rule you implemented stated in the pull request.
    • Or an owned fee and examination test plan executed against every release.
    • A regression list covering the calculations most likely to be quietly wrong.
    • A written closing review of your two months.

The work

What you will actually do

  • Test the fee lifecycle properly: partial payments, concessions, late fees, cancelled receipts, a payment recorded twice, and whether the receipt number sequence can ever repeat or skip.
  • Work the examination path — mark entry, moderation, grade computation, result publication — and check what happens when a mark is edited after results are published.
  • Prove parent-portal scoping: a parent must see their own child’s attendance, fees and results and never another student’s, including through a direct URL or a stale session.
  • Test the academic-year rollover — the single most dangerous operation in a school ERP — and document exactly which records carry forward and which must not.
  • Test the attendance register against edge dates: holidays, half days, a student admitted mid-term, a section that changes in the middle of the year.
  • After the gate: reviewed pull requests on real defects — a fee calculation rule, a receipt-numbering guard, a register query that got slow, a PDF that renders wrong on one browser.

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 TypeScript and follow an Express route from request to database query.
  • You are comfortable being careful with arithmetic and with rules that have exceptions. Money and marks do not tolerate approximate reasoning.
  • Git basics: clone, branch, commit, push, open a pull request.
  • You can write clearly in English and record what you tested, not only what you found.
  • You are willing to spend the first three weeks testing before touching the codebase.

Nice to have

  • Enough SQL to check a total on screen against a SUM in the database.
  • You have seen a school or college ERP from the student side and remember what annoyed you.
  • You have generated a PDF from code, or fought with one.
  • Basic understanding of how a payment gateway callback works.

The stack

What you would be working with

  • React 18 + TypeScript (Vite)
  • Node.js + Express
  • PostgreSQL with per-school tenant scoping
  • Role-based access via Flocci Identity — admin, teacher, accountant, parent
  • Server-side PDF generation for receipts, report cards and registers
  • PayU for fee collection
  • Git with conventional commits, OVHcloud VPS behind nginx and pm2

What you leave with

What you will learn that college does not teach

  • How to read a business requirement precisely enough to settle an argument with it.
  • Why money paths are engineered differently — idempotency, sequences, audit trails and why "just retry it" is a dangerous instinct.
  • How multi-tenancy works in practice, and how a tenant-scoping bug becomes a privacy incident.
  • How to test a batch operation like an academic-year rollover, where the failure only becomes visible weeks later.
  • How performance degrades with data rather than with time — a query that is fine for one section and painful for forty.

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 and the two written answers below.
  2. A 20-minute screening call, part of which is us reading you a rule and asking what it does not cover.
  3. A practical exercise: we give you a small fee structure with a concession and a late fee, and ask you to compute three cases and state your assumptions.
  4. A conversation with the engineer who owns Schools Suite about your exercise and the two months.
  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 Software Engineering Intern position on Flocci Schools Suite

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

Elsewhere in the cohort

Other open roles

Software Engineering Intern

Flocci Schools Suite · closes 30 September 2026