Behavioral & Bar Raiser BQ Set

Oracle weighs behavioural rounds heavily — both as standalone bar-raiser / hiring-manager interviews and as 5-15 minute BQ openers folded into nearly every technical round. The recurring question bank is small enough to drill cold, and the bar raiser ("Bartender" / BT in OHAI) intentionally applies BQ-pressure follow-ups. Requirements Most Oracle loops include one full behavioural round (typically the bar raiser / BT in OHAI or the HM round in OCI / NetSuite). Almost every other round opens with 5-15 minutes of BQ before the technical portion. Stories should be calibrated to the level being targeted — IC4+ stories must include cross-team scope and explicit decision-making. The bar raiser sometimes intentionally pressure-tests stories with sharper follow-ups to gauge composure. A dedicated SMTS behavioural round explicitly required STAR-formatted answers. Notes High-frequency BQ topics (consolidated across recent loops) Most proud project / most challenging project — opening question for nearly every behavioural round. Project that went badly / missed deadline — recurring; interviewers probe for ownership without blame-shifting. Cross-team initiative you owned — IC4+ leveling probe. Out-of-scope work — "a time you did something beyond your stated role." Asked in at least 2 reported loops. Mentorship / growing others — IC4+ leveling probe. Receiving and acting on feedback — paired with the mentorship probe. Conflict resolution / disagreement with a peer or senior — recurring. Dealing with tough or unresponsive collaborators — paired with the conflict question. Ambiguous requirements / tight deadlines — "time was short and the requirement was unclear, what did you do?" Recurring. Creative problem-solving — single instance, but recurring across companies. Disagreement turning out to be right / wrong — calibration probe. Automation / scope change you initiated — appears as a tech-screen behavioural opener. Prioritisation approach — "how do you decide what to work on first when everything is urgent?" Asked in a hiring-manager-led behavioural round. Handling failure — "a time you failed, and what you did next." Recurring. Customer / user impact — work where you drove measurable customer impact. Why are you leaving your current company — phone-screen / recruiter opener. Decision-making with very little information — explain what evidence was available, how uncertainty was bounded, and why the decision was still reversible or justified. Difficult technical decision — isolate the competing constraints, the decision made, and the concrete outcome. Role flexibility — willingness to work across frontend and backend rather than staying within one narrow layer. Using AI to improve a personal project — discuss the concrete improvement, how output quality was checked, and what remained under human control. AI in daily engineering work — explain how AI is used in practice, where human verification stays essential, and how it can improve software engineering. Bar Raiser / Bartender style The bar raiser (OCI) or Bartender / BT (OHAI) is an experienced, non-team interviewer with veto power on behavioural fit. Their style is intentionally combative or pressure-applying: sharp follow-ups, scepticism about the candidate's role in a story, fast topic switching. The scoring axis is composure under pressure, not whether the candidate agrees with the interviewer. Tactical tip: when a BT sharpens a follow-up, do not retract your story — restate the specific contribution you made and let the interviewer push again if they want. HM round / Final-round behavioural Hiring-manager rounds are explicitly leveling-bearing. The HM's read shapes the eventual offered level — see the leveling briefing. Topics here tend toward scope, decision-making, and motivation: why Oracle, why this team, what would your first 90 days look like. One OCI virtual onsite opened with a full hour of behavioural-only questions — 8-9 back-to-back BQ from the hiring manager with no coding at all; budget for the BQ round being one of the longest in the loop. One MLE phone-screen-HM combo was reported to have folded an HM down-level decision purely on "have you led others on this?" (vs "have you done it yourself?") — a present-tense scope question. For conflict questions, a generic escalation process is not enough. The HM may interrupt and ask for a real disagreement, the actions taken, and the outcome; lead with the specific incident before explaining the framework. Preparation Maintain 8-10 STAR stories covering: 1 hardest tech problem, 1 cross-team win, 1 failure / missed deadline, 1 mentorship, 1 conflict / disagreement, 1 ambiguous-requirement story, 1 ownership-beyond-scope story, 1 "feedback I received and acted on" story. Calibrate stories to one level above current — present-tense scope language ("I owned", "I decided") is the leveling signal. Rehearse staying neutral and structured under combative follow-ups; the bar raiser specifically scores composure. For the HM round, prepare a 60-90-second answer to "why Oracle / why this team" and one specific question for the HM that demonstrates research into their org.