Pros: At every point in my short tenure there, I was treated like a human with a life that sometimes gets messy and requires an alternative working schedule, last-minute days off, or medical treatment. Even in the end, with needing to escape a toxic home life, they helped me get home safely and not have to worry about my job, treating me like my own safety was more important. The culture is unmatched from my past experience. Everyone is friendly, with lots of opportunities to make friends and form good working relationships. It pays great for the region.

Cons: A 6-month probationary period was not disclosed to me until after I had joined the company. It was probably just an oversight, but it was a source of stress.

Pros: Fantastic perks. Really smart team. Great leadership & direction. Lots of growth opportunities.

Cons: No downsides I've experienced so far.

Pros: - Great office. - Excellent pay. - Reasonable onboarding process for general corporate things and general engineering things.

Cons: - The team didn't use a structured container of work model, such as sprints. - The team didn't have daily video stand-ups, nor other regular rituals. - The backlog of work wasn't prioritised, and cards didn't have well-defined definitions of done. - The team didn't have shared deliverables, and the team was split into silos of knowledge. - A lot of implicit social coordination and coalition-building skills were required. - Nobody on the team was colocated. - There was a lot of red tape. To get something simple approved in one instance, I needed to get sign-off from my manager's manager's manager. - There was heaps of back-and-forth on design docs without being able to align quickly on what needs doing. - Newbie tasks were not already scoped and were secretly "redesign our entire team workflow". - There was a culture of everyone on the team working on their own thing, with no shared team deliverables. - The review culture was not aligned towards shipping and was mildly antagonistic. - There was a culture of introducing scope from, for example, a Slack message from the previous day that the newbie was supposed to be keyed into, into otherwise small pull requests.