Spoken answers: one point, one example, then stop

Connected dashboard practice: Practise a hypothetical metric decision here, then use one sourced SBI story when asked about your experience.

These are proposed scripts, not additional career facts. Time targets are approximate. Read aloud, remove a sentence if needed, and pause after STOP. Never recite the source or claim-limit notes unless the question calls for them.

A01 · Tell me about yourself.

Interviewer intent: Can you select relevant experience for this hands-on PO role?

Type: SBI

20–30 seconds

I lead B2B products by turning customer needs into clear priorities and usable workflows. At Rakuten, I combined customer interviews with account health and usage reviews to prioritize reliable sharing and access over feature expansion. That is the approach I would bring to a SaaS product with several AI capabilities. STOP.

60–90 seconds

I lead B2B products by turning customer needs into clear priorities and usable workflows.

Situation: At Rakuten Drive, core sharing and access needs competed with further feature expansion. The platform served more than a million users, so choosing the next problem mattered.

Behavior: I combined twenty customer interviews with account-health scoring and thirty-day usage reviews, then prioritized reliable releases and core workflows. My role was to turn those signals into a product choice with the delivery team.

Impact: The broader platform improvements were associated with forty percent growth in active business accounts during my tenure. I would not attribute all of that growth to one decision.

For this role, I would apply the same discipline to the path from creating a video to reviewing and using it.

STOP.

Optional deeper evidence

• What did you defer?
• How did you define an active business account?
• What evidence would have changed the choice?

Deliberately left out: Career chronology, degrees and other AI projects: none is needed to establish the central product approach.

Source: Both CVs p1 Rakuten. Approximate word counts: 51 / 128. Short aims at 20–30 seconds; expanded aims at 60–90 seconds. Word counts are estimates; PJ must test aloud.

A02 · How do you prioritize conflicting requests?

Interviewer intent: Can you make a decision from broad evidence?

Type: SBI

20–30 seconds

I look for the customer problem supported by several kinds of evidence. At Rakuten, twenty interviews, account-health scoring and usage reviews helped me prioritize reliable sharing and access over feature expansion. The broader work was associated with business-account growth; I would explain that as a team result, not the isolated effect of my choice. STOP.

60–90 seconds

I look for the customer problem supported by several kinds of evidence, then make the trade-off explicit.

Situation: At Rakuten, we had a broad platform and competing requests. Adding more features was one option, but core sharing and access needed attention.

Behavior: I combined customer interviews with health scoring and usage reviews rather than letting a single request decide the roadmap. I used those inputs to prioritize reliable releases and the workflows customers depended on. The decision was about where to concentrate delivery effort, not just which request had the highest volume.

Impact: Broader platform improvements were associated with forty percent growth in active business accounts during my tenure. Several changes and teams contributed, so I would keep the result at that level.

At AI Studios, I would first test whether the main constraint is starting, reviewing or distributing useful videos.

STOP.

Optional deeper evidence

• Name a deferred feature only if you can verify it.
• Which customer signals disagreed?
• What did engineering challenge?

Deliberately left out: Other employers and a generic prioritization-framework lecture. One decision and its evidence answer the question.

Source: Both CVs p1 Rakuten. Approximate word counts: 55 / 142. Short aims at 20–30 seconds; expanded aims at 60–90 seconds. Word counts are estimates; PJ must test aloud.

A03 · How hands-on are you with AI agents?

Interviewer intent: Can you build something useful and partner responsibly with engineers?

Type: SBI

20–30 seconds

I use prototypes to test workflow behavior. At Edugo, I prototyped transcript-to-activity agents in Gumloop, documented prompts and expected outputs, then partnered with engineers to deploy the tested logic in LangChain. Teacher checks and client approval stayed in the release process. STOP.

60–90 seconds

I use prototypes to test workflow behavior, then work with engineering on what belongs in production.

Situation: At Edugo, generated learning activities needed to fit a learner’s level and remain suitable for student release. A convincing generated example was not enough.

Behavior: I prototyped transcript-to-activity workflows in Gumloop to iterate quickly, documented prompts, inputs and expected outputs, and partnered with engineering to deploy the tested workflow logic in LangChain. I also defined teacher checks and used Sentry production traces to investigate failed or low-quality runs. I owned product behavior and delivery decisions; I would not claim to have built every production component myself.

Impact: The broader product improvements reported a thirty percent increase in content relevance and twenty-five percent fewer support tickets. Those were broader outcomes, not a controlled estimate of the Gumloop prototype’s effect.

STOP.

Optional deeper evidence

• What did the prototype disprove?
• How did you evaluate quality?
• What was yours versus engineering’s?

Deliberately left out: An invented architecture, model training, RLHF, and unsupported claims about autonomous agents.

