Quality Engineering track

Quality Engineering Intern

Flocci Hotels 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 Quality Engineering Intern position on Flocci Hotels Suite?

A two-month on-job training position on the quality engineering track for Flocci Hotels Suite. You test folios, the housekeeping state machine, POS edge cases and the reservation calendar against written requirements, and after the gate you move from running given charters to owning a surface and fixing small defects yourself.

The role

What this posting actually is

A hotel runs on state. A room is vacant-dirty or occupied or blocked; a folio is open or settled; a reservation is confirmed, checked in, no-show or cancelled. Every one of those is a transition somebody triggers at a front desk at an awkward hour, often twice because the first click did not appear to do anything. Quality engineering on a property system is the work of finding the transitions that should be impossible and are not.

You will test folios until the arithmetic is boring to you: a charge posted, split across two guests, transferred to a company account, voided after the tax was applied, settled by two payment methods. You will drive the housekeeping board through its whole state machine and find the path where a room becomes ready without being inspected. You will post a POS bill to a room after the guest has checked out and find out what the system thinks it should do.

This is not a track for people who could not get the engineering one. Clearing the gate here means you stop executing charters someone else wrote and start owning a surface: reading the code to work out where the risk actually is, designing the test plan yourself, and fixing the small defects you find. The engineers hold your reports to the same standard they hold each other’s.

The product team

The product you would join: Flocci Hotels Suite

Flocci Hotels Suite is a property management system that carries the back office too: reservations, front desk, folios, housekeeping, hotel POS, HRMS, finance and channel operations in one system.

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

    Application testing across desk, folio and POS

    You get a staging property seeded with rooms, rate plans, reservations and a POS menu, plus the requirement notes for each module. You execute charters given to you at first, then start writing your own. Every finding is reproducible or it does not count.

    What you produce

    • A folio test matrix covering post, split, transfer, void and multi-method settlement, with the balance verified after each.
    • A housekeeping state diagram you drew from the product, with the illegal transitions you managed to perform marked on it.
    • POS defect reports for at least the void-after-KOT and post-to-vacated-room cases, with steps and evidence.
    • A written list of the non-functional requirements a front desk imposes — how fast the room board must load, what must survive a lost connection — and how you tested each.

  2. The gate — not everyone passes

    Phase 2Week 4

    The gate — explain the system you have been breaking

    You walk an engineer through what happens when a POS bill is posted to a room: which service takes it, how it reaches the folio, what is written, and what should happen if the guest checked out thirty seconds earlier. You classify your defects functional or non-functional, and you say where the property system will strain on a full-house check-out morning.

    What you produce

    • An end-to-end account of a POS charge landing on a guest folio.
    • Your defects classified against functional and non-functional requirements, in your words.
    • A prediction of what degrades first when every room checks out within the same hour, with reasoning.
    • The track decision for month two: own a surface and fix defects, or continue on structured charters with supervision.
  3. Phase 3Weeks 5–8

    Own a surface

    You take one area — folios, housekeeping or POS — and it becomes yours. You write the test plan, you run it before every release, you sign it off, and you fix the small defects you find in reviewed pull requests. Interns who did not clear the gate continue on structured charters with supervision, finish the programme and receive the same certificate.

    What you produce

    • A test plan for your surface that the team runs at every release.
    • A regression list built from the defects you found, not from a template.
    • Merged fixes for small defects you filed yourself, reviewed by the engineer who owns the module.
    • A written closing review of your two months.

The work

What you will actually do

  • Test folio arithmetic exhaustively — post a charge, split it, transfer it to another folio or a company account, void it after tax, settle it across two payment methods — and confirm the folio still balances after every one.
  • Drive the housekeeping state machine end to end (vacant-dirty, cleaning, inspected, vacant-ready, out of order) and find every path that lets a room reach ready without passing inspection.
  • Break the reservation calendar on purpose: same-day check-out and check-in, a stay extended past a blocked date, a group booking partly cancelled, an early departure with a rate plan that changed mid-stay.
  • Test the hotel POS against the real awkward cases — an item voided after the KOT fired, a bill posted to a room the guest has already vacated, a discount applied after the tax line.
  • Run the night audit and check that what it produces reconciles with the folios and the POS closings that fed it.
  • Write the test charters and the regression list, not just execute them — and after the gate, fix the small defects you filed yourself.

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 be systematic — the kind of person who writes down what they tried before trying the next thing.
  • You can read enough JavaScript or TypeScript to follow what a screen does when a button is pressed. You do not need to write much of it in the first month.
  • You are comfortable in browser DevTools and willing to learn to read an API response and a database row.
  • You can write a defect report a stranger can follow — this is the core skill of the track, not a side skill.
  • You accept that quality engineering is engineering. If you are hoping to skip the rigour, this is the wrong posting.

Nice to have

  • You have stayed in a hotel and noticed something wrong at the front desk. Genuinely useful here.
  • Enough SQL to read a table and check a total.
  • You have used Postman, curl or the DevTools network panel to call an API by hand.
  • You have drawn a state diagram for something, in any course.
  • Any exposure to test case design — boundary values, equivalence classes — even from a textbook.

The stack

What you would be working with

  • The live product across desk, housekeeping and POS surfaces
  • Browser DevTools — network, console, device emulation
  • Postman or curl for calling the API directly
  • Read-only psql against the staging PostgreSQL database
  • Socket.io event inspection for the live room-status board
  • The issue tracker and the release checklist the team actually uses
  • Git and conventional commits, for the fixes you ship after the gate

What you leave with

What you will learn that college does not teach

  • How to test a state machine properly instead of clicking around — enumerate the states, enumerate the transitions, then attack the ones nobody drew.
  • How to check a system against itself: does the folio total agree with the sum of its postings, does the night audit agree with the day.
  • The difference between a functional failure (the folio does not balance) and a non-functional one (the room board takes eight seconds to load at check-out time).
  • How to write a defect report that gets fixed instead of being sent back for more detail.
  • How to read a codebase in order to test it better — where the risk concentrates, and which change touched what.

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 or any link to work you have done, and the two written answers below. The answers decide most of it.
  2. A 20-minute screening call, mostly you talking us through how you would test something ordinary.
  3. A practical exercise: we hand you a small booking screen and ask for ten test cases, ordered by what you would run first and why.
  4. A conversation with the engineer who owns Hotels 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 Quality Engineering Intern position on Flocci Hotels Suite

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

Elsewhere in the cohort

Other open roles

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

Quality Engineering Intern

Flocci Hotels Suite · closes 30 September 2026