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
Technical projects
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




Career development
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
First week
Meet your team virtually and get to know your direct manager
Activate your Greenhouse-provided equipment and understand how to use our IT systems securely
Get familiar with details about payroll and the benefits Greenhouse offers
Join onboarding sessions for a warm welcome to Greenhouse and an introduction to cross-functional teams
First month
Continue learning about cross-functional teams, complete compliance trainings and develop a high-level understanding of the Greenhouse product suite
Deepen relationships with your team members and other collaborators
Develop fluency in the necessary systems and processes
Take part in the existing operating rhythm by joining company and team meetings
First quarter
Wrap up standardized onboarding sessions with cross-functional teams
Learn more about how Greenhouse creates belonging through equitable practices and allyship
Start to identify areas of improvement and think about how your professional development goals map to success in your role
More Engineering resources
In the weeds blog
Read our blog for a more detailed look into how the team operates on a day-to-day basis.
Greenhouse on Glassdoor
Read reviews from candidates on our interview process and reviews from employees on what it’s like to work at Greenhouse.
Greenhouse bug bounty program
Have a security issue to report? We manage our bug bounty program using HackerOne.