Source: Both CVs p1 Edugo. Approximate word counts: 42 / 136. Short aims at 20–30 seconds; expanded aims at 60–90 seconds. Word counts are estimates; PJ must test aloud.

A04 · How do you know automation helped?

Interviewer intent: Can you distinguish activity from useful outcomes?

Type: SBI

20–30 seconds

I measure completed work and remaining effort. At KidsLoop, reporting across five regions depended on manual collection. I led the move to centralized, automated learner reporting, reducing staff hours per reporting cycle by eighty percent. That is an operational result; it does not establish better learning outcomes. STOP.

60–90 seconds

I measure the completed task and the work people still have to do.

Situation: At KidsLoop, collecting learner information for reporting involved manual work across five regions. The problem was the staff effort needed to complete a reporting cycle.

Behavior: I led the transition to centralized, automated learner reporting. My product responsibility was organizing the reporting workflow and the move away from manual collection. The point was to make the reporting cycle repeatable across regions and reduce the manual collection required to complete it.

Impact: Staff hours per reporting cycle fell by eighty percent. That is an operational result, not a claim about learner achievement. The important distinction is that we measured the work needed to finish reporting, rather than treating more system activity as success.

For AI Studios, I would include proofreading and repair effort when assessing the benefit of faster video generation.

STOP.

Optional deeper evidence

• What was included in staff hours?
• Was quality maintained?
• What work remained manual?

Deliberately left out: Activity-completion metrics and unrelated automation projects; they would dilute the operational example.

Source: Both CVs p1 KidsLoop Senior PM. Approximate word counts: 48 / 145. Short aims at 20–30 seconds; expanded aims at 60–90 seconds. Word counts are estimates; PJ must test aloud.

A05 · How do you evaluate AI quality?

Interviewer intent: Can you define task-specific quality with domain partners?

Type: SBI

20–30 seconds

I define quality with the people who must use and approve the output. At Edugo, I defined criteria for vocabulary, grammar complexity and learning-level fit, alongside teacher and client review. We used production traces to investigate failures. A model response was not ready simply because it sounded fluent. STOP.

60–90 seconds

I define quality with the people who must use and approve the output.

Situation: At Edugo, generated activities could look plausible while being unsuitable for the learner’s language level. The decision concerned student-facing material, so domain judgment mattered.

Behavior: I defined CEFR-aligned criteria for vocabulary, grammatical complexity and learning-level fit. I combined checks implemented with LangChain with teacher and client review, documented expected behavior, and used Sentry traces to investigate production failures and low-quality responses. The engineering and domain roles were complementary: technical checks helped enforce structure, while reviewers judged whether the activity made sense for the learner.

Impact: Broader improvements increased reported content relevance by thirty percent and reduced support tickets by twenty-five percent. I would verify the original relevance definition before discussing how that percentage was calculated.

For localized video, I would similarly combine structural checks with bilingual review of meaning, numbers and pronunciation.

STOP.

Optional deeper evidence

• How were reviewers calibrated?
• What failure required human judgment?
• What was the denominator?

Deliberately left out: A generic accuracy score or claim that Sentry itself judged educational quality.

Source: Both CVs p1 Edugo. Approximate word counts: 49 / 147. Short aims at 20–30 seconds; expanded aims at 60–90 seconds. Word counts are estimates; PJ must test aloud.

A06 · What pricing experience do you bring?

Interviewer intent: Can you be commercially precise without overstating ownership?

Type: SBI

20–30 seconds

I have supported pricing decisions through cost and acquisition modeling. At KidsLoop, I partnered with sales, finance and data teams to model learner acquisition and content-creation costs across five regions, informing pricing recommendations. I would not present that as owning a payment system or proving a checkout conversion lift. STOP.

60–90 seconds

I have supported pricing decisions through cost and acquisition modeling, and I would be precise about the scope.

Situation: At KidsLoop, a new learning service needed pricing recommendations that accounted for regional acquisition and content costs. Choosing a price without that context would have hidden important assumptions.

Behavior: I worked with sales, finance and data teams to model learner acquisition and content-creation costs across five regions. My contribution was connecting product choices with the commercial inputs needed for pricing recommendations, while partnering with the teams responsible for their underlying evidence.

Impact: The work informed pricing recommendations. My contribution was the analysis and recommendations; payment implementation and a measured conversion result would be separate evidence.

For AI Studios, I would extend that approach by separating video count, dubbing minutes and generative credits, then testing customer comprehension and sustainable cost.

STOP.

Optional deeper evidence

• Which assumption was most sensitive?
• What would you test before changing a plan?
• Who approved pricing?

Deliberately left out: Unverified revenue, price elasticity, ownership of billing engineering and invented conversion lift.

