Hire Metabase Developers With a Structured Scorecard
Define the work, required evidence, and interview criteria before sourcing Metabase Developer candidates. This guide turns the role into a consistent, auditable hiring process.
Decide whether Metabase is an internal analytics tool, a customer-facing embedded product, or both. Embedding raises the bar: authentication, tenant separation, and survival of schema changes. Ask candidates how they kept dashboards working when a table was renamed, and how they made one filter drive many cards.
Metabase work ranges from building questions and collections for internal teams to embedding analytics into a SaaS product. The skills diverge sharply between those two, so use this guide to choose which one you need and to hold every candidate to the same bar.
What Metabase Developers do day to day
The core work of the role, before tools and titles. Check that your brief, your interviews, and your scorecard all cover it.
Set up Metabase dashboards and questions for business teams
Model data and create clean saved questions and models
Manage permissions, collections, and embedding
Keep queries fast and dashboards trustworthy
Skills to look for in Metabase Developers
Group requirements by area so the job post, the interview plan, and the scorecard test the same things.
01
Metabase
Questions, models, dashboards, and filters.
02
SQL
Native queries and data preparation.
03
Administration
Permissions, collections, embedding, and hosting.
Which specialization do you need?
Most Metabase Developers lean toward one of these. Name the one you need in the brief instead of listing every tool.
Startup analytics
First dashboards for a small team.
Embedded analytics
Metabase dashboards inside a product.
Self-hosted administration
Running and upgrading Metabase.
Metabase role levels and evaluation evidence
Adjust the scope to the actual job. Seniority should reflect decision ownership and system complexity, not years alone.
1
Junior
Typical scope
Entry-level profile with a strong foundation in SQL query building, basic dashboard design, and collection organization.
Knowledge areas
SQLPostgreSQLDashboard DesignData Visualization
What to look for
Hands-on experience building Questions and organizing them into Collections for team consumption. Familiarity with at least one underlying database such as PostgreSQL, MySQL, or Snowflake.
2
Mid
Typical scope
Mid-level profile with proven expertise in Field Filter implementation, embedded dashboard architecture, and native SQL optimization.
Knowledge areas
Field FiltersEmbedded AnalyticsNative SQLAPI Integration
What to look for
Demonstrated ability to implement Field Filters that create dynamic, context-aware dashboard widgets. Experience embedding Metabase dashboards into customer-facing SaaS applications with proper authentication.
3
Senior
Typical scope
Senior profile with deep mastery of dependency graph management, schema migration strategy, and enterprise-scale embedded deployments.
Proven track record managing 50+ embedded questions across production environments with frequent schema changes. Experience architecting multi-tenant Metabase deployments with role-based access control and performance optimization.
What should a Metabase Developer role brief include?
Describe the connected databases, the audience for dashboards, and whether any content is embedded in a customer-facing product. State who manages permissions and who owns the underlying schema. Require SQL and a sound permissions mindset; familiarity with Metabase's interface is quick to acquire.
Connected databases and how often their schemas change
Internal versus customer-facing dashboards and the embedding method
Tenant separation and permission rules needed for each audience
Ownership of collections, naming, and cleanup of stale questions
How should Metabase Developer candidates be compared?
Give every candidate the same sample database and ask for a dashboard with a filter that applies across cards, then ask how they would embed it for one customer without exposing others. Strong answers cover parameter handling, signed embedding, and what breaks if a column is dropped.
Ask for one dashboard filter driving several differently written questions
Ask how they would limit an embedded dashboard to a single tenant
Ask how they would find questions affected by a schema change
Rate SQL quality, security reasoning, and maintainability separately
What to probe when interviewing Metabase Developer candidates
These are risks a weak hire in this role tends to bring. Turn each into a work-sample task or follow-up question that produces evidence for or against it, and score every candidate on the same set.
Can they handle a production environment where the underlying schema changes frequently without breaking 50+ embedded questions?
Have they implemented Field Filters that create truly dynamic, context-aware widgets rather than static dropdowns?
Do they understand dependency graphs well enough to prevent cascading failures across customer dashboards?
Job description template
A starting draft built from this guide. Replace the bracketed parts, cut anything that does not apply, and keep every requirement tied to the work.
Job description template
About the role
[Two or three sentences on the product, the team, and why this role is open now.]
What you will do
Set up Metabase dashboards and questions for business teams
Model data and create clean saved questions and models
Manage permissions, collections, and embedding
Keep queries fast and dashboards trustworthy
What you bring
Metabase: Questions, models, dashboards, and filters.
SQL: Native queries and data preparation.
Administration: Permissions, collections, embedding, and hosting.
Nice to have
Startup analytics
Embedded analytics
Self-hosted administration
Level and scope
Junior: Entry-level profile with a strong foundation in SQL query building, basic dashboard design, and collection organization.
Mid: Mid-level profile with proven expertise in Field Filter implementation, embedded dashboard architecture, and native SQL optimization.
Senior: Senior profile with deep mastery of dependency graph management, schema migration strategy, and enterprise-scale embedded deployments.
How we hire
A structured interview and a short work sample, scored against the same criteria for every candidate.
Full-time, contract, or freelance?
Metabase setup is usually a short project, so a contractor or part-time analyst often fits. Hire full-time when you need an analyst who owns reporting and uses Metabase daily. SQL skill matters most.
FAQ
Frequently Asked Questions About Hiring Metabase Developers
Direct answers for role definition, evaluation, specialist depth, and compensation research.
What is a Metabase developer responsible for?
They build questions and dashboards, write native SQL where the query builder falls short, organize collections, manage permissions, and keep content working as databases change. In product teams they may also embed dashboards into an application and wire up authentication. The brief should separate internal reporting duties from embedding duties.
Which Metabase skills deserve real testing?
Test SQL, field filters and parameters, dashboard design, permissions, and API use. For embedding, test signed token flows and tenant isolation. Also ask about housekeeping: how they track which questions depend on which tables, since that determines whether dashboards survive database changes.
How do I check a candidate's Metabase ability in an interview?
Use a short practical task on a sample database: build a parameterized dashboard and describe the embedding approach for one customer. Keep the data, time limit, and rubric identical for everyone. Ask a follow-up about maintaining the content when a table is restructured.
When is a Metabase specialist worth it compared with an analyst?
An analyst is enough for internal dashboards. A specialist helps when analytics are part of your product, when many embedded questions depend on a changing schema, or when permissions are complex. Senior profiles design multi-tenant deployments and manage dependencies across many questions.
How do I set pay expectations for Metabase developers?
There is rarely a Metabase-only benchmark, so look at neighboring roles: BI developers, analytics engineers, and full-stack developers who embed analytics. Pull postings and recruiter input from your hiring market, date each figure, and weigh how much of the job is embedding versus internal reporting.
ConnectDevs can support discovery and structured interview workflows, but the hiring team remains responsible for the role definition, evidence standard, final decision, compensation validation, and applicable legal review.