Google is testing a 'Buy' button for Flipkart inside Gemini. The question about the skills you don't have yet.
In a report published September 27, 2026, TechCrunch said Google has started testing a way for shoppers in India to buy products from Walmart-owned Flipkart directly through Gemini and AI Mode. According to people familiar with the matter and an experience seen by TechCrunch, users in the test see a "Buy" button on select Flipkart product listings, which takes them to a Flipkart checkout flow without leaving the AI interface. The test is limited to some users and a small selection of products, and one person said Google plans to roll it out more broadly later in October. Google itself confirmed nothing specific: a spokesperson told TechCrunch the company is "always testing new features and experiences to help people discover and connect with businesses more easily," and had no further details to share.
The detail worth sitting with is the checkout. Earlier this year, TechCrunch noted, Google introduced the Universal Commerce Protocol and said shoppers would be able to buy through a Google-hosted checkout experience. The Flipkart test appears different: tapping the button brings up a Flipkart-branded checkout flow, and TechCrunch reports it is not clear what technology powers it. The same report notes Google invested about $350 million in Flipkart in 2024, taking a minority stake. Nobody has said why the test is built this way, and this article will not guess. But the general shape is one experienced managers know well. Recommending a product and completing a sale are different jobs, and moving from the first to the second exposes everything the first never demanded. That moment, when the job changes underneath someone and their existing competence stops being enough, is exactly what an interviewer is reaching for with this question: "Tell me about a time when you realized you did not have the skills needed to do the job."
Why they ask it
Senior roles rarely stay the shape they were hired for. Scope expands, a team is inherited, a function is merged in, and the skills that earned the promotion are not the skills the new remit requires. The interviewer is not testing whether a candidate has ever been out of their depth. Everyone has. They are testing calibration: how early the candidate noticed, what evidence told them, and what they did in the gap between noticing and being competent.
There is a second signal underneath. A manager who cannot see the edges of their own ability will not see them in their reports either. The question is a proxy for whether this person will surface a problem while it is still cheap, or defend a position until it becomes expensive.
The trap
The most common failure is the disguised strength. The candidate describes a gap so small it was never a risk, such as a tool they picked up over a weekend, and the story ends in triumph. It reads as evasion, because it is.
The second failure is the confession without a recovery. The gap is real, the candidate is admirably candid about it, and then the story trails off into what they learned in general terms. Candour is not the point. What they did next is.
The third is the gap that belongs to someone else: the requirements were unclear, the training never came, the previous owner left no documentation. All of that may be true, and none of it answers the question. A strong answer names a specific, relevant skill the candidate personally lacked, shows the evidence that revealed it, and walks through a deliberate plan that included asking for help, with a visible result and an honest cost.
Applying STAR-T
Situation. After a reorganisation, my team inherited the payments integration for our marketplace. For years we had built ranking and recommendation systems. None of us, including me, had run a system where an error meant a customer was charged twice.
Task. I was accountable for shipping the integration in time for the next seasonal launch and for its reliability afterwards, which meant owning reconciliation with finance and on-call for a system that moved money.
Action. I realised the gap in my first review with the finance lead. She asked how we would detect a mismatch between our records and the processor's, and I did not have an answer. I did not have the vocabulary to form one. That was the evidence: not a feeling of unease, but a question central to the job that I could not engage with. I told my director that week and named the gap precisely, reconciliation and failure handling for payment flows, rather than a vague lack of experience. I asked to borrow an engineer from the payments platform team for the build, set up a standing review with finance, and rewrote the launch plan so that reconciliation was designed first instead of bolted on. I also shadowed the payments on-call rotation myself, because I could not credibly lead an incident review on a system I did not understand.
Result. We launched a few weeks later than the original date, with reconciliation running cleanly from the first day. My team now owns the system without borrowed help, and my director reused the plan when another team took on a similar handover.
Trade-off. The slip cost me standing with the product lead, who had promised the original date upstream, and we deferred a ranking project to free the borrowed engineer. I would make the same call again, but it was not free, and pretending otherwise would make the rest of the story less believable.
The follow-up that breaks weak answers
The follow-up that separates candidates is rarely about the story itself. It is: what skill are you missing for this role? A rehearsed candidate who has just delivered a polished account of past growth often freezes here, or retreats to a disguised strength. The question tests whether the calibration they described is a habit or an anecdote.
A strong answer treats it exactly like the original story, only in the present tense. It names a real gap that matters for the role on offer, explains how the candidate knows it is a gap, and describes what they are already doing about it. Interviewers do not penalise an honest gap with a plan. They penalise a candidate who, having just claimed to see their own limits clearly, suddenly cannot find any.
A quieter version of the same probe is: when did you tell your manager? The timing gives the answer away. Days suggests calibration. Weeks, or after the first missed milestone, suggests the story has been edited.
Score your answer against the director’s bar
Q: Tell me about a time when you realized you did not have the skills needed to do the job.
Bank the one story where the job outgrew your skills, and rehearse it until the moment you noticed comes before the fix. Try it free →