Work with smart and friendly developers on cool projects.
Everything revolves around stroking the CEO's ego.
You'll waste a lot of energy looking over your shoulder in case the thought police come for you.
Leadership talks a good game about everyone being open and sharing their opinions, but the reality is, it's like a cult and you have to conform to the CEO's genius ideas.
Salaries are way below market. Just check any public salary survey. But leadership will keep telling you the opposite.
You have to believe them because it's like you're in a cult. You'll end up questioning your own self worth.
Work at Clio for a couple of years, get some experience and then move on to a better paying job in a sane environment.
Or just skip Clio and get the experience somewhere else while earning better cash.
Before taking a job at Clio, read Disrupted, by Daniel Lyons, to know what you're getting into.
A cult is inhumane. I'm not sure what to say.
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
The screening and technical interviews were pleasant. Each person I interviewed with was easy-going and kind. The coding challenge was fairly straightforward, and I believe the system design went well. The downside is that after the technical interv
Started with a two-hour+ technical interview. The first half was programming, and the second was a system design question. I found the question in the first half to be relatively easy, but the interviewer seemed fairly skeptical of the methods I use
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
The screening and technical interviews were pleasant. Each person I interviewed with was easy-going and kind. The coding challenge was fairly straightforward, and I believe the system design went well. The downside is that after the technical interv
Started with a two-hour+ technical interview. The first half was programming, and the second was a system design question. I found the question in the first half to be relatively easy, but the interviewer seemed fairly skeptical of the methods I use