None I can think of, unless you enjoy high school cliques.
I worked for Capital One as a contracted "consultant" (in quotes, as my employing consulting firm, which assigned me to Capital One, has its own faults in this situation).
First, let's talk about the onboarding. It is mostly automated and very, very flaky. You need many permissions just to start work, and due to the flakiness of their AD-driven, automated system, which drops permissions requests regularly, it can take several weeks to start contributing.
The org was shifting constantly, speaking of both personnel structure/assignment and the work itself.
Comps provided by UX were seldom close to finished by the time a ticket for work was created. Business requirements for a feature were also in flux much of the time, during the work. You will be criticized when your work doesn't align, despite the fact that you completed it per the provided UX comps and business requirements.
People who "own" a domain of work will take it from you out of pure territorialism, sometimes citing complete nonsense as a justification for doing so. You will then be criticized and/or untrusted toward future work. Sometimes, they will simply block or sit on your work.
As you are either new or a contractor, you have little say in changing or moving anything, and then you'll be criticized for that as well.
Get a clue. Or, if you can't manage your own org and work, don't shoot the messenger when they're honest with you about it.
It was amazing. Recruiter communicated at every stage over phone call and explained the whole process. First, solve the coding problems online. Then, four rounds: pair coding, system design, behavioral, and manager meet. CapOne has been a nice em
It was a standard interview process. Your technical interview, which included multiple different rounds all in one day, included a coding question, a systems design question, a business use case question, and a behavioral interview.
Normal powerday interview. It was pretty easy. Normal OOP technical with a banking question. The case interview was a little harder. Behavioral was normal. Focus on OOP concepts. All interviewers were really nice and helpful.
It was amazing. Recruiter communicated at every stage over phone call and explained the whole process. First, solve the coding problems online. Then, four rounds: pair coding, system design, behavioral, and manager meet. CapOne has been a nice em
It was a standard interview process. Your technical interview, which included multiple different rounds all in one day, included a coding question, a systems design question, a business use case question, and a behavioral interview.
Normal powerday interview. It was pretty easy. Normal OOP technical with a banking question. The case interview was a little harder. Behavioral was normal. Focus on OOP concepts. All interviewers were really nice and helpful.