I've worked at companies with great cultures before, so I had high expectations for Clio. Clio did not disappoint. The culture here is extremely strong; everyone exudes a passion for the company's beliefs and values.
To succeed and enjoy yourself at Clio, you have to check your ego at the door and really live that learning mindset. If you are one that likes to learn and reevaluate what you already know (as Clio is incredibly dynamic), then it will be a pretty good match for you. For myself, I've learned more in the past 3 weeks than I have in the previous 5 years of my career.
Working at Clio is like riding in a car that's constantly being rebuilt while everyone is questioning the best way to get to our destination. If that makes you feel uncomfortable, it might not be the best fit for you. If that excites you, then it'll feel really good to be a part of it and have a say.
Other pros:
If you do not align with the organization's core values, then it will feel really challenging to work here. You will want to think deeply if you are comfortable with Clio's tenets, as they are taken very seriously.
Also, there are sometimes lots of meetings.
The process took 2 weeks. 1. Phone screening by recruiter 2. Virtual On-site Interview with 4 rounds, 3hrs 15 min a. Pair programming (45 min) Write a console app to parse a file b. Technical Deep Dive (1 hr) Talk about a past p
Initial contact with the hiring team (through LinkedIn). Pair programming technical test - a pretty simple challenge, and the person made me feel comfortable enough that it felt like we were doing it together. Technical interview - In-depth coverag
Initial contact with the hiring team (though linked in, I think). Technical test - usual stuff, practice on the various sites like LeetCode etc., to get your head back into that space. Technical interview - In-depth coverage of a previous workplace
The process took 2 weeks. 1. Phone screening by recruiter 2. Virtual On-site Interview with 4 rounds, 3hrs 15 min a. Pair programming (45 min) Write a console app to parse a file b. Technical Deep Dive (1 hr) Talk about a past p
Initial contact with the hiring team (through LinkedIn). Pair programming technical test - a pretty simple challenge, and the person made me feel comfortable enough that it felt like we were doing it together. Technical interview - In-depth coverag
Initial contact with the hiring team (though linked in, I think). Technical test - usual stuff, practice on the various sites like LeetCode etc., to get your head back into that space. Technical interview - In-depth coverage of a previous workplace