# Eric Wang · Google GCS Strategy & Operations Senior Analyst
## Master Story Bank & Interview Talking Points (Revision 3 - v3)

> **SYNC NOTE FOR ERIC & AGENTS:** This markdown file is the primary human-editable text source for your talking points. All content is 100% grounded in your confirmed facts (K01–K44) and resume facts (F1–F12). Exactly 1 optional `[OPEN]` tag remains in Story S01 result for your review.

**Target Role:** Strategy & Operations Senior Analyst, Google Customer Solutions (GCS)  
**Interview Date:** Monday, October 5, 2026 (Round 1: 45 min hiring team)  
**Build Version:** 2026-09-30-v3  

---

## 1. Executive Pitch & Core Positionings

### 1.1 Tell Me About Yourself (TMAY)

#### 60-Second Version (High-Impact Headline)
I'm a Business Intelligence and Analytics professional specializing in translating ambiguous commercial problems into structured measurement frameworks, decision-support models, and operational strategies. My career spans corporate FP&A at Internet Brands, where I maintained financial forecasting models and aligned operating budgets across 3 business units; Revenue Operations at CoreLogic, where I modeled sales funnels, pinpointed a 22% drop-off between sales qualification and initial demonstration, and eliminated a backlog of ~150 orphan accounts saving ~8 hours per week; and Deloitte Consulting, where as sole data modeler I led consensus workshops across 8 merchandising teams to standardize Store Traffic KPIs in Snowflake across 500+ stores, uncovered $9M+ in lease savings, and as product owner built remodeling tools simulating scenarios in under 10 minutes. What excites me about Google GCS Strategy & Operations is bringing this commercial and analytical toolkit to empower millions of SMB advertisers at global scale.

#### 2-Minute Version (Full Commercial Arc)
I describe my background as the intersection of quantitative modeling, commercial revenue strategy, and enterprise analytics architecture. I hold a BS in Financial Mathematics and Statistics from UC Santa Barbara and a Master of Science in Business Analytics from USC Marshall.

I began my career in Corporate FP&A at Internet Brands, using SQL and Excel to build monthly P&Ls, maintain financial forecasting models, and align operating budgets across 3 business units. That experience gave me a grounded understanding of how commercial operations connect to top-line revenue and margin performance.

I then moved to Revenue Operations at CoreLogic as a Business Intelligence Analyst. There, I built SQL funnel attribution models to diagnose pipeline progression and pinpointed a 22% drop-off between sales qualification and initial solution demonstration. I also wrote an automated Python reconciliation script to streamline Master Data Management parent-child mapping workflows, eliminating a backlog of ~150 orphan accounts and saving ~8 hours per week in manual operations.

Most recently at Deloitte Consulting, I have worked as a Business Intelligence and Analytics Consultant. As product owner and developer, I built self-service capacity planning tools simulating remodeling scenarios across 500+ locations in under 10 minutes, identified $9M+ in potential lease savings through automated data extraction, and served as sole data modeler leading consensus workshops across all 8 merchandising teams to standardize Store Traffic KPIs across 500+ stores in Snowflake for YoY and FY19 pre-pandemic benchmarking. Within our GenAI practice, I also implemented RAGAS evaluation frameworks measuring 150 prompt-response pairs across 4 metrics and LLM Guard safety scanning maintaining latency under 85 milliseconds.

I'm interviewing for the GCS Strategy & Operations Senior Analyst role because it brings all of these threads together: optimizing commercial sales funnels, standardizing operational KPIs, and delivering data-driven decision frameworks to help Google's sales teams grow SMB businesses globally.

---

### 1.2 The Three Whys (90 Seconds Each)

#### Why Google?
Google is unique because of its scale, technical excellence, and the principle of 'Respect the User, Respect the Opportunity, Respect Each Other.' I want to work where data infrastructure and analytical decision-making operate at the highest global standards, and where the questions being answered directly impact millions of small businesses worldwide.

#### Why Google Customer Solutions (GCS)?
Google Customer Solutions (GCS) is the growth engine for millions of small- and medium-sized businesses. SMBs are the backbone of local economies, and helping them succeed with digital advertising through Acquire, Onboard, and Grow journeys is both commercially vital and deeply meaningful. StratOps sits at the heart of that mission, ensuring sales teams have the insights, tools, and operational cadences to deliver value to advertisers.

#### Why Strategy & Operations (StratOps)?
Strategy & Operations is where deep analytical modeling connects with frontline sales execution. I love translating ambiguous business challenges into clear KPI trees, designing operational processes that help sellers focus their time, and providing executive leadership with data-committed recommendations that guide sustainable business growth.

---

### 1.3 Candidate Gaps & Strategic Bridges

- **Perceived Gap:** Direct Digital Advertising Experience
  - **Authentic Bridge:** While my background is in commercial analytics, RevOps, and enterprise consulting, the core mechanics of GCS—funnel conversion modeling, customer retention, seller capacity planning, and unit economics—are identical to the sales operations problems I solved at CoreLogic and Deloitte.

- **Perceived Gap:** Consulting to In-House Transition
  - **Authentic Bridge:** Having worked in corporate FP&A at Internet Brands and RevOps at CoreLogic prior to consulting, I have deep in-house operational experience maintaining live business models and partnering with sales and finance leads over multi-quarter cycles.

- **Perceived Gap:** Years of Experience (4-year requirement)
  - **Authentic Bridge:** I have over 4 years of continuous professional experience across commercial FP&A, revenue operations, and analytics consulting, supported by dual STEM degrees in statistics and business analytics.

- **Perceived Gap:** Executive Stakeholder Exposure
  - **Authentic Bridge:** At Deloitte, my $9M+ lease optimization findings and capacity planning scenario models were approved by executive committees; at CoreLogic, my funnel bottleneck findings prompted RevOps leadership to restructure the demo handoff workflow; and at Internet Brands, I aligned cross-business-unit operating budgets across 3 business units for corporate finance leadership.

---

### 1.4 High-Impact Questions to Ask the Hiring Team

1. "How does the GCS StratOps team prioritize between long-term strategic initiatives and rapid weekly operational support for sales leaders?"
2. "With the rapid rollout of AI campaign features like Performance Max, what have been the biggest operational challenges in seller enablement?"
3. "What does a successful partnership look like between the Strategy & Operations Senior Analyst and regional sales directors?"
4. "How does the team currently measure the incremental effectiveness of seller interventions versus self-service advertiser growth?"
5. "What are the highest-priority cross-functional initiatives currently being planned across Acquisitions and Onboarding?"
6. "How has the RSO operating model evolved over the past year to support changing SMB advertiser needs?"
7. "What data infrastructure or tooling investments would most accelerate the team's analytical velocity today?"
8. "How does GCS leadership foster continuous learning and professional development across the StratOps analyst cohort?"

---

### 1.5 Interview Closing Statement
Thank you for the thoughtful discussion today. I'm deeply excited about this opportunity with GCS Strategy & Operations. My experience across sales funnel modeling, metric standardization in Snowflake, and operational automation aligns directly with the team's mission, and I would love to bring that quantitative and commercial toolkit to Google.

---

## 2. Master STAR Story Bank (11 Stories)

### S01: Identifying $9M+ in Retail Lease & Co-Tenancy Rent Savings
- **Primary Attributes:** `GCA, RRK` | **Resume Anchor:** `F2`
- **Recruiter Themes:** *Large goals; Complex problems and how success was measured; Detailed vs. executive views*

