Unproductive Work Environment
Unproductive Work Environment
• Cool campus (Richmond) • Reasonable pay
You rarely get any work done due to corporate proxy.
Excessive security and rehydrations in test environments; testing simple things takes days.
Unstable corporate tools that are enforced on dev teams.
Too much focus on the use of particular tools rather than creating business value.
Useless meetings.
Performance management.
Excessive employee rotation and reorgs. I have seen tens of people leaving and replaced with new ones in just 6 months, including managers and directors. Everything is unstable in the company.
Focus on keeping your engineers engaged and happy.
Make developer-friendly test environments. Nobody is going to hack a test environment.
Was this helpful?
Capital One Interview Questions
Capital One Interview Experiences
Principal Software Engineer
30 min quick call. Technical round of LeetCode-type questions. Unfortunately, it ended there as I didn't pass that round. Presumably, it was going to be system design after this online LeetCode question, and then onsite.
Principal Software Engineer
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.
Principal Software Engineer
First, I was reached by HR for basic information gathering. Then came the code test. It wasn't too difficult, but you do need to have a good understanding of algorithms and data structures. Next was the onsite interview, with two hiring managers an
Principal Software Engineer
Toronto, Ontario, CanadaNovember 5, 202530 min quick call. Technical round of LeetCode-type questions. Unfortunately, it ended there as I didn't pass that round. Presumably, it was going to be system design after this online LeetCode question, and then onsite.
Principal Software Engineer
United StatesNovember 24, 2025It 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.
Principal Software Engineer
Chicago, Illinois, United StatesJanuary 1, 2020First, I was reached by HR for basic information gathering. Then came the code test. It wasn't too difficult, but you do need to have a good understanding of algorithms and data structures. Next was the onsite interview, with two hiring managers an
