Only Four Interviews After a Layoff: My Takeaways

Company A (XX Exchange)

The interview focused on the candidate’s Java background, asking about Spring Cloud features, MySQL indexing, singleton implementation, thread pools, Map interface implementations, SQL optimization, and cookie‑session based login. The candidate felt the questions matched his strengths, but the SQL task was a weak point and likely contributed to the rejection.

Company B (XX Travel)

This interview was chaotic: the interviewer, unfamiliar with concurrency, forced concurrency questions and seemed dissatisfied with the answers. Questions covered self‑introduction, MySQL indexing, Redis replication and cache issues, high‑concurrency system design, volatile, Java locks, and the Java memory model. The candidate noted the interview was poorly structured and the interviewers appeared unprofessional.

Company C (XXX Middleware)

The interview began with a senior developer asking about the candidate’s expertise in concurrency, JVM, RPC, and Netty, followed by a question on the Java memory model and Netty’s reactor model versus traditional NIO. A middleware lead then asked the candidate to write sorting and filtering code on a whiteboard, discuss common design patterns, and share GC optimization experience. The interviewers demonstrated deep technical knowledge, especially about Linux system‑level problems.

Company D (XX Doctor)

The first interviewer asked about data structures (linked list and skip list), cookie‑session implementation for “remember me”, session storage scalability, ticket‑booking table design, HashMap internals, and thread‑safety concerns. The second interviewer gave coding puzzles, such as string filtering and grouping, and a numeric sequencing problem, and criticized the candidate’s thinking style. The interview was unusually long, with poor logistics (late start, no water).

Summary

The author reflects that limited MySQL and Redis depth hurt performance in some interviews, that the resume and applied positions were not well aligned with his skill set, and that encountering a competent interviewer is crucial. He advises maintaining a calm attitude, treating interviews as a matchmaking process, and continuing to seek roles that truly fit one’s abilities.