Senior engineer at both these companies.
TC is similar. Both around 500k
Dropbox pros: seems extremely employee friendly with great wlb
And the benefits are awesome
They’re going after Docusign, which is a huge business with great margins so the company looks quite enticing
Cons: they need to execute with the hellosign acquisition. They are making a profit now, but have to see how they do in future
Uber pros: market leader in its space
Cons: interview process and people I interviewed with seemed very unhappy and chaotic. It seemed all the engineers were primarily being overworked
IC4 vs 5b
Want to see the real deal?
More inside scoop? View in App
More inside scoop? View in App
blind
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
FOLLOWING
Industries
Job Groups
- Software Engineering
- Product Management
- Information Technology
- Data Science & Analytics
- Management Consulting
- Hardware Engineering
- Design
- Sales
- Security
- Investment Banking & Sell Side
- Marketing
- Private Equity & Buy Side
- Corporate Finance
- Supply Chain
- Business Development
- Human Resources
- Operations
- Legal
- Admin
- Customer Service
- Communications
Return to Office
Work From Home
COVID-19
Layoffs
Investments & Money
Work Visa
Housing
Referrals
Job Openings
Startups
Office Life
Mental Health
HR Issues
Blockchain & Crypto
Fitness & Nutrition
Travel
Health Care & Insurance
Tax
Hobbies & Entertainment
Working Parents
Food & Dining
IPO
Side Jobs
Show more
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
comments
Looks like Dropbox’s market share is slightly behind google drive - https://www.wallstreetzen.com/stocks/us/nasdaq/dbx/statistics
From a growth perspective, it depends on the domain you want to grow at. For me, I would join dropbox cause I like to work on ~strong consistency models and their problems, we have such at Amazon but with less salary and worse WLB. Even if this already exists, I would still have a chance to grow.
I have interviews with both soon. Do you have any advice? I highly appreciate it if you can provide per-round advice, I don't care much about pure coding/algorithmic interviews (unless there is something specific like a follow-up to scale the solution), while I care too much about all the others like concurrency, dive deep interview, behavioral, sys design.
For ex: we know that if we have transactions in databases the latency can be higher, so the interviewer wanted to reduce latency but not use any no sql db. The solution they were looking for was send a notification to the user that were working on it , and in the background do the processing