The process was very simple. They conducted a quick call to determine interest in a technical phone screen, and then scheduled a code-sharing technical phone screen with one of their engineers.

I rate the overall experience as negative because my interviewer attended a very prestigious math/science university in the Boston area and had interned at a FANG company. He was bored, and he couldn't hide it during the technical phone screen.

I've had many experiences with phone screens, and they generally fall into one of a few categories:

• Helpful interviewer, reached on-site.
• Bored interviewer, still reached on-site.
• Helpful interviewer, failed to reach on-site.
• Bored interviewer, failed to reach on-site.

This experience fell into the last category.

I believe most interviewers, when they know they won't advance a candidate to the next round, should focus on being friendly and helpful for the remainder of the technical phone screen. Some interviewers remain like a mute fish, which is how my interviewer behaved. Meanwhile, he spoke at length about their culture and how friendly it is. It was a classic case of ingroup/outgroup mentality.

You start with a straightforward OOP question: designing a class with a constructor. The company makes sensors for shipping and trucks, so the class was for a Trailer and a Container. You perform some simple functions related to adding containers to the trailer. Then, you move to a function where they want to know how to determine a Trailer's weight at any given time.