Weedmaps Software Engineer Interview Questions
& Process

A recruiter found me on LinkedIn and initiated contact. They first did a phone screen that was like a "tech trivia" quiz, covering Ruby on Rails. It was a bit amusing when they asked me the standard difference between a stack and a queue. Following that, there was a take-home coding assignment that I had 5 days to finish. The instructions recommended a maximum of 4 hours of work. I had to create a completely new boilerplate project from scratch since no starter code was provided. The assignment involved building an API, writing unit tests, and setting up a database. There was also a "Bonus" section where I could add an image upload endpoint and deploy the application to Heroku. Honestly, I can't fathom how anyone could complete the bonus part, let alone the main assignment, within the suggested 4 hours. Another odd requirement was submitting it as a new GitHub repository with well-documented commit messages, apparently to assess the commit history.

They started with an HR screen that included one easy data structures question. Then, there was a dev screen with easy questions to confirm Rails/Elixir experience. After that, a take-home assessment was given, with 72 hours to complete. The task was a straightforward CRUD app without user authentication, offering bonus points for file uploading, deployment, or a frontend. A heads-up: meeting all explicit requirements and bonus points might not be enough, as reviewers can penalize for things like not knowing basic commands (cd/ls), using default frontend styling, or not meeting unspecified code coverage standards. They might even use added code coverage dependencies against you, and ultimately, they might reject your submission based on styling preferences.

Really awesome company, the interview experience was fantastic. I was super impressed by the company and everyone I met. Definitely stood out among the companies I interviewed with – very professional, super driven developers, and a genuine culture. Wasn't where I initially thought I'd end up, but so glad I applied. The recruiter was friendly, knowledgeable, and responsive, doing a great job communicating throughout. They were flexible with scheduling across timezones. The whole thing moved fast on their end, about a month and a half, mainly due to their flexibility with my schedule. Had a chat with the dev team manager a few days later who asked some general background and high-level questions. There was also a small coding project covering basics of the stack, due in a couple of days. Nothing too out there. The in-person interview was fantastic and the biggest surprise. Met a bunch of people, all attentive, interesting, and seeming to enjoy their work. They weren't trying to quiz me with canned questions, it was more about getting to know them and the company. Each conversation made me think 'Wow, that's the kind of person I'd want on my team.' The on-site interview was when I really got what Weedmaps is about, it totally exceeded expectations. If it sounds interesting, just apply, you might be surprised! Excited to get started with the Weedmaps team!