#### Question Prompts Covered:
- *"Tell me about a time you found an analytical insight that others had missed."*
- *"Describe a complex data analysis you conducted that directly influenced executive decision-making."*
- *"How do you bridge granular data findings into high-level business recommendations?"*

**Situation:** At Deloitte Consulting supporting a commercial client with a retail footprint across 500+ locations, the business faced rising occupancy expenses. Client asset managers initially resisted portfolio-wide scrutiny, saying lease covenants had too many localized landlord exceptions to model systematically.

**Task:** My task was to analyze lease structures, co-tenancy covenants, and occupancy terms across the 500+ locations to identify contractual optimization opportunities. I personally wrote the Python extraction scripts and SQL analytical queries; the engagement manager led the client real estate director reviews.

**Action:**
- I developed Python extraction scripts to parse semi-structured lease contracts, isolating co-tenancy thresholds, occupancy covenants, and rent adjustment schedules.
- I wrote centralized SQL analytical queries cross-referencing co-tenancy covenants against traffic and occupancy data across the 500+ locations.
- I built interactive dashboards providing executive leadership with macro-portfolio savings views while allowing asset managers to inspect store-specific lease terms.

**Result:** I identified $9M+ in potential rent savings through co-tenancy and lease restructuring opportunities across the 500+ locations. [OPEN: Number of leases or renegotiation packages prioritized, optional]

**Measure of Success:** Delivered $9M+ in identified rent recovery potential across 500+ locations with full portfolio visibility. The client real estate committee approved the findings to start formal landlord renegotiation.

**Lesson Learned:** Large datasets often conceal high-leverage commercial value in contract terms; success requires translating legal clauses into repeatable data logic that leadership can act upon.

**Google GCS / RSO Bridge:** In GCS RSO, identifying underperforming spend segments or margin leakage across thousands of SMB accounts requires the same discipline: transforming complex contractual and billing data into actionable seller recommendations.

#### Rehearsal Talk Tracks (Polished Clean Speech):
**60-Second Version:**  
At Deloitte Consulting supporting a retail client across 500+ locations, the business faced rising occupancy expenses. Client asset managers initially resisted portfolio-wide scrutiny, saying lease covenants had too many localized landlord exceptions to model systematically. My task was to evaluate lease terms across the full portfolio. I personally wrote the Python extraction scripts and SQL analytical queries; the engagement manager led the client real estate director reviews. I cross-referenced co-tenancy covenants against traffic and occupancy data, synthesizing findings into interactive dashboards. Through this analysis, I identified $9M+ in potential rent savings across the 500+ locations. The client real estate committee approved the findings to start formal landlord renegotiation. This mirrors GCS RSO, where transforming complex billing and tier data into clear commercial actions helps sales leaders unlock hidden revenue headroom.

**2-Minute Version:**  
At Deloitte Consulting, I supported a client operating 500+ retail locations that faced escalating occupancy expenses. Client asset managers initially resisted portfolio-wide scrutiny, saying lease covenants had too many localized landlord exceptions to model systematically.

My task was to analyze lease structures and co-tenancy covenants across all 500+ locations to identify contractual optimization opportunities. I personally wrote the Python extraction scripts and SQL analytical queries; the engagement manager led the client real estate director reviews.

I approached this in three steps: First, I built Python extraction scripts to parse lease agreements and extract critical co-tenancy covenants and rent adjustment terms. Second, I wrote SQL analytical queries joining these covenants against traffic and occupancy data across all 500+ locations. Third, I synthesized the granular findings into interactive dashboards that gave leadership macro-portfolio visibility while allowing asset managers to inspect localized terms.

As a result, I identified $9M+ in potential rent savings through co-tenancy and lease restructuring opportunities across the 500+ locations. The client real estate committee approved the findings to start formal landlord renegotiation.

This experience reinforced that executive impact requires bridging granular contract analysis with strategic decision-making. At Google GCS, this translates directly to evaluating thousands of SMB customer tiers to uncover revenue leakage and guide seller territory planning.

#### Follow-Up Defense:
- **Q:** How did you measure the $9M+ in potential savings across the 500+ locations?
  - **A:** I calculated the difference between actual rent paid and the adjusted contractual rent permitted under triggered co-tenancy clauses across all 500+ locations. Coach: answer from memory — keep it to how you measured, not new numbers.
- **Q:** When asset managers resisted portfolio-wide scrutiny due to localized landlord exceptions, how did you get them aligned?
  - **A:** I walked them through the logic step-by-step, showing how the SQL queries explicitly accounted for localized landlord exceptions and lease amendment dates rather than applying blunt assumptions.
- **Q:** How did you validate the findings before the engagement manager presented to the real estate committee?
  - **A:** I audited a representative sample of lease agreements against the automated SQL flags to ensure covenant breach triggers were verified before the real estate committee initiated formal landlord renegotiation.

---

### S02: Standardizing Store Traffic KPIs Across 8 Categories & 500+ Stores in Snowflake
- **Primary Attributes:** `Leadership, Googleyness` | **Resume Anchor:** `F3`
- **Recruiter Themes:** *Multi-stakeholder projects; Ambiguous problems; Navigating complexity and balancing stakeholder interests; Building connections across teams to deliver impact at scale*

#### Question Prompts Covered:
- *"Tell me about a time you had to align multiple stakeholders around a single metric definition."*
- *"How do you handle situations where different teams use competing numbers to measure success?"*
- *"Describe a time you navigated organizational ambiguity to establish a source of truth."*

**Situation:** At Deloitte Consulting supporting retail operations across 500+ stores, regional merchandising teams used conflicting store traffic calculations. Category leads initially defended their own legacy definitions of a store visit, because each had been reporting with a different definition.

**Task:** I was responsible for establishing a standardized Store Traffic KPI framework across 8 categories and 500+ stores in Snowflake, enabling consistent YoY and FY19 pre-pandemic benchmarking. I was the sole data modeler and business translator: I defined the metric logic and led consensus workshops across all 8 merchandising teams.

**Action:**
- I audited legacy reporting queries across departments to document where the definitions diverged.
- I led consensus workshops across all 8 merchandising teams, walking through the 3 conflicting departmental definitions together.
- I engineered production Snowflake data pipelines embedding the single production metric definition across all 8 retail categories for 500+ stores.

**Result:** Replaced 3 conflicting departmental definitions with 1 production metric definition across 8 categories and 500+ stores, enabling verified YoY and FY19 pre-pandemic benchmarking.

**Measure of Success:** Delivered consistent benchmarking across 8 categories and 500+ stores in Snowflake. The metric was integrated into the core enterprise data warehouse as the standard store-traffic dimension.

**Lesson Learned:** Metric standardization is primarily a stakeholder alignment challenge; the technical query is straightforward once organizational consensus and transparency are achieved.

**Google GCS / RSO Bridge:** In GCS Strategy & Operations, aligning marketing, acquisitions, and onboarding teams on unified definitions of advertiser activation and active customer status is essential for accurate cross-functional governance.

