Company Interview Questions · IT Services
Mphasis & Persistent: GenAI / AI-ML Engineer
Mphasis & Persistent Systems: GenAI / AI-ML Engineer Interviews (2025). Rounds, real reported questions and model answers, compiled from public candidate reports (sources at the end). Practice mode hides every answer: say your answer first, press Show answer, then rate yourself. Use 🔁 Review again to build your revision list and 🎲 Random question for a quick drill.
About this interview
Compiled from public candidate reports: Mphasis Gen AI Engineer (Bengaluru, April 2025, offer) and Persistent Systems AI/ML Engineer (Pune, June 2025, offer declined), plus a public process guide for Persistent's GenAI Engineer role. The questions are paraphrased, and the model answers are written by EasyLearnSpace.
| Mphasis | Persistent Systems | |
|---|---|---|
| Role | Gen AI Engineer | AI/ML Engineer; GenAI Engineer |
| Rounds | Project-focused interview; polite interviewer, quick follow-up | R1: projects + simple Python + ML; R2: real-time scenario questions |
| Outcome | Offer accepted | Cleared; candidate declined the offer |
| Guide topics | n/a | GANs vs VAEs vs diffusion, evaluating generative models, personalised content system, real-time AI architecture |
01Rounds at a glance
- Mphasis: a conversational deep dive into the projects you have done. Explain them clearly and confidently.
- Persistent: project + Python + ML, then L2 scenarios ("the model is underperforming in production, what do you do?"), then behavioural and HR.
02Questions and model answers
Q1
Compare GANs, VAEs and diffusion models.
| GAN | VAE | Diffusion | |
|---|---|---|---|
| Idea | Generator vs discriminator game | Encode to a latent distribution, then decode | Learn to reverse gradual noising |
| Quality | Sharp | Blurrier | State of the art (Stable Diffusion, Imagen) |
| Training | Unstable, prone to mode collapse | Stable (ELBO loss) | Stable but slow to sample (many steps) |
| Latent space | Implicit | Smooth, interpretable | Noise space; latent diffusion uses a VAE latent |
- Uses: GANs for super-resolution and style transfer; VAEs for anomaly detection and representation learning; diffusion for text-to-image, image editing and audio.
Q2
How do you evaluate a generative model?
- Images:
- FID: the distance between real and generated feature distributions. Lower is better.
- Inception Score, precision/recall for generative models, and CLIP score for text-image alignment.
- Text: task metrics (exact match, ROUGE), LLM-as-judge, human preference, and faithfulness for RAG.
- Always include human evaluation on a sample, plus safety checks (toxicity, bias) and diversity versus quality trade-offs.
Q3
Scenario: your model performs well offline but underperforms in production. What do you do?
- Check the data first: a feature pipeline mismatch between training and serving (training-serving skew), missing features, or schema changes.
- Drift: compare production input distributions with training (PSI, KS test). Concept drift means the label relationship has changed.
- Evaluation flaws: leakage in the offline set, or a random split when it should have been time-based.
- Fix: retrain on recent data, add monitoring and alerts, run a shadow model, and roll back if needed.
- Prevent: a feature store, data contracts, and a scheduled re-evaluation.
Q4
Design a system that generates personalised content (for example, marketing emails) for users.
- Inputs: a user profile and segment, recent behaviour, product catalogue and brand guidelines.
- Pipeline: 1. A candidate generator: rules plus a recommender picks products and offers. 2. An LLM writes copy from a template prompt (tone, length, compliance rules), with structured output. 3. Guardrails: banned claims, PII, brand checks. 4. Human approval for new templates.
- Scale: batch generation overnight and caching by segment; real-time generation only for high-value triggers.
- Measure: an A/B test on open rate, click-through and conversion, plus unsubscribe rate as a guardrail.
Q5
What architecture would you use for a real-time AI application?
- Event stream (Kafka or Kinesis) → stream processor (Flink or Spark Streaming) that computes features → online feature store (Redis) → model service (low-latency REST or gRPC, autoscaled) → decision / action.
- Keep offline training consistent with the same feature definitions.
- Latency budget: under 100 ms, using lightweight models, cached features and async logging.
- Reliability: fallback rules if the model times out, canary deploys, and monitoring of latency and drift.
Q6
Write a function that generates synthetic data from a given distribution.
import numpy as np
def synth(n, dist="normal", seed=42, **p):
rng = np.random.default_rng(seed)
if dist == "normal": return rng.normal(p.get("mu", 0), p.get("sigma", 1), n)
if dist == "poisson": return rng.poisson(p.get("lam", 3), n)
if dist == "categorical":
cats, probs = zip(*p["probs"].items()); return rng.choice(cats, size=n, p=probs)
raise ValueError(dist)
print(synth(5, "categorical", probs={"A": .5, "B": .3, "C": .2}))
- For realistic tabular synthetic data, mention SDV (CTGAN or Gaussian copula), keeping correlations, and privacy checks.
03How to prepare
- Mphasis: polish two projects you can explain end to end, including your own role and the results.
- Persistent: prepare scenario answers (drift, underperformance, latency) and generative-model basics.
Sources
- Glassdoor: Mphasis Gen AI Engineer, Bengaluru (2025)
- Glassdoor: Persistent Systems AI/ML Engineer, Pune (2025)
- Dataford: Persistent Systems GenAI Engineer guide
Created by Ajeetkumar