How to Apply to Looker

9 min read Last updated April 20, 2026 1 open positions
Blake Crosley
Blake Crosley Researched using publicly available information, hiring data, and ATS analysis.

Key Takeaways

  • Looker is no longer an independent company — you are applying to Google, with all that implies for compensation, process, and culture.
  • Apply at careers.google.com searching for 'Looker' or 'Google Cloud Data Analytics' — there is no separate Looker careers site anymore.
  • Compensation follows Google's industry-leading L-level bands — frequently 30-50% above what competing BI startups offer at equivalent levels.
  • Interview process is rigorous and takes six to twelve weeks; plan your job search timeline accordingly and stay patient with the hiring committee model.
  • Domain expertise in BI, SQL, dimensional modeling, and ideally LookML or similar semantic-layer experience strongly differentiates Looker product team candidates.
  • Google sponsors visas widely and hires globally, but most Looker product team roles concentrate in San Francisco, Mountain View, Sunnyvale, Seattle, NYC, Boulder, Dublin, Tokyo, and Bangalore.
  • Post-acquisition culture is real — some Looker veterans have left for startups like Omni Analytics; understand the trade-off between Google's stability and a startup's intensity before signing.

About Looker

Looker is a business intelligence and data analytics platform best known for LookML, its proprietary semantic modeling layer that lets organizations define governed metrics once and reuse them everywhere. Founded in 2012 in Santa Cruz, California by Lloyd Tabb and Ben Porterfield, Looker built a reputation for engineering rigor and a developer-first approach to BI that contrasted sharply with drag-and-drop tools of its era. In June 2019 Google announced its $2.6 billion acquisition of Looker, and the deal closed in early 2020. Today Looker is no longer an independent company. It is an offering inside Google Cloud, formally branded as 'Looker (Google Cloud core),' sitting alongside BigQuery, Dataform, and Looker Studio in Google Cloud's Data Analytics portfolio. What this means for candidates is direct and important: when you 'apply to Looker,' you are applying to Google. The employer of record is Google LLC, the careers portal is careers.google.com, the compensation bands are Google's L-level bands, the interview process is the standard Google loop, and the org chart rolls up to Google Cloud's Data and Analytics organization under SVP Thomas Kurian. The legacy looker.com/careers URL redirects to Google's careers site. Former CEO Frank Bien transitioned out post-integration, and the original Santa Cruz headquarters has been scaled down or consolidated as engineering moved into Google's broader regional footprint. The Looker product itself remains very much alive. It powers enterprise dashboards, embedded analytics, and increasingly serves as the governed semantic layer that AI agents and LLMs query when they need trustworthy metrics. Google released Looker Modeler as a standalone semantic-layer offering in 2024, reflecting the growing strategic importance of governed metrics in an AI-first data stack. Engineering work spans the LookML compiler, the query engine, dashboarding UI, embedded analytics SDK, and tight integrations with BigQuery and other cloud warehouses. Competition is fierce. Looker contends with Tableau (Salesforce), Power BI (Microsoft), Qlik, ThoughtSpot (which acquired Mode in 2023), Sigma Computing, Hex, and a wave of newer entrants including Omni Analytics, founded in 2022 by ex-Looker leaders (notably Colin Zima, former Chief Analytics Officer) who carried the LookML philosophy into a fresh codebase and have raised significant venture funding. Many original Looker employees have departed to these startups, and Google Cloud has not been immune to the broader 2023-2025 cloud-sector workforce reductions, which have touched Looker teams along with the rest of Google Cloud. Candidates evaluating Looker should weigh the stability and resources of Google against the post-acquisition cultural shift away from the scrappy startup the founders built.

