← Google Interview Insights

Google·Software Engineer·Hiring Manager Screen·Intermediate

Intermediate
Jul 2026

Summary

Interviewed for a BA role at Google and got hit with a data quality question that felt deceptively simple but had a lot of layers to it.

Questions Asked (1)

Q1

Can you describe a time you had to work with poor-quality data, or when you proposed new tracking to fill a gap?

Product Analytics & MetricsRoot Cause AnalysisAdaptability & Ambiguity
Author's notes

I went straight into a story about a dashboard with missing event data and how I flagged it to the eng team.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Choose a concrete example where you encountered poor-quality data or identified a tracking gap, and walk through how you diagnosed the issue, quantified its impact, and implemented a solution. Emphasize the engineering rigor you applied—such as data validation, instrumentation design, and cross-functional collaboration—and the measurable outcome.

Pro tip: Show that you think about data quality as a product feature: propose tracking that not only fills the gap but also prevents future issues, and tie it to a business metric like user engagement or revenue.

1. Set the context

Briefly describe the project, your role, and why the data was critical. Mention the specific data quality issue or tracking gap you faced.

2. Diagnose the problem

Explain how you identified the issue (e.g., anomaly detection, user reports, manual audit) and assessed its impact on decisions or product performance.

3. Propose and implement a solution

Describe the technical approach you took to clean the data or design new tracking, including any tools, validation rules, or instrumentation you built.

4. Collaborate and validate

Highlight how you worked with data scientists, product managers, or other engineers to validate the solution and ensure alignment with business goals.

5. Measure and reflect

Share the quantifiable outcome (e.g., improved data accuracy, new insights) and what you learned about data quality or instrumentation.

Key Points to Mention

  • Data validation techniques (e.g., schema checks, outlier detection, deduplication)
  • Instrumentation design (e.g., event tracking, logging, metrics definition)
  • Impact quantification (e.g., how much the issue cost in time, money, or user trust)
  • Cross-functional collaboration (e.g., working with data scientists, PMs)
  • Root cause analysis (e.g., tracing data lineage, identifying upstream issues)
  • Preventive measures (e.g., automated monitoring, data quality dashboards)

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.