Engineering track

Software Engineering Intern

Flocci Talent Suite · product team

talent.flocci.in
InternshipRemote (India)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 Talent Suite?

A two-month remote on-job training position on Flocci Talent Suite, our applicant tracking system. You start on application testing — pipeline stages, resume parsing, permissions, notification email — and after the gate you write reviewed code in a product where a wrong permission or a lost stage transition affects somebody’s job application.

The role

What this posting actually is

Talent Suite carries a role from requisition to offer: job posts, applications, structured screening, a candidate pipeline, interview scheduling and the people-operations work that follows an offer. AI resume screening ranks applicants against the requirement instead of keyword-matching them. You are, at this exact moment, a candidate in a system very much like it — which is the most useful perspective an intern on this product can have.

That perspective is also the responsibility. A pipeline stage that silently fails to save means a recruiter thinks they rejected someone they did not. A permissions rule that leaks an internal note means a candidate sees an opinion about them that was never meant to leave the team. A resume that is a scanned image rather than text has to fail loudly, not quietly produce an empty profile. Your first three weeks are spent proving which of those hold and which do not.

After the gate, the code you touch is the code that decides what a recruiter sees and in what order. Small changes, reviewed by the engineers who own the service: a validation rule on a stage transition, a duplicate-candidate check, a notification that fires once instead of three times.

The product team

The product you would join: Flocci Talent Suite

Flocci Talent Suite is an AI-native applicant tracking system that carries a role from requisition to offer — structured screening, candidate pipeline, interview workflow and people operations.

Read the full Flocci Talent 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 the path a candidate takes

    You are given a staging Talent Suite with seeded requisitions and candidates, and the requirement notes for the pipeline. You play every role in turn — candidate, recruiter, interviewer, admin — and you find the places where the system lets somebody do something the requirement never allowed.

    What you produce

    • A stage-transition matrix: which role may move a candidate from which stage to which, tested and marked pass or fail.
    • A resume-intake defect set covering malformed, oversized and non-text files, each with the file that reproduces it.
    • Reproducible reports on any permission leak, ranked by what a real person would actually see.
    • A written list of the non-functional requirements you believe hiring data imposes — retention, access, auditability — and how you checked each.
  2. The gate — not everyone passes

    Phase 2Week 4

    The gate — explain who is allowed to do what, and why

    You walk an engineer through the architecture behind a single action: an interviewer submitting feedback. Which service verified the session, where the organisation scope was applied, what was written, who can now read it. Then you classify your own defects as functional or non-functional failures and defend each call.

    What you produce

    • An end-to-end account of one authenticated write, from the gateway’s session check to the row in PostgreSQL.
    • Your defects sorted into functional and non-functional, with the reasoning stated.
    • Your prediction of the first thing to break when one organisation has far more candidates than the seeded data assumed.
    • The track decision for month two, told to you directly with reasons.
  3. Phase 3Weeks 5–8

    Ship into a system people’s applications live in

    On the codebase track you take real defects on the pipeline, the intake or the screening surface, in small reviewed pull requests. On the testing track you own the permission and pipeline test plan and run it before every release. Both are held to the same standard: nothing goes out that you cannot explain.

    What you produce

    • Merged, reviewed commits on the Talent Suite repositories in conventional-commit form.
    • Or an owned permission and pipeline test plan, executed against every release.
    • A regression list for the candidate journey that stays in use after you leave.
    • A written closing review of your two months.

The work

What you will actually do

  • Drive a candidate through the entire pipeline — applied, screening, interview, offer, rejected — and find every transition that can be performed twice, skipped, or done by a person who should not be allowed to.
  • Test resume intake against the files people actually upload: a scanned image PDF, a 12MB document, a file with no extension, a resume in two columns, a name written in Devanagari.
  • Prove the permission model rather than trusting it — what a recruiter sees versus an interviewer versus an org admin, using Flocci Identity roles, and what happens when someone’s role changes mid-process.
  • Check the AI screening output against the requisition it is scoring: is the ranking explainable, does it degrade sensibly when the resume is thin, and what does it do when the AI layer returns nothing at all?
  • Follow the transactional email path through Flocci Notifications — does a rejection go out once, to the right address, with the right role name, and is it logged?
  • After the gate: reviewed pull requests on real defects — a stage-transition guard, a duplicate-candidate check, a screening result that has to render an honest empty state.

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, full-time and remote.
  • You can read TypeScript and follow a React component and an Express route without needing every line explained.
  • You understand what a database relation is — that a candidate, an application and a job posting are three different things that point at each other.
  • Git basics, and enough discipline to work unsupervised from home and still be visible every day.
  • Clear written English. Remote work is writing; there is no corridor to catch someone in.
  • You are willing to spend the first three weeks testing before touching the codebase.

Nice to have

  • You have applied for internships and formed opinions about the portals that made you do it.
  • You have written a SQL JOIN and understood the result.
  • You have used Postman, curl or the DevTools network panel to call an API by hand.
  • You have seen role-based access control before, even in a college project with an admin flag.

The stack

What you would be working with

  • React 18 + TypeScript (Vite)
  • Node.js + Express
  • PostgreSQL with multi-tenant organisation scoping
  • Flocci Identity for organisations, teams, roles and seats
  • Flocci Intelligence for AI resume screening (DeepSeek behind a provider abstraction)
  • Flocci Notifications for transactional email
  • Git with conventional commits, OVHcloud VPS behind nginx and pm2

What you leave with

What you will learn that college does not teach

  • How a real permission model is designed and, more importantly, how you prove one is correct rather than assuming it.
  • Why file upload is one of the most defect-dense features in any product, and how to test it properly.
  • How an AI feature is judged in production — not "does it look smart" but "is it explainable, and what does it do when it fails".
  • How to reason about state machines: which transitions are legal, which are reversible, and which must never happen twice.
  • How to work remotely in a way people trust — the written update, the reproducible report, the commit that explains itself.

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, roughly 40 hours a week.
  • Remote from anywhere in India, with a workspace and connection you can hold a video call from.
  • Your own laptop.
  • If this is a college-mandated OJT, your institution must accept an unpaid, remote 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. The answers matter more than the resume — which is a slightly funny thing to say about an ATS internship, and we mean it.
  2. A 20-minute screening call about how you approach a problem you have not seen before.
  3. A practical exercise: we describe a hiring rule in one sentence and ask you to list every way a user could violate it.
  4. A conversation with the engineer who owns Talent 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 Talent Suite

2 openings · Remote (India) · Next cohort begins October 2026. Applications close 30 September 2026.

Elsewhere in the cohort

Other open roles

Software Engineering Intern

Flocci Talent Suite · closes 30 September 2026