Engineering at Greenhouse
Our engineering culture fosters an environment of learning and focus on personal growth by both teaching and learning from each other. We are continuously reflecting on ways to better our code, our processes and ourselves.
Learning and development
We value a learning culture, where people are continuously improving, so we can become better humans and technologists. The entire team contributes to each other’s growth in many ways, such as:
- Regular lunch and learns where team members present on topics they are excited about
- Grassroots learning initiatives started by individuals on the team
- A yearly learning and development budget for each person to use on things like books, workshops and conferences related to technology, communication skills, management skills and more
Engineers at Greenhouse work with high autonomy on technical projects to address customer requests, mitigate and prevent performance issues, improve developer workflows, scale our services and more. Some projects that are currently in production:
- An internal high volume document processing service written in Go to convert Word documents to PDFs for use in our customer-facing applications
- Production and development applications managed via an internal deployment platform built on Kubernetes, Docker and AWS to give developers fine-grained control, allowing us to deliver stable and performant services
- Running multiple instances of Greenhouse Recruiting to keep pace with a growing customer base, enable scaling of our web application and data stores, adhere to security requirements and set ourselves up for global availability
We do our best to help people figure out how to get the most out of their time at Greenhouse. We use structured, skills-based career ladders to coach and promote people and offer opportunities to explore different career paths. Here are some of the things people have done:
- Internally, we’ve had colleagues join us from Sales, Customer Support, and Account Management and find their place on the engineering team
- Engineers have switched between being individual contributors and being managers and are supported in whatever path they choose
- Engineers have done short-term rotations on, or have moved between, various teams such as Infrastructure, Solutions, Performance, DevOps and Product Engineering
Our interview process
We use a structured interviewing process so that all candidates have a fair chance to assess Greenhouse and show us their abilities through practical exercises relevant to their role. Learn more about what to expect when you interview at Greenhouse.
We take onboarding seriously
Starting a new job can be stressful, so we guide people through all the ins and outs of our onboarding process. Here's what usually happens:
Your first few days
Before you start, log onto Greenhouse Onboarding to check out company resources.
- Review your onboarding schedule for your first week
- See who’s on your team
- Understand our policies and benefits (health insurance, PTO, etc.)
Your first day – it'll fly by!
- Meet your new hire buddy – They’ll answer your questions about processes and how to get things done to help you get started
- Meet your team – They’ll get you settled and set up with your development environment
Your first week
- Engineering – Learn about the functions your team owns and how they work when shipping something to production
- Other departments – Learn what they do and how it all fits together
- Our products – Learn about the suite of products we build, the ideas behind them and why they matter
- Get to know your team during virtual 1:1 coffee or water cooler chats with every member of the team
- Start regular 1:1 meetings with your manager and talk about goals
- Get acquainted with team meetings like standups, planning meetings, and retros
Three months and beyond
- Become knowledgeable in the product, codebase and business – ask lots of questions and keep shipping
- We hope you feel like you’re part of the team and can contribute to your team’s goals!