#### Rehearsal Talk Tracks (Polished Clean Speech):
**60-Second Version:**  
At Deloitte Consulting, regional merchandising teams across 500+ stores relied on conflicting store traffic metrics. Category leads initially defended their own legacy definitions of a store visit, because each had been reporting with a different definition. I was responsible for standardizing Store Traffic KPIs across 8 categories and 500+ stores in Snowflake to enable YoY and FY19 pre-pandemic benchmarking. I was the sole data modeler and business translator: I defined the metric logic and led consensus workshops across all 8 merchandising teams. Through these sessions, I replaced 3 conflicting departmental definitions with 1 production metric definition. The metric was integrated into the core enterprise data warehouse as the standard store-traffic dimension. This mirrors GCS StratOps, where unifying definitions of SMB advertiser engagement across sales and onboarding enables coherent regional portfolio management.

**2-Minute Version:**  
At Deloitte Consulting, I encountered a major governance challenge where retail teams across 500+ stores used competing store traffic calculations. Category leads initially defended their own legacy definitions of a store visit, because each had been reporting with a different definition.

My responsibility was to establish a single Store Traffic KPI across 8 categories and 500+ stores in Snowflake, enabling consistent YoY and FY19 pre-pandemic benchmarking. I was the sole data modeler and business translator: I defined the metric logic and led consensus workshops across all 8 merchandising teams.

I executed this across three phases: First, I audited the SQL queries used by each department to isolate mathematical divergences in session windows and filtering logic. Second, I led consensus workshops across all 8 merchandising teams to establish shared business rules and provide bridge charts so historical performance remained transparent. Third, I replaced 3 conflicting departmental definitions with 1 production metric definition in centralized Snowflake pipelines.

This unified reporting across all 500+ stores for YoY and FY19 pre-pandemic comparisons. The metric was integrated into the core enterprise data warehouse as the standard store-traffic dimension, eliminating metric discrepancies across executive reviews.

This initiative proved that lasting data governance requires empathy and stakeholder partnership. In GCS, establishing unified operational definitions ensures sales leadership and product teams pull in the exact same direction.

#### Follow-Up Defense:
- **Q:** How did you get the category leads to give up their legacy definitions?
  - **A:** I led consensus workshops across all 8 merchandising teams, walking through the 3 conflicting departmental definitions together and providing historical bridges so no team felt disadvantaged.
- **Q:** How did you validate that the 1 production metric definition worked across all 8 categories?
  - **A:** I back-tested the single production metric definition against pre-pandemic FY19 baseline data in Snowflake across all 500+ stores to ensure it captured foot-traffic patterns consistently.
- **Q:** How did you ensure the new definition was permanently adopted rather than bypassed?
  - **A:** Because I was the sole data modeler and business translator, I codified the definition directly into the core enterprise data warehouse as the standard store-traffic dimension, deprecating legacy reporting pipelines.

---

### S03: Introducing Contribution to Growth (CTG) Framework to Replace Manual Attribution
- **Primary Attributes:** `GCA, RRK, Leadership` | **Resume Anchor:** `F4`
- **Recruiter Themes:** *Complex problems and how success was measured; Navigating complexity and balancing stakeholder interests; Detailed vs. executive views*

#### Question Prompts Covered:
- *"Tell me about an analytical framework you developed to solve a complex attribution problem."*
- *"How do you introduce new quantitative concepts to non-technical business stakeholders?"*
- *"Describe a time you simplified a complex operational reporting process."*

**Situation:** At Deloitte Consulting supporting a retail client across 500+ stores, merchandising leaders lacked an objective method to explain which categories drove total store traffic growth. Merchandising leads resisted at first because simple percentage changes were easier to understand than additive contribution math.

**Task:** My task was to develop an objective framework to evaluate category performance across 8 categories and 500+ stores. I formulated the CTG decomposition formula and built the automated reporting workflow in Python and SQL.

**Action:**
- I formulated the mathematical CTG decomposition formula, quantifying each category's contribution to total store traffic growth in an additive model.
- I engineered automated data pipelines in Python and SQL to calculate CTG across 8 categories and 500+ stores, replacing disjointed spreadsheets.
- I conducted enablement sessions with merchandising leads, demonstrating how additive CTG math prevented small categories from distorting top-line performance.

**Result:** Eliminated approximately 12 hours of weekly manual reporting across category analytics teams while establishing mathematical attribution integrity.

**Measure of Success:** Delivered full attribution coverage across 8 categories and 500+ stores. Business reviews adopted CTG as the way to evaluate category performance across 500+ stores.

**Lesson Learned:** An analytical metric is only as valuable as its organizational interpretability; pairing rigorous mathematical formulation with intuitive visualization drives executive adoption.

**Google GCS / RSO Bridge:** In GCS, evaluating product growth across Search, PMax, and YouTube requires isolating whether ad revenue growth is driven by budget expansion, product mix, or macro seasonality.

#### Rehearsal Talk Tracks (Polished Clean Speech):
**60-Second Version:**  
At Deloitte Consulting supporting a retail client across 500+ stores, merchandising teams struggled to explain which categories were driving total traffic growth. Merchandising leads resisted at first because simple percentage changes were easier to understand than additive contribution math. My task was to establish an objective evaluation framework across 8 categories and 500+ stores. I formulated the CTG decomposition formula and built the automated reporting workflow in Python and SQL. This eliminated approximately 12 hours of weekly manual reporting across category analytics teams. Business reviews adopted CTG as the way to evaluate category performance across 500+ stores. This approach maps directly to GCS StratOps, where decomposing advertiser spend growth into ad product adoption and budget intensity helps leadership allocate seller resources effectively.

**2-Minute Version:**  
At Deloitte Consulting, I supported a retail client with 500+ stores where category attribution relied on disconnected manual spreadsheets. Merchandising leads resisted at first because simple percentage changes were easier to understand than additive contribution math.

My task was to build a rigorous analytical framework to evaluate performance across 8 categories and 500+ stores. I formulated the CTG decomposition formula and built the automated reporting workflow in Python and SQL.

I approached this in three phases: First, I developed the mathematical CTG decomposition formula to quantify each category's contribution to total traffic growth. Second, I automated the workflow in Python and SQL, eliminating approximately 12 hours of weekly manual reporting across category analytics teams. Third, I held working sessions with category leads, showing that additive contribution math provided fair attribution without penalizing mature categories.

As a result, Business reviews adopted CTG as the way to evaluate category performance across 500+ stores, giving leadership a clear view of which categories drove traffic growth.

This project proved that analytical rigor must be paired with stakeholder education. In GCS, decomposing revenue growth across Search, PMax, and YouTube ensures sales leaders understand the true drivers of SMB customer expansion.

#### Follow-Up Defense:
- **Q:** How did you measure the approximately 12 hours of weekly manual reporting eliminated?
  - **A:** I baselined the time category analytics teams spent manually pulling and reconciling disjointed spreadsheet attribution reports each week before automating the CTG decomposition workflow in Python and SQL. Coach: answer from memory — keep it to how you measured, not new numbers.
- **Q:** How did you convince merchandising leads who preferred simple percentage changes to adopt additive math?
  - **A:** I demonstrated how simple percentage growth distorted performance by treating small sub-categories identically to anchor departments, whereas additive CTG math proved exact dollar contribution to top-line performance.
- **Q:** How did you institutionalize the CTG framework across the organization?
  - **A:** Business reviews adopted CTG as the way to evaluate category performance across 500+ stores, embedding the automated CTG output into leadership review cadences.

---

### S04: Scaling Self-Service Capacity Planning & Remodeling Tools Across 500+ Locations
- **Primary Attributes:** `GCA, Leadership` | **Resume Anchor:** `F1`
- **Recruiter Themes:** *Building connections across teams to deliver impact at scale; Detailed vs. executive views; Complex problems and how success was measured*

