The interview process began with a one-hour phone interview featuring three questions, followed by five one-hour on-site interviews, including lunch.

The phone interview consisted of fairly easy questions, drawn from LeetCode and CTCI.

The on-site interviews presented a mixed experience:

• Two coding interviews
• One hiring manager interview
• One system design interview
• One technical communication round

Having interviewed at many companies and conducted numerous candidate interviews myself, I have never encountered such an unprofessional display of character.

The first coding interview involved a "master" interviewer and an "apprentice." While the questions were relatively simple, the interviewers' behavior was pathetic. The "master" interviewer exhibited a condescending attitude and demonstrated poor interviewing skills. Both interviewers laughed at my answers, and their conduct was disgraceful. They are ill-suited for conducting interviews and need to develop better soft skills.

The system design interview was not as problematic, but it featured two inexperienced engineers. It appeared the "master" interviewer had decided against engaging with me within the first five minutes. System design interviews are intentionally vague, expecting candidates to elicit information, but a lack of dialogue leaves the candidate lost. When I asked the "master" for specifics, she responded, "What kind of specifics?" It was evident she was not listening. They also struggled with common terminologies like "Cloud Management Platform."

System design interviews should be conducted by engineers with at least 5-6 years of industry experience, not by individuals with only a couple of years in the field. They lack the experience to recognize that open-ended problems have multiple solutions, each with its own trade-offs. Their approach seemed to be "my way or the highway." While they might be competent coders, true professionalism extends beyond sitting at a computer and writing code.

During lunch, I was accompanied by a very senior engineer who was a gentleman. The company boasts an excellent cafe and provides good employee care. The other interviews proceeded well, and I have no complaints regarding them.

The Tools team appears to be a positive environment. New projects are determined organically and from the bottom up, with the team deciding on features and improvements rather than management dictating objectives. Everyone seems passionate about their work, suggesting it's a good place to learn.

Considering the entire experience, I do not believe I received a fair evaluation. It is disheartening that the choice of interviewers can significantly impact a candidate's chances. Had I been interviewed by more mature professionals, the outcome might have been different.

Interviewers must respect candidates' time rather than acting imperiously. While some junior engineers at this company seem to forget their responsibilities and use interviews as an opportunity to boost their egos, they have important duties to fulfill.

Expand a URL that has a pattern with CSV values or ranges. For example: www.linkedin[1-4, 6,8].com needs to be expanded to [www.linkedin1.com, www.linkedin2.com, www.linkedin3.com, www.linkedin4.com, www.linkedin6.com, www.linkedin8.com].

Resolve references in a dictionary. A variation of DFS.

Given an array of numbers, determine if there is at least one triplet that can form a triangle.

Given a set of points, find the maximum number of collinear points.

System design: Design a service deployer. Me: "What kind of services? Can you give me some specifics?" Interviewer: "What kind of specifics?" Me: Perplexed

Phone interview: Check if a string is a reversal of another, merge two sorted lists in a Pythonic way (i.e., using yield), print all IP addresses in a log file.