Good pay. Great 401k match (they give 7.5% if you give 6%). Financial benefits are good (ESPP, insurance).
They pride themselves on being "just like Amazon," but their tech decisions, red tape, and hesitancy to create new resources have just gotten in the way.
I've been on a product that was a dead end, and PMs got political about their products without actually building a good product.
I wasted so many months here just getting paid because of the economy. The work is unfulfilling if it isn't your first job.
Even the TDP I've mentored can miss hours of work each day and be fine. It's like work is a joke.
I've disliked my job for almost the entirety of my one year so far.
You're not Amazon. So make changes if you want to hold on to that claim.
Make sure product is making decisions that are backed by data, that product is okay with getting their hands dirty.
Oh, and stop marking someone as "Low Performer" every six months because you're trying to "raise the bar."
Applied online. The whole process took about a month: HR follow-up call, coding test followed by a phone screen, and an onsite "power day" which consisted of 4 1-on-1 interviews. Two of them were technical, while the others were behavioral (be prepar
I was contacted by Capital One's internal recruiter, who found my profile on LinkedIn. During the initial telephone interview, I was asked to write code in a chat session. I was presented with some apparently broken Perl code (which actually wasn't
The "Power Day" consisted of four interviews: * Coding * System Design * Case * Behavioral Coding was LeetCode style. System Design involved a standard whiteboard question. Case involved discussing a problem, followed by code reviewing. The Behavio
Applied online. The whole process took about a month: HR follow-up call, coding test followed by a phone screen, and an onsite "power day" which consisted of 4 1-on-1 interviews. Two of them were technical, while the others were behavioral (be prepar
I was contacted by Capital One's internal recruiter, who found my profile on LinkedIn. During the initial telephone interview, I was asked to write code in a chat session. I was presented with some apparently broken Perl code (which actually wasn't
The "Power Day" consisted of four interviews: * Coding * System Design * Case * Behavioral Coding was LeetCode style. System Design involved a standard whiteboard question. Case involved discussing a problem, followed by code reviewing. The Behavio