My favorite interview experience was with my current company. Highlights:<p><i></i>1st Interview:<i></i><p>Lunch interview with my boss. Conversation was casual, covering my background & goals, the leadership's background, and the tech stack. After lunch we expanded a little on our conversation with a showcase of certain features of the company's product.<p><i></i>2nd Interview:<i></i><p>Met with the company's founder for about an hour, followed by individual meetings with a few engineers. During the meeting with the founder we exchanged some background information and I was shown some info on the company's performance thus far; this was huge personally as transparency had become a huge pain point with my previous employer. The engineering meetings went smooth; I'd consider them casual but the technical discussion was more in-depth than the 1st interview.<p><i></i>Code test:<i></i><p>After the 1st Interview I was given a take-home code test; building a simple card game using the MEAN stack (shuffle deck, deal cards, score game based on card's position relative to a brand new deck, store results & calculate ongoing average). It took me about 12 hours over the course of a week (evenings mostly - I was employed during this interview) to complete. Since our product has no relation to card games, IMO the code test sought to prove that:<p>1. I was capable of taking a spec to code completion<p>2. I was capable of working within the confines of the company's tech stack (MEAN)<p>It took my boss less than a day to review my submission before offering me a position on his team.<p>Aside from my best interview experience, I've had some not-so-great experiences, here's a few that I encourage avoiding:<p>- No call, no show. Be mindful of your schedule and if you can't keep the commitment, inform the candidate. Candidates hate wasting their time, especially if they're still employed since it usually means taking time off.<p>- Impromptu skill evaluations. If you tell a candidate that the 1st round interview is going to be non-technical, then they're going to prepare accordingly. Shotgun questioning is not well received.<p>- Surprises on code tests. If your code test is going to measure one's ability to work within your stack, make sure the technologies come up during the interview conversations prior to issuing the code test.