Application Process

  1. 1
    Search careers

    Search careers.google.com for 'Looker' or filter by team 'Data Analytics' within Google Cloud — there is no separate Looker careers page anymore.

  2. 2
    Submit a tailored resume as a clean PDF; Google's recruiters scan for prestigiou

    Submit a tailored resume as a clean PDF; Google's recruiters scan for prestigious credentials, FAANG experience, quantified impact, and direct BI or data-warehousing keywords.

  3. 3
    Expect a recruiter screen within one to three weeks if your resume passes initia

    Expect a recruiter screen within one to three weeks if your resume passes initial review; the recruiter will calibrate level (L3 through L7) and confirm role fit.

  4. 4
    Complete a technical phone screen

    Complete a technical phone screen — typically a 45-minute coding interview on a shared editor (CoderPad or Google Docs), LeetCode-medium difficulty for SWE roles.

  5. 5
    If you advance, you enter the onsite loop: four to five interviews covering codi

    If you advance, you enter the onsite loop: four to five interviews covering coding, system design, domain knowledge (BI, SQL, LookML for product roles), and Googliness/leadership.

  6. 6
    Senior candidates (L5 and above) get a dedicated system design round and may fac

    Senior candidates (L5 and above) get a dedicated system design round and may face a hiring committee panel separately from interviewers.

  7. 7
    All feedback goes to a hiring committee, which decides hire/no-hire independentl

    All feedback goes to a hiring committee, which decides hire/no-hire independently of your interviewers — there is no single decision-maker, which lengthens timelines.

  8. 8
    Expect six to twelve weeks from first contact to offer; Google's process is famo

    Expect six to twelve weeks from first contact to offer; Google's process is famously thorough and slow. Stay patient and follow up politely with your recruiter every two weeks.

  9. 9
    Compensation negotiation happens after the committee approval; Google will reque

    Compensation negotiation happens after the committee approval; Google will request competing offers in writing and will counter materially for strong candidates.

  10. 10
    Background check and offer letter follow within one to two weeks of accepted com

    Background check and offer letter follow within one to two weeks of accepted compensation; start dates are typically four to six weeks out.

Resume Tips for Looker

recommended

