1

Looker Lookml Developer Jobs (NOW HIRING)

Experienced Looker Engineer that can design, build and optimize the Looker semantic layer and ... years of experience with Looker, LookML models, looks and dashboards creation 3+ years of ...

Looker / Look ML Expert

Lexington, MA ยท On-site

$65 - $75/hr

... engineering, or a closely related field. * Advanced expertise in Looker and LookML, with a strong track record of building robust semantic models and dashboards. * Proven success converting existing ...

Gemini Enterprise Developer United States (Remote) 06 Months Contract Seeking a Gemini Enterprise ... Looker / LookML and semantic layer implementation. * RAG, Agentic AI architectures, vector ...

Senior BI Engineer

Austin, TX ยท On-site

$110/hr

Looker (LookML) * Power BI * Tableau * Cognos * Develop and optimize data pipelines and workflows ... Data Engineering, or Analytics * Bachelor s degree in a relevant field (Master s preferred ...

Sr BI Engineer - Full-time

Austin, TX ยท On-site

$50.50 - $65.75/hr

Looker (LookML) * Power BI * Tableau * Cognos * Develop and optimize data pipelines and workflows ... Data Engineering, or Analytics * Bachelor s degree in a relevant field (Master s preferred ...

New

Sr BI Engineer - Full-time

Austin, TX ยท Hybrid

$47.50 - $61.50/hr

Looker (LookML) * Power BI * Tableau * Cognos * Develop and optimize data pipelines and workflows ... Data Engineering, or Analytics * Bachelor's degree in a relevant field (Master's preferred ...

New

Job Title: Sr. Full stack Developer Job Location: Austin, Texas Job Type: Contract * Architect and ... Implement custom Looker dashboards and LookML models to enhance the reporting capabilities and data ...

RESPEC is hiring a BI Developer to support a public sector partner by administering, developing ... This role is hands-on and highly technical, with a strong focus on Google Looker (LookML) and SQL ...

next page

Showing results 1-20

Looker Lookml Developer information

What is a Looker LookML developer?

Looker LookML Developers are professionals who specialize in creating and managing data models using LookML, the modeling language for Looker. They design, develop, and optimize data models that transform raw data into accessible, meaningful insights for business users. Their responsibilities typically include defining dimensions, measures, and data relationships, implementing business logic, and ensuring data security within Looker. These developers collaborate closely with data analysts, engineers, and business stakeholders to enable self-service analytics and robust reporting. Their expertise helps organizations make data-driven decisions by leveraging the full capabilities of Looker.

What are the key skills and qualifications needed to thrive as a Looker LookML developer?

To thrive as a Looker LookML Developer, you need expertise in SQL, data modeling, and a strong understanding of business intelligence concepts, often supported by a degree in computer science or a related field. Proficiency in Looker, LookML, and familiarity with data warehouses like BigQuery or Redshift are typically required, and Looker certifications are highly valued. Strong analytical thinking, problem-solving abilities, and effective communication skills help you translate business requirements into actionable data solutions. These skills ensure accurate, scalable data models and empower business users with reliable insights for decision-making.

What are some common challenges Looker LookML developers face when collaborating with data analysts and business stakeholders?

Looker LookML Developers often encounter challenges in translating business requirements into efficient data models and dashboards. Effective communication is key, as stakeholders may not always be familiar with data structures or technical constraints. Developers must strike a balance between performance optimization and user-friendly reporting while managing version control and documentation in shared environments. Additionally, aligning on data definitions and governance standards is crucial to ensure consistency and accuracy across teams.

What is the difference between Looker Lookml Developer vs Data Analyst?

AspectLooker Lookml DeveloperData Analyst
Primary RoleDesigns and maintains Looker data models using LookMLAnalyzes data to generate reports and insights
Skills & CertificationsLookML, SQL, data modeling, BI toolsExcel, SQL, data visualization tools
Work EnvironmentData teams, BI departments, cloud-based platformsBusiness units, analytics teams, reporting platforms
Industry UsageTech, finance, e-commerce, any data-driven industryMarketing, finance, operations, business units

While both roles work with data, a Looker Lookml Developer specializes in creating and managing Looker data models using LookML, focusing on data structure and platform configuration. A Data Analyst interprets data to produce reports and insights, often using various tools. The roles are complementary but distinct in scope and technical focus.

What are popular job titles related to Looker Lookml Developer jobs?

For Looker Lookml Developer jobs, the most frequently searched job titles are:

Infographic showing various Looker Lookml Developer job openings in the United States as of September 2026, with employment types broken down into 87% Full Time, 3% Part Time, and 10% Contract. Highlights an 77% Physical, 5% Hybrid, and 18% Remote job distribution.

Cloud & Data Platform Architect(Looker/LookML)

San Ramon, CA โ€ข On-site

Apetan Consulting llc
IT Servicesย โ€ขย 1 - 10 employees

$72.75 - $92.50/hr

Contractor

Posted 4 days ago


Job description

Position: Cloud & Data Platform Architect(Looker/LookLM)
Location: San Ramon, CA (On-Site)
Employment Type: Contract
 
Job Description-:
We run production cloud and data platforms for enterprise clients — multi-region GCP estates, BigQuery warehouses feeding hundreds of downstream consumers, and BI layers that executives look at every morning. Those platforms are increasingly not single-cloud. Workloads, identity, and data land in both GCP and Azure, and someone has to own the shape of the whole thing rather than one slice of it.
This is that owner. It is a hands-on architect role, not a slideware role. You will design the landing zones, review the Terraform, sit in the incident call when the warehouse queues, and then present the remediation to a client CIO the same week.

What you will own

Platform architecture

• Target-state architecture for cloud infrastructure and data platforms across GCP (primary) and Azure (secondary but real)

• Landing zone design: org/subscription hierarchy, network topology, connectivity (Interconnect / ExpressRoute), DNS, egress control

• Identity and access architecture spanning Google Cloud IAM and Microsoft Entra ID, including federation and workload identity

• Cost architecture — capacity vs on-demand models, BigQuery editions and slot reservations, Azure reservations, chargeback/showback

Data platform

• Warehouse and lakehouse architecture: BigQuery, ADLS Gen2, Synapse or Fabric, Databricks where relevant

• Ingestion and orchestration design: Pub/Sub, Dataflow, Datastream, Cloud Composer / Airflow, Azure Data Factory

• Transformation layer standards: Dataform and/or dbt — repo structure, environments, promotion path, CI gates, testing

• Data governance: catalog, lineage, classification, retention, PII handling, and the controls that make a GDPR/DPDP audit uneventful BI and semantic layer

• Looker platform ownership: LookML model architecture, Explore design, PDT/aggregate-awareness strategy, performance tuning

• Access architecture in Looker — model sets, user attributes, row-level security patterns that survive an audit

• Instance administration, upgrades, embed and API usage, and migration work off legacy BI tools

Engineering discipline

• Infrastructure as code as the only path to production — Terraform modules, state strategy, policy-as-code

• CI/CD across Cloud Build / GitHub Actions / Azure DevOps

• Observability and SLOs for both infrastructure and data (freshness, volume,schema, cost anomalies)

• Reliability practice: runbooks, RCA ownership, postmortems that change the design

Client and commercial

• Translate a business problem into an architecture and a defensible estimate

• Lead technical discovery, write solution sections of proposals, and present to client architecture review boards

• Mentor 5–10 engineers; set the technical bar in design reviews and code reviews

Must have

• GCP, deep: BigQuery, GKE, Cloud Run, Cloud Storage, VPC design and VPC Service Controls, IAM and org policies, Cloud Composer, Pub/Sub, Cloud Build, Artifact Registry, Cloud Logging/Monitoring

• Azure, working depth: landing zones per Cloud Adoption Framework, AKS, Azure Storage/ADLS Gen2, Azure Data Factory, Entra ID, Azure Policy, Azure

Monitor, Azure DevOps

• Infrastructure: networking that you can whiteboard from memory — routing, peering, private endpoints, hybrid connectivity, firewall and egress design

• SQL at an expert level, plus Python for tooling and automation

• Terraform in production, with modules you have authored and maintained

• Data modelling — dimensional and denormalised, and the judgement to know when each is right

• Demonstrated ownership of a production platform at meaningful scale: TB-to-PB warehouse, 100+ source systems, or 500+ BI users

• Experience running a multi-cloud or hybrid estate in reality, not just in a diagram

• Client-facing communication strong enough to hold a room of skeptical senior stakeholders

Strongly preferred

• Looker / LookML hands-on: development and administration. This is the single biggest differentiator among otherwise equal candidates

• Dataform or dbt at scale, with a real promotion process between environments

• FinOps track record — a specific cost reduction you can quantify and explain

• Migration experience: on-prem to cloud, or BI tool consolidation (Domo, Tableau, Power BI, Qlik → Looker)

• Exposure to production GenAI or agentic workloads on cloud infrastructure

• Certifications: GCP Professional Cloud Architect or Professional Data Engineer; Azure Solutions Architect Expert (AZ-305); Looker LookML Developer

Nice to have

• Kafka or Confluent; streaming-first architectures

• Databricks, Snowflake, or Fabric comparative experience

• Regulated-industry background (BFSI, healthcare, telco) with the compliance posture that comes with it

• Pre-sales or partner co-sell experience with a hyperscaler field team