#### Question Prompts Covered:
- *"Describe a tool or model you built that scaled across a large organization."*
- *"How do you balance centralized analytical standards with decentralized operational needs?"*
- *"Tell me about a time you empowered operational teams through self-service analytics."*

**Situation:** At Deloitte Consulting supporting a retail client across 500+ stores, annual remodeling planning was bottlenecked by manual spreadsheets. Store operations leads were skeptical that a centralized tool could account for regional differences in store layouts.

**Task:** My task was to design an automated planning solution to evaluate capacity trade-offs across 500+ locations. I was product owner and developer. I gathered store layout requirements and partnered with store operations leads to capture operational constraints, and I built the interactive tool, including all of the backend scenario calculations.

**Action:**
- I partnered with store operations leads to capture physical layout constraints, foot-traffic flows, and construction phasing variables.
- I engineered the backend scenario calculation engine in Python and SQL, modeling space elasticity and sales displacement curves.
- I designed the self-service interactive tool, allowing regional managers to dynamically simulate remodeling permutations and floor plan adjustments.

**Result:** Enabled store operations teams to simulate remodeling scenarios across 500+ locations in under 10 minutes, eliminating weeks of manual spreadsheet modeling.

**Measure of Success:** Scaled self-service simulation capability across 500+ stores. Executive leadership approved the annual capital expenditure plan based on the tool's scenario outputs.

**Lesson Learned:** Operational tools succeed when end users participate in defining constraints; co-designing logic with frontline teams builds trust and accelerates enterprise adoption.

**Google GCS / RSO Bridge:** In GCS StratOps, optimizing seller capacity and territory planning requires the same balance: centralized analytical models that account for regional sales motion differences.

#### Rehearsal Talk Tracks (Polished Clean Speech):
**60-Second Version:**  
At Deloitte Consulting supporting a retail client across 500+ stores, annual store remodeling planning was slowed by disconnected spreadsheets. Store operations leads were skeptical that a centralized tool could account for regional differences in store layouts. I was product owner and developer. I gathered store layout requirements and partnered with store operations leads to capture operational constraints, and I built the interactive tool, including all of the backend scenario calculations. The tool enabled store operations teams to simulate remodeling scenarios across 500+ locations in under 10 minutes. Executive leadership approved the annual capital expenditure plan based on the tool's scenario outputs. This relates directly to GCS Strategy & Operations, where building scalable capacity models helps sales leadership optimize seller coverage across regional books of business.

**2-Minute Version:**  
At Deloitte Consulting, I worked with a national retailer operating 500+ stores where evaluating store remodeling plans required weeks of manual spreadsheet exchanges. Store operations leads were skeptical that a centralized tool could account for regional differences in store layouts.

I was product owner and developer. I gathered store layout requirements and partnered with store operations leads to capture operational constraints, and I built the interactive tool, including all of the backend scenario calculations.

I executed this across three stages: First, I held discovery sessions with regional operators to document physical constraints and department adjacency rules. Second, I developed the backend calculation engine in Python and SQL, modeling foot-traffic flows and sales displacement. Third, I built an interactive interface that allowed operators to test remodeling scenarios in real time.

This enabled store operations teams to simulate remodeling scenarios across 500+ locations in under 10 minutes. Executive leadership approved the annual capital expenditure plan based on the tool's scenario outputs, establishing the platform as the standard planning intake.

This project demonstrated that building operational tools requires deep empathy for frontline constraints. In GCS StratOps, deploying self-service seller tooling ensures sales teams spend less time on administration and more time accelerating SMB growth.

#### Follow-Up Defense:
- **Q:** How did you measure the under 10 minutes runtime for simulating remodeling scenarios across 500+ locations?
  - **A:** I timed the end-to-end execution of the backend scenario calculation engine across the full 500+ store footprint, compared to the multiple days of manual spreadsheet iterations previously required. Coach: answer from memory — keep it to how you measured, not new numbers.
- **Q:** How did you overcome store operations leads' skepticism regarding regional differences in store layouts?
  - **A:** As product owner and developer, I partnered directly with store operations leads to capture localized architectural constraints and build flexible parameter toggles for regional differences directly into the interactive tool.
- **Q:** What was executive leadership's reaction to the capital expenditure scenario outputs?
  - **A:** Executive leadership approved the annual capital expenditure plan based on the tool's scenario outputs because the simulations provided clear, data-driven trade-offs between remodel costs and expected store capacity gains.

---

### S05: Migrating Fragmented Legacy Workflows into Centralized Airflow 3 Orchestration
- **Primary Attributes:** `Googleyness, GCA` | **Resume Anchor:** `F5`
- **Recruiter Themes:** *Building connections across teams to deliver impact at scale; Navigating complexity and balancing stakeholder interests; Complex problems and how success was measured*

#### Question Prompts Covered:
- *"Tell me about a technical infrastructure project you led that improved team efficiency."*
- *"How do you manage technical transitions when downstream teams fear disruption?"*
- *"Describe a time you centralized fragmented processes into a scalable architecture."*

**Situation:** At Deloitte Consulting, multiple analytics workflows ran across disconnected cron jobs and ad-hoc scripts, creating pipeline fragility. Two engineering teams were reluctant to migrate their scheduled cron jobs because of concerns about pipeline downtime during release.

**Task:** My task was to centralize disparate workflows into a robust orchestration platform using Airflow 3. I worked with client platform engineering to define the DAG architecture and personally migrated the data transformation tasks.

**Action:**
- I audited existing data scripts to map task dependencies, execution schedules, and failure alert paths.
- I worked with client platform engineering to define the DAG architecture in Airflow 3, implementing automated retries, dependency triggers, and standardized alerting.
- I personally migrated the data transformation tasks, running the new DAGs in parallel with existing cron jobs to prove pipeline stability before cutover.

**Result:** Consolidated pipelines from 4 separate repositories into 1 centralized orchestration environment in Airflow 3 with automated monitoring.

**Measure of Success:** Achieved centralized workflow management in Airflow 3. Pipeline failure resolution times dropped noticeably, and engineering teams gained end-to-end visibility.

**Lesson Learned:** Infrastructure modernization requires proving stability before forcing cutover; parallel validation builds technical credibility and minimizes operational risk.

**Google GCS / RSO Bridge:** In GCS, maintaining dependable automated data pipelines across seller CRM, customer spend, and onboarding telemetry is the foundation for trustworthy Strategy & Operations reporting.

#### Rehearsal Talk Tracks (Polished Clean Speech):
**60-Second Version:**  
At Deloitte Consulting, critical analytics workflows were fragmented across disconnected schedules. Two engineering teams were reluctant to migrate their scheduled cron jobs because of concerns about pipeline downtime during release. My task was to centralize workflows with Airflow 3. I worked with client platform engineering to define the DAG architecture and personally migrated the data transformation tasks. I consolidated pipelines from 4 separate repositories into 1 centralized orchestration environment. After the migration, pipeline failure resolution times dropped noticeably, and engineering teams gained end-to-end visibility. In GCS StratOps, robust workflow orchestration ensures that seller dashboards and executive reporting update reliably without manual intervention.

**2-Minute Version:**  
At Deloitte Consulting, our client's analytical workflows were fragmented across independent servers and scripts. Two engineering teams were reluctant to migrate their scheduled cron jobs because of concerns about pipeline downtime during release.

My responsibility was to centralize disparate processes into Airflow 3. I worked with client platform engineering to define the DAG architecture and personally migrated the data transformation tasks.

