The interview process was smooth. I applied on their website, and a recruiter reached out fairly quickly, stating interest in my background and experience. I was thrilled and was quickly moved onto the phone screen stage.

The phone screen went smoothly. The question was a rudimentary FE product request type of question to quickly wire up. Feedback came back within a few days, and they invited me onsite in SF.

They covered flight and a $400 coupon for Airbnb lodging, with expense reports to submit for food and other miscellaneous expenses afterward. On the day of the interview, I showed up and was greeted by a very beautiful recruiter. She escorted me to the den where they conduct interviews, a small room with an iMac hooked up to the wall and a terrible keyboard and mouse.

Interviewers came one after the other, and in my opinion, they all went very smoothly. I felt like I knocked the FE coding questions out of the park, as they were fairly rudimentary. I did stumble somewhat in the BE coding question, and that threw me off my base a little, but I felt like I rebounded decently well, producing a working solution to the problem set. I thoroughly enjoyed the cross-functional questions, as both interviewers were very polite and welcoming and allowed me to take the conversation anywhere.

All in all, I had a great experience and left their office hoping for and anticipating good feedback. The next working day, I received feedback that they had positive signals but not enough to move forward with an offer at this time. They communicated that they'd be open to revisiting the process in 6-8 months, but I'm sure that's the standard rejection template.

I asked for more details, but the recruiter admitted to not being technical and stated that "code quality and execution" were stated as stopping points. My only takeaway is that the questions may be deliberately easy to test other coding skills that I wasn't being mindful of.

I'm definitely dissatisfied with the result. Usually, I know beforehand whether I performed well or not, and in this circumstance, I wish I could've received more detailed feedback to better understand where they felt things went wrong.

Two front-end coding questions, one back-end coding question.

These are grounded around real-life problems or product requests, not "BS" coding challenges.

Two cross-functional interviews with random personality questions.