Kuku FM AI Generalist Interview Questions & Rounds
Kuku FM AI Generalist interview guide: the assignment round, how work is evaluated and preparation advice from real 2026 campus experiences.
On this page
[Draft] How to Crack Kuku FM: The AI Generalist Interview, From Real Experiences
Last reviewed November 20, 2026 · 14 min read · For candidates targeting AI Generalist and AI Engineer campus roles in India
Researched and written by the Codinzhub Editorial Team from six external sources: five 2026 campus process notes and one public assignment repository. Kuku FM has no internal candidate records in our dataset. Every prompt below comes from a sourced report; nothing was invented to fill a round.
Why this is a draft. All five campus reports describe a take-home assignment instead of an online assessment. None reports a technical interview question, an HR question, an outcome or recruiter feedback. One drive's shortlist was not even out when it was reported. This guide documents the assignment stage in detail and labels every later stage as unreported.
The 30-second version: Kuku FM's 2026 AI Generalist and AI Engineer campus drives at four IITs replaced the OA with a take-home assignment. Deadlines ranged from 48 hours to 3 days, and AI tools were explicitly allowed. The one fully public assignment, "Find the Promos", asks for an auditable system that ranks 20-60 second promotional clips from timestamped microdrama screenplays using a two-stage pipeline: heuristic screening, then bounded LLM scoring. Other drives mention AI agents, an LLM model for an episode script, and a generic AI-assisted assignment. No interview questions were reported.
Important things to know before you start
There was no OA in the reported drives. All four IIT campus notes say a take-home assignment was given instead. Do not prepare for a standard coding test on the basis of this evidence.
AI tools are part of the task, not a shortcut. The Gandhinagar note says assignments are "to be done using AI". The public assignment solution disclosed ChatGPT, Groq GPT-OSS-20B, Python and Streamlit, and kept raw model responses for audit.
The assignment is judged as a system, not a single model call. The public task requires parsing, candidate generation, heuristic screening, bounded LLM scoring, validation, deduplication, ranked exports and a human review queue.
Deadlines are short. Reported windows were 48 hours and 2 to 3 days. Plan a minimal working pipeline first and document what you did not implement.
Editorial quality is not guaranteed by clean code. The public run had zero structural validation failures, yet its own review classified the 20 recommendations as 7 promising, 10 needing review and 3 weak.
What this guide is, and what it is not
This guide covers AI Generalist and AI Engineer campus hiring at Kuku FM, India, in 2026. It is a draft because the evidence covers only the assignment stage. It is not a guide to Kuku FM software engineering, management trainee, growth intern or QA hiring; Glassdoor and AmbitionBox report questions for those roles, but the pages are login-walled or role-mixed and none was AI Generalist specific.
Scope: Five first-hand campus notes from IIT BHU, IIT Gandhinagar, IIT Hyderabad and IIT Guwahati, plus one public assignment repository. Job descriptions were checked only for role context, not as candidate experience.
Selected vs. rejected: do this, not that
No outcomes were reported, so this table is editorial advice drawn from the assignment's own requirements and limitations.
| Do this | Not that | Why it matters |
|---|---|---|
| Ship a working end-to-end pipeline first. | Perfect one component and leave no output. | The assignment asks for parsing through ranked recommendations. |
| Use AI tools openly and document them. | Hide LLM use or fabricate evaluation evidence. | The public solution includes an AI-tools disclosure and audit trail. |
| Keep raw model responses and scores. | Report only final numbers. | Auditable output is part of the stated deliverable. |
| Validate duration, timestamps, overlap and duplicates. | Trust the model to respect constraints. | The public system separates deterministic validation from semantic scoring. |
| State limitations and leave room for human review. | Claim fully automated editorial decisions. | The assignment explicitly keeps final publishing decisions with editors. |
Round-by-round breakdown
Stage 1: Application
Four campus drives are attested, all in November 2026: IIT Guwahati on 6 November, IIT Hyderabad on 7 November, IIT Gandhinagar on 12 November and IIT BHU on 13 November. The BHU note says shortlisting is based on the assignment and resume.
Stage 2: Shortlisting
The assignment itself is the shortlisting filter. One Gandhinagar report says the interview shortlist was not yet out at the time of writing. No recruiter screen, eligibility call or assessment-format briefing was reported.
Stage 3: Assignment stage
How it works. No online assessment was reported. Candidates received a take-home task with a deadline of 48 hours to 3 days. AI use was permitted in at least two drives. The only fully described task is "Find the Promos".
At a glance: one assignment per drive; 48 hours to 3 days; take-home format with AI tools allowed. Topics: LLM systems, prompt engineering, AI agents, screenplay parsing, ranking and validation.
| Reported prompt | What it requires | Deadline | Scope | Source type |
|---|---|---|---|---|
| Find the Promos: rank 20-60 second clips from timestamped screenplays. | Parse scenes and dialogue, generate clips, score hook, cliffhanger, clarity and impact, validate timestamps, deduplicate and rank for editorial review. | 2 days in the public run | AI Generalist assignment | Public assignment repository |
| Build an LLM-based model for an episode script. | Given the script of an episode, build an LLM-based model for it. | 2 days | IIT Guwahati FTE | Campus note |
| Complete an assignment related to AI Agents. | Build something involving AI agents; exact statement not shared. | Not reported | IIT BHU AI Engineer | Campus note |
| Complete an AI-assisted assignment. | Assignment to be done using AI. | 2-3 days | IIT Gandhinagar AI Generalist | Campus note |
| Submit the assignment within 48 hours. | Exact content not shared. | 48 hours | IIT Hyderabad AI Engineer | Campus note |
The fully public assignment, in detail
The "Find the Promos" repository describes a two-stage design. A parser reads timestamped microdrama screenplays with scenes, dialogue, action and camera blocks. Candidate generation produces continuous 20-60 second clips on natural screenplay boundaries. An inexpensive, deterministic heuristic scorer screens all candidates. A bounded, diverse shortlist is then evaluated by an LLM, which produces structured scores, explanations and content warnings. Python handles duration, timestamp and overlap validation, suppresses near-duplicates and limits each episode to two selected promos.
The scoring weights are explicit: opening hook 30%, ending cliffhanger 30%, standalone clarity 25% and dramatic impact 15%, each scored 0 to 10. The weighted total is 3 × Hook + 3 × Cliffhanger + 2.5 × Clarity + 1.5 × Impact. The reported 50-episode run processed 50 episodes, scored 600 candidates heuristically, evaluated 30 with the LLM, and returned 20 ranked recommendations across 17 episodes with no structural failures.
The public deliverables include a Streamlit app, CLI, tests, architecture notes, raw candidate records, ranked JSON and CSV exports, a quality report and a manual-audit queue. Confidential screenplays and model responses were kept out of the public repository and submitted through an authorized channel.
Stage 4: Technical interview
Not reported. No first-hand account describes what happens after the assignment. The Gandhinagar note says the shortlist was pending. Do not assume a LeetCode-style round from other companies.
Stage 5: HR round
Not reported. No behavioural question, duration or interviewer behaviour was found for this role.
Stage 6: Decision
No offer, rejection, feedback, compensation or timeline was reported for AI Generalist or AI Engineer drives. The only timeline anchors are the assignment deadlines themselves.
Candidate experiences reviewed
| Background | Role and reported outcome | What was reported |
|---|---|---|
| IIT Guwahati - Nov 2026 | FTE, round not named - outcome not reported | Build an LLM-based model for an episode script in 2 days |
| IIT Hyderabad - Nov 2026 | AI Engineer FTE - outcome not reported | Assignment with a 48-hour submission window |
| IIT Gandhinagar - Nov 2026 | AI Generalist FTE - shortlist pending | AI-assisted assignment, 2-3 day deadline, no OA |
| IIT BHU - Nov 2026 | AI Engineer FTE - outcome not reported | AI Agents assignment; shortlist based on assignment and resume |
| Public assignment repository | AI Generalist - not a candidate outcome | Find the Promos task, full architecture and 50-episode evaluation |
Assignment playbook
This is editorial advice based on the public assignment requirements, not a claim about a scoring rubric.
- Build the pipeline in order: parse, generate candidates, screen heuristically, shortlist, score with an LLM, validate, deduplicate, rank, export.
- Implement deterministic validation before semantic scoring. Duration, timestamp and overlap checks are cheap and make the output auditable.
- Use a bounded LLM shortlist. The public run evaluated 30 of 600 candidates, not all 600.
- Write an output contract with scores, explanations, rationale and content warnings.
- Keep an audit trail: raw candidates, raw model responses, run configuration and a manual review queue.
- Disclose AI tools and explain which decisions were made by code, which by the model and which by a human.
- State limitations honestly and finish within the 48-hour to 3-day window.
How this role differs from a standard SWE role
| Aspect | What the evidence shows | What it does not show |
|---|---|---|
| Screening | Take-home AI assignment, not an OA | Any timed coding platform |
| Core work | LLM pipelines, agents, prompt engineering, ranking and validation | Data structures and algorithms rounds |
| Tool use | AI tools explicitly allowed | Any prohibition or proctoring rule |
| Evaluation | Assignment and resume shortlisting | Interview or HR criteria |
| Outcomes | None reported | Offers, rejections or compensation |
Job postings for Kuku FM AI Engineer roles mention prompt pipelines, generative model integration, LLM APIs, LangChain, LangGraph, Python, RAG and prompt engineering for content production at scale. This is role context from job descriptions, not evidence of interview questions.
Most-asked topics
Frequency cannot be computed from five assignment prompts. The table lists what was explicitly named.
| Topic | Where it appeared | Evidence |
|---|---|---|
| LLM systems and pipelines | Find the Promos; episode-script model; AI-assisted assignment | Reported in three prompts |
| Prompt engineering and structured scoring | Find the Promos; AI-assisted assignment | Reported in two prompts |
| AI agents | IIT BHU assignment | Reported once |
| Screenplay parsing and clip ranking | Find the Promos | Reported once |
| Validation, deduplication and audit | Find the Promos | Reported once |
The patterns that keep coming back
1. Assignment replaces OA
- Recognise it: a drive note saying "no OA" and an assignment deadline.
- Action: treat the assignment as the primary filter and start immediately.
2. Build a system, not a demo
- Recognise it: requirements for parsing, validation, exports and audit trails.
- Action: ship an end-to-end run with documented limitations rather than a perfect single component.
3. Human-in-the-loop output
- Recognise it: "for editorial review" or "final decisions remain with editors".
- Action: include a review queue and explain where human judgement overrides the model.
How to handle an unfamiliar assignment prompt
- Restate the deliverable in one sentence and list every required input and output.
- Identify deterministic constraints such as time windows, counts and validation rules.
- Choose the smallest architecture that satisfies the contract end to end.
- Use AI tools deliberately and record what they produced.
- Create a small synthetic test set instead of waiting for confidential data.
- Finish early enough to write limitations and an audit note.
Why candidates were rejected
No rejection reasons were reported. Any explanation would be invented, so none is offered.
If you remember only five things
- This is a draft based only on the assignment stage.
- Expect a take-home AI assignment, not an OA.
- Deadlines are 48 hours to 3 days.
- Build an auditable system with validation and a human review queue.
- Disclose AI tools and state limitations honestly.
Frequently asked questions (FAQ)
Is this a complete interview guide?
No. It is marked [Draft] because no technical interview, HR or outcome questions were found. Only the assignment stage is evidenced.
Does Kuku FM use an OA for AI Generalist?
None of the five 2026 campus reports mentions one. All describe a take-home assignment instead.
Are AI tools allowed in the assignment?
Yes in the reported drives. The Gandhinagar note explicitly says assignments are to be done using AI, and the public solution discloses ChatGPT and Groq GPT-OSS-20B.
What is "Find the Promos"?
A public AI Generalist assignment asking for a system that ranks 20-60 second promotional clips from timestamped microdrama screenplays using heuristic screening and bounded LLM scoring.
Where did the five prompts come from?
Four are campus process notes from a public placement tracker; one is the public assignment repository. No internal Codinzhub records exist for Kuku FM.
Are there practice links?
No. No specific LeetCode, GeeksforGeeks or InterviewBit problem was verified as a match for an assignment prompt, so none is listed.
About this guide and methodology
This guide was compiled by the Codinzhub Editorial Team from six external sources: five 2026 campus process notes and one public assignment repository. Glassdoor, AmbitionBox, Indeed and generic prep sites were checked but excluded because their content was login-walled, role-mixed or unattributed. No external research URLs, internal record identifiers or private ledgers appear in this article.
Disclaimer: This reflects early and incomplete reporting from one hiring season. It is not an official statement from Kuku FM. Confirm the current process with your recruiter.
Other company and role guides
Search the question bank
The questions from each round above, with practice links for similar problems. Log in to search every question we collected for this role, including questions shared on Codinzhub.
Showing 15 of 15 questions
Find the Promos: rank 20-60 second clips from timestamped screenplays.
Level: 2 days in the public run.
Build an LLM-based model for an episode script.
Level: 2 days.
Complete an assignment related to AI Agents.
Level: Not reported.
Complete an AI-assisted assignment.
Level: 2-3 days.
Submit the assignment within 48 hours.
Level: 48 hours.
LLM systems and pipelines
Level: Reported in three prompts.
Prompt engineering and structured scoring
Level: Reported in two prompts.
AI agents
Level: Reported once.
Screenplay parsing and clip ranking
Level: Reported once.
Validation, deduplication and audit
Level: Reported once.
1
Level: LLM systems, Prompt engineering, System design.
2
Level: LLM systems.
3
Level: AI agents.
4
Level: LLM systems, Prompt engineering.
5
Level: LLM systems.
Keep preparing on Codinzhub
- Browse Kuku FM online assessment questions — filter the Codinzhub question bank by company.
- Amazon Data Scientist interview guide — the Amazon process, rounds and question patterns.
- Google Data Scientist interview guide — the Google process, rounds and question patterns.
- Flipkart AI Engineer interview guide — the Flipkart process, rounds and question patterns.
- All company interview guides — every guide on the Codinzhub blog.
Keep track of what you’ve learned.