The engineering round: Mudit Gupta or one of his Managing Directors, an architecture discussion, a Partner round after. This page is the AI engineering substance. The governance material lives in the deck and gets one answer here, because at this level they are testing whether you can build the thing, not whether you can document it.
How to use this page
- These are positions with receipts, not a script. Learn the shape and the specifics, then say it your way.
- The specifics are the point. "We use caching" is nothing. "Cache reads cost about a tenth of input tokens, and if your hit rate is zero you have a timestamp in your system prompt" is an engineer talking.
- At Manager they want to know you build. Reach for the mechanism, then the tradeoff you owned.
- Fill every [bracket] before the call. Those are facts only you know.
Workflow firstagency is earned, not assumed
Context is a budgetnot a place to put things
Retrieval ≠ generationevaluate them separately
Gate, don't measurean eval that can't fail a build is a dashboard
Tools are the APIagent quality is tool quality
Somnathex-IBM Research, OR background, Sibos
Possible interviewer · researched 3 Nov 2026
Somnath Mukherjee
Twelve years at EY, entered through Advisory in the Financial Services Office. White Plains, New York, so this is an on-shore conversation, not GDS. Before EY: four years as a system engineer at IBM, then three and a half years as a Data Specialist in Advanced Analytics and Data Mining at IBM Research. Master of Computer Applications, West Bengal University of Technology. They are a BI and data-engineering practitioner who moved into analytics and then ML, not an LLM researcher.
Two things to check before the call
They may no longer be a Senior Manager. Several sources show their current title as Managing Director, promoted around June 2026, while older scrapes still say Senior Manager. Look at the live profile yourself. If they are an MD, this is a hiring-manager or skip-level conversation, two ranks above the Manager seat, and you should treat it as a judgment interview rather than a peer technical screen.
They have no publications, patents or public code. That is a verified negative, not a gap in the search. Do not walk in planning to reference their work. The IBM Research role was a practitioner line inside the research org, not a research-scientist one. Note also that Sumanta Mukherjee, one letter away, is an IBM Research India scientist with a long publication list. Different person. Do not mix them up out loud.
Their one recent public statement, and your best hook
They attended Sibos 2026 in Miami, 28 September to 1 October, and posted about it about five weeks before your interview. The substance, verified across several sources:
The AI conversation in financial services has shifted, from experimentation to real business workflows.
They named five domains: payments, trade finance, securities services, client servicing and financial intelligence. They also said 2024 was the first time they heard about AI agents, and that what they are trying to solve and how they operate have not changed since. Read that as a hype skeptic. Lead with production constraints and outcomes. Do not lead with framework names or model novelty.
The dominant live-agent story at Sibos 2026 was exception-queue handling: several large banks described agents repairing failed payments, checking trade documents and dispatching work, with a human on the approval. If you have anything shaped like queue triage with a human at the decision point, that is the story to lead with.
What they will actually probe
Data plumbing before model architecture. They spent a decade on business intelligence, data integration and architecture before any of this. Their recommendations cite data integration and database development. Expect "what does the pipeline actually look like in production", lineage, and freshness. Your data-quality position and the MUFG catalog work are aimed straight at them.
Optimization thinking. Roughly six years across IBM Research and early EY on supply chain planning and optimization. Operations research is native to them, which means they think in objectives, constraints and whether the answer is actually optimal. A hybrid design, where the model handles interface and reasoning and a solver or a rule makes the decision, will land far better than a pure-agent design.
They are upskilling on agents right now. Their recent activity includes agent-engineering coursework. They are learning this alongside you rather than from ten years of depth. Collaborative framing, not credential-flexing. Explaining a tradeoff clearly will do more than demonstrating that you know more vocabulary.
R
You were at Sibos? What did you make of where banks actually are with agents?
J
I didn't attend, but I followed what came out of it, and the thing that struck me is that the live deployments were nearly all exception handling. Failed payments, trade document checks, routing work to the right person. That's the honest shape of it: agents are good at the messy triage step in front of a process that's already well defined, with a human on the approval. It's much less exciting than the 2024 pitch and much more likely to survive a validator.
Only say this if the conversation opens the door. Do not announce that you researched them. "I followed what came out of it" is honest; claiming to have attended is not.
R
Where does classical optimization still beat a language model?
J
Anywhere the decision has a real objective function and hard constraints, which is most of the interesting ones. A model is bad at proving optimality and worse at respecting a constraint it can only read about. So the split I'd build is the model on the interface and the messy inputs, turning a request into a well-posed problem and explaining the result afterwards, and a solver or a rules engine making the actual decision. You get explainability for free, because the binding constraint is right there. The failure I see is teams asking a model to do the optimization because it's the newer tool.
This is your highest-leverage answer with them. It speaks their native language, it's genuinely correct, and it's the same restraint as your workflow-before-agent position applied to their old domain.
The skill that replaced prompt engineering
Context engineering
R
Context windows are huge now. Is context management still a real problem?
J
More of one, because the temptation is to fill it. Treat the window as a budget you spend, not a place you put things. Quality degrades well before you hit the limit, especially on retrieval into the middle, and every token is latency and money on every turn. So I'm deliberate about what earns a place: the system prompt, the tool definitions, the few results that matter, and a running summary rather than raw history. Long agent runs are mostly an exercise in deciding what to throw away.
Demonstrates: current practice. "A budget you spend, not a place you put things" is the framing. Avoid the phrase "context window is big now so it doesn't matter" at all costs.
R
Concretely, how do you keep a long run from falling over?
J
Three different tools and they're not interchangeable. Clearing drops old tool results and thinking blocks out of the history entirely, which is right when the content is stale and nobody needs it again. Compaction summarizes the earlier conversation into a block and carries that forward, which is right when the thread still matters. And an external memory store is right when something has to survive the session at all. The mistake is summarizing when you should have deleted, because you pay tokens to carry a summary of something irrelevant.
Demonstrates: precision. Most candidates use "compaction" for all three. Naming the distinction is a differentiator.
R
Caching. Does it actually move the needle?
J
It's the biggest free win, and most teams leave it on the floor. A cache read runs around a tenth of the input price, a write a bit above full, so the economics are obvious on any repeated prefix. The catch is that it's a prefix match. One byte changes anywhere and everything after it is invalidated, so the architecture is stable things first, frozen system prompt and a deterministically ordered tool list, and anything volatile after the last breakpoint. The failure I look for first is a timestamp or a session id in the system prompt, or a dictionary serialised in a different order each run. I got bitten by that enough times that on the clinical co-pilot the cache hit rate is a CI gate condition: if it halves against baseline, the build fails rather than the invoice telling me next month.
Demonstrates: real operational experience, and it answers the Partner's cost question before it's asked. The "check the usage field" detail proves you have debugged this.
Evidence · about 40 seconds each
Your three receipts
Have these cold. Each names what it is, the hard part, and what it proves. The hard part is the interesting bit; lead with it when they are short on time.
R
Show me the shape of something you built this year.
J
A continuous red-teaming platform for a clinical AI assistant. A red team agent generates attacks, a judge scores them, an orchestrator decides what to test next. The part worth talking about is what happens after a finding. A reproducer confirms the attack fires at least two times in three, and then it gets promoted into a permanent regression case that replays by response hash, with no model in the replay loop at all. So the corpus grows itself and the regression suite stays deterministic. I also refused the pass-fail binary there and made it three states, pass, fail and drift, because a test that passes because behaviour wandered is worse than no test.
Lead with the replay loop, not the agents. "The corpus grows itself and the replay has no model in it" answers the question every AI platform interviewer actually has: how do you know you did not regress. Have the drift line ready; it is the one that gets repeated.
R
Anything closer to a regulated decision?
J
A clinical co-pilot that writes an overnight pre-rounds brief from the chart. Retrieval is hybrid, BM25 for the exact terms and dense vectors in pgvector for meaning, merged and then reranked down to three passages. Eighty-one golden cases behind it, including adversarial ones like forged citations and tampered dates. Two things I'd point at. The five gating rubrics are deterministic Python, not a model, and they're calibrated against human labels so I can report precision and recall on the grader itself. And the gate fails the build if median cost per turn goes more than fifty percent above baseline or the prompt cache hit rate halves. That last one catches a prompt edit that bloats the cached prefix before it reaches production.
The cost and cache assertion is the rarest thing you own. Almost nobody asserts cost in CI. It also proves the caching answer earlier is lived rather than read. Say the three failure modes it catches if they lean in.
R
How do you know your evaluation is itself sound? A judge is just another model.
J
A benchmark harness comparing two architectures for live speech interpretation, voice-to-voice against a streaming cascade. It matters because of how the judging works. Scores are MQM-normalised for length with the raw penalty shown next to the number, so no reviewer has to trust a single figure. Significance uses a paired bootstrap, because the runs are paired and the scores are not normally distributed, so a t-test would be the wrong tool, with Benjamini-Hochberg correction across the rubric dimensions. And the merge gate only blocks on a drop that is both more than two points and statistically significant, with the whole verdict voided unless the judge agrees with human labels at a kappa above zero point six. I gated the gate on its own measured agreement.
This is your answer to "your LLM judge is just another unreliable model." With an interviewer whose background is optimisation and statistics, this is the strongest thing you own. Do not rush it.
R
And the bank platform on your resume?
J
Climate scenario analysis for the credit portfolio at US Bank. Physical hazard across more than thirty-six building types, a portfolio above two hundred fifty billion, feeding credit loss estimates. There was no budget for a vendor, so I made the case to build in-house on open source. I'll be precise: it's a quantitative simulation platform, not an agent system. What transfers is the other half. Getting it through model risk management and in front of the board risk committee was harder than the modeling, and that's the muscle an agentic system needs now.
Volunteer the limitation. Saying "not an agent system" before they are asked is what makes the agentic claims credible. See the vendor item in Still to decide.
Do not oversell these three
The insurance underwriting project. Its six-agent pipeline is simulated: every agent call is a timed delay over sample data, with no model calls at all. Presenting it as a multi-agent system would not survive one follow-up question.
The Riverside interview kit. LangGraph, pgvector and reranking appear only in slide copy. The three live endpoints are single-shot calls in a small Node server. It is a pitch artifact, not a build.
The sales-call analyser. A genuine tool-use loop, but 189 lines and two tools. Real, small, and worth exactly that much. The voice sales agent is the substantial one in that family.
One answer each, then move on
The two gaps
Governance gets one answer here rather than a section, because this round is about building. The Databricks gap is the real risk: Mudit leads EY's FS Databricks business and will find it within two questions.
R
How does an agentic system get past model risk management?
J
By building the evidence as you go instead of writing it afterwards: inventory entry, documented intended use and limitations, validation artifacts, a change log. The thing people miss is that the Fed replaced SR 11-7 with SR 26-2 in April, and SR 26-2 scopes generative and agentic systems out. That sounds like relief and isn't, because it means the bank's own governance has to carry them with no supervisory template. That gap is the work, and I've sat on the other side of that table at two banks.
One answer, then back to engineering. Most candidates will not know SR 11-7 was superseded at all. Do not expand unless asked.
R
Your platform work is Snowflake. We are Databricks on the FS side.
J
A gap I'd name before you had to, and I'm not going to pretend otherwise. What transfers is most of it: lineage, data products, retrieval, governance and the medallion pattern are the same problems with different names. What doesn't transfer is hands-on specifics, Unity Catalog, Delta Live Tables, the notebook and job model. I'd expect to be fluent inside the first engagement, and if it's useful I'll come back with a retrieval pipeline built on Delta with Unity Catalog governing access and my eval harness pointed at it. A day of work, and it would tell you more than another hour of talking.
Name it, size it, offer evidence. Never claim fluency you lack to the person who runs that business. If you make the offer, build it.
If they take up the screen-share
Ten minutes, in this order
You offer this in the recruiter screen, so be ready. Rehearse the order, not the words. Have every tab open before the call; never build context live.
- 0:00 — the harness, not the demo. Open the eval suite first. Show a test, show it failing on a deliberate regression, show the golden hash. Everyone else opens with the demo; this inverts it and lands harder.
- 2:00 — trajectory scoring. Show that you score the path, not only the answer, and name a case where the right answer came via a tool call that should not have happened.
- 3:30 — the tool definitions. Show one good tool: the description written as a prompt, the strict schema, and an error message that teaches the model how to retry.
- 5:00 — the deterministic verifier. The thing in front of model output enforcing what the rules permit. Your workflow-before-agent position, made visible.
- 6:30 — the cost invariant. One assertion, one sentence: the build fails if inference gets more expensive.
- 7:30 — the audit log. One record end to end: input, tool calls, decision, approver. Say "this is what I would hand a validator."
- 8:30 — stop early and ask. "What would you want to see that I haven't shown you?" Leaving ninety seconds unused reads as control; running over reads as nervous.
Open and ready: eval suite, one failing test, a tool definition, an audit log record, the routing config. Close Slack and email. Share one window, not the desktop.