Spotify genuinely cares about its employees, and it shows. They invest in employees with a week-long "intro days" trip to Stockholm HQ. The organization is relatively flat, with opportunities to move laterally and try new things, as well as grow your career and responsibilities. There is very little resistance from the org if you want to invest time and energy. Hack time is great and well-respected by the company from the top down, including a hack day usually every 2 weeks and a full, organized hack week every so often.
There is a strong ethic of questioning things, even well-established things, and making sure that ideas still pass the test. There is some really top-notch engineering talent and few people who are not at least very good engineers.
Food is really good. Plenty of good options for breakfast and lunch, and often there is food to be had for dinner as well, and plenty of beverages, including iced coffee, espresso, and a good selection of beers.
The technology infrastructure and client are pretty well established, and a lot of technology decisions are already made. There is some pretty strong resistance to introducing new technology for fairly legitimate reasons. Spotify is really becoming a data-driven company, and there are some excellent opportunities for data engineering. There are too many internal quirky libraries and systems that could be better served by using something open source or more standard. This seems to have been recognized, and this is gradually being phased out.
Benefits could be a little stronger, like paid transportation and gym memberships, for instance, which would really be nice.
I need to mend more fences with the artistic community.
I had a 1 hour and 15 minute phone interview, which consisted of 1 hour for coding, 10 minutes for general theoretical programming questions, and 5 minutes for any questions I might have. After passing the phone interview, I was invited for an onsit
I was reached out to via LinkedIn by a recruiter. We scheduled a chat and decided to move forward. Another recruiter scheduled my second interview for that same week, as they knew I had another third-round interview scheduled then. This interview in
The phone screen was relatively easy. They asked about details on Java, and then some questions involving data structures and algorithms. Nothing too deep; if you've been studying, you'll pass this phase without difficulties. At the on-site, I could
I had a 1 hour and 15 minute phone interview, which consisted of 1 hour for coding, 10 minutes for general theoretical programming questions, and 5 minutes for any questions I might have. After passing the phone interview, I was invited for an onsit
I was reached out to via LinkedIn by a recruiter. We scheduled a chat and decided to move forward. Another recruiter scheduled my second interview for that same week, as they knew I had another third-round interview scheduled then. This interview in
The phone screen was relatively easy. They asked about details on Java, and then some questions involving data structures and algorithms. Nothing too deep; if you've been studying, you'll pass this phase without difficulties. At the on-site, I could