Interview preparation · Updated
AI Foundations Path interview questions and answers
38 questions AI Foundations Path candidates are asked in 2026, in the order a real interview usually goes, each with an easy answer you can study and say out loud. Then 21 quick quiz questions to test yourself. For a scored session with your gaps explained, use interview practice.
How an AI Foundations Path interview usually goes
- HR or recruiter screen (15 to 30 min): background, why AI, notice period
- Online test: aptitude, Python basics, a few SQL and ML MCQs
- Technical interview: ML concepts in plain words, Python and SQL questions, a deep walk through of your project
- Managerial or HR round: attitude, learning ability, salary
Based on 2026 candidate reports. Companies vary, so use this as a map.
👋 Opening: about you
Almost every interview starts here. These answers set the tone, so prepare them word for word and practise them out loud.
-
1Tell me about yourself.
💬 Easy answer
Use present, past, future, in about 60 to 90 seconds. Present: "I'm a Java backend developer with four years at a fintech company, where I build payment APIs." Past: "Over the last year I moved towards AI. I built a document question answering app with RAG and an evaluation set, and I used an LLM to classify support tickets at work, which cut manual triage by about 30%." Future: "Now I want to do this full time as an AI engineer, and this role fits because you build LLM features on top of real backend systems, which is exactly where my strengths meet."
✅ A strong answer covers
- Present: current role and one concrete thing you do
- Past: the 1 or 2 experiences that lead to this role, with a number
- Future: why this role and this company is the logical next step
- Keep it under 2 minutes; don't recite your whole resume
What they're really checking: Can you tell a clear, relevant story about yourself? It's also a test of communication: structure and confidence matter more than detail.
📖 Learn it: Landing the AI role: resume, applications and interviews
-
2Why do you want to move into AI, and why this particular role?
💬 Easy answer
Give a real reason and connect it to evidence. "In my testing work I kept seeing the same problem: thousands of test cases written and checked by hand. When I tried an LLM to draft test cases, it saved hours, but it also made mistakes I had to catch. That got me interested in building AI systems that are actually reliable. I've since completed projects in RAG and evaluation. I'm applying for this role because it focuses on shipping AI features to users, and my background in quality and testing directly helps with evaluating AI output."
✅ A strong answer covers
- A specific moment or problem that sparked the interest (not "AI is the future")
- Proof you've acted on it: courses finished, projects built
- How your previous experience transfers to this role
- Why this role, not just AI in general
What they're really checking: Is your interest genuine and backed by action? Interviewers worry about people chasing hype who will lose interest.
📖 Learn it: Landing the AI role: resume, applications and interviews · Building a portfolio project that gets interviews
-
3Why do you want to work here?
💬 Easy answer
Show you've done homework. Mention one thing about their product, one thing about how they work, and link both to you. "I've used your app for expense reports, and I noticed the receipt scanning recently got much better, so I read your engineering blog about it. I like that your team publishes how you evaluate models, because I care about measuring AI quality. And since you serve small businesses in India, my experience building for that market would help from day one."
✅ A strong answer covers
- Something specific about their product or users
- Something about their team, values or engineering approach
- Why you fit: a direct link to your skills
- Avoid answers that fit any company ("great culture", "big brand")
What they're really checking: Have you researched the company, and are you likely to stay?
📖 Learn it: Landing the AI role: resume, applications and interviews
-
4You haven't had an AI job title yet. Why should we hire you over someone who has?
💬 Easy answer
Don't be defensive. Turn the gap into a strength. "That's fair. What I bring is production experience: I've spent five years shipping and supporting real systems, handling incidents and working with stakeholders. Many AI projects fail at exactly that stage, after the demo. On the AI side, I've built two end to end projects with evaluation, which I can show you. So you'd get someone who learns fast and already knows how to make software work in production."
✅ A strong answer covers
- Acknowledge it calmly in one sentence
- Name the transferable strengths (production, domain, communication)
- Show evidence of AI skills: projects, results, code
- End with what you'll deliver, not what you lack
What they're really checking: How do you handle a tough question about a weakness? Calm, honest and evidence based beats defensive.
📖 Learn it: Building a portfolio project that gets interviews · Landing the AI role: resume, applications and interviews
🧱 Fundamentals
Short concept questions to check your basics. Answer in 3 to 5 sentences, with one example.
-
5What's the difference between AI, machine learning, deep learning and generative AI?
💬 Easy answer
They are circles inside each other. AI is the broad goal of making computers do things that seem intelligent. Machine learning is one way to do that: instead of writing rules, we let the computer learn patterns from examples. Deep learning is machine learning with many layered neural networks, which works well for images, audio and text. Generative AI uses deep learning models, like LLMs, to create new content such as text, images or code, instead of only predicting a label.
✅ A strong answer covers
- AI ⊃ ML ⊃ deep learning; GenAI is an application of deep learning
- ML learns from data instead of hand written rules
- One example for each (spam filter, image recogniser, ChatGPT)
What they're really checking: Can you explain basics clearly without jargon? This is often the very first technical question for freshers and PMs.
📖 Learn it: What is AI? AI vs ML vs Deep Learning vs GenAI
-
6Explain supervised, unsupervised and reinforcement learning, with an example of each.
💬 Easy answer
Supervised learning learns from examples that have the right answer, called labels. For example, emails marked spam or not spam, so the model learns to predict spam. Unsupervised learning has no labels; it finds structure by itself, like grouping customers into segments by behaviour. Reinforcement learning learns by trial and error with rewards, like a game playing agent or a robot that gets a reward when it does the task well. LLMs also use reinforcement learning from human feedback to make answers more helpful.
✅ A strong answer covers
- Supervised = labelled data, predicts a known target
- Unsupervised = no labels, finds groups or patterns
- Reinforcement = actions, rewards, learning by trial and error
- A real example for each
What they're really checking: Basic vocabulary and whether you can give examples on the spot.
📖 Learn it: How machines learn: features, labels and training · Two kinds of prediction: regression and classification
-
7What is overfitting, and how do you prevent it?
💬 Easy answer
Overfitting is when a model memorises the training data, including its noise, so it scores very well on training data but badly on new data. It's like a student who memorises last year's answers but can't solve a new question. You spot it when training accuracy is high and validation accuracy is much lower. To prevent it: get more data, use a simpler model, add regularisation, use cross validation, stop training early, and for neural networks use dropout.
✅ A strong answer covers
- Definition: good on training data, poor on unseen data
- How to detect: compare train vs validation scores
- At least three fixes: more data, simpler model, regularisation, early stopping, dropout
- Mention underfitting as the opposite
What they're really checking: The single most asked ML concept. They want the detection method, not only the definition.
📖 Learn it: Train/test split and overfitting
-
8What is the bias variance trade off?
💬 Easy answer
Bias is error from a model that's too simple, so it misses real patterns. That's underfitting. Variance is error from a model that's too sensitive to the training data, so small changes in the data change it a lot. That's overfitting. Making a model more complex usually lowers bias but raises variance. The goal is the sweet spot where total error on new data is lowest, which we find using validation data. For example, a straight line through curved data has high bias; a very deep decision tree has high variance.
✅ A strong answer covers
- Bias = too simple, underfits
- Variance = too sensitive, overfits
- Complexity trades one for the other; pick by validation error
- An example of each
What they're really checking: Whether you understand why models fail, not just how to train them.
📖 Learn it: Train/test split and overfitting
-
9Why do we split data into training, validation and test sets?
💬 Easy answer
The training set is what the model learns from. The validation set is used while building, to compare models and tune settings like depth or learning rate. The test set is kept locked away until the very end to get an honest estimate of how the model will do on new data. If you tune on the test set, you slowly overfit to it and your final number becomes too optimistic. For time based data, split by time, so you train on the past and test on the future.
✅ A strong answer covers
- Train = learn, validation = choose and tune, test = final honest check
- Never tune on the test set
- Split by time for time series; split by user or group to avoid leakage
What they're really checking: Experiment discipline. Many candidates forget the role of the validation set.
📖 Learn it: Train/test split and overfitting
-
10Explain precision and recall. When would you prefer one over the other?
💬 Easy answer
Precision: of everything the model flagged as positive, how many were really positive. Recall: of all the real positives, how many the model caught. For a cancer screening test or fraud detection, missing a real case is very costly, so we prefer high recall, even if we get some false alarms. For a spam filter, putting a real email into spam is annoying, so we prefer high precision. F1 score combines both when you need one number, and you can move between them by changing the decision threshold.
✅ A strong answer covers
- Precision = correctness of positive predictions
- Recall = coverage of actual positives
- Choose based on which mistake costs more, with an example
- Threshold controls the trade off; F1 balances them
What they're really checking: Whether you can connect a metric to a business cost.
📖 Learn it: Measuring models: accuracy, precision and recall
-
11Your model is 99% accurate, but the business says it's useless. How is that possible?
💬 Easy answer
Probably the classes are imbalanced. If only 1% of transactions are fraud, a model that always says "not fraud" is 99% accurate and catches zero fraud. Accuracy hides that. I'd look at the confusion matrix, precision and recall for the rare class, and metrics like PR AUC. Then I'd check the business goal: maybe they need to catch 80% of fraud while keeping false alarms low enough for the review team to handle, and I'd tune the threshold for that.
✅ A strong answer covers
- Class imbalance makes accuracy misleading
- Use confusion matrix, precision, recall, PR AUC
- Tie the metric to the business goal and capacity
- Fixes: threshold tuning, class weights, resampling
What they're really checking: Can you think beyond the headline number? Very common in 2026 interviews.
📖 Learn it: Measuring models: accuracy, precision and recall
-
12What is regularisation? What's the difference between L1 and L2?
💬 Easy answer
Regularisation adds a penalty for large weights to the loss, which keeps the model simpler and reduces overfitting. L2, also called ridge, penalises the square of weights, so it shrinks all weights smoothly towards zero but rarely to exactly zero. L1, also called lasso, penalises the absolute value, which pushes some weights to exactly zero, so it also does feature selection. In neural networks we also use dropout and weight decay, which is L2 in practice.
✅ A strong answer covers
- Penalty on weight size added to the loss
- L2 shrinks smoothly; L1 makes some weights exactly zero
- Strength is a hyperparameter tuned on validation data
What they're really checking: Standard ML theory; they may follow up with why L1 creates zeros.
📖 Learn it: Train/test split and overfitting · Gradients and gradient descent: how models improve
-
13What's the difference between a random forest and gradient boosting?
💬 Easy answer
Both combine many decision trees. A random forest trains lots of deep trees independently on random samples of rows and features, then averages their votes. That reduces variance and is hard to break. Gradient boosting trains small trees one after another, where each new tree fixes the errors of the ones before it. Boosting, like XGBoost or LightGBM, usually gives the best accuracy on tabular data but needs more careful tuning and can overfit if you add too many trees.
✅ A strong answer covers
- Forest = parallel trees, averaged, reduces variance
- Boosting = sequential trees correcting errors, reduces bias
- Boosting is often the strongest for tables; forests are robust defaults
What they're really checking: Practical model knowledge for tabular data, which is still most industry ML.
📖 Learn it: Decision trees, random forests and boosting
-
14Explain gradient descent in simple words. What does the learning rate do?
💬 Easy answer
Imagine you're on a hill in fog and want to reach the bottom. You feel which way the ground slopes and take a step downhill, again and again. Gradient descent does the same with the model's error: the gradient tells us which direction increases the error, so we move the weights a small step in the opposite direction. The learning rate is the step size. Too big and you overshoot and bounce around; too small and training is very slow. In practice we use mini batches and optimisers like Adam.
✅ A strong answer covers
- Loss = how wrong the model is; gradient = direction of steepest increase
- Update weights opposite to the gradient
- Learning rate = step size, with the risk of too big or too small
- Mention mini batch SGD or Adam
What they're really checking: Do you understand how models actually learn?
📖 Learn it: Gradients and gradient descent: how models improve
-
15How does an LLM generate text?
💬 Easy answer
An LLM is a neural network, a transformer, trained on huge amounts of text to predict the next token, which is a word or piece of a word. When you send a prompt, it's split into tokens, the model calculates probabilities for every possible next token, picks one, adds it to the text, and repeats until it's done. Settings like temperature control how random that choice is. Because it predicts plausible text rather than looking up facts, it can confidently produce wrong answers, which we call hallucinations.
✅ A strong answer covers
- Trained to predict the next token
- Generates one token at a time in a loop
- Temperature controls randomness
- Explains why hallucinations happen
What they're really checking: Basic GenAI literacy, asked for nearly every role now.
📖 Learn it: What is an LLM? Tokens, context and temperature
-
16What do temperature and top p control? What would you use for a data extraction task?
💬 Easy answer
Both control randomness when choosing the next token. Temperature reshapes the probabilities: low temperature makes the model pick the most likely tokens, so it's more consistent; high temperature makes it more creative and varied. Top p limits choices to the smallest set of tokens whose probabilities add up to p. For extraction or classification I'd use temperature 0 or close to it, plus a fixed output format, because I want the same input to give the same, correct output. For brainstorming I'd raise it.
✅ A strong answer covers
- Both control randomness of token choice
- Low = consistent, high = creative
- Extraction: temperature near 0 and structured output
What they're really checking: Practical prompting judgement.
📖 Learn it: What is an LLM? Tokens, context and temperature · Prompting: giving clear instructions to an LLM
-
17What's the difference between a list, tuple, set and dictionary in Python? When would you use each?
💬 Easy answer
A list is an ordered, changeable collection; good for sequences you add to, like rows to process. A tuple is ordered but can't be changed; good for fixed records like coordinates, and it can be a dictionary key. A set holds unique items with very fast membership checks; good for removing duplicates or checking "have I seen this ID?". A dictionary maps keys to values with fast lookup; good for things like user ID to user details. Checking membership in a set or dict is O(1) on average, but O(n) in a list.
✅ A strong answer covers
- List: ordered, mutable
- Tuple: ordered, immutable, hashable
- Set: unique, fast membership
- Dict: key to value, fast lookup; mention O(1) vs O(n)
What they're really checking: Python fluency, plus whether you think about performance.
📖 Learn it: Lists and dictionaries: storing many values
-
18Explain INNER JOIN vs LEFT JOIN with an example.
💬 Easy answer
An INNER JOIN returns only rows that match in both tables. A LEFT JOIN returns every row from the left table, plus matches from the right; where there's no match, the right side columns are NULL. Example: customers and orders. An inner join gives only customers who have ordered. A left join from customers gives all customers, and those with NULL order IDs are the ones who never ordered, which is a common way to find inactive customers.
✅ A strong answer covers
- Inner = only matching rows
- Left = all left rows, NULLs where no match
- Use a left join plus IS NULL to find missing matches
- Watch for duplicate rows when the join key isn't unique
What they're really checking: The most common SQL basic. A mention of the duplicate row trap stands out.
📖 Learn it: SQL JOINs: combining tables
-
19What are window functions? Explain ROW_NUMBER, RANK and DENSE_RANK.
💬 Easy answer
Window functions calculate something across related rows without collapsing them like GROUP BY does. For example, a running total or each employee's salary rank within their department, using OVER (PARTITION BY department ORDER BY salary DESC). With ties: ROW_NUMBER gives unique numbers 1, 2, 3 even for ties, so add a tie breaker column to make it deterministic. RANK gives ties the same number and then skips, like 1, 1, 3. DENSE_RANK gives ties the same number without gaps, like 1, 1, 2. LAG and LEAD let you compare a row with the previous or next one.
✅ A strong answer covers
- Compute over a window of rows, keeping every row
- PARTITION BY groups, ORDER BY sets order
- ROW_NUMBER vs RANK vs DENSE_RANK on ties
- Uses: top N per group, running totals, LAG and LEAD for changes
What they're really checking: Window functions are the core of most data SQL rounds in 2026.
📖 Learn it: SQL basics: asking a database questions · SQL JOINs: combining tables
-
20Write a query to get the top 3 products by revenue in each category.
💬 Easy answer
I'd rank products within each category and then filter. First, in a subquery or CTE, compute revenue per product and add DENSE_RANK() OVER (PARTITION BY category ORDER BY revenue DESC) AS rnk. Then select rows WHERE rnk <= 3. I'd say out loud how I handle ties: DENSE_RANK keeps all tied products, which could return more than 3 rows; if they want exactly 3, I'd use ROW_NUMBER with a tie breaker like product ID.
✅ A strong answer covers
- CTE to aggregate revenue per product
- Window rank partitioned by category
- Filter rank ≤ 3 in the outer query (you can't filter a window function in WHERE directly)
- State how ties are handled
What they're really checking: A classic SQL task. Explaining tie handling shows maturity.
📖 Learn it: SQL basics: asking a database questions
-
21What's the difference between correlation and causation? How would you prove causation?
💬 Easy answer
Correlation means two things move together; causation means one actually causes the other. Ice cream sales and drownings are correlated because both rise in summer, not because ice cream causes drowning. In products, users who use a new feature might retain better simply because they were already more engaged. To show causation, the best tool is a randomised A/B test: randomly give the feature to half the users, so the only systematic difference is the feature, then compare outcomes.
✅ A strong answer covers
- Correlation ≠ causation; hidden third factors (confounders)
- Selection bias: who opts in is different
- Randomised experiment is the gold standard
What they're really checking: Statistical thinking for decisions; critical for PMs and analysts.
📖 Learn it: Correlation vs causation, and sampling bias · Metrics and A/B testing for AI features
🛠️ Role skills
The technical heart of the interview for this role. Interviewers go deeper with follow up questions, so understand the why, not just the definition.
-
22How do you approach feature engineering for a new problem?
💬 Easy answer
I start from the domain: what would a human expert look at to make this decision? For predicting late loan payments, that's things like income to EMI ratio, past late payments and recent changes in spending. Then I clean and encode: handle missing values, one hot encode categories, scale numbers if the model needs it, and create time based features like "days since last purchase". I check every feature for leakage and measure value with validation scores and feature importance. Usually a few good domain features beat many random ones.
✅ A strong answer covers
- Start with domain knowledge and the decision being made
- Clean, encode, scale, create ratios and time features
- Check each feature for leakage
- Validate importance with experiments
What they're really checking: Practical modelling sense. Domain driven features impress more than tool lists.
📖 Learn it: Feature engineering: turning raw data into useful inputs
-
23How do you handle an imbalanced dataset, like 1% fraud?
💬 Easy answer
First, choose the right metric: precision, recall, PR AUC, not accuracy. Then options: use class weights so mistakes on the rare class cost more; resample, either undersample the majority or oversample the minority (SMOTE), only on the training data; and tune the decision threshold to hit the recall or precision the business needs. Also make sure the validation split keeps the same ratio, using a stratified split. Often, getting more examples of the rare class or better features helps most.
✅ A strong answer covers
- Right metric first
- Class weights, resampling (train only), threshold tuning
- Stratified splits
- More data or better features for the rare class
What they're really checking: A follow up to the accuracy question; very common.
📖 Learn it: Measuring models: accuracy, precision and recall
-
24How do you deal with missing values?
💬 Easy answer
First I ask why they're missing, because that changes the fix. If income is missing because people didn't want to share it, the fact that it's missing may itself be a signal. Options: drop rows if very few are missing; fill with the median or most common value; fill using a model or a group average; or add a "was missing" flag column alongside the filled value. Tree models like XGBoost can handle missing values natively. Whatever I do, I fit the filling logic on the training data only.
✅ A strong answer covers
- Understand why it's missing first
- Drop, impute (median, mode, model), or add a missing flag
- Fit imputation on train only to avoid leakage
What they're really checking: Data cleaning judgement, not just a pandas command.
📖 Learn it: Pandas: working with tables of data · Feature engineering: turning raw data into useful inputs · Data quality: catching bad data early
-
25How do you choose which model to use?
💬 Easy answer
I start with a simple baseline, like logistic regression or even a rule, so I know what "good" means. For tabular data, I'd then try gradient boosting because it's usually strongest. For images, text or audio, I'd use pretrained deep learning models or an LLM. Then I consider constraints: latency, cost, how much data I have, and whether the result must be explainable, for example in lending. I pick the simplest model that meets the target on validation data, because it's easier to maintain.
✅ A strong answer covers
- Start with a baseline
- Data type guides the family (tables → boosting; text/images → pretrained deep models)
- Constraints: latency, interpretability, data size, cost
- Simplest model that meets the goal
What they're really checking: Engineering judgement over chasing the fanciest model.
📖 Learn it: Two kinds of prediction: regression and classification · Decision trees, random forests and boosting
-
26What steps do you follow in a machine learning project, from start to finish?
💬 Easy answer
One, understand the problem and the success metric with the people who need it. Two, collect the data and explore it: size, missing values, distributions and obvious errors. Three, clean the data and create features. Four, split into training, validation and test sets. Five, train a simple baseline, then better models, comparing them on validation data. Six, evaluate the final model once on the test set and check its mistakes. Seven, deploy it, for example as an API or a Streamlit app. Eight, monitor it and retrain when data changes.
✅ A strong answer covers
- Problem and metric first
- Data exploration and cleaning
- Baseline, then improvement on validation
- Test once, deploy, monitor
What they're really checking: Do you see the whole life cycle, not just model.fit()?
📖 Learn it: How machines learn: features, labels and training · Train/test split and overfitting · Training vs inference: how ML runs in production
-
27You get a new dataset. How do you explore it?
💬 Easy answer
I start with the shape and column types, then look at the first few rows to understand what each column means. Next, missing values per column, duplicates, and basic statistics like mean, median, minimum and maximum, which reveal impossible values like negative ages. I plot distributions with histograms and count the categories. Then I look at relationships: how each feature relates to the target, and correlations between features. I write down surprises and questions for the data owner, because many problems are understood only by asking.
✅ A strong answer covers
- Shape, types, sample rows
- Missing values, duplicates, summary stats, outliers
- Distributions and relationships with the target
- Note questions for the data owner
What they're really checking: Practical data sense; freshers are often asked to describe this step by step.
📖 Learn it: Pandas: working with tables of data · Averages and spread: mean, median, variance
-
28How did you learn AI, and what are you learning right now?
💬 Easy answer
Be concrete and honest. "I started with Python and statistics, then did a structured machine learning course and built small projects on Kaggle datasets. The biggest jump came from building end to end projects: a loan default model I deployed on Streamlit, and a PDF question answering app with an LLM API. Right now I'm learning how to evaluate LLM apps properly, because my first version gave wrong answers I didn't notice until I built a test set."
✅ A strong answer covers
- A clear learning path
- Projects, not just certificates
- What you're learning now and why
- Honest about what you don't know yet
What they're really checking: Learning ability matters most for freshers.
📖 Learn it: Building a portfolio project that gets interviews · Landing the AI role: resume, applications and interviews
🏗️ Design and case questions
Open questions with no single right answer. Clarify first, then structure your answer, then talk about trade offs, measurement and failure cases.
-
29How would you build a spam email classifier?
💬 Easy answer
Clarify: what counts as spam, and which mistake is worse? Usually marking a real email as spam is worse, so precision matters. Data: emails labelled spam or not. Features: start with text turned into numbers, using TF IDF, plus simple signals like number of links or the sender's history. Model: a baseline with logistic regression or naive Bayes, which works well for text, then compare with a fine tuned small language model if needed. Evaluate with precision and recall on a test set, and pick a threshold that keeps false positives very low. Deploy it as a service, collect "not spam" corrections from users, and retrain regularly because spammers change tactics.
✅ A strong answer covers
- Clarify which mistake is worse
- Text features (TF IDF) plus extra signals
- Simple baseline first
- Precision focused threshold; feedback and retraining
What they're really checking: A classic fresher design question: a full, simple pipeline with good reasoning.
📖 Learn it: Two kinds of prediction: regression and classification · Measuring models: accuracy, precision and recall · Feature engineering: turning raw data into useful inputs
-
30How would you build a chatbot that answers students' questions from college notices and PDFs?
💬 Easy answer
I'd use RAG. First, collect the notices and PDFs, extract their text, split it into chunks of a few paragraphs, create embeddings and store them in a vector database. When a student asks a question, embed the question, find the most similar chunks, and send them to an LLM with the instruction to answer only from them and to show which notice the answer came from. If nothing relevant is found, it should say so and point to the office. I'd test it with 30 real student questions, fix the failures, deploy it with Streamlit, and add a feedback button.
✅ A strong answer covers
- RAG: ingest, chunk, embed, store
- Retrieve and answer with citations
- "I don't know" when there's no answer
- Test set, deployment, feedback
What they're really checking: Can a fresher design a realistic GenAI project end to end?
📖 Learn it: RAG: letting an LLM answer from your documents · Embeddings and vector databases: searching by meaning · Evaluating AI: how to know it actually works
🤝 Projects and behaviour
Use the STAR method: Situation, Task, Action, Result. Include a number in the result whenever you can.
-
31Walk me through a project you're proud of.
💬 Easy answer
Use STAR and go deep on your own decisions. "Situation: our support team was overwhelmed with repeated questions. Task: I wanted to build an assistant that answers from our help docs. Action: I built a RAG pipeline, but the first version answered only 60% of test questions correctly. I created an evaluation set of 80 real questions, found that most failures came from chunks splitting tables, switched to structure aware chunking and added reranking. Result: correct answers rose to 86%, and in a pilot it resolved about a quarter of tickets without an agent." Be ready for "why did you choose that?" at every step.
✅ A strong answer covers
- STAR structure
- Your personal decisions and trade offs
- A problem you hit and how you solved it
- A measurable result; what you'd do differently
What they're really checking: Ownership, depth and honesty. Most interviews spend 10 to 20 minutes here.
📖 Learn it: Building a portfolio project that gets interviews
-
32Tell me about a time something you built failed.
💬 Easy answer
Pick a real failure with a lesson, not a fake one. "I shipped a classification model that looked great offline, with 92% accuracy, but within two weeks users complained. I had split data randomly, and the same customers appeared in both training and test, so the score was too optimistic. I owned it with my manager, re split by customer, got a realistic 81%, and improved features to reach 86%. Since then, I always ask how the data is grouped before splitting, and I add a review of the evaluation setup to my checklist."
✅ A strong answer covers
- A real failure where you were responsible
- What you did immediately
- The root cause, honestly
- The lasting change in how you work
What they're really checking: Ownership and learning. Blaming others is a red flag.
📖 Learn it: Train/test split and overfitting
-
33Tell me about a disagreement with a teammate or stakeholder.
💬 Easy answer
Show you disagree with data and respect. "A product manager wanted to launch our AI reply feature to all customers. I was worried because our tests showed it sometimes made up refund policies. Instead of just saying no, I showed five real examples and the error rate from our eval set, and proposed launching to 10% of tickets with agent approval first. We agreed on criteria to expand. Two weeks later the error rate was below our threshold and we expanded. We kept a good relationship because we focused on the shared goal."
✅ A strong answer covers
- Situation and both perspectives fairly
- You used evidence, not authority
- A compromise or experiment
- Outcome and the relationship afterwards
What they're really checking: Collaboration and influence.
📖 Learn it: Explaining AI to non-technical people
-
34Explain a technical concept to me as if I'm not technical.
💬 Easy answer
Pick something from your work and use an everyday analogy. For example, explaining RAG: "Imagine a very smart new employee who has read a lot but knows nothing about our company. If you ask them a policy question, they might confidently guess. RAG is like giving them the right pages of our policy manual before they answer, and asking them to point to the page. So answers are based on our actual documents, and you can check them." Then check understanding: "Does that make sense?"
✅ A strong answer covers
- Everyday analogy
- No jargon, or jargon explained
- Why it matters to the listener
- Check understanding
What they're really checking: Communication, essential for FDE, PM and senior roles.
📖 Learn it: Explaining AI to non-technical people
-
35How do you keep up with the fast changes in AI?
💬 Easy answer
Be specific and show you filter noise. "I follow a few high quality sources instead of everything: release notes from the main model providers, a couple of newsletters, and papers when something important comes up. But mostly I learn by building: when something new appears, like a new tool calling feature, I try it on a small project within a week and write a short note about what worked. I also review what changed in our own evals when we upgrade models, which teaches me more than reading headlines."
✅ A strong answer covers
- Specific sources, not "everything"
- Learning by building
- A recent example
- Filtering hype from what matters
What they're really checking: Learning habits in a fast field.
📖 Learn it: Building a portfolio project that gets interviews
-
36How do you use AI coding assistants in your work, and how do you make sure the code is right?
💬 Easy answer
Be honest and responsible. "I use AI assistants daily for boilerplate, tests, unfamiliar libraries and explaining code. But I treat the output like code from a new colleague: I read every line before accepting it, I make sure there are tests, I check security sensitive parts like authentication and SQL myself, and I never paste secrets or confidential data into tools that aren't approved. It makes me faster, but I'm still responsible for what I ship."
✅ A strong answer covers
- Where it helps you most
- Review, tests and verification
- Security and confidentiality
- You remain accountable
What they're really checking: Asked in most 2026 engineering loops: productive and responsible.
📖 Learn it: AI safety in products: hallucinations, prompt injection and guardrails
❓ Closing: your questions and salary
The last five minutes matter. Good questions show you're serious; a calm salary answer protects your offer.
-
37Do you have any questions for us?
💬 Easy answer
Always say yes and ask two or three real questions. Good ones: "What would success look like for this role in the first 6 months?", "What's the biggest challenge the team is facing with AI right now?", "How do you evaluate model or feature quality before shipping?", "How is the team split between building new features and maintaining existing ones?", and "What do people who do well here have in common?". Avoid asking about leave or salary in a technical round, and don't ask things that are on their website.
✅ A strong answer covers
- Ask 2 or 3 thoughtful questions
- About success, challenges, how they work
- Show interest in quality and impact
- Avoid basic or purely self focused questions
What they're really checking: Curiosity and seriousness. "No questions" can cost you.
📖 Learn it: Landing the AI role: resume, applications and interviews
-
38What are your salary expectations?
💬 Easy answer
Research first, using sites like Glassdoor, AmbitionBox, levels.fyi and people in similar roles, then give a range based on the role, not on your current pay. "Based on my research for this role and level in Bangalore, and my experience, I'm looking at a range of ₹22 to ₹28 lakh fixed. I'm flexible depending on the overall package, and I'm most interested in the role itself." If they insist on your current salary, you can share it, but steer back to the market range for the new role. Never accept or reject on the spot; ask for the offer in writing.
✅ A strong answer covers
- Research market ranges for the new role
- Give a range anchored on the role, not current pay
- Mention flexibility on the overall package
- Get the offer in writing before deciding
What they're really checking: Confidence and preparation. A calm, researched range protects your offer.
📖 Learn it: Landing the AI role: resume, applications and interviews
🧪 Quick quiz: test yourself
Short questions by skill area. Try each one before you open the answer.
Python & coding
-
What does len({'a': 1, 'b': 2, 'a': 3}) return?
- It raises an error
- 2
- 3
- 1
Show answer
2. Dictionary keys are unique. The second 'a' overwrites the first, leaving 2 keys.
-
You need to check whether 1 million IDs are in a collection of 1 million known IDs. What's the efficient approach?
- Keep the known IDs in a list and use `in`
- Sort both lists and compare index by index in a nested loop
- Convert the IDs to strings first
- Put the known IDs in a set and use `in`
Show answer
Put the known IDs in a set and use `in`. Membership checks in a set are O(1) on average, but O(n) in a list. With a list this becomes about a trillion comparisons.
-
What's wrong with `def add(item, basket=[]): basket.append(item); return basket`?
- Nothing, it's idiomatic
- The default list is created once and shared between calls, so items leak across calls
- append returns None, so the function always returns None
- Lists can't be default arguments
Show answer
The default list is created once and shared between calls, so items leak across calls. Default values are evaluated once, when the function is defined. Use `basket=None` and create a new list inside the function.
-
What does df.groupby('city')['amount'].mean() return?
- The overall mean amount
- The cities sorted by amount
- One average amount per city
- A count of rows per city
Show answer
One average amount per city. groupby splits the rows by city, then mean() averages 'amount' within each group, giving a Series indexed by city.
Statistics & data
-
Salaries in a team are mostly around ₹8 LPA, with one executive at ₹2 crore. Which best describes a typical salary?
- The median
- The mean
- The sum divided by 2
- The maximum
Show answer
The median. One extreme value pulls the mean up a lot. The median, the middle value, isn't affected by outliers.
-
Users who turned on a new 'focus mode' spend 30% more time in the app. Can you say focus mode caused it?
- Yes, if the sample has more than 1,000 users
- No. People who opt in may already be more engaged, so run a randomised A/B test
- No, time-in-app can never be measured
- Yes, the difference is large
Show answer
No. People who opt in may already be more engaged, so run a randomised A/B test. This is self-selection: the opt-in group differs from everyone else. Only random assignment isolates the feature's effect.
Learn: Correlation vs causation, and sampling bias · Metrics and A/B testing for AI features
SQL & data modelling
-
You want only the cities with more than 100 orders. Which clause filters those groups?
- HAVING COUNT(*) > 100
- ORDER BY COUNT(*) > 100
- LIMIT 100
- WHERE COUNT(*) > 100
Show answer
HAVING COUNT(*) > 100. WHERE filters rows before grouping. HAVING filters groups after aggregation.
-
How do you find customers who have never placed an order?
- INNER JOIN orders and keep the matches
- SELECT DISTINCT customer_id FROM orders
- GROUP BY customer_id HAVING COUNT(*) > 0
- LEFT JOIN orders and keep rows where the order id IS NULL
Show answer
LEFT JOIN orders and keep rows where the order id IS NULL. A LEFT JOIN keeps every customer. Those with no match have NULL order columns.
Learn: SQL JOINs: combining tables
ML fundamentals
-
Training accuracy is 98% and test accuracy is 65%. What's happening, and what's a reasonable fix?
- Underfitting, so add more layers
- Everything is fine
- Overfitting, so simplify the model, regularise or get more data
- The test set is wrong, so delete it
Show answer
Overfitting, so simplify the model, regularise or get more data. A large train/test gap means the model memorised the training data. Reduce its complexity, regularise, or add data.
-
A fraud model is 99% accurate, and 1% of transactions are fraud. What's your first reaction?
- Increase the epochs
- Accuracy is the only metric that matters
- Great, ship it
- Compare against the baseline and check precision and recall, because predicting 'not fraud' for everything also scores 99%
Show answer
Compare against the baseline and check precision and recall, because predicting 'not fraud' for everything also scores 99%. With rare classes, accuracy is misleading. Precision and recall show whether fraud is actually being caught.
-
A fraud model uses 'refund_issued' as a feature and scores 0.99 AUC in testing. What's the problem?
- Data leakage: refunds happen after fraud is confirmed, so this information isn't available at prediction time
- The feature needs scaling
- AUC can't exceed 0.95
- Nothing, it's a strong feature
Show answer
Data leakage: refunds happen after fraud is confirmed, so this information isn't available at prediction time. Features must only use information available at the moment of prediction. Otherwise test scores are inflated.
Learn: Feature engineering: turning raw data into useful inputs
-
For a churn model on a 30-column customer table, what's a strong first choice after a baseline?
- A chatbot
- Gradient-boosted trees such as XGBoost or LightGBM
- A large transformer
- K-means clustering
Show answer
Gradient-boosted trees such as XGBoost or LightGBM. Boosted trees are usually the most accurate, fastest and most explainable option for tabular data.
-
For a cancer-screening model, which metric should you usually prioritise?
- Model size
- Recall
- Training speed
- Precision
Show answer
Recall. Missing a real case is far more costly than a false alarm, which only leads to another test.
-
Explain overfitting to a non-technical person, and how you'd detect and fix it. open question
A strong answer covers:
- A simple analogy (memorising past papers)
- Detection: a gap between training and test scores
- Cross-validation for a reliable estimate
- Fixes: a simpler model, regularisation, more data, early stopping
- A small numeric example
Show model answer
Overfitting is like a student who memorises last year's paper word for word and then struggles with new questions. To detect it, I keep a test set the model never sees: if training accuracy is 98% but test accuracy is 70%, it has memorised rather than learned. Cross-validation gives a more reliable estimate. To fix it, I'd use a simpler model or regularisation, get more or cleaner data, or stop training earlier.
LLMs & prompting
-
You need consistent, repeatable answers for extracting invoice fields. How should you set temperature?
- High (1.0+)
- Change it randomly per request
- Low (around 0)
- It doesn't matter
Show answer
Low (around 0). Low temperature makes outputs focused and repeatable. Higher temperature adds variety, which suits brainstorming.
-
Why do LLMs sometimes state wrong facts confidently?
- Only small models do this
- Their internet connection is slow
- They are lying on purpose
- They generate plausible text and don't verify facts unless given sources or tools
Show answer
They generate plausible text and don't verify facts unless given sources or tools. Grounding answers in sources (RAG), using tools, and showing citations reduces hallucination.
Learn: What is an LLM? Tokens, context and temperature · AI safety in products: hallucinations, prompt injection and guardrails
-
In simple words, what is an LLM, and what is one important limitation? open question
A strong answer covers:
- It predicts the next token, trained on huge amounts of text
- Tokens and the context window
- It generates plausible text, not verified facts
- The hallucination limitation, with an example
- A mitigation: RAG, tools, citations
Show model answer
An LLM is a model trained on a huge amount of text to predict the next word, or token. Doing that at scale lets it write, summarise and answer questions. It works within a context window, a limit on how much text it can consider at once. A key limitation is that it produces plausible text rather than checked facts, so it can confidently state something wrong. You reduce this by giving it trusted sources at question time (RAG), asking for citations, and using tools for calculations or live data.
Learn: What is an LLM? Tokens, context and temperature · RAG: letting an LLM answer from your documents
Communication
-
Tell me about yourself and why you're moving into this AI role. open question
A strong answer covers:
- Current role and years of experience in one or two lines
- 2–3 transferable skills that matter for this AI role
- A concrete AI project, with a measurable result
- Why this specific role fits you (not just 'AI is hot')
- What you'll bring to the team in the first months
Show model answer
I'm a backend engineer with 8 years in fintech, building payment APIs that handle about 2 million requests a day. Over the last six months I've been moving into LLM engineering: I built a support-triage agent with tool calling and an eval suite, which raised correct routing from 71% to 89% on 200 real tickets. This role fits because it combines what I'm already good at, reliable APIs and production debugging, with the agent work I enjoy most. In the first months I'd bring production discipline: tracing, evals and cost controls for your agents.
Learn: Landing the AI role: resume, applications and interviews
-
Walk me through an AI or ML project you built end to end. open question
A strong answer covers:
- The problem and who it was for
- The data: source, size and cleaning
- The approach, and why you chose it over alternatives
- How you evaluated it, with numbers
- How it was deployed or used
- What failed, and what you'd improve next
Show model answer
I built a policy assistant for branch staff who spent about 25 minutes a day searching PDFs. I indexed 140 policy documents with chunking and metadata, used hybrid search, and required citations with a 'not found' rule. I chose RAG over fine-tuning because the policies change monthly. On a 60-question eval set built with staff, correct-and-cited answers went from 68% to 90% after I added re-ranking. It's deployed as an internal web app. The main failure was tables in PDFs; next I'd add table-aware parsing.
-
Tell me about a time something you built failed. What did you do? open question
A strong answer covers:
- The situation, briefly (STAR format)
- Your own responsibility, without blaming others
- How you diagnosed it, step by step
- The outcome, with numbers if possible
- What you changed so it doesn't happen again
Show model answer
Our nightly data pipeline silently loaded duplicate orders for three days, inflating revenue on a dashboard by 12%. I owned that pipeline. I traced it to a retry that re-appended a partial load, so the job wasn't idempotent. I fixed the data, switched the load to overwrite-by-partition, and added a uniqueness check that fails the run. Since then we've had no duplicate incidents, and I now design every pipeline to be safely re-runnable.
Learn: Landing the AI role: resume, applications and interviews
ML system design
-
Design a fraud-detection system for UPI payments. open question
A strong answer covers:
- Requirements: latency budget (e.g. under 100 ms), volume, the cost of a miss vs a false alarm
- Features: real-time (amount vs the user's usual, velocity) and historical, with no leakage
- Model choice (e.g. gradient boosting) and threshold set by business cost
- Serving: a low-latency API plus a streaming feature store
- Monitoring: drift, delayed fraud labels as feedback, and retraining
- A human review queue for borderline cases
Show model answer
I'd start from requirements: decisions in under 100 ms at peak volume, and an explicit cost for missed fraud vs blocking a genuine payment. Features combine real-time signals, such as amount versus the user's usual, transactions in the last 10 minutes and a new device or payee, with historical aggregates from a feature store, all computed only from data available at payment time. A gradient-boosted model fits tabular signals well. I'd set the threshold to minimise expected cost and send a middle band to manual review. It would be served behind a low-latency API with streaming feature updates. I'd monitor input drift and precision and recall as chargeback labels arrive weeks later, and retrain on a schedule.
Learn: Feature engineering: turning raw data into useful inputs · Measuring models: accuracy, precision and recall · Monitoring models: drift and silent failures
More questions to prepare
- What's the difference between a list and a tuple?
- Explain bias vs variance in one minute.
- How do you handle missing values, and when would you drop rows?
- What is a p-value, in plain words?
- Why is Python popular in AI?
- Describe a time you learned something difficult on your own.
Practise with a score and gap analysis
Answer these as a timed practice session. Multiple-choice answers are scored automatically, open answers are self-checked against key points, and your report links the exact lessons for every gap.
Start AI Foundations Path interview practiceAlso for AI Foundations Path
Sources
Questions were compiled from 2026 interview guides and candidate reports, then rewritten with simple answers and checked against our lessons.
- 50 AI Engineer Interview Questions: 2026 LLM Guide (Let's Data Science)
- AI Engineer Interview Questions 2026: RAG, Agents, Evals and Production Systems (PracHub)
- AI engineering interview questions (GitHub, amitshekhariitbhu)
- Machine Learning Interview Questions 2026 (Aced, formerly Exponent)
- AI/ML Engineer Interview Questions 2026 (KORE1)
- Forward Deployed Engineer Interview: The Definitive 2026 Guide (Harvard FAS Career Services)
- Palantir Forward Deployed Engineer Interview Guide (Aced)
- AI Product Manager Interview Questions 2026 (Aced, formerly Exponent)
- AI Product Manager Interview Questions 2026 Guide (Northeastern University)
- Top 31 MLOps and Deployment Interview Questions 2026 (DataInterview)
- Data Engineering Interview Questions and Answers for 2026 (Dataquest)
- Data Engineering Interview Prep 2026: What Actually Matters (DEV Community)
- AI Product Engineer Interview 2026: The New Hybrid Role (techinterview.org)
- Top 30 AI and ML Interview Questions for Freshers 2026 (FACE Prep)