Veteran Java dev blindsided by modern switch syntax in interview gauntlet

“Interview asked me to turn a switch-statement into a ‘switch-expression with pattern-matching and sealed hierarchy deconstruction’. Cool - didn’t realize I’d signed up to write Kotlin in disguise while the compiler still calls itself javac.”

Ten years of shipping enterprise Java, but the interviewer wants you to live-code pattern matching with sealed classes while explaining the JVM memory model changes since Valhalla - all while they're secretly just checking if you remembered to handle the null case

After a decade of Java development, you've seen every anti-pattern in production. But technical interviews? That's where you discover someone's refactored switch statements into a factory pattern that returns lambdas wrapping strategy objects - and they want you to explain why it's 'cleaner.' The real test isn't solving the problem; it's keeping a straight face when the interviewer calls this 'industry best practices.'

That “20-minute code eval” turns into a JEP speedrun when they expect a switch expression with pattern matching and yield; your Java 8 muscle memory keeps typing break

Nothing humbles 10 years of Java faster than a code test where switch is an expression, yield is a keyword, and your muscle memory still types break;

10 years Java exp: expert at semicolons, rookie at release notes past 2014