I structured the migration in three steps: First, I mapped all data dependencies, runtimes, and upstream inputs across existing tasks. Second, I worked with client platform engineering to define the DAG architecture in Airflow 3, introducing standardized logging, modular operators, and dependency triggers. Third, I personally migrated the data transformation tasks and ran them in parallel with legacy cron jobs over two release cycles to guarantee zero data loss.

As a result, I consolidated pipelines from 4 separate repositories into 1 centralized orchestration environment. Pipeline failure resolution times dropped noticeably, and engineering teams gained end-to-end visibility across all production data flows.

This project reinforced that technological transitions succeed through operational reliability and risk mitigation. At Google, where data infrastructure supports thousands of sellers, disciplined orchestration ensures executive decisions are always based on timely and dependable metrics.

#### Follow-Up Defense:
- **Q:** How did you convince the two engineering teams concerned about pipeline downtime during release?
  - **A:** I ran the new Airflow 3 DAG architecture in parallel with their existing scheduled cron jobs for two release cycles to prove zero data loss and zero downtime before switching production.
- **Q:** How did you approach consolidating pipelines from 4 separate repositories?
  - **A:** I audited each repository to map data dependencies, worked with client platform engineering to establish a unified DAG architecture, and personally migrated the data transformation tasks into centralized Airflow 3 DAGs.
- **Q:** How did you assess that failure resolution times dropped noticeably?
  - **A:** Engineering teams gained end-to-end visibility with automated alerting and centralized logs, allowing them to pinpoint and resolve task failures immediately rather than diagnosing fragmented crontabs. Coach: answer from memory — keep it to how you measured, not new numbers.

---

### S06: Developing Custom Tableau Viz Extension Beyond Native Platform Capabilities
- **Primary Attributes:** `RRK, GCA` | **Resume Anchor:** `F6`
- **Recruiter Themes:** *Detailed vs. executive views; Insight from large data drove an exec decision; Complex problems and how success was measured*

#### Question Prompts Covered:
- *"Describe a time you pushed beyond the native capabilities of a tool to deliver a business solution."*
- *"How do you tailor visual analytics to executive versus operational audiences?"*
- *"Tell me about a technical innovation you introduced to improve data communication."*

**Situation:** At Deloitte Consulting, executive stakeholders needed to interact with complex multi-dimensional retail performance data without switching across multiple worksheets. The client BI team initially opposed the extension because of the development time relative to the value it would return.

**Task:** My task was to create an advanced visual component beyond native Tableau capabilities. I wrote the JavaScript and HTML integration code for the Tableau Extension API and consulted with dashboard designers on the UI flow.

**Action:**
- I evaluated the Tableau Extension API architecture and designed a custom client-side visual layout using JavaScript and HTML.
- I wrote the JavaScript and HTML integration code for the Tableau Extension API, enabling dynamic dimension toggling within a single view.
- I consulted with dashboard designers on the UI flow, ensuring the extension matched executive viewing habits and passed performance reviews.

**Result:** Replaced 4 disconnected reporting dashboards with 1 unified interactive view, significantly improving navigation efficiency for leadership.

**Measure of Success:** Delivered custom extension functionality beyond native platform limits. The client analytics team incorporated the extension into their standard executive reporting template.

**Lesson Learned:** When off-the-shelf BI tools hit platform boundaries, targeted software development can unlock substantial executive efficiency and clarity.

**Google GCS / RSO Bridge:** In GCS StratOps, delivering executive reporting often requires innovating beyond standard dashboard templates to present multi-dimensional sales performance clearly to leadership.

#### Rehearsal Talk Tracks (Polished Clean Speech):
**60-Second Version:**  
At Deloitte Consulting, executive stakeholders needed to evaluate multi-dimensional retail performance without navigating complex worksheet layers. The client BI team initially opposed the extension because of the development time relative to the value it would return. My task was to extend platform capabilities using custom code. I wrote the JavaScript and HTML integration code for the Tableau Extension API and consulted with dashboard designers on the UI flow. Through this development, I replaced 4 disconnected reporting dashboards with 1 unified interactive view. The client analytics team incorporated the extension into their standard executive reporting template. This experience directly informs my approach in GCS StratOps, where synthesizing multi-layered advertiser metrics into intuitive executive interfaces accelerates leadership decision-making.

**2-Minute Version:**  
At Deloitte Consulting, our client's executive leadership required an interactive view of multi-dimensional performance metrics, but standard native visual components forced users to jump across multiple tabs. The client BI team initially opposed the extension because of the development time relative to the value it would return.

My task was to build a tailored solution using the Tableau Extension API. I wrote the JavaScript and HTML integration code for the Tableau Extension API and consulted with dashboard designers on the UI flow.

I structured the initiative into three stages: First, I built a rapid functional prototype using HTML and JavaScript to prove that custom extension components could render responsive layouts with zero latency overhead. Second, I wrote the JavaScript and HTML integration code for the Tableau Extension API to synchronize data queries between the custom component and the underlying workbook. Third, I consulted with dashboard designers on the UI flow to ensure the interactive controls felt natural to executive users.

As a result, I replaced 4 disconnected reporting dashboards with 1 unified interactive view. The client analytics team incorporated the extension into their standard executive reporting template for regular business reviews.

This project taught me that data visualization must be built around decision workflows, not tool constraints. In GCS, creating clear, cohesive analytical presentations empowers regional directors to spot strategic trends rapidly.

#### Follow-Up Defense:
- **Q:** How did you resolve the client BI team's objection regarding development time relative to value?
  - **A:** I built a rapid working prototype using HTML and the Tableau Extension API, demonstrating that replacing 4 disconnected reporting dashboards with 1 unified interactive view would immediately reduce navigation complexity.
- **Q:** What was your division of labor between front-end coding and dashboard design?
  - **A:** I wrote the JavaScript and HTML integration code for the Tableau Extension API and consulted with dashboard designers on the UI flow to ensure the extension integrated seamlessly with their dashboard layout.
- **Q:** How did the client analytics team adopt the extension long-term?
  - **A:** The client analytics team incorporated the extension into their standard executive reporting template, making it the core interactive component for regular leadership reviews.

---

### S07: Implementing RAGAS Evaluation Framework for GenAI & RAG Pipelines
- **Primary Attributes:** `RRK, GCA` | **Resume Anchor:** `F7`
- **Recruiter Themes:** *Complex problems and how success was measured; Navigating complexity and balancing stakeholder interests; Insight from large data drove an exec decision*

#### Question Prompts Covered:
- *"How do you measure and evaluate quality in non-deterministic or AI-driven systems?"*
- *"Tell me about a quantitative evaluation framework you built from scratch."*
- *"Describe a time you established quality standards for an emerging technology."*

**Situation:** At Deloitte Consulting within our GenAI practice, our team deployed Retrieval-Augmented Generation (RAG) pipelines for enterprise knowledge retrieval. Prompt engineering team members questioned whether automated metrics could reliably evaluate subjective LLM response quality.

**Task:** My task was to establish an objective, repeatable evaluation methodology across 4 core dimensions: Faithfulness, Answer Relevance, Context Recall, and Context Precision. I integrated the RAGAS evaluation library in Python, set up the scoring pipeline, and generated baseline metric reports across 4 metrics.

