Senior Software Engineer Interview Experience - San Francisco, California
Process
Don’t waste your time until you are desperate for a job.
You will probably have an initial call with a sourcer who will keep asking you the number of years of experience you have in a particular language. They themselves would not understand how it matters or not. If you do get past that, they would be looking for some keywords.
After these uncomfortable 30 minutes, you will speak with a senior engineer. This is the part that seems professional, as the engineer I spoke to was great, and we had a productive conversation.
Now, the recruiter will give you a take-home assignment and also give you their own timeline. They would probably say, "Do this in a couple of days." Well, once you do that, the recruiter will not get the time from their team to review the assignment for weeks. (Why would someone who is not desperate go through this? Maybe because they like problems.)
The problem will ask you for something specific to duplicate. Weeks later, when you do ask for an update, you will get a response that there was duplication of code (this is exactly stated in the requirement!). Also, they would expect the candidate to spend days on it, but they themselves won't even either compile or run it.
I think the recruiting process lacks both professionalism and competence to first build a problem and then expect a solution. Also, why go through this horrible experience?
Questions
It's a fairly simple client-server application where the focus is on log statements (yes, you guessed it right: a series of log statements!). You can build it in any way, though, which should be exactly how the said engineer expects it.
Was this helpful?
Interview Statistics
The following metrics were computed from 2 interview experiences for the Ripple Senior Software Engineer role in San Francisco, California.
Success Rate
Ripple's interview process for their Senior Software Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for Ripple's Senior Software Engineer interview process in San Francisco, California.
Ripple Work Experiences
- 2.0Culture is becoming toxicSenior Software Engineer • Current EmployeeSan Francisco, California, United StatesAugust 25, 2023Pros: Good benefits. Some teams are good.Cons: Most of the teams are toxic. Poor WLB. Amazon execs have brought their culture. Blame game and intolerance towards suggestions.
- 5.0A great place to learn and growSenior Software Engineer • Current EmployeeSan Francisco, California, United StatesJanuary 1, 2023Pros: Great Leadership with amazing vision for the productCons: None that I can think of
- 1.0Why is everyone leaving?!Senior Software Engineer • Former EmployeeSan Francisco, California, United StatesMay 28, 2021Pros: It's unclear why over 25% of the company has left now, and sees no sign of slowing down. Engineers, managers, product folks, VPs are all leaving in droves. Why on earth is this!? There are so many good things about the engineering department here: * Aging tech stack that middle-management is hell-bent on keeping relevant because it keeps them relevant. * Appear to be working for one of the best companies in FinTech and SF due to constant gaslighting from management gently coercing employees to fill out positive engagement surveys. * Increase your communication skills by working with departments hiding mediocrity inside of heavy and unnecessary processes. * Feel good about yourself for participating in faux diversity and inclusion efforts, and then watch as HR executes witch hunts against other departments for fake violations of diversity and inclusion. * Work-life balance realized by constant Zoom meetings, late-night and weekend work requirements to hit deadlines, and release after failed release after failed release.Cons: Politics here like you've never seen. Consider that if Ripple is successful, they'll be one of the most powerful companies on Earth. Greed rules here, and managers at all levels will be the first to throw peers and staff under the bus so fast to save their own jobs or butts. Engineers at all levels that are able to play politics and tow the company line derail entire initiatives because they happen to know better for one reason or another over senior engineers. It's a mess because there is no rudder, and all teams are spinning in weird circles trying to either keep their heads down or play political games. Engineers have little autonomy. Engineers that have been around for many years ignore the processes that newer managers have put up, so they're able to get work done. Otherwise, management constantly tells employees what to work on and when to have it delivered. Innovation is actively squashed by middle management. Managers that are fearful of new innovations being spawned by the company to help with faster delivery are killed by institutional teams for fear of losing their own jobs. Prisma was created because ODL was unable to deliver quickly and safely. Yet, Prisma got constant pushback because they worked in a different way. No matter that they released many times a week safely and were able to create an entirely new platform – it's a threat to other managers and is fought tooth and nail. Snakes in leadership at all levels will lie to you directly to your face and then go do other things behind closed doors. There's no other way to explain it. Be careful what you say and who you say it to, or else HR will come and find you.
Ripple Interview Questions
