Extremely skilled colleagues, perfectly healthy work/life balance, calm Swedish environment (it's totally fine when people come late or leave early for a proper reason), no insane deadlines, very knowledgeable management and Product Owners.
Cool and colorful office, free snacks and drinks, occasional music events with live bands performing.
Tons of learning opportunities and technological challenges - you can switch a team and learn something new that you've always wanted.
Free Spotify Premium on top of everything else :)
Open-sourcing tools built isn't in the DNA of a company. Consequently, very few teams do so. It's just of low priority for everyone, so people never really get to this.
Visiting conferences may require some bureaucracy and talking about why you go, why it's important for a company, and who you go with. There's a limit of 3 conferences a year, which may be discouraging to some.
High volume of written communication. Be prepared for your Slack client and Gmail inbox to practically explode with incoming messages from your colleagues and other departments. Catching up on emails is essential to stay in the loop, but I never liked doing it, as I generally consider "email time" a waste.
The company doesn't encourage remote work and doesn't allow it for long periods. Even occasional WFH may be a problem. Too much relies on face-to-face communication, so being out of the office makes one disconnected from a team.
Low pay, at least in Stockholm. A senior engineer's salary is only enough to keep one's family afloat, so the expectation is both parents are employed. Rent prices are very high in Stockholm (10-15K SEK a month), and lots of single people rent tiny 30-40m² apartments. A relocation package exists, but it is lower compared to other well-established companies of similar fame.
Paying people on par with Googles of the world would go a long way.
Same as treating open-source contributions seriously and making it an integral part of the company's culture.
Letting people choose the conferences to go to without going through rounds of conversations and confirmations every time would be very nice.
Same goes for remote work.
The screening round included a discussion about a previous project, some generic questions about software and debugging, and a code challenge. This was fairly easy. This was followed by a values round, a case study (debugging skills) round, a coding
The interview process began with a recruiter screen, followed by a technical screening. The tech screen consisted of a mix of easy to medium LeetCode questions, chosen on the spot, along with random JavaScript trivia. The interviewers were friendly
Phone screen, followed by an onsite interview. The onsite focused on core JavaScript concepts, system design, and a values interview. This was pretty standard overall. For the values round, focus on STAR format answers. System design was more focus
The screening round included a discussion about a previous project, some generic questions about software and debugging, and a code challenge. This was fairly easy. This was followed by a values round, a case study (debugging skills) round, a coding
The interview process began with a recruiter screen, followed by a technical screening. The tech screen consisted of a mix of easy to medium LeetCode questions, chosen on the spot, along with random JavaScript trivia. The interviewers were friendly
Phone screen, followed by an onsite interview. The onsite focused on core JavaScript concepts, system design, and a values interview. This was pretty standard overall. For the values round, focus on STAR format answers. System design was more focus