Lead with quantified impact — Google reviewers expect metrics ('reduced query la

Lead with quantified impact — Google reviewers expect metrics ('reduced query latency 40%,' 'shipped feature used by 12M users') in every bullet, not responsibilities.

recommended

Call out direct BI tool experience by name: Looker, LookML, Tableau, Power BI, Q

Call out direct BI tool experience by name: Looker, LookML, Tableau, Power BI, Qlik, ThoughtSpot, Mode, Hex, Sigma, Metabase, Superset — all signal domain literacy.

recommended

Highlight cloud data warehouse fluency: BigQuery (especially valuable), Snowflak

Highlight cloud data warehouse fluency: BigQuery (especially valuable), Snowflake, Redshift, Databricks; Looker sits on top of these and product engineers need warehouse intuition.

recommended

If you have Ruby on Rails experience, surface it — Looker's core codebase is his

If you have Ruby on Rails experience, surface it — Looker's core codebase is historically Rails, and that legacy stack is niche enough to be a real differentiator.

recommended

For frontend roles call out modern React, TypeScript, and component-library work

For frontend roles call out modern React, TypeScript, and component-library work; Looker's UI has been progressively modernized away from older Rails views.

recommended

Mention dimensional modeling, semantic layer concepts, governed metrics, and SQL

Mention dimensional modeling, semantic layer concepts, governed metrics, and SQL fluency explicitly; these are the conceptual core of Looker's value proposition.

recommended

Use a clean single-column PDF, no tables or graphics — Google's ATS parses these

Use a clean single-column PDF, no tables or graphics — Google's ATS parses these reliably and recruiters skim quickly; aim for one page if under ten years experience.

recommended

Include GitHub, technical blog, or open-source contributions if relevant; Google

Include GitHub, technical blog, or open-source contributions if relevant; Google reviewers do click through and a strong public footprint accelerates calibration.

recommended

Name top-tier credentials prominently if you have them: top-30 CS programs, prio

Name top-tier credentials prominently if you have them: top-30 CS programs, prior FAANG or unicorn experience, recognizable open-source projects.

recommended

Avoid jargon-only bullets — Google reviewers want to see that you understand bus

Avoid jargon-only bullets — Google reviewers want to see that you understand business context, not just that you used a buzzword.

ATS System: Google Careers (custom internal ATS)

Google operates a proprietary applicant tracking system at careers.google.com rather than using a third-party ATS like Greenhouse or Workday. The system is custom-built, integrates with internal hiring committee tooling, and applies the same workflow whether you are applying to Looker, Search, Ads, YouTube, or any other Google product team. Resumes are parsed by both automated systems and human recruiters, with FAANG-trained ML models flagging strong matches. Hiring rates across Google are notoriously low — frequently cited as under 0.2% of applicants — so optimizing every signal matters.

  • Submit a single-column PDF resume — Google's parser handles this format most reliably and avoids layout issues that can hide content from recruiters.
  • Use exact keyword matches from the job description, especially for technical skills, frameworks, and BI domain terms; the system surfaces matches to recruiters.
  • Apply through careers.google.com directly rather than through aggregators like LinkedIn — direct applications get cleaner attribution and faster routing.
  • Use a Google account with a professional email when submitting; it integrates with the application portal and makes status checks easier.
  • Do not submit duplicate applications to multiple Looker or Cloud Data roles simultaneously — pick the best fit; recruiters can see all your active applications and dilution hurts.
  • If a recruiter contacts you on LinkedIn for a role, confirm the requisition ID and apply through the official portal too — recruiter referrals get priority routing but need a record.

Interview Culture

Google's interview culture is rigorous, structured, and famously slow — expect six to twelve weeks end-to-end.

The bar is high and the process is designed to minimize false positives even at the cost of false negatives, so strong candidates are sometimes rejected for fit rather than capability. Interviewers are calibrated, take detailed notes, and submit independent written feedback that a hiring committee reviews without ever meeting you. This means no single interviewer can champion you across the line — every loop must be solid. For Looker product team roles specifically, expect a blend of generalist Google interviews and domain-specific rounds. Coding interviews follow LeetCode-medium to LeetCode-hard patterns: data structures, algorithms, complexity analysis, and clean code under pressure. System design interviews at L5 and above probe distributed systems, data pipelines, query optimization, and BI-specific concerns like multi-tenant dashboards or governed metric layers. Domain rounds for the Looker product team often dive into LookML semantics, dimensional modeling, SQL optimization, or analytics platform architecture. Googliness, the leadership and behavioral round, evaluates collaboration, intellectual humility, comfort with ambiguity, and customer focus. Google Cloud under Thomas Kurian is more enterprise-and-sales-oriented than Search or Ads, and that posture surfaces in interviews — expect questions about working with enterprise customers, partnering with Field teams, and shipping for paying customers rather than free consumer audiences. Post-acquisition Looker has its own micro-culture; some veterans miss the startup intensity, and interviewers may probe how you adapt to a large matrixed organization. Be honest about preferences — culture-mismatch is a leading rejection reason.

What Looker Looks For

  • Strong fundamentals — data structures, algorithms, system design — at a level commensurate with the L-level you're targeting (L3 entry through L7 principal).
  • Demonstrated impact at scale: shipped features used by many users, performance wins, revenue impact, reliability improvements, all quantified.
  • BI and analytics domain literacy — having worked with Looker, Tableau, Power BI, or similar tools and understanding the semantic-layer problem space.
  • SQL fluency at a deep level, including window functions, query optimization, and dimensional modeling concepts.
  • Cloud-native engineering experience, ideally on GCP but AWS or Azure work translates; familiarity with Kubernetes, GKE, and microservices is valuable.
  • Customer empathy and product thinking — Google Cloud roles increasingly weight ability to engage directly with enterprise customers and partners.
  • Intellectual humility and collaborative posture; Google's interview rubric explicitly weights how you handle disagreement, ambiguity, and feedback.
  • Strong written communication — design docs, technical writing, and clear async communication are core to how Google Cloud operates.
  • For senior roles, demonstrated leadership without authority — mentoring, cross-team initiatives, and influence beyond your immediate team.
  • Comfort with Google's hybrid model — three days per week in office at most Google Cloud locations; fully-remote roles exist but are rarer than they once were.

Frequently Asked Questions

Is Looker still an independent company I can apply to?
No. Google acquired Looker for $2.6 billion in 2019 and the deal closed in early 2020. Looker is now an offering within Google Cloud, branded as 'Looker (Google Cloud core).' All hiring goes through Google's careers portal at careers.google.com, and your employer of record will be Google LLC. The Looker product persists, but the company does not.
What does compensation look like for Looker product team roles?
Google's L-level bands apply. In the Bay Area, mid-level software engineers (L4) typically see total compensation of $250K-400K; senior engineers (L5) range from $400K-600K; staff engineers (L6) reach $600K-900K; principal engineers (L7) can hit $900K-1.4M. Compensation is heavily weighted toward four-year vesting RSUs with a one-year cliff. Levels.fyi has detailed live data.
Where is the Looker product team based now?
The original Santa Cruz headquarters has been scaled down or consolidated post-acquisition. Engineering is now distributed across Google's regional hubs: San Francisco, Mountain View, Sunnyvale, Seattle, NYC, Boulder, Dublin (EU Cloud HQ), Tokyo, and Bangalore. Many team members work hybrid under Google's three-days-in-office mandate; fully-remote roles exist but are less common than during the pandemic era.
Does Google sponsor visas for Looker roles?
Yes. Google is one of the largest H-1B sponsors in the United States and routinely sponsors L-1 transfers, O-1 visas, and country-specific equivalents in the UK, Ireland, India, Japan, and Australia. International candidates with strong technical credentials should not be deterred by sponsorship needs.
How long does Google's interview process take?
Six to twelve weeks is typical, sometimes longer at senior levels. The hiring committee model means feedback consolidation alone can take two to three weeks after your onsite. Stay patient, follow up with your recruiter every two weeks, and continue interviewing elsewhere — Google explicitly expects candidates to have other options.
What does Google look for on resumes?
Quantified impact metrics, prestigious credentials (top CS programs, prior FAANG or unicorn experience), strong open-source or technical-writing footprint, and domain alignment with the role. For Looker specifically: BI tool experience, SQL fluency, cloud data warehousing, and ideally Ruby on Rails for legacy product code or React/TypeScript for modern frontend work.
Is Ruby on Rails experience really useful for Looker product roles?
Yes — surprisingly so. Looker's core codebase is historically Ruby on Rails, and that stack remains in heavy use within the product team even as newer services adopt Java, Go, and TypeScript. Rails experience is uncommon among 2020s-era candidates, which makes it a meaningful differentiator if you have it.
Should I have experience with competing BI tools like Tableau or Power BI?
Absolutely. Domain literacy matters more than specific-tool exclusivity. Recruiters and interviewers value candidates who understand the BI problem space — having worked with Tableau, Power BI, Qlik, ThoughtSpot, Mode, Hex, Sigma, Metabase, or Superset all signal that you can reason about dashboards, semantic layers, and analytics workflows.
What is the deal with Omni Analytics and ex-Looker employees?
Omni Analytics was founded in 2022 by ex-Looker leaders, including former Chief Analytics Officer Colin Zima, and has raised significant venture funding. They built a fresh BI platform inspired by the LookML philosophy. Many original Looker employees have moved to Omni or other startups, citing post-acquisition culture changes. This is worth understanding honestly before joining Google's Looker team — the founding-era talent largely has not stayed.
What is Google Cloud's return-to-office policy?
Google Cloud follows Google's broader hybrid mandate of three days per week in a designated office. Most Looker product team roles will be hybrid at one of Google's hub locations. Fully-remote roles exist for specific positions but are increasingly rare, especially for engineering. Confirm specific expectations with your recruiter before accepting an offer.
What is the difference between Looker and Looker Studio?
Looker (Google Cloud core) is the enterprise BI platform built on LookML — paid, governed, semantic-layer-driven. Looker Studio (formerly Google Data Studio) is Google's free dashboarding tool aimed at marketers and individual analysts. They share branding but are distinct products with different teams, codebases, and customer segments. Be clear which product team you are applying to.
Has Looker been affected by Google Cloud layoffs?
Yes. Google Cloud has gone through multiple rounds of workforce reductions in 2023-2025, and the Looker product team has not been exempt. This is worth weighing realistically. That said, Google Cloud Data Analytics remains a strategic priority for Google, and Looker is positioned at the center of the AI-driven semantic-layer trend, which provides some structural tailwind.
What is Looker Modeler and why does it matter?
Released in 2024, Looker Modeler is a standalone offering of Looker's semantic modeling layer — LookML decoupled from the dashboarding product. The strategic bet is that AI agents and LLMs need governed metrics to query data correctly, and Looker Modeler positions the semantic layer as foundational AI infrastructure. For candidates, it signals that semantic-layer expertise is increasingly valuable.

Open Positions

Looker currently has 1 open positions.

Check Your Resume Before Applying → View 1 open positions at Looker

Related Resources

Similar Companies

Related Articles

Sources

  1. Google Cloud — Looker Product Page —
  2. Google Cloud Looker Documentation —
  3. Google to acquire Looker for $2.6 billion (Reuters, June 2019) —
  4. Google Closes $2.6 Billion Acquisition of Looker (Google Cloud Blog) —
  5. Looker Modeler: a standalone semantic layer (Google Cloud, 2024) —
  6. Google Careers Portal —
  7. Levels.fyi — Google Compensation Data —
  8. Glassdoor — Google Cloud Reviews —
  9. Omni Analytics raises Series A from ex-Looker founders (TechCrunch) —
  10. Lloyd Tabb — Looker Founder Background (Forbes) —
  11. ThoughtSpot acquires Mode Analytics (2023) —
  12. Google's Hybrid Work Policy (CNBC) —
  13. Google Cloud Layoffs Coverage (The Information) —
  14. Frank Bien Departure from Looker post-acquisition (Business Insider) —
  15. LinkedIn — Looker Company Page (Google Cloud) —