Growth Engineer

A Growth Engineer at Supabase takes charge of the entire growth experiment process, from concept to execution. This includes designing A/B tests to boost user adoption and retention, analyzing product data to spot friction points, and collaborating with cross-functional teams to bridge insights with product development. Growth Engineers are crucial for identifying and addressing roadblocks to enhance user success.

To apply for the Growth Engineer position at Supabase, candidates should have experience in growth engineering or a related field, a good grasp of data tools like Postgres and BigQuery, and a familiarity with programming in TypeScript. Previous work in developer tooling or high-growth startups is highly beneficial. Proving your proficiency with Supabase and sharing relevant side projects can give you an edge.

As a Growth Engineer at Supabase, you will be tracking key growth metrics such as user adoption rates, retention, and expansion. You'll leverage tools like PostHog to monitor success indicators and share your insights with the broader team, ensuring constant improvement and alignment with user needs.

Absolutely! The Growth Engineer role at Supabase is fully remote. We promote a culture of autonomy, allowing you to own your roadmap and execution while working from wherever you are most productive.

For the Growth Engineer position at Supabase, candidates should be proficient in TypeScript, as well as SQL with Postgres and BigQuery. Familiarity with post-analysis tools like PostHog, and cloud services such as AWS, would be beneficial. While experience with Supabase is not mandatory, it is regarded favorably.

When answering this question, showcase specific A/B tests you've designed and how they impacted key growth metrics. Be sure to discuss your thought process in determining hypotheses, designing experiments, and evaluating results. Highlighting quantitative outcomes will demonstrate your effectiveness in a growth role.

Discuss your methodology for data analysis, such as using SQL queries to dive into datasets. Explain how you track user interactions, identify trends, and collect feedback to pinpoint barriers. Use concrete examples of how you’ve successfully resolved user pain points in previous jobs.

In your response, reference specific tools you’ve used, such as PostHog, Google Analytics, or custom SQL databases. Explain how you leverage these tools for tracking user behavior, optimizing the funnel, and collaborating with teams to derive actionable insights.

Provide a detailed narrative of a successful experiment. Discuss what metrics you were aiming to improve, the steps you took to design the experiment, the outcome, and the lessons learned from it. Highlighting a growth experiment that yielded significant results will demonstrate your skills effectively.

Be honest about your experience level with the Supabase technology stack. If you have hands-on experience, describe specific projects or tasks you undertook with Supabase tools. Even if it’s limited, express your eagerness to deepen your knowledge and demonstrate competence.

Explain that collaboration is essential for understanding user needs and aligning growth efforts with product development. Discuss examples where you worked closely with product teams, marketing, or developers to achieve common goals. Showcase how teamwork fueled your successes.

Highlight your approach to sharing insights, such as creating detailed reports, visualizations, or presentations. Emphasize the importance of tailoring communication to different team members and stakeholders to ensure clarity and foster understanding of the growth strategies you propose.

Discuss your criteria for prioritizing projects, such as potential impact on metrics, alignment with company goals, and resource availability. Share how you balance short-term gains against long-term growth strategies to provide a comprehensive outlook on your project prioritization approach.

Explain your process from ideation to execution in deploying growth initiatives. Discuss importance of thorough testing, feedback loops, and iterating based on results. Stress the need for a clear roadmap with timelines and safe fail paths to ensure project success.

A failure can often be as informative as a success. Discuss a specific instance where an initiative did not perform as expected. Emphasize the valuable lessons learned, adjustments made, and how you applied this knowledge to future growth projects.