First you speak to a HR for culture fit. Second they make you build a Rails Todo app and a Weather App in React. They told the recruiter I was not technically adept enough even though they didn't review the PR or check off their internal boxes for the Rails App. They "reviewed" the weather app an hour after another team member told me they'd review it next week. Asked me why I didn't use state management for a SPA with one input field and then asked me how I could overcome the problem in the api of cities with the same names. ~~~ THEY DIDN'T LOOK AT THE CODE BEFORE ASKING QUESTIONS ~~~ I had built the weather app using the zip code option in the API which solves this problem. Had they actually looked before asking questions, the question wouldn't have been asked. Lets recap: They weren't communicating internally before reviewing (next week vs. an hour later) They didn't look at the code properly before asking questions. They didn't review the other app at all. Don't interview here. Their engineering team clearly has communication issues and problems reviewing code after asking you to make two applications for them.

Interviewing at Contently was an exciting and friendly experience. The process consisted of two phone screenings, and two in-person meetings. The first phone call was with the Director of People Operations and lasted about 20 minutes. We discussed my basic background, items on my resume, and why I was interested in the position. The second phone screening was later that afternoon with the VP of Engineering. In this phone call, we talked more about my technical skills and web development background–including specific examples of my work and how I approached programming related problems in the past. After these phone screenings, I was invited to the office to meet 1-on-1 with members of the team I would be working with. In these interviews, I was asked more about my background, coding questions related to TDD and refactoring, along with my career goals for the future. The team made me feel very comfortable and allowed me to ask many questions about their individual backgrounds, standards of code quality, how they collaborate, and more. My final interview and second in-office visit consisted of a short, 15-minute pair programming session and a meeting with two of the co-founders. The pairing was by-far the best technical interview I've ever had–it allowed me to gain an understanding of their code base while also illustrating how I would approach a given problem. Lastly, speaking with two of the co-founders gave me a high-level view of the company, its background and future goals. Overall, my experience interviewing with Contently was extremely positive–they made plenty of time to answer all of the questions and I could tell they cared deeply about finding a mutual fit for the role. It's the type of place where you wake up excited to go to work every day.