Job Opportunities API

About Brilliant   Brilliant is creating a world of better problem solvers. We deliver learning that's interactive, adaptive, and fun – at scale. You can learn more about our approach, learners, and method on our about page.   We have always prioritized building a real, healthy business, and we make hires very selectively and intentionally. We serve hundreds of thousands of paid subscribers, and want you to help us serve millions.   In our day-to-day, we value adventure, excellence, generosity, and candor. We are optimists in the face of uncertainty, we take pride in our work, we go the extra mile for each other, and we tell it like it is (the good and the bad). We’re here to do the best work of our lives together.   We believe that real-time collaboration and human connection are necessary ingredients in building a high-velocity, high-trust team. We maintain core hours (9:30am - 2:30pm Pacific) when everyone is online, regardless of timezone. About half of us are located near our hubs in SF and NYC.   In addition to what’s below, you can see all open roles and learn more about our culture on our careers page. The Role   Note: This particular posting serves as a "future consideration" form for engineering, as opposed to a formal application to any current openings. Unfortunately, we are not hiring early/mid-career software generalists at this time.   Engineers at Brilliant work in small, elite teams alongside colleagues from Product, Design, and Data to achieve the best possible outcomes for our learners and business. While we’re already happy with our current team size and velocity, we occasionally hire exceptional software engineers with demonstrated histories of transformative impact to further elevate the team. You can apply to this role to be considered for such opportunities in the future.   Engineers we’ve hired through this general interest form in the past include former founders, early employees who grew into staff engineers at companies that achieved massive growth, and experienced engineering leaders who returned to the individual contributor path. These sorts of folks make up a significant percentage of our current team, and we’re interested in talking with more of them to explore what sort of transformative impact they might be able to achieve here.