What is a contrarian tech opinion you have?
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to see whether you can hold a thoughtful, independent technical opinion without sounding rigid, performative, or dismissive of others. They are usually testing judgment more than the opinion itself: how you reason, how you weigh tradeoffs, and whether you can disagree in a constructive way. Strong answers show nuance, context, and the ability to update your view when conditions change.
Key Insights
- You do not get points for being edgy. Pick an opinion grounded in real engineering tradeoffs, not a hot take designed to sound bold.
- Your best answer usually includes context for when your opinion holds and when it does not. That signals judgment rather than ideology.
- You should make other smart engineers with different views sound reasonable. The interviewer is often listening for humility, empathy, and whether you can work well through disagreement.
What interviewers probe atlevel
Top Priority
A good junior answer sounds like a flexible principle, not a rule you apply everywhere.
Good examples
š¢I lean toward simple implementations first, but if we're touching a part of the system that's risky or likely to be reused, I'd spend more time designing it carefully.
š¢I usually prefer reviews that focus on important issues, but if I'm new to a codebase and still learning conventions, I value more style feedback because it helps me ramp up.
Bad examples
š“I pretty much always prefer to just build the simplest thing and avoid planning too much ahead.
š“My view is that local testing is enough in most cases, so I usually don't spend much time on broader test coverage.
Weak answers apply the opinion mechanically; strong answers show the candidate can recognize when the surrounding conditions are different.
Valuable
Example answers atlevel
Great answers
A contrarian tech opinion I have is that simpler, less abstract code is often better than a more reusable design, at least at the start. In school projects and in my internship, I saw us spend a lot of time trying to predict future use cases, and sometimes that made the first version harder to understand without actually helping. So my default is to solve the problem that's real today and wait to generalize until I can point to a second or third case that truly needs it. I don't mean abstraction is bad ā if something is clearly reused or risky to duplicate, I'd pull it into a shared pattern. But I think teams often underestimate how much complexity they add by trying to be elegant too early.
One contrarian opinion I have is that the fastest way to ship something useful is sometimes to talk to a few people first instead of building a rough version immediately. In a past internship, I noticed we were about to spend time polishing a feature that sounded good in the ticket, but when I asked a couple of users what they actually needed, the real problem was a little different. That saved us from building the wrong thing and made the final version much more helpful. I know "just build it" is often good advice, and I do like moving quickly, but I think junior engineers can accidentally optimize for writing code instead of solving the right problem. For me, a short conversation or a quick check-in can be a better use of time than jumping straight into implementation.
Poor answers
My contrarian opinion is that comments are usually unnecessary if the engineer is good. I prefer code to speak for itself, and I think a lot of comments just create clutter and become outdated anyway. In general I try not to overexplain things in code because that usually means the implementation wasn't clean enough. So I would say I disagree with teams that want lots of inline documentation.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Late July, 2026
During 1 hr manager screen!
Late July, 2026
Late June, 2026
During manager screen; caught me off guard.
Hello Interview Premium
Your account is free and you can post anonymously if you choose.