Head of Growth
About SqlDBM
SqlDBM is the enterprise data modeling platform built for collaborative data teams. We give data architects, engineers, and analytics leaders a single place to design, govern, and document their data estate: from conceptual and logical models through physical schemas and the semantic layer that sits on top of them.
We work natively with the modern data stack: Snowflake, Databricks, Google BigQuery, Microsoft Fabric, Azure Synapse, and Amazon Redshift, alongside Oracle, Teradata, SQL Server, PostgreSQL, and MySQL; with integrations into dbt, GitHub, GitLab, Jira, Confluence, and Collibra.
The problem we solve is easy to state and expensive to ignore: in most enterprises, data is built everywhere and defined nowhere. As more of the business runs on cloud data platforms, and as AI agents increasingly depend on trustworthy metadata to be useful at all, the modeling and semantic layer has moved from a nice-to-have to a control point. That shift is why demand is accelerating, and it is why we are creating this role.
About the role
We are hiring a Head of Growth to own everything that happens before an opportunity reaches an Account Executive. You will be accountable for all pipeline: its volume, its quality, and its predictability. You will build it through two engines: a repeatable outbound and inbound motion run by our BDR team, and a partner-sourced motion that you will build and personally carry before you scale it.
This is a builder's role. The BDR function is two people today. The partner function is one person. You will inherit a product with real enterprise pull and customers who reference well; what is missing is the system that converts that pull into a forecastable stream of qualified pipeline. You will design that system, run it yourself first, and hire against it as it proves out.
You will report directly to the SVP of Sales & Customer Success and work shoulder to shoulder with Sales, Customer Success, Marketing, and Product.
What you'll do
- Pipeline: you own the number
- Own the company's pipeline target: sourced, qualified, and accepted
- Build and maintain the model that connects activity to pipeline to closed revenue, so we know which levers actually move the number and which are noise.
- Report pipeline health to the leadership team with a clear read on coverage, conversion, velocity, and where the leaks are.
- Allocate your team's capacity deliberately across net-new logos, partner-sourced deals, and expansion in the installed base.
BDR team: build a repeatable outbound motion
- Lead, coach, and grow the BDR team (two today), with a hiring plan tied to proven capacity and conversion rather than headcount ambition.
- Design the outbound playbook: ICP definition, account tiering, territory and named-account coverage, persona-level messaging for data architects, heads of data platform, and analytics engineering leaders, sequence and channel mix, and the objection handling that comes with selling into technical, skeptical buyers.
- Build the operating discipline underneath the playbook: activity standards, call and email QA, discovery frameworks, qualification criteria, and CRM hygiene so performance is coachable and results are diagnosable rather than anecdotal.
- Own inbound execution with the same rigor as outbound: speed-to-lead standards, routing rules, lead scoring, and a follow-up cadence that means no hand-raise goes cold. Inbound is our most expensive lead source and will be treated accordingly.
- Run the ramp: onboarding, product and domain certification, and a 1:1 and pipeline-review rhythm that makes a new BDR productive quickly.
- Make the role a career step. BDRs you develop should become the AEs and partner managers we promote from within.
Partners: player and coach
- Own a personal partner-sourced pipeline number while building the function around it. In the first year you will be sourcing, negotiating, and activating partner relationships yourself, with