Faire Software Engineer Interview Questions
& Process

I applied online and had a phone screen with the recruiter. After that, I did a technical interview on CoderPad. They sent a prep guide that was 18 pages long, mostly about graphs and topological sort (like the Alien Dictionary problem) and basic data structures, mentioning arrays. But the actual interview was about interval scheduling using sweep line algorithms, which was way more advanced than what the prep guide covered. It wasn't basic array stuff at all. I didn't know the pattern, and even with hints, their explanations weren't clear. They asked if I had questions with 5 minutes left instead of letting me finish. I got rejected soon after. The prep material didn't match the actual test, so I couldn't show what I know.

The interview process began with an asynchronous coding interview featuring four leetcode-style algorithmic questions of increasing difficulty. This was followed by a second step with three parts. The first part involved a technical question presented by two potential team members, with a one-hour time limit for a solution. The second part focused on cultural fit, where the company's background was explained, and hypothetical scenarios were used to gauge reactions; this lasted 30 minutes. The third part was another technical question, this time with a member from a different team, also with a one-hour time limit. Approximately 5-6 days later, an offer was extended, and negotiations commenced. The overall experience was positive, with friendly and supportive interviewers, even accommodating minor technical issues.

The interview process starts with a recruiter call, followed by several coding interviews that they call pair programming. The process felt broken to me. I was able to solve all the Leetcode medium problems presented in the hour-long sessions. I asked clarifying questions to ensure alignment. I felt good about my performance, but they later told me interviewers thought I asked for too much help and suggested I practice more Leetcode. This is unbelievable. What thought process are you assessing if I just memorize solutions? Why would I go to your office for the same shared code editor thing as the phone screen, but with someone physically present? As a full-time employee, I'm not wasting my time memorizing impractical problems. I'd rather discuss my experience, technical challenges, past and current projects, open-source contributions, system design, and leadership. Does asking a question I know well but you don't make me inept? It was a waste of a vacation day.