We focus on making the user's life simpler, and we are trying to build a company that makes money because people pay us for what we offer, which is fairly unique in this day and age where most companies are focused on eyeballs to show ads.
We also solve challenging technical problems at scale, both on the client (large amounts of personal data, in fast, low-resource clients, across a wide variety of platforms) and in our backend (large amounts of data, mostly unique per user). When we build things, we strive to build them correctly, both because we're protecting data that is precious to our users, but also because we believe in quality and things just working for our users.
Benefits, time off, etc., are all world-class, but they're not the reason you should work here. The reason to work here is the focus on the user, the focus on quality, and solving hard engineering problems.
The company is growing fast, and growing causes pain.
Medium-term goals change more often than at a big company or than they would if it was a less competitive space, since we're always trying to balance being nimble without getting distracted.
It's part of the fun, but it can take a little to get used to.
The interview process was a coding assessment and a phone screen. The coding assessment was a design question consisting of four parts. It increased in difficulty and involved designing a system to do a certain task.
Phone interview: The question was to find all duplicate files in a file system. Follow-up questions included: * What if files are large? * What if files are small? The interviewer was kind of indifferent.
After the resume screen, the second stage was a coding interview. I was asked one question related to recursion, specifically to find a duplicate file in a filesystem. This was conducted in a browser-based text editor.
The interview process was a coding assessment and a phone screen. The coding assessment was a design question consisting of four parts. It increased in difficulty and involved designing a system to do a certain task.
Phone interview: The question was to find all duplicate files in a file system. Follow-up questions included: * What if files are large? * What if files are small? The interviewer was kind of indifferent.
After the resume screen, the second stage was a coding interview. I was asked one question related to recursion, specifically to find a duplicate file in a filesystem. This was conducted in a browser-based text editor.