Development Standards and Governance Questions

Focuses on establishing, communicating, and enforcing team and cross team processes that ensure consistent technical quality. Topics include coding standards and style guides, code review policies and workflows, branch and release strategies, continuous integration and continuous delivery pipelines, static analysis and linting toolchains, automated quality gates and pre commit checks, integration of testing into pipelines, metrics for defect rates complexity and coverage, strategies to manage technical debt and legacy code, governance models for exceptions and escalation, and balancing standard strictness with developer productivity. Interviewers look for experience designing standards, driving adoption, integrating tool chains, and measuring impact.

MediumTechnical

61 practiced

You find that an ETL change deployed earlier in the day caused multiple dashboards to show stale or missing rows. Outline an incident response runbook tailored to BI pipeline outages: include detection, triage, roles and responsibilities, rollback or fix steps, stakeholder communication templates, and postmortem actions.

MediumTechnical

54 practiced

Describe a governance model for exceptions and escalations when a BI artifact needs to bypass a standard (for example, a dashboard needs custom SQL that violates the standard). Include who approves, documentation required, automatic expiration of exceptions, and how to audit and review exceptions over time.

HardTechnical

47 practiced

Design a strategy to version and tag datasets (tables and views) consumed by dashboards so reports are reproducible for audits. Explain approaches such as time travel, snapshotting, schema hashes, and lightweight data hashing, and how to minimize storage cost while keeping point-in-time reproducibility.

HardTechnical

51 practiced

How would you implement pre-deployment data contract testing between upstream ETL teams and BI consumers to prevent schema and semantic breaks? Describe a contract format (for example JSON schema or Avro), enforcement points (CI, pre-merge), contract versioning, and the process for coordinated contract changes.

MediumSystem Design

53 practiced

Design a release workflow for Looker LookML changes in a company where many dashboards depend on shared explores and views. How would you detect and prevent breaking changes, handle schema migrations, automate tests, and coordinate releases across teams who own different models?

Unlock Full Question Bank

Get access to hundreds of Development Standards and Governance interview questions and detailed answers.

Join thousands of developers preparing for their dream job.