IBM Applied AI Engineer interview questions

Continued pretraining injects domain knowledge that fine-tuning cannot, but naively it wrecks general ability. The signal is the replay ratio, learning-rate rewarming, and how you measure forgetting.

A from-scratch staple that checks whether you understand the conditional-independence assumption and why you work in log space. The signal is fitting per-class means and variances, summing log-likelihoods, and adding the log prior. Here is the implementation.

The 'naive' independence assumption is wrong on real data, yet the classifier is a strong baseline for text. The interesting answer explains why classification survives a broken assumption, plus smoothing and the variants. Here it is.

There is no single fairness number, and a famous result proves you cannot satisfy the main three together. The signal is defining each metric precisely and explaining the impossibility, not picking one blindly. Here is the answer.

Healthcare is the highest-stakes AI domain: a wrong answer can harm a patient, and regulators are watching. The signal is designing decision support with grounding, human oversight, and guardrails, never an autonomous diagnoser. Here is the design.

Some questions need precise multi-hop facts that vector retrieval can't chain. The signal is entity linking plus query translation over a graph (or GraphRAG), and knowing when the graph is worth its maintenance cost. Here is the design.

When a model regresses or an auditor asks 'how was this built,' guesswork is a failing answer. The signal is tracking the whole chain so any model is reproducible and any past decision is explainable. Here is the chain.

Promotion is the easy part. Governance is who is allowed to ship what, on whose sign-off, with what documented, and how a model gets retired. Here is the control plane an auditor actually asks for.

Governance is where enterprise AI deals are won or lost, and engineers who can speak it stand out. The signal is treating it as documentation, accountability, and risk-tiered controls across the lifecycle, not a legal afterthought.

Regulators and enterprises increasingly demand explanations for AI decisions, and the two terms get used loosely. The signal is separating inherently interpretable models from post-hoc explanations and naming the right technique for the stakes.

The NIST AI RMF is the most-referenced voluntary framework for managing AI risk, and enterprises ask about it. The signal is treating it as a continuous process built on four functions, not a compliance checklist. Here is the answer.

Model cards and datasheets are the standard responsible-AI documentation artifacts, increasingly required by regulation and buyers. The strong answer knows what each documents and that honest disclosure of limitations, not marketing, is the entire point. Here is the answer.

The EU AI Act tiers obligations by risk, and that classification is a first-order design decision, not a legal footnote. The signal is knowing the four tiers and what high-risk systems must prove before they ship.

Audit logging is the backbone of AI accountability, but logging everything naively turns your logs into the biggest privacy liability you own. The signal is what to log to replay any decision, and how to do it without hoarding PII.

Every third-party model, dataset, and library is an attack surface: backdoors, poisoning, arbitrary code on load, license landmines. The signal is treating models and data as supply-chain artifacts that need provenance and vetting. Here is the answer.

For consequential decisions, 'the model said so' is not a legal answer. Adverse-action notices and the right to explanation constrain what model you can even ship. Here is the governance view.

ISO 42001 is the certifiable AI management-system standard, the AI analogue of ISO 27001. The signal is knowing it is an auditable management system, not a technical control list, and how it sits next to NIST and the EU AI Act. Here is the answer.

A fairness audit is a defined process: pick protected attributes, choose metrics that fit the harm, measure disaggregated performance, and document findings. The signal is knowing the metrics conflict and which one the use case demands. Here is the answer.

The EU AI Act assigns different duties to high-risk deployers, GPAI model providers, and limited-risk systems. The signal is naming the specific obligations per tier, not just reciting that risk tiers exist. Here is the answer.

Distributed, cross-cultural work is the default for forward-deployed roles. Interviewers want to see deliberate async habits and cultural awareness, not heroics. Here is what scores.

Almost everyone can quote softmax(QKᵀ/√d_k)V. The interviewer wants the variance argument and the exact training failure the scale prevents. Here is the answer that separates memorization from understanding.

The single most-asked applied GenAI question, and the one most candidates answer as a definition dump. The interviewer wants a decision framework with a default and the conditions that flip it. Here is the call that scores.

The modal Applied AI design round. Anyone can draw embed-retrieve-generate. The signal is in chunking, hybrid retrieval, the rerank/latency tradeoff, and how you prove it works. Here is the structure that scores.

MoE is why some frontier models have huge parameter counts but serve cheaply. The signal is the sparse-activation idea, the routing mechanism, and the operational cost (memory, load balancing) that the FLOP savings quietly hide.

These are the knobs every LLM product tunes, and the interviewer wants to know what each does to the probability distribution and which setting fits which task. Including why factual and creative tasks want opposite settings.

Agents are over-applied. The strong answer resists the hype: most tasks want a single structured call, and agents earn their cost only under specific conditions. Here is when to reach for one and how to stop it from compounding errors.

The two knobs that make or break a RAG system, and the ones candidates hand-wave. The signal is tuning chunking against recall and knowing exactly what dense retrieval misses that BM25 catches. Here is the reasoning, not the rules of thumb.

Applied AI rarely waits for certainty, and companies (Amazon's Bias for Action, NVIDIA's speed) test whether you can act decisively without freezing or being reckless. The signal is a reversible, well-reasoned call with a plan to validate. Here is the arc that lands.