Country or region and language

    Choose your country or region and your language.

    Suggested for you

      All countries and regions

        Choose your character

        It shows in the top bar and on your profile. Change it any time.

        Interviews in Looker and LookML

        Work in the tool while you explain your decisions.

        Choose a role and level. Each interview has a new task, follow-up questions and a report that checks your work and your explanation.

        Speak or type. Sign in to save your results across devices.

        Timed assessment

        • 12 practical questions
        • 45 minutes
        • Mid level

        Questions are drawn from a bank of 36. Your report includes a skill breakdown and lessons to practice next.

        Practice interviews

        Junior tasks cover the fundamentals. Mid and senior tasks add debugging, changing requirements and review decisions.

        10 interviews

        • BI developer
        • Junior
        • 30 min

        A channel revenue handoff

        Build the regional sales handoff with channel as the only dimension and total order revenue as the measure. Keep only complete orders in the assigned region. The assigned region is North.

        Start interview
        Skills and rubricA channel revenue handoff
        • I group complete orders by channel and sum revenue within the assigned region because the handoff needs channel sales at that population. I check that the channel totals add back to the source revenue for the same region and status.
        • I keep customer ID out of the grouping because one customer can place several orders and the requested output has only channel grain. I check that adding an extra dimension would split the channel totals, while order count would measure volume instead of revenue.
        • I retain the source records, the saved work and the checked output because another analyst must be able to reproduce this result. I record the observation window and the unresolved limitation. The decision owner approves any exception before this result changes a business action.
        • Analytics engineer
        • Junior
        • 30 min

        Average ticket and unique customers

        For the assigned region, show average order revenue and distinct customer count by channel. Keep every status. Do not replace customers with order count. The assigned region is West.

        Start interview
        Skills and rubricAverage ticket and unique customers
        • I use average order revenue and count distinct customer IDs by channel because ticket size and customer reach have different denominators. I retain every status and the assigned region, then check repeat customers and NULL IDs separately so missing customer identity doesn't remove an order from the revenue average.
        • I compare distinct customer IDs with order count because repeat customers make those totals differ. I also check orders with NULL customer IDs: their non-NULL revenue still belongs in average ticket even though they contribute no identified customer. The two measures therefore need separate denominators.
        • I retain the source records, the saved work and the checked output because another analyst must be able to reproduce this result. I record the observation window and the unresolved limitation. The decision owner approves any exception before this result changes a business action.
        • Data analyst
        • Junior
        • 30 min

        A reusable contribution field

        Add a numeric contribution dimension equal to order revenue minus order cost, then add total_contribution as its sum measure. Query total contribution by channel for complete orders in the assigned region. The assigned region is East.

        Start interview
        Skills and rubricA reusable contribution field
        • I define contribution as revenue minus cost and sum that numeric field because the model must reuse the same row calculation in every channel. I retain NULL contribution when revenue is NULL, then check field types and reconcile the grouped contribution to the eligible source rows.
        • I check contribution against revenue less cost on the changed fixture because small totals can conceal reversed subtraction or cost deducted twice. I compare row calculations before the channel sum and retain NULL when revenue is missing, so a plausible grouped total can't substitute for the correct arithmetic.
        • I retain the source records, the saved work and the checked output because another analyst must be able to reproduce this result. I record the observation window and the unresolved limitation. The decision owner approves any exception before this result changes a business action.
        • BI developer
        • Mid
        • 30 min

        A completion-safe revenue definition

        Create completed_revenue as a sum measure of revenue with a measure-level status filter for complete. Run it by channel in the assigned region without an Explore status filter. The assigned region is North.

        Start interview
        Skills and rubricA completion-safe revenue definition
        • A correct-looking query-level filter does not repair a reusable measure. A later unfiltered Explore would expose the missing measure filter.
        • I add a second filtered revenue measure for returned orders and retain the completed definition. I avoid a global completion filter because it would remove returned rows before that second measure can use them.
        • I retain the source records, the saved work and the checked output because another analyst must be able to reproduce this result. I record the observation window and the unresolved limitation. The decision owner approves any exception before this result changes a business action.
        • Analytics engineer
        • Mid
        • 30 min

        Retain unassigned customer orders

        Repair the customer join so the Explore retains orders without a matched customer. Join customer_id to customers.id at many-to-one cardinality. Report completed revenue by customer segment and channel.

        Start interview
        Skills and rubricRetain unassigned customer orders
        • I check both an unmatched order and an order whose ID happens to equal a customer ID because coincident values don't establish the join key. I keep the customer_id relationship and compare the left join with an inner join to identify the revenue that the narrower population would remove.
        • I make the narrower population explicit and use an inner join or a documented non-NULL customer restriction. I reconcile the excluded order revenue before comparing the two reports.
        • I retain the source records, the saved work and the checked output because another analyst must be able to reproduce this result. I record the observation window and the unresolved limitation. The decision owner approves any exception before this result changes a business action.
        • Data analyst
        • Mid
        • 30 min

        A fanout-resistant category review

        Repair the orders-to-items semantic join so revenue remains correct when category is selected. Declare a primary key on orders.id and an orders-to-items one-to-many relationship. Compare order revenue and item amount by item category.

        Start interview
        Skills and rubricA fanout-resistant category review
        • I check an order with several items in one category because an ordinary joined sum would repeat its order revenue. I also compare different orders with equal revenue so deduplication must use order identity rather than the revenue amount. Each order contributes once within a category, while item amounts retain item grain.
        • Not automatically. One order can belong to more than one category, so category groups overlap at order grain. I run an ungrouped order total and explain the overlap rather than adding category totals.
        • I retain the source records, the saved work and the checked output because another analyst must be able to reproduce this result. I record the observation window and the unresolved limitation. The decision owner approves any exception before this result changes a business action.
        • BI developer
        • Mid
        • 30 min

        A customer-grain completion summary

        Create a customer_sales derived view from complete orders. Select customer_id and SUM(revenue) AS sales grouped by customer_id. Add customer_id as a dimension and sales as a sum measure, then expose the customer_sales Explore.

        Start interview
        Skills and rubricA customer-grain completion summary
        • A customer can have both returned and complete orders. Aggregating first without the status predicate changes the sales definition. NULL customer IDs form their own group rather than becoming a real customer.
        • I include region in both the derived SELECT and GROUP BY and expose it as another dimension. I document that the derived grain is now customer and region before joining or reusing the summary.
        • I retain the source records, the saved work and the checked output because another analyst must be able to reproduce this result. I record the observation window and the unresolved limitation. The decision owner approves any exception before this result changes a business action.
        • Analytics engineer
        • Senior
        • 30 min

        A region-restricted Explore

        Add an access_filter on orders.region driven by the region user attribute. Run channel and total revenue without an editable region filter. The assigned attribute should constrain every query from this Explore. The assigned region is West.

        Start interview
        Skills and rubricA region-restricted Explore
        • The same access filter should use the second user attribute without editing the model. I test both identities and the missing-attribute case, then retain the allowed row sets as evidence.
        • I retain the source records, the saved work and the checked output because another analyst must be able to reproduce this result. I record the observation window and the unresolved limitation. The decision owner approves any exception before this result changes a business action.
        • An editable Explore filter is not an access boundary. Removing it would expose other rows. A hard-coded region also fails when another authorized user has a different attribute.
        • Data analyst
        • Senior
        • 30 min

        A two-view operations dashboard

        Build an Operations handoff dashboard with two table tiles: Revenue by channel and Orders by region. The first uses channel and total revenue; the second uses region and order count. Apply complete as a dashboard status filter and use the assigned refresh interval. Set the refresh interval to 6 minutes.

        Start interview
        Skills and rubricA two-view operations dashboard
        • I revise the filter mapping or create a separate section so the pending tile is not constrained to complete orders. I test all tiles after changing the shared control and label their populations.
        • I retain the source records, the saved work and the checked output because another analyst must be able to reproduce this result. I record the observation window and the unresolved limitation. The decision owner approves any exception before this result changes a business action.
        • I compare each tile query with its title because a correct label can sit above the wrong measure. I check order count separately from revenue and confirm that both receive the completion filter. The refresh interval only controls this local report setting; it doesn't prove that the warehouse source has fresh data.
        • BI developer
        • Senior
        • 30 min

        A bounded Data Studio ticket report

        In Data Studio (formerly Looker Studio), use orders as the source, channel as the dimension, and revenue with AVG aggregation. Use a bar chart for complete orders, the assigned October date range, and viewer credentials. Leave the blend key empty. Use 2026-10-03 through 2026-10-18, inclusive.

        Start interview
        Skills and rubricA bounded Data Studio ticket report
        • I remove the channel breakdown, change revenue aggregation to SUM and choose a scorecard. I keep the same date and completion scope so the new total answers a different question over the same population.
        • I retain the source records, the saved work and the checked output because another analyst must be able to reproduce this result. I record the observation window and the unresolved limitation. The decision owner approves any exception before this result changes a business action.
        • SUM revenue gives channel sales, not average ticket. The date range changes the source population, while a blend key is unnecessary for a single-source report.

        Interview Hub access

        The Interview Hub is included in All Access. Choose a plan or sign in to your account to continue.

        View plansSign in or join

        Your Work Gym account

        Save your progress and pick up on another device. Your browser's progress comes with you.

        or

        You can keep practicing without an account.

        Change your plan

        Checking the price

        Help and feedback

        Ask a question, tell us what is not working, or share an idea. We reply by email.

        What is it about?

        We use it only to reply to you.