Krutrim (Ola Krutrim) is India's first AI unicorn, founded by Ola's Bhavish Aggarwal to build a full-stack AI company for India: from silicon (AI chips) up through foundation models, an AI cloud, and consumer and developer products. Krutrim builds multilingual large language models for Indian languages, GPU cloud infrastructure, and has publicly announced ambitions in AI silicon. For ML engineers, systems and infrastructure engineers, and researchers, Krutrim is one of the most ambitious, fastest-moving AI companies in India, spanning a wider stack than most pure-model startups. This guide covers the interview process, what Krutrim looks for, and how to prepare.
The Krutrim hiring process: what to expect
The Krutrim interview process typically runs across 4–5 rounds over 2–3 weeks. Because Krutrim spans models, cloud infrastructure, and silicon, the exact rounds vary more by team than at a single-focus startup:
1. Resume and portfolio screen: Krutrim's recruiting team shortlists on relevant depth for the specific team: ML/NLP for the foundation-model group, distributed systems and GPU infrastructure for the AI cloud group, and low-level systems or hardware for the silicon group. A GitHub profile with real projects (fine-tuning an LLM, building an inference server, contributing to an ML framework, systems work) meaningfully increases shortlist probability. Prior startup or high-scale infrastructure experience is a plus given how fast Krutrim moves.
2. Technical phone screen (45–60 min): A call with an engineer covering fundamentals for your role. For ML/research roles: transformer architecture, attention, training and fine-tuning LLMs, tokenisation for Indic languages. For AI-cloud/platform roles: coding (Python, Go, or C++), systems design basics, distributed systems and networking fundamentals. For infra roles specifically, expect questions on GPU scheduling, containers, and orchestration.
3. Core technical round (60–90 min): The deepest technical interview. For ML/research: transformer internals, fine-tuning strategies for low-resource Indian languages, data curation for multilingual pretraining, evaluation of LLMs, inference optimisation (quantisation, KV-cache, batching). For AI-cloud/infra: design and operation of large GPU clusters, distributed training (data/tensor/pipeline parallelism), high-throughput low-latency inference serving, storage and networking for ML workloads. For silicon/systems roles: computer architecture, memory hierarchies, and hardware-software co-design fundamentals.
4. Systems design round: A scenario-based design interview. Examples: design a multi-tenant GPU cloud that serves LLM inference to thousands of developers with predictable latency; design the training data pipeline for a multilingual model covering 10+ Indian languages; or design an inference-serving layer that autoscales across heterogeneous GPUs. Focus on scalability, cost efficiency (GPU utilisation is expensive), reliability, and latency.
5. Founder or leadership conversation: A conversation with a founder or department head. Topics: why Krutrim specifically (the full-stack, India-first AI thesis), what draws you to building AI infrastructure for India, your biggest technical achievement and what you learned, and how you operate in a fast-scaling, ambiguous environment. This round weighs mission alignment and ownership as much as technical depth.
What Krutrim interviewers look for
Based on what is known about Krutrim's engineering culture and its full-stack ambitions, these qualities tend to stand out:
1. Comfort with an unusually broad stack: Unlike a pure-model or pure-app startup, Krutrim spans silicon, models, cloud, and products. Even if you interview for one team, showing that you understand how the layers connect (why model architecture choices affect inference cost, why GPU cloud economics shape what models are viable) signals the systems thinking Krutrim values.
2. Depth in your core area: Krutrim works on genuinely hard problems in each layer. Interviewers prefer clear depth in one domain (LLM training, inference systems, distributed infrastructure, or hardware) over shallow familiarity with all of them. Be ready to go very deep on your strongest area.
3. First-principles and cost-aware thinking: GPU compute is the dominant cost in AI infrastructure. Expect questions that probe whether you reason about efficiency: 'How would you improve GPU utilisation during training?' 'Why does batching improve inference throughput, and what breaks it?' 'What determines the cost per million tokens served?'
4. Bias toward building and ownership: Krutrim scales aggressively and values engineers who ship real systems under constraints and take end-to-end ownership. Demonstrating that your work reached production (a deployed service, a shipped model, an open-source release) carries more weight than experiments that never left a notebook.
How to prepare for a Krutrim interview
Targeted preparation for Krutrim roles across the model, cloud, and systems tracks:
1. Understand transformer and LLM fundamentals deeply: Be able to explain multi-head self-attention (Q, K, V, scaled dot-product attention, why multiple heads), positional encodings, pre-LN vs post-LN blocks, and the mechanics of pretraining vs fine-tuning vs instruction-tuning. Understand tokenisation for Indic languages: subword (BPE/unigram) tokenisation, why morphologically rich languages like Tamil and Hindi behave differently from English, and Unicode normalisation for Indic scripts.
2. Study LLM inference and training systems: For inference: KV-cache, batching and continuous batching, quantisation (INT8/FP8), speculative decoding, and how these trade off latency, throughput, and cost. For training: data, tensor, and pipeline parallelism; mixed-precision training; checkpointing; and what limits scaling across many GPUs (communication overhead, memory).
3. Study GPU cloud and distributed-systems design: Understand GPU cluster orchestration (Kubernetes, scheduling, bin-packing GPUs), high-performance networking (InfiniBand/RDMA at a conceptual level), storage for large datasets and checkpoints, and multi-tenant isolation. Be ready to design a service that serves model inference at scale with predictable latency and high GPU utilisation.
4. Practise system design for AI products: Practise designing: (a) an LLM inference API serving multiple Indian languages with strict latency SLAs, (b) a multilingual training-data collection and curation pipeline, (c) a cost-efficient autoscaling GPU serving layer. Always discuss cost and GPU utilisation explicitly: it is central to AI-infrastructure roles.
5. Prepare your 'why Krutrim' story: Be ready to answer why Krutrim specifically over a FAANG AI role or another startup. Have a genuine answer that connects to the full-stack, India-first AI mission (building foundation models, cloud, and eventually silicon for India) rather than only equity or growth. Krutrim looks for people aligned with that ambition.
Frequently asked questions
Explore more
