Mass interview, then one day pairing with other developer, before final interview. I thought that the second phase of the interview process was not conducive to people in there early career.

They typically use the Xtreme Interview process which is a group interview process, where Menlo employees observe candidate's behaviors when they interact with each other (i.e. kindergarten skills) and how they approach solving a problem. There is no directly technical aspect to this interview. The candidates are then reviewed by all observers who participated via are ranking using descriptions of behaviors that they exhibited. Depending on staffing needs, a subset of candidates are invited back for One-Day Interviews, where a candidate pairs with two Menlonians (first half and second half of the day) either working on a contrived internal project or genuine project for a client or to supplement Menlo's needs. There is also a lunch where other Menlonians join in to meet the candidate - there is no explicit interview process surrounding the lunch and it is relatively casual. Finally there is a 3-week 'interview' process to help Menlo and the candidate gauge whether they are a good fit for company culture and if they are adjusting to paired programming. The candidate actively pairs with a variety of Menlonians and potentially works on a variety of projects. Depending on performance, the candidate may get a offer or rejection prior to completion of the 3 weeks. For both the 1-day and 3-week interviews the candidate is paid hourly. There are occasionally circumstances where candidates may circumvent the interview processes via connections/previous engagements or if there are problems around scheduling - do not rely on this as there are many candidates who do not have scheduling conflicts. Furthermore, the interview process is not applied to summer employees (college students), albeit getting one of these positions typically requires having a strong connection to someone at the company.