My journey to Menlo was a bit different from most. While Menlo’s hiring process is typically 3 steps including an Extreme Interview, a 1-Day interview, and a 3-Week Trial, mine was spread out over my final year of college.
While I was in undergrad studying computer science at the University of New Hampshire, I first heard about Menlo during a weekly stand up meeting with my research team. I was part of a team helping to maintain the Integrated Science Investigation of the Sun (ISOIS) codebase, which processes data from NASA’s Parker Solar Probe (PSP). My supervisor, Jon, mentioned a company called Menlo Innovations that was developing software for the recently launched Interstellar Mapping and Acceleration Probe (IMAP) NASA mission. He spoke highly of Menlo’s methodology, especially paired programming.
A few semesters later, Jon showed me the software Menlo was building for the IMAP mission: CAVA, a plotting tool that helps scientists quickly visualize and analyze data from the IMAP and PSP missions to study solar wind. The solar wind, which is the charged particles emitted from the sun that cause the Northern Lights and sometimes disrupt power grids, can be visualized with CAVA to show activity across the heliosphere, the magnetic bubble that shields our solar system from cosmic radiation.
That summer, Jon asked me to test a new CAVA feature that let advanced users write Python scripts to transform data in custom ways. Around the same time, I was considering topics for my senior computer science thesis. Jon suggested pairing remotely with Menlo developers to contribute to CAVA and explore Agile software development in practice. The idea fit perfectly, and Menlo agreed to be a part of the experiment.
I was eager to begin and curious to learn firsthand how Agile and paired programming come to life in a professional environment. I’d only experienced pairing a few times and I worried I wouldn’t have much to contribute; every codebase has its quirks, and I’d heard it can take weeks to feel confident working in a large project.
When the day of my first pairing arrived, I joined a Google Meet and met my Menlo pair partner for the afternoon. After a quick setup of Menlo’s remote connection software, he walked me through their process and rhythm. We started on a part of the codebase that was new to both of us, but he had enough context to guide our next steps.
My nerves quickly faded. Together, we figured out how our task fit into the larger system. Before we wrote any code, my partner reminded me to start with a test, a cornerstone of Menlo’s test-driven development process. He showed me the structure and reasoning behind it, and soon we were writing production code to make the test pass.
That first session left me energized and eager for more. My partner’s patience and openness made learning easy, and I soon realized those traits weren’t unique to him—they were part of Menlo’s culture. Through continued pairings, I experienced Agile development in a way no classroom could replicate. Working alongside seasoned developers showed me how Agile truly functions when it’s lived, not just taught.
As I conducted research for my thesis, I learned that many teams struggle when methodologies become rigid rituals instead of flexible tools. Menlo’s approach stood out because they constantly refine their processes to support people and adapt to what actually works, both for their team and their clients.
By the end of my senior year, I knew Menlo was exactly the kind of company I wanted to join. I decided to apply, and began preparing for the Extreme Interview process and even looked up flights to Michigan for the 3-Week Trial. Instead, during a Zoom call, the team surprised me and let me know they wanted to bring me on board without the formal interviews, already seeing my year of pairing as an extended interview.
Now, after joining full-time in July, my appreciation for Menlo’s philosophy has only deepened. I’ve worked on new projects and seen firsthand how the team adapts its methods to each client and context. There’s still so much to learn, but I know I’m surrounded by people, and a culture that makes that journey possible.