The business is well run fiscally. This can be seen by, to date, no layoff rounds and incredibly healthy financial metrics.
There is a large amount of autonomy if you build trust with leadership that you can produce the right impact.
People actually care. They care about the quality of their work, and they care about their colleagues.
The company continues to grow and get wealthier. This is seen in initiatives like sponsoring the Canucks and bringing the whole company together for a company-wide all-hands. But this simply isn't being reflected in investments that would make the day-to-day lives of employees better.
Right now, the benefits package at Clio has not seen a major revision in several years. While we can and should continue to focus on flashy, public-facing expenditures, it would be really reassuring to see some of this money reinvested directly back into doing simple improvements for the people actually making this company so successful.
This is feedback specifically for Jack. I understand you're proud of being a successful Canadian entrepreneur, and you should be. You want to use that success to continue to grow Clio's profile. However, you need to spend some time focusing on what the pain points are for the people making you so successful.
I urge you to take time to review the deficiencies we have right now:
Focus on this stuff and get involved. It is clear you are OK to spend money on things you feel matter, so show the people that matter most you're willing to invest more of that money in making them feel more appreciated and valued.
Has a call with HR twice. And twice the experience was catastrophic. First time, a recruiter asked a few questions and rejected my candidature because I was “too front end and not enough back end,” despite asking me no questions about back-end syste
The recruiter was great, but once I interviewed with the hiring manager... so many red flags. First off, he swore like a sailor, which did not offend me but was very odd given the context. Second, he seemed very culture-bound. All questions seemed
Very lengthy process for a small company like this. 1. Technical coding challenge: 1 hr Parse a .csv file and match entries with each other such that no combination is repeated. 2. Discuss your project in detail: 1 hr This was a very good round, an
Has a call with HR twice. And twice the experience was catastrophic. First time, a recruiter asked a few questions and rejected my candidature because I was “too front end and not enough back end,” despite asking me no questions about back-end syste
The recruiter was great, but once I interviewed with the hiring manager... so many red flags. First off, he swore like a sailor, which did not offend me but was very odd given the context. Second, he seemed very culture-bound. All questions seemed
Very lengthy process for a small company like this. 1. Technical coding challenge: 1 hr Parse a .csv file and match entries with each other such that no combination is repeated. 2. Discuss your project in detail: 1 hr This was a very good round, an