Greenhouse is an innovation team focused on tackling complex and persistent challenges in education. As a mission-driven, not-for-profit organization, College Board’s mission is to clear a path for all students to own their future. We serve 7 million students each year and partner with thousands of member institutions to expand access to higher education and support college and career readiness. Through Greenhouse, we are investing in building scalable, sustainable, and human-centered solutions that can drive meaningful progress in education.
Despite decades of effort across K-12 and higher education, major challenges persist. Student outcomes have remained largely unchanged in key areas; chronic absenteeism has increased, and fewer than 40 percent of community college students complete a credential within six years. At the same time, institutions face growing pressure from shifting demographics, questions about the value of postsecondary education, and the rapid impact of emerging technologies like AI.
Greenhouse exists to take on these challenges directly by identifying high-impact opportunities and developing solutions that can improve outcomes for learners, particularly those underserved by existing systems.
Our team brings together a unique mix of product leaders, engineers, and service designers, many of whom come from startup environments and public service. We operate in small, cross-functional teams with a shared commitment to human-centered design, rapid learning, and building alongside the users we serve. As a team, we value curiosity, candor, and shared ownership, and we are continuously shaping how we work as we build new solutions and contribute to broader innovation across College Board.
Greenhouse Engineers work day-to-day within our Greenhouse teams, while remaining part of our Engineering organization. That keeps your career path, technical standards, and peer network within our engineering track. Like every College Board technology team, Greenhouse is organized around products, not projects: our teams own what they build and keep making it better. We expect every engineer and architect to keep learning as the field moves, and we invest in that growth.
Falling behind on technology means falling behind on talent: the best technologists want to work with modern tools, not legacy ones. Staying current isn't optional for us.