**Action:**
- I integrated the RAGAS evaluation library in Python into our CI/CD pipeline, connecting vector store retrieval contexts with model completions.
- I set up the scoring pipeline and established metric scoring scripts evaluating Faithfulness, Answer Relevance, Context Recall, and Context Precision.
- I generated baseline metric reports across 4 metrics and demonstrated that automated scoring closely tracked human evaluation benchmarks.

**Result:** Evaluated an initial benchmark set of 150 prompt-response pairs to validate metric stability, identifying specific context retrieval bottlenecks.

**Measure of Success:** Delivered systematic evaluation across 4 RAGAS metrics. RAGAS was adopted as the standard quality gate before deploying pipeline prompt updates.

**Lesson Learned:** Evaluating generative AI requires disciplined quantitative metrics; breaking subjective quality into component dimensions enables rigorous engineering optimization.

**Google GCS / RSO Bridge:** As Google accelerates AI-powered campaign features like Performance Max and Gemini-assisted seller tools, StratOps must define rigorous evaluation rubrics to measure recommendation quality and user trust.

#### Rehearsal Talk Tracks (Polished Clean Speech):
**60-Second Version:**  
At Deloitte Consulting within our GenAI practice, our team developed enterprise RAG pipelines for knowledge retrieval. Prompt engineering team members questioned whether automated metrics could reliably evaluate subjective LLM response quality. My task was to establish an objective quality evaluation framework. I integrated the RAGAS evaluation library in Python, set up the scoring pipeline, and generated baseline metric reports across 4 metrics: Faithfulness, Answer Relevance, Context Recall, and Context Precision. I evaluated an initial benchmark set of 150 prompt-response pairs to validate metric stability. RAGAS was adopted as the standard quality gate before deploying pipeline prompt updates. This aligns with GCS StratOps, where establishing disciplined metrics to evaluate AI recommendations ensures sales teams and advertisers trust automated tools.

**2-Minute Version:**  
At Deloitte Consulting within our GenAI practice, we developed Retrieval-Augmented Generation systems to help enterprise clients query proprietary knowledge bases. Prompt engineering team members questioned whether automated metrics could reliably evaluate subjective LLM response quality.

My responsibility was to implement an objective, repeatable evaluation framework across 4 core metrics: Faithfulness, Answer Relevance, Context Recall, and Context Precision. I integrated the RAGAS evaluation library in Python, set up the scoring pipeline, and generated baseline metric reports across 4 metrics.

I executed this across three steps: First, I integrated the RAGAS evaluation library in Python, connecting retrieved document chunks and generated outputs to the scoring pipeline. Second, I evaluated an initial benchmark set of 150 prompt-response pairs to validate metric stability and prove that automated scores correlated strongly with manual human ratings. Third, I identified that low Faithfulness scores were caused by chunk truncation, enabling our prompt engineers to tune retrieval parameters.

As a result, RAGAS was adopted as the standard quality gate before deploying pipeline prompt updates to production.

This project reinforced that even non-deterministic AI systems require rigorous measurement frameworks. At Google GCS, as AI features like Performance Max expand, StratOps must establish objective quality gates to ensure advertiser performance and trust are never compromised.

#### Follow-Up Defense:
- **Q:** How did you validate that automated metrics could evaluate subjective LLM response quality?
  - **A:** I benchmarked 150 prompt-response pairs across the 4 RAGAS metrics (Faithfulness, Answer Relevance, Context Recall, Context Precision) and correlated the scores against human reviewer evaluations to prove metric consistency.
- **Q:** How did you set up the scoring pipeline in Python?
  - **A:** I integrated the RAGAS evaluation library in Python, set up the scoring pipeline to ingest retrieval contexts and generated completions, and generated baseline metric reports for the engineering team.
- **Q:** How was RAGAS operationalized into the deployment workflow?
  - **A:** RAGAS was adopted as the standard quality gate before deploying pipeline prompt updates, ensuring no prompt or retrieval modification degraded baseline metric scores.

---

### S08: Implementing LLM Guard Output Scanning for Safety, Quality, and Compliance
- **Primary Attributes:** `Googleyness, RRK` | **Resume Anchor:** `F8`
- **Recruiter Themes:** *Navigating complexity and balancing stakeholder interests; Complex problems and how success was measured; Building connections across teams to deliver impact at scale*

#### Question Prompts Covered:
- *"How do you balance user experience and latency against safety and compliance guardrails?"*
- *"Describe a time you implemented risk controls in an operational system."*
- *"Tell me about a technical project where you had to manage strict performance trade-offs."*

**Situation:** At Deloitte Consulting, deploying generative AI applications for enterprise clients required strict guardrails against toxic completions, prompt injections, and PII leaks. Product stakeholders worried that aggressive safety scanning would add noticeable latency to user queries.

**Task:** My task was to implement output scanning guardrails while maintaining strict response latency SLAs. I configured the LLM Guard scanners, defined risk thresholds, and integrated the scanning module into the response generation pipeline.

**Action:**
- I configured the LLM Guard scanners in Python, calibrating toxicity, sensitive data, and hallucination filters against enterprise policies.
- I benchmarked individual scanner runtimes, optimizing token processing pipelines to eliminate processing bottlenecks.
- I defined risk thresholds and integrated the scanning module into the response generation pipeline, allowing low-risk completions to pass while intercepting policy breaches.

**Result:** Kept scanning latency overhead under 85 milliseconds per request, maintaining an optimal real-time conversational experience.

**Measure of Success:** Achieved enterprise compliance scanning within latency SLAs. The guardrails intercepted compliance risks and toxic completions without degrading user experience.

**Lesson Learned:** Governance and speed are not mutually exclusive; thoughtful calibration of risk thresholds enables enterprise-grade safety without sacrificing operational agility.

**Google GCS / RSO Bridge:** In Google Customer Solutions, maintaining brand safety and ad policy compliance across millions of automated campaigns requires the exact same balance: robust automated guardrails that operate without friction.

#### Rehearsal Talk Tracks (Polished Clean Speech):
**60-Second Version:**  
At Deloitte Consulting, deploying client-facing generative AI tools required rigorous output safety and compliance controls. Product stakeholders worried that aggressive safety scanning would add noticeable latency to user queries. My task was to implement real-time safety guardrails within strict performance budgets. I configured the LLM Guard scanners, defined risk thresholds, and integrated the scanning module into the response generation pipeline. I kept scanning latency overhead under 85 milliseconds per request. The guardrails intercepted compliance risks and toxic completions without degrading user experience. This mirrors GCS StratOps, where automated ad policy enforcement and brand safety protections must protect users while maintaining a seamless advertiser experience.

**2-Minute Version:**  
At Deloitte Consulting, our enterprise AI practice deployed generative assistants handling sensitive domain workflows. Product stakeholders worried that aggressive safety scanning would add noticeable latency to user queries.

My responsibility was to implement comprehensive output validation that satisfied compliance requirements without hurting the real-time user experience. I configured the LLM Guard scanners, defined risk thresholds, and integrated the scanning module into the response generation pipeline.

I approached this across three steps: First, I configured the LLM Guard scanners to evaluate completions for toxicity, PII leakage, and output structure. Second, I profiled scanner execution times, ran asynchronous parallel checks, and tuned token windows to optimize throughput. Third, I defined risk thresholds that intercepted severe compliance violations immediately while routing borderline cases for asynchronous review.

As a result, I kept scanning latency overhead under 85 milliseconds per request. The guardrails intercepted compliance risks and toxic completions without degrading user experience, establishing the security baseline for client deployment.