Source: Both CVs p1 KidsLoop Head of Product. Approximate word counts: 50 / 139. Short aims at 20–30 seconds; expanded aims at 60–90 seconds. Word counts are estimates; PJ must test aloud.

A07 · How do you establish AI use as a team workflow?

Interviewer intent: Can adoption become repeatable work with review?

Type: SBI

20–30 seconds

I make AI useful through repeatable tasks and review responsibilities. At Fayston, I worked with teachers and leaders on lesson-planning and assessment workflows, then supported ten staff through ChatGPT and Codex training and reusable templates. Feedback and observation suggested about twenty percent time savings on supported tasks; that was an estimate. STOP.

60–90 seconds

I make AI useful through repeatable tasks, shared templates and clear review responsibilities.

Situation: At Fayston, teachers and leaders had time-consuming planning and assessment tasks. The aim was to make AI support practical in their existing work.

Behavior: I worked with them to identify suitable tasks and prototype assistance with human review. I led ChatGPT and Codex adoption for ten teachers and school leaders through training, reusable workflows and templates. The emphasis was a repeatable procedure people could inspect and adapt, rather than encouraging AI use as an end in itself.

Impact: Staff feedback and observation indicated estimated time savings of twenty percent on supported tasks. This was not a controlled study or a measured saving across every school activity.

For this PO role, I would start with one frequent team task, agree what needs human review, and measure both useful completion and remaining workload.

STOP.

Optional deeper evidence

• Which task was repeated?
• What did reviewers check?
• How would you improve the estimate?

Deliberately left out: Claims of school-wide productivity or learning improvement; neither follows from the estimate.

Source: Both CVs p1 Fayston. Approximate word counts: 52 / 146. Short aims at 20–30 seconds; expanded aims at 60–90 seconds. Word counts are estimates; PJ must test aloud.

A08 · How do you work with global engineering teams?

Interviewer intent: Can you coordinate clear decisions and ownership?

Type: SBI

20–30 seconds

I give distributed teams clear product decisions and expected behavior. At Edugo, I was the sole product leader working with five engineers across Dubai, Argentina and Germany. I ran delivery and prepared CEO reports, while using prototypes and documented inputs and outputs to make the workflow concrete. STOP.

60–90 seconds

I give distributed teams a clear product decision and explicit expected behavior.

Situation: Edugo had a distributed engineering team and an AI language-learning workflow with enterprise, facilitator and learner needs. Coordination had to connect those needs to delivery.

Behavior: As the sole product leader, I owned product strategy and operations, led delivery with five engineers across Dubai, Argentina and Germany, ran Scrum and prepared reports for the CEO. For the AI activity workflow, I used prototypes and documented prompts, inputs and expected outputs to make intended behavior reviewable with engineers and domain reviewers.

Impact: The tested workflow logic was deployed through engineering partnership in LangChain. The broader product improvements reported better relevance and fewer support tickets, but I would not claim geography or Scrum alone caused those outcomes.

I would bring that clarity to coordination across AI Studios product, engineering, customer and locale-review teams.

STOP.

Optional deeper evidence

• How did you resolve a real disagreement?
• What artifact prevented ambiguity?
• Were those engineers direct reports?

Deliberately left out: Invented meeting schedules, a fabricated conflict story and direct-report claims for the engineering team.

Source: Both CVs p1 Edugo. Approximate word counts: 48 / 145. Short aims at 20–30 seconds; expanded aims at 60–90 seconds. Word counts are estimates; PJ must test aloud.

A09 · How do you improve delivery speed?

Interviewer intent: Can you fix a bottleneck without ignoring quality?

Type: SBI

20–30 seconds

I identify the release bottleneck first. At Rakuten, I used cycle-time data to find release constraints and led automation of repeatable checks with engineering using Jenkins. Release cycle time fell thirty percent. I would also examine escaped defects before treating faster delivery as a complete success measure. STOP.

60–90 seconds

I identify the release bottleneck before asking the team to move faster.

Situation: At Rakuten, release cycle time was a product-delivery constraint. Asking for more output without understanding the bottleneck would not have addressed it.

Behavior: I used cycle-time data to identify release bottlenecks and led automation of repeatable checks with engineering using Jenkins. I owned the product and delivery coordination, with engineers implementing the technical checks. The practical choice was to reduce repeated work in the release process while keeping the checks connected to the product behavior we needed.

Impact: Release cycle time was reduced by thirty percent, as stated in my CV. I would also examine the timing distribution and escaped defects before treating faster delivery as the whole success story.

For video workflows, I would apply the same distinction to machine waiting, human review queues and active repair work.

STOP.

Optional deeper evidence

• What was the bottleneck?
• Was thirty percent median or mean?
• What quality guardrail changed?

