General notes
You’re being considered for a position on Visor’s growth engineering team. We consider every part of the customer’s experience to be a part of our product. That includes both the core application (the actual Visor collaboration software) as well as our other customer-facing experiences in our ecosystem. However, we’ve chosen to split our engineering team between those who build and maintain the core application (”application engineering”) and those who build and maintain our ecosystem (”growth engineering”).
Why we have a dedicated “Growth engineering” team
While some companies have an engineering team that occasionally works on growth engineering tasks, we believe the work of growth engineering is so important that we should have a team dedicated entirely to this high-priority work.
The following are areas owned by growth engineering:
- The billing and subscription management system
- Our marketing automation system (including email marketing)
- The onboarding checklist, guides, and helpers inside the core application
- Our marketing website (www.visor.us)
- Our landing pages for SEM
- Our blog
- Our template system
- Our knowledge base & video guides
- The telemetry and analytics systems across the entire ecosystem
How this team collaborates with others
As a member of Visor’s growth engineering team, you’ll be a business-minded engineer. You’ll need to understand the principles of marketing applied by your colleagues on the marketing team. And you’ll be the bridge between marketing & growth goals and engineering implementation. You can expect to work cross-functionally with content marketers, digital marketers, product marketers, product managers, and designers.
For example, Visor’s main strategy for acquiring customers is based on inbound marketing. Our goal is to make it likely that customers will easily find us when browsing online for solutions to problems our product solves. While our marketing team will be focused on ensuring our content improves our ability to rank in searches (SEO), our growth engineering team will be responsible for choosing and maintaining an architecture that boosts SEO. And you’ll be collaborating with the others to ensure that everything we do connects in a way that maximizes SEO — from product release notes to email marketing.
How this team collaborates with the core application engineers
Given our scale, it will still feel like we have just one engineering team. We’ll still meet all together (typically for 3x per week standups). We also share the same planning and pipeline for work. The main difference is just regarding what priorities each team takes on.
Our tools for growth engineering
Here are some of the technologies we work with today:
- HubSpot
- Stripe
- Salesforce
- Google Ads
- Metabase
- Webflow
- Vimeo
We’ve also built many in-house solutions, including for:
- In-app analytics and telemetry
- Onboarding checklists
- Feature explainer guides
- Video tutorials
Tips for the technical interview
We run identical technical interviews for members of our core application engineering team and our growth engineering team. That’s because our technical interview is designed to test your general cognitive abilities — not necessarily any specific knowledge you have.
Here are some important topics that may come up on our technical interviews:
- Classes
- Promises
- Symbols
- Proxies
- Arrow functions
- The … operator (rest/spread)
- Maps / Sets
- Default parameters
- Arrays
- Strings
- Dates
- Scope & hoisting
- Debugging
You’ll have an opportunity to demonstrate your specific skills relevant to this engineering team later in the interview process during the take-home project.
Tips for the take-home project
The take-home project for growth engineers involves creating a ground-up system for enabling non-technical marketers to quickly create stylish, SEO-optimized landing pages. You’ll be asked to use VueJS and design a system.
We’ll provide more information to you when you get to this point in the interview process.