This project taught me that operational guardrails must be engineered with the end-user journey in mind. In GCS, ensuring that automated campaign recommendations meet Google's high quality and policy standards protects advertiser trust at global scale.

#### Follow-Up Defense:
- **Q:** How did you measure and validate the scanning latency overhead under 85 milliseconds?
  - **A:** I benchmarked per-request latency across the response generation pipeline before and after adding LLM Guard, tuning scanner rules to ensure total overhead remained under 85 milliseconds per request. Coach: answer from memory — keep it to how you measured, not new numbers.
- **Q:** How did you balance aggressive safety scanning against user query latency concerns?
  - **A:** I configured the LLM Guard scanners and calibrated risk thresholds iteratively, ensuring we intercepted compliance risks and toxic completions without adding noticeable latency or creating false-positive blocks.
- **Q:** Where did the scanning module sit within the technical architecture?
  - **A:** I integrated the scanning module directly into the post-generation pipeline, validating model completions before streaming outputs to the user.

---

### S09: Optimizing Sales Funnels & Bottlenecks at CoreLogic Revenue Operations
- **Primary Attributes:** `RRK, GCA` | **Resume Anchor:** `F9`
- **Recruiter Themes:** *Insight from large data drove an exec decision; Complex problems and how success was measured; Navigating complexity and balancing stakeholder interests*

#### Question Prompts Covered:
- *"Tell me about a time you identified and resolved a major bottleneck in a commercial sales funnel."*
- *"How do you use data to diagnose why prospective customers drop off?"*
- *"Describe an analysis that led sales leadership to change their operational processes."*

**Situation:** At CoreLogic within Revenue Operations, our team tracked pipeline progression across commercial pipeline accounts. Sales reps felt conversion reporting unfairly blamed their closing skills rather than poor inbound lead quality.

**Task:** My task was to identify conversion bottlenecks and optimize sales funnels across commercial pipeline accounts. I built the SQL funnel attribution models and designed the pipeline conversion dashboards in revenue operations.

**Action:**
- I built the SQL funnel attribution models in revenue operations, mapping stage progression milestones across commercial pipeline accounts.
- I analyzed conversion velocity across opportunity stages, pinpointing that drop-offs were occurring in handoff scheduling rather than pitch rejection.
- I designed pipeline conversion dashboards visualizing conversion drop-offs, isolating handoff delays between sales qualification and the initial solution demonstration.

**Result:** Pinpointed a 22% drop-off between sales qualification and the initial solution demonstration, isolating scheduling lag as the primary driver.

**Measure of Success:** Delivered funnel attribution models across commercial pipeline accounts. RevOps leadership restructured the demo handoff workflow to improve qualification progression.

**Lesson Learned:** Sales friction is frequently a process handoff failure rather than an individual closing failure; objective stage data redirects focus from blame to operational redesign.

**Google GCS / RSO Bridge:** In GCS, diagnosing drop-off between advertiser account creation and first ad launch requires the exact same funnel analytics: identifying whether leakage is caused by onboarding friction or customer fit.

#### Rehearsal Talk Tracks (Polished Clean Speech):
**60-Second Version:**  
At CoreLogic within Revenue Operations, our team tracked pipeline progression across commercial pipeline accounts. Sales reps felt conversion reporting unfairly blamed their closing skills rather than poor inbound lead quality. My task was to identify bottlenecks and optimize sales funnels across commercial pipeline accounts. I built the SQL funnel attribution models and designed the pipeline conversion dashboards in revenue operations. Through this analysis, I pinpointed a 22% drop-off between sales qualification and the initial solution demonstration. RevOps leadership restructured the demo handoff workflow to improve qualification progression. In GCS StratOps, diagnosing funnel drop-offs between advertiser sign-up and sustained spending ensures sales and onboarding teams eliminate conversion leakage.

**2-Minute Version:**  
At CoreLogic, I operated as a Business Intelligence Analyst within Revenue Operations, monitoring commercial sales funnels across commercial pipeline accounts. Sales reps felt conversion reporting unfairly blamed their closing skills rather than poor inbound lead quality.

My task was to objectively diagnose funnel bottlenecks and optimize conversion reporting. I built the SQL funnel attribution models and designed the pipeline conversion dashboards in revenue operations.

I structured the analysis across three phases: First, I built SQL funnel attribution models to track opportunity progression across all funnel stages. Second, I designed pipeline conversion dashboards to evaluate conversion velocity and time-in-stage metrics across commercial pipeline accounts. Third, I pinpointed a 22% drop-off between sales qualification and the initial solution demonstration.

Locating the drop-off at a specific stage moved the conversation from individual rep performance to the process itself. RevOps leadership restructured the demo handoff workflow to improve qualification progression.

This experience highlighted how objective funnel modeling shifts organizational focus from finger-pointing to operational solutions. In GCS, evaluating advertiser progression from acquisition through onboarding requires the same data-driven rigor to drive sustainable growth.

#### Follow-Up Defense:
- **Q:** How did you validate the 22% drop-off between sales qualification and the initial solution demonstration?
  - **A:** I built SQL funnel attribution models tracking opportunity stage transitions across commercial pipeline accounts, isolating timestamps to verify that 22% of qualified leads dropped off before the initial solution demonstration.
- **Q:** How did you address sales reps who felt conversion reporting unfairly blamed their closing skills?
  - **A:** I showed the data dispassionately: the drop-off was occurring during the demo handoff scheduling window rather than inside the sales pitch itself, demonstrating it was a process handoff bottleneck rather than individual closing skills.
- **Q:** What process change did RevOps leadership execute based on your findings?
  - **A:** RevOps leadership restructured the demo handoff workflow to improve qualification progression, streamlining scheduling between qualifying reps and solution consultants.

---

### S10: Automating MDM Workflows & Aligning Account Hierarchies at CoreLogic
- **Primary Attributes:** `Leadership, GCA, Googleyness` | **Resume Anchor:** `F10`
- **Recruiter Themes:** *Complex problems and how success was measured; Navigating complexity and balancing stakeholder interests; Building connections across teams to deliver impact at scale*

#### Question Prompts Covered:
- *"Tell me about a time you automated a complex, error-prone manual process."*
- *"How do you build trust with teams that are hesitant to adopt automated tools?"*
- *"Describe a data reconciliation project that significantly improved operational efficiency."*

**Situation:** At CoreLogic, maintaining accurate account hierarchies across commercial customer portfolios was hindered by fragmented records. The operations team was used to manual spreadsheet adjustments and resisted trusting an automated hierarchy script.

**Task:** My task was to streamline Master Data Management workflows and automate parent-child account mapping. I designed and wrote the automated Python reconciliation script and set data validation rules for parent-child accounts.

**Action:**
- I analyzed parent-child account relationships across commercial accounts to identify common hierarchy mismatch patterns.
- I designed and wrote the automated Python reconciliation script, establishing standardized hierarchy mapping logic and data validation rules.
- I validated the script's output against the operations team's manual spreadsheet results before switching over, so they could see it matched their own decisions.

**Result:** Eliminated a backlog of ~150 orphan parent-child accounts at CoreLogic, ensuring consistent account structures across reporting systems.

**Measure of Success:** Automated commercial account reconciliation. The automated process saved ~8 hours per week and provided clean hierarchy data for monthly reporting.

**Lesson Learned:** Automation projects succeed through transparent validation; showing that the code matches the team's own judgment is what earns their trust.

