I'm a couple of months past my 2-year anniversary at SoFi, and I still hold that this is the best job I've ever had.
It's a great place to work if you like a fast, challenging pace. Individual work and initiative is noticed—for better or worse (depending on your output).
No one slides by very long on someone else's coattails (which is good for the guy wearing the coat). Opinions are heard, respected, and often accepted on everything from administrative rules to engineering solutions; I have yet to see anyone afraid to voice an opinion (critical or otherwise) here.
Free lunches every day, snacks and beverages (including two soda fountains) always stocked, unlimited (within reason) time off, casual workspace (read: Nerf wars)—the perks go on. Work hard, play hard. You'll never be bored.
If you're not a quick learner or a self-motivated worker, you'll likely struggle.
Likewise, this shop uses Mac/Unix heavily, so it could be a steep learning curve for users who aren't comfortable with command-line consoles.
The fast development of ideas from inception to implementation can be disorienting at times. This could be a pro or a con, depending on the employee.
The flip side of extremely flexible time off is the occasional need to be available for late-night or weekend work.
As SoFi continues to grow, try not to lose the awesome start-up culture that made it so appealing to begin with.
Reached out by a recruiter on LinkedIn. It was a standard recruiter call. After that, there was a phone screen. The phone screen consisted of two medium LeetCode questions. I was unprepared as I thought there would only be one. It seems like there
This is the worst company I've ever interviewed with. I cleared the OA with 100% test cases passing for both coding questions. The recruiter said they would be moving forward and scheduling the onsite. After two days, instead of getting the onsite i
The interview process involved a standard tech screen call. This was followed by a LeetCode-style question. After that, there were two technical interviews focusing on designing an efficient algorithm and writing maintainable code. The design inte
Reached out by a recruiter on LinkedIn. It was a standard recruiter call. After that, there was a phone screen. The phone screen consisted of two medium LeetCode questions. I was unprepared as I thought there would only be one. It seems like there
This is the worst company I've ever interviewed with. I cleared the OA with 100% test cases passing for both coding questions. The recruiter said they would be moving forward and scheduling the onsite. After two days, instead of getting the onsite i
The interview process involved a standard tech screen call. This was followed by a LeetCode-style question. After that, there were two technical interviews focusing on designing an efficient algorithm and writing maintainable code. The design inte