Deliberately left out: Unverified release-frequency metrics and a claim of personally building the entire Jenkins system.

Source: Both CVs p1 Rakuten. Approximate word counts: 48 / 143. Short aims at 20–30 seconds; expanded aims at 60–90 seconds. Word counts are estimates; PJ must test aloud.

A10 · What kind of product leader are you?

Interviewer intent: Does leadership improve decisions rather than distance you from delivery?

Type: SBI

20–30 seconds

I focus on clear decisions and developing people. At KidsLoop, I led ten product managers and designers and managed a five-hundred-thousand-dollar hiring and training budget. Three team members were promoted. For this hands-on PO role, I would use that leadership experience to improve collaboration while staying responsible for a specific customer outcome. STOP.

60–90 seconds

I try to make the decision and its ownership clear, while helping people develop their judgment.

Situation: At KidsLoop, the product organization supported expansion across five regions. The role involved both product direction and developing the PM/design team.

Behavior: I led ten product managers and designers and managed a five-hundred-thousand-dollar hiring and training budget. I also worked with leadership and cross-functional teams on product requirements and preparation for the company’s next stage. The role combined responsibility for team capacity, product direction and coordination across functions.

Impact: Three team members were promoted. That is the supported people-development result; it does not by itself prove which coaching action caused each promotion.

This posting appears hands-on, so my first priority would be owning the SaaS problem and delivery choices, with the role’s actual decision rights confirmed.

STOP.

Optional deeper evidence

• Give one verified coaching example.
• What did you delegate?
• How does this fit an individual PO role?

Deliberately left out: Fundraising as a personal achievement and an assumed management mandate in the new role.

Source: Both CVs p1 KidsLoop Head of Product. Approximate word counts: 53 / 135. Short aims at 20–30 seconds; expanded aims at 60–90 seconds. Word counts are estimates; PJ must test aloud.

A11 · Why DeepBrain AI?

Interviewer intent: Is motivation specific to the work?

Type: SBI

20–30 seconds

I am interested in the work between AI capability and customer use. AI Studios combines production, localization and team workflows, and this role explicitly connects the roadmap with customer feedback, metrics and prototyping. My Edugo experience gives me a relevant example of turning an AI prototype into reviewed delivery. STOP.

60–90 seconds

I am interested in the product work between a strong AI capability and a workflow a customer can trust.

Situation: At Edugo, a generated activity needed to be suitable for real learners, not merely impressive as a demo. That made the handoff between generation, review and release central to the product.

Behavior: I prototyped transcript-to-activity workflows, documented expected behavior and partnered with engineering on deployment, while retaining teacher checks and client approval. I found that work valuable because it connected technical capability to a task people actually needed to complete.

Impact: The tested workflow logic moved into engineering delivery, and broader improvements reported better relevance and fewer tickets. Those were team outcomes across several changes.

AI Studios presents a similar product question in a different domain: can a team produce, review and use the right video with predictable effort and cost? That is a concrete reason the role interests me.

STOP.

Optional deeper evidence

• Which workflow would you investigate first?
• Why video rather than only education?
• What have you personally tested?

Deliberately left out: Generic praise, unverified company growth, and a claim that learning-content experience equals video-model expertise.

Source: Both CVs p1 Edugo + dated public product/role review. Approximate word counts: 50 / 151. Short aims at 20–30 seconds; expanded aims at 60–90 seconds. Word counts are estimates; PJ must test aloud.

A12 · What are you working to improve?

Interviewer intent: Can you acknowledge feedback and change behavior?

Type: Direct reflection

20–30 seconds

I received feedback that I needed to identify the most important points from broad information and communicate them more concisely. I am practicing a one-sentence answer, one relevant example and a clear stopping point. I want the interviewer to choose where we go deeper. STOP.

60–90 seconds

I am working on choosing the main point and stopping once I have supported it.

After my SORI interview, I received feedback that my answers did not clearly enough identify the most important points from broad information. My response is to practice making the decision first: what is this question really asking, which one example supports my answer, and what can I leave out?

I am using a one-sentence answer followed by one Situation, Behavior, Impact example. I keep the deeper evidence available for a follow-up rather than adding several projects. I am testing the answers aloud and checking whether my personal action and supported result are clear.

That is a practice change, not a claim that I have already solved the issue. STOP.

Optional deeper evidence

• What did you deliberately remove?
• Give me a concise answer now.

Deliberately left out: No invented transcript of the prior interview and no claim that a practice score proves improvement.

Source: User-provided SORI feedback in this request. Approximate word counts: 45 / 124. Short aims at 20–30 seconds; expanded aims at 60–90 seconds. Word counts are estimates; PJ must test aloud.

Use the built-in timer beside the player. The short scripts are approximately 42–55 words; timing still needs your spoken test.