**Google GCS / RSO Bridge:** In GCS Strategy & Operations, managing customer hierarchies across global agencies, holding companies, and direct SMB advertisers is crucial for fair seller quota credit and portfolio planning.

#### Rehearsal Talk Tracks (Polished Clean Speech):
**60-Second Version:**  
At CoreLogic, maintaining clean commercial account hierarchies was slowed by disconnected account records. The operations team was used to manual spreadsheet adjustments and resisted trusting an automated hierarchy script. My task was to streamline Master Data Management workflows. I designed and wrote the automated Python reconciliation script and set data validation rules for parent-child accounts. After validating the output against the manual process, I eliminated a backlog of ~150 orphan parent-child accounts. The automated process saved ~8 hours per week and provided clean hierarchy data for monthly reporting. In GCS StratOps, maintaining pristine customer hierarchy structures ensures accurate advertiser segmentation and seamless seller book assignments.

**2-Minute Version:**  
At CoreLogic, our operations team spent significant manual effort reconciling parent-child commercial customer accounts across fragmented data sources. The operations team was used to manual spreadsheet adjustments and resisted trusting an automated hierarchy script.

My task was to modernize and automate our Master Data Management hierarchy workflows. I designed and wrote the automated Python reconciliation script and set data validation rules for parent-child accounts.

I tackled this across three stages: First, I audited manual adjustments to document the decision rules governing parent-child groupings. Second, I designed and wrote the automated Python reconciliation script to parse corporate structures and automatically map subsidiaries. Third, to overcome stakeholder resistance, I validated the script's output against their manual spreadsheet results before switching over, so the team could see it matched their own decisions.

This eliminated a backlog of ~150 orphan parent-child accounts. The automated process saved ~8 hours per week and provided clean hierarchy data for monthly reporting.

This initiative proved that automation builds trust through verifiable accuracy. In GCS Strategy & Operations, maintaining accurate account hierarchies across agencies and SMB subsidiaries is critical for fair territory alignment and incentive compensation.

#### Follow-Up Defense:
- **Q:** How did you measure the ~8 hours per week saved by the automated reconciliation script?
  - **A:** I tracked the manual spreadsheet reconciliation time previously required each week to audit and map parent-child accounts, verifying that the automated Python script completed the validation in minutes. Coach: answer from memory — keep it to how you measured, not new numbers.
- **Q:** How did you get the operations team comfortable trusting an automated hierarchy script over manual spreadsheets?
  - **A:** I validated the script's output against their manual spreadsheet results before switching over, so they could see the rules matched their own hierarchy decisions. Coach: describe how you compared them — don't add new numbers.
- **Q:** How did you eliminate the backlog of ~150 orphan parent-child accounts at CoreLogic?
  - **A:** I set automated data validation rules identifying root parent IDs and subsidiary accounts, reconciling the backlog of ~150 orphan parent-child accounts and ensuring clean hierarchy data for ongoing reporting.

---

### S11: A Failure / Something I'd Do Differently: Scoping an Analytical Model Without Early Stakeholder Alignment
- **Primary Attributes:** `Googleyness, Leadership` | **Resume Anchor:** ``
- **Recruiter Themes:** *Challenging situations; Complex problems and how success was measured; Navigating complexity and balancing stakeholder interests*

#### Question Prompts Covered:
- *"Tell me about a time a project failed or didn't go as planned, and what you learned."*
- *"Describe a situation where you received difficult or critical feedback on your work."*
- *"What is something you would do differently in a past analytical project?"*

**Situation:** At Deloitte Consulting on a client forecasting engagement, I was eager to demonstrate advanced predictive capabilities. In review, the client director told us the team couldn't trust a "black box" model they couldn't explain to their VP.

**Task:** My task was to build a forward-looking revenue demand projection model. I built an advanced forecasting model with complex econometric variables before first scoping user requirements with business leads.

**Action:**
- I spent 3 weeks building advanced statistical features that stakeholders ultimately asked me to simplify, incorporating multi-factor econometric regressions.
- When presented with the client director's direct feedback, I resisted defensiveness, paused the rollout, and held working sessions to understand their operational decision flow.
- I restructured the forecasting tool around transparent baseline heuristics that business leads could explain intuitively to their leadership.

**Result:** I learned to co-design a minimum viable model with end users before adding complexity, and I now run an iterative review cadence.

**Measure of Success:** Successfully rebuilt stakeholder trust and delivered an intuitive forecasting tool. The simplified model was officially adopted for monthly planning.

**Lesson Learned:** Analytical sophistication is useless if decision-makers cannot explain the model's logic; co-designing transparent solutions with stakeholders is essential for adoption.

**Google GCS / RSO Bridge:** In GCS StratOps, analytical models must empower sales managers and directors. Starting with clear, explainable heuristics ensures sales leadership embraces the guidance rather than rejecting an opaque algorithm.

#### Rehearsal Talk Tracks (Polished Clean Speech):
**60-Second Version:**  
At Deloitte Consulting on a client forecasting engagement, I was eager to build a highly sophisticated analytical solution. I built an advanced forecasting model with complex econometric variables before first scoping user requirements with business leads. I spent 3 weeks building advanced statistical features that stakeholders ultimately asked me to simplify. In review, the client director told us the team couldn't trust a 'black box' model they couldn't explain to their VP. I listened without defensiveness and simplified the framework around intuitive operational drivers. I learned to co-design a minimum viable model with end users before adding complexity, and I now run an iterative review cadence. In GCS StratOps, ensuring predictive models are transparent and explainable is vital for helping sales leaders act on strategic recommendations with confidence.

**2-Minute Version:**  
At Deloitte Consulting on a client forecasting engagement early in my consulting tenure, I led the development of a predictive demand model. I was eager to showcase advanced modeling capabilities, so I built an advanced forecasting model with complex econometric variables before first scoping user requirements with business leads.

I spent 3 weeks building advanced statistical features that stakeholders ultimately asked me to simplify, integrating multi-factor regression curves and external market indices. However, in review, the client director told us the team couldn't trust a 'black box' model they couldn't explain to their VP.

That feedback was humbling but invaluable. Instead of defending the mathematics, I scheduled working sessions with operational leads to understand how they made weekly allocation decisions. I stripped away the opaque econometric layers and rebuilt the model around intuitive operational drivers that the business could interpret immediately.

Through that experience, I learned to co-design a minimum viable model with end users before adding complexity, and I now run an iterative review cadence. The simplified tool was adopted for ongoing planning, and the client commended our willingness to adapt.

This failure fundamentally shaped my approach to Strategy & Operations. At Google, analytical recommendations must be interpretable by frontline sales leaders; transparent models that inspire action are infinitely more powerful than complex models that sit on a shelf.

#### Follow-Up Defense:
- **Q:** How did you react when the client director called the model a black box they couldn't explain to their VP?
  - **A:** I accepted the feedback directly without being defensive. I recognized that analytical elegance is meaningless if business leaders cannot explain the drivers to their VP, and immediately pivoted to co-designing a transparent model.
- **Q:** What happened to the 3 weeks of work spent building advanced statistical features?
  - **A:** I simplified the model to core operational drivers that stakeholders understood and trusted, keeping the advanced econometric variables documented as potential future phases once the baseline was adopted.
- **Q:** How has this failure changed the way you approach new analytical projects today?
  - **A:** I now always co-design a minimum viable model with end users before adding complexity, establishing an iterative weekly review cadence to ensure alignment at every step.

---