The two most appealing parts about working for Clio are how integral a learning mindset is to the culture, and how empowered you are to make a difference. The two really go hand in hand.
At Clio, you are always working on difficult and interesting problems. You are given a lot of flexibility in how you solve those problems, with the caveat that "good enough" solutions need not apply. What makes that so appealing is that absolutely everyone you work with is incredibly smart and is in every way willing to help you learn. The collaborative learning culture creates really positive feedback loops where everyone feels like they can constructively contribute.
As a remote employee, I also feel that Clio does an excellent job supporting their remote teams. The Employee Experience team works hard to ensure that remotes feel included in company events, and the product team has a long history of remote workers, so the tools and attitudes are already in place to facilitate that.
Clio has almost doubled in size since I started, and there are sometimes the growing pains that come with rapid growth. Most of this comes down to policy and execution (whether that's too much, or too little), rather than a lack of desire to see things done well. The positive is that when mistakes are made, they are owned, and improvement does happen.
Keep putting the right people in the right spots to succeed. Whether it has been internal promotions or bringing in new people, there have been a number of changes over the last 2+ years which have had exceedingly positive impacts on the company culture and direction.
Areas of clear weakness have been turned into serious strengths in fairly short order. Continue to recognize where change needs to happen and get the right people in those positions.
Phone screening, a call with hiring manager, coding, system design, and behavioral. The call with the hiring manager is mostly talking about your previous roles and your experience. For coding, you can google.
A recruiter reached out to me to schedule a call on a Friday afternoon (5 PM EST). And he did NOT call! Complete waste of my time and quite unprofessional.
Pair programming with developer: Easy read file contents and array of objects manipulation with duplicate data, such that one value only appears once. Not required to solve fully, but more interested in how the problem is being approached. System de
Phone screening, a call with hiring manager, coding, system design, and behavioral. The call with the hiring manager is mostly talking about your previous roles and your experience. For coding, you can google.
A recruiter reached out to me to schedule a call on a Friday afternoon (5 PM EST). And he did NOT call! Complete waste of my time and quite unprofessional.
Pair programming with developer: Easy read file contents and array of objects manipulation with duplicate data, such that one value only appears once. Not required to solve fully, but more interested in how the problem is being approached. System de