Java Spring Boot 10+ Yrs Interview Experience [Lead Developer]

Profile & context

• Candidate: Sep — ~10+ years experience in Java, Spring Boot and microservices; currently Principal Software Engineer.
• Recent project: US utilities platform (electricity/gas offers by ZIP code). Team is migrating the codebase to Spring Boot 3 and Java 21 and encountering migration issues.

Migration & modernization

Migration plan (monolith → microservices)

• Add critical unit and integration tests for high-risk APIs first.
• Stabilize and validate major APIs before extracting services.
• Refactor in small chunks to preserve existing behavior.
• Integrate SonarQube for static quality checks.

Migration pain points experienced

• javax → jakarta package changes break imports.
• JPA/Hibernate syntactic and compatibility errors across versions.
• Maven build/compilation failures due to dependency incompatibilities.

Java / JVM topics

• JVM architecture: class loaders (bootstrap / extension / application), runtime areas (heap for objects, stack per thread for locals, method area / constant pool for static data).
• Stack vs heap: stack holds per-thread locals/refs; heap holds objects, GC-managed and sharable.
• Thread lifecycle: new → runnable → running → blocked/waiting → terminated (differences between blocked and waiting noted).
• Virtual threads (Java 21 / Project Loom): lightweight JVM-managed threads enabling massive concurrency — recommended to prepare for Java 21.
• JVM startup optimizations mentioned: GraalVM native images, class-data-sharing (CDS), AOT compilation and related techniques to reduce startup time.
• Object pooling: reuse expensive-to-create objects (e.g., connections) to reduce allocation and GC overhead.

Concurrency & collections

• ConcurrentHashMap: avoids ConcurrentModification issues by partitioning (segments/stripes) and locking at finer granularity so threads can operate on different parts concurrently.
• Thread-safe Set options:
  • ConcurrentHashMap.newKeySet() — high concurrency.
  • Collections.synchronizedSet() — simpler but uses coarse-grained locking and can reduce throughput.

Spring framework specifics

• @Async: runs annotated methods in a separate thread pool / task executor to enable non-blocking behavior.
• @EventListener: declarative event handling (replaces ApplicationListener), supports conditional and async processing.
• Retry strategies:
  • Declarative: @Retryable (configurable).
  • Manual: custom retry logic for specialized behavior.
• Distributed locking: use Redis, ZooKeeper (or DB-based locks) to coordinate critical sections across instances.
• Architectural patterns:
  • Anti-Corruption Layer (ACL): translator/adapter layer to decouple from external or legacy systems.
  • Sidecar pattern: run helper components (logging, networking, security, monitoring) alongside a service (common in service mesh).
  • Blue–Green deployment: maintain blue (live) and green (new) environments and switch traffic when green is validated for safe rollout and easy rollback.

Security & secrets

• API vulnerability prevention: input validation, prepared statements, CSRF tokens, safe headers, filters/regex to detect malicious payloads; avoid exposing sensitive info in errors.
• Secrets management/rotation: use AWS Secrets Manager or other secret managers with scheduled rotation, plus monitoring/alerting for unauthorized access or retrieval failures; avoid hardcoding credentials.

Performance & scalability

• Handling 100x traffic spikes:
  • Design stateless services for horizontal scaling.
  • Keep service count minimal to avoid over-fragmentation.
  • Use load balancers and caching (e.g., Redis) to reduce backend load.
  • Scale out instances during spikes.
• Emphasized techniques: caching, connection pooling, and minimizing synchronous/blocking work.

Reactive & other technologies

• WebFlux / reactive programming was mentioned; candidate had not used Spring WebFlux.
• Kafka and ZooKeeper were referenced in the context of distributed coordination.

Coding questions & approaches

• Third-highest distinct number from a list:
  • Approaches: use a TreeSet (sorted unique set), sort + pick, or Stream API: distinct().sorted(Comparator.reverseOrder()).skip(2).findFirst().
• Substring existence check:
  • Simple methods: String.indexOf(sub) >= 0 or String.contains(sub).
  • For collections: use streams, e.g., stream().filter(s -> s.contains(sub)).

Interview kit / learning resources

Interview preparation kit contents (as promoted in the video):

1. Complete interview prep material covering ~99% of commonly asked questions (Java, Spring Boot, Spring Security, Spring Data, JPA, microservices, Kafka, Maven, coding questions, Stream API).
2. Two real enterprise client projects with code + recorded sessions (suitable to add to a resume).
3. Lifetime chat support for doubts.
4. Referral support to top MNCs.

Sep’s review: found the kit very helpful for concepts, interview prep, implementation tips and cracking interviews; recommended it.

Practical notes & misc

• Candidate demonstrated live coding (editor) and reasoning through Java 8 streams and classic approaches.
• Hands-on experience with AWS secret management and real migration issues when upgrading major Java / Spring versions.

Main speakers / sources

• Sep (candidate / principal software engineer)
• Ali (interviewer / host)