Good work-life balance, decent pay, difficult transitional time
Good work-life balance, decent pay, difficult transitional time
Excellent WLB. "Unlimited" PTO as a Software Engineer. Plenty of interesting things to do.
Less and less control over how you deploy and manage your products.
Too many heavy-handed requirements on all teams with no exceptions.
In the long run, it should hopefully get better.
Additional Ratings
Was this helpful?
Capital One Interview Questions
Capital One Interview Experiences
Principal Software Engineer
Standard half-day multi-interview. Interviews included: * Behavioural * Technical * Manager * Business person (analyst, I think) All interviewers, except the manager, seemed uninterested and largely stuck to formal questions. The business person a
Principal Software Engineer
The interview process was multi-step, involving three phone interviews and one face-to-face interview. The people were very nice, smart, and professional. I felt bad for turning down their offer; it really looked like a nice company. In hindsight,
Principal Software Engineer
The interview process included a phone interview, a code test, a job fit session, and finally a pair programming session. The pair programming session was part code and part discussion of design choices. You could choose any programming language, bu
Principal Software Engineer
United StatesMay 1, 2020Standard half-day multi-interview. Interviews included: * Behavioural * Technical * Manager * Business person (analyst, I think) All interviewers, except the manager, seemed uninterested and largely stuck to formal questions. The business person a
Principal Software Engineer
North York, Ontario, CanadaApril 1, 2017The interview process was multi-step, involving three phone interviews and one face-to-face interview. The people were very nice, smart, and professional. I felt bad for turning down their offer; it really looked like a nice company. In hindsight,
Principal Software Engineer
Toronto, Ontario, CanadaJanuary 13, 2021The interview process included a phone interview, a code test, a job fit session, and finally a pair programming session. The pair programming session was part code and part discussion of design choices. You could choose any programming language, bu
