Learning roadmap
Choose a goal, then follow each stage as an ordered, explained outline.
You have not recorded evidence yet. Start with the first recommended topic, then mark the evidence you can demonstrate.
Your progress is available for this visit only because browser storage is unavailable. Keep this page open or record your evidence elsewhere.
Build a durable mental model, then transfer it into a working application.
Stage purpose: Establish the vocabulary and first working mental model.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Explain the core idea and use it in a small example.
Estimated time: 140 minutes
Prerequisites: Java Http Rest
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: The Layer Map — Use explain what spring boot automates as the base, then name the main application layers in The Layer Map.
Prerequisites: Java Interfaces
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: From an empty folder to a running endpoint — Use name the main application layers as the base, then run a spring boot app in From an empty folder to a running endpoint.
Prerequisites: Introduction to Spring Boot
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: REST API Backend, Beneath the Hood — Use run a spring boot app as the base, then trace an http request in REST API Backend, Beneath the Hood.
Prerequisites: Java Http Rest
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Foundation retrieval review — Use trace an http request as the base, then retrieve the foundation concepts without notes in Foundation retrieval review.
Prerequisites: REST API Backend, Beneath the Hood
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Spring Core — IoC & Dependency Injection — Use retrieve the foundation concepts without notes as the base, then explain inversion of control in Spring Core — IoC & Dependency Injection.
Stage purpose: Connect the concepts into a repeatable problem-solving model.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Apply the model to a representative exercise without copying a recipe.
Estimated time: 360 minutes
Prerequisites: Java Interfaces, Java Object Composition
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Controller -> Service -> Repository, wired — Use explain inversion of control as the base, then wire controller service and repository in Controller -> Service -> Repository, wired.
Prerequisites: Spring Core — IoC & Dependency Injection
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Spring Data JPA — From Object to Table — Use wire controller service and repository as the base, then map an entity in Spring Data JPA — From Object to Table.
Prerequisites: Controller -> Service -> Repository, wired
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Real data with JPA, H2 & Lombok — Use map an entity as the base, then persist data with jpa in Real data with JPA, H2 & Lombok.
Prerequisites: Spring Data JPA — From Object to Table
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: API Boundaries: DTOs, Validation & Errors — Use persist data with jpa as the base, then separate api and persistence shapes in API Boundaries: DTOs, Validation & Errors.
Prerequisites: Controller -> Service -> Repository, wired
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Relationships & Transactions — Use separate api and persistence shapes as the base, then map entity relationships in Relationships & Transactions.
Prerequisites: Spring Data JPA — From Object to Table
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Spring Security — Basic Auth — Use map entity relationships as the base, then separate authentication from authorization in Spring Security — Basic Auth.
Prerequisites: REST API Backend, Beneath the Hood
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: JWT Authentication with Spring Security — Use separate authentication from authorization as the base, then explain jwt verification in JWT Authentication with Spring Security.
Prerequisites: Spring Security — Basic Auth
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Core concepts retrieval review — Use explain jwt verification as the base, then explain a layered request path in Core concepts retrieval review.
Prerequisites: JWT Authentication with Spring Security
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Test Doubles & Mockito — Use explain a layered request path as the base, then distinguish test doubles in Test Doubles & Mockito.
Stage purpose: Transfer the concepts into a realistic implementation task.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Produce a small artifact that proves the decision works.
Estimated time: 185 minutes
Prerequisites: Spring Core — IoC & Dependency Injection
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Proving it works: Mockito & slice tests — Use distinguish test doubles as the base, then write a service test in Proving it works: Mockito & slice tests.
Prerequisites: Test Doubles & Mockito
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: NoSQL, MongoDB & Spring Data — Use write a service test as the base, then compare document and relational models in NoSQL, MongoDB & Spring Data.
Prerequisites: Spring Data JPA — From Object to Table
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Logging in Spring Boot — Use compare document and relational models as the base, then configure useful application logs in Logging in Spring Boot.
Prerequisites: From an empty folder to a running endpoint
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Logging: SLF4J, Logback & Log4j — Use configure useful application logs as the base, then add structured logs in Logging: SLF4J, Logback & Log4j.
Prerequisites: Logging in Spring Boot
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Applied skills retrieval review — Use add structured logs as the base, then choose a focused test strategy in Applied skills retrieval review.
Prerequisites: Logging: SLF4J, Logback & Log4j
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: From requirements to a blueprint — Use choose a focused test strategy as the base, then turn requirements into a design in From requirements to a blueprint.
Stage purpose: Combine the individual concepts in a deliberate exercise.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Explain the choices and verify the result end to end.
Estimated time: 170 minutes
Prerequisites: Controller -> Service -> Repository, wired
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Design in action: blueprint to working code — Use turn requirements into a design as the base, then implement a design incrementally in Design in action: blueprint to working code.
Prerequisites: From requirements to a blueprint
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Security: Spring Security & Basic Auth — Use implement a design incrementally as the base, then configure a security filter chain in Security: Spring Security & Basic Auth.
Prerequisites: Spring Security — Basic Auth
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Stateless auth with JWT — Use configure a security filter chain as the base, then issue a signed token in Stateless auth with JWT.
Prerequisites: Security: Spring Security & Basic Auth
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: TaskFlow Integration Sprint — Use issue a signed token as the base, then integrate spring boot skills in one application in TaskFlow Integration Sprint.
Stage purpose: Transfer the path into an independent build.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Plan, implement, and review a project using the full path.
Estimated time: 150 minutes
Prerequisites: Design in action: blueprint to working code
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Build from scratch — Use integrate spring boot skills in one application as the base, then plan an independent spring boot build in Build from scratch.
Prerequisites: TaskFlow Integration Sprint
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Complete this path by applying these outcomes in your own project.
Prioritise high-frequency material, retrieve it quickly, and practise explaining it clearly.
Stage purpose: Secure the concepts that recur in most interviews.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Give a concise, accurate explanation with one concrete example.
Estimated time: 94 minutes
Prerequisites: Java Http Rest
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Spring Core — IoC & Dependency Injection — Use explain what spring boot automates as the base, then explain inversion of control in Spring Core — IoC & Dependency Injection.
Prerequisites: Java Interfaces, Java Object Composition
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: REST API Backend, Beneath the Hood — Use explain inversion of control as the base, then trace an http request in REST API Backend, Beneath the Hood.
Prerequisites: Java Http Rest
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Spring Data JPA — From Object to Table — Use trace an http request as the base, then map an entity in Spring Data JPA — From Object to Table.
Prerequisites: Controller -> Service -> Repository, wired
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Test Doubles & Mockito — Use map an entity as the base, then distinguish test doubles in Test Doubles & Mockito.
Prerequisites: Spring Core — IoC & Dependency Injection
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Spring Security — Basic Auth — Use distinguish test doubles as the base, then separate authentication from authorization in Spring Security — Basic Auth.
Prerequisites: REST API Backend, Beneath the Hood
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: The Layer Map — Use separate authentication from authorization as the base, then name the main application layers in The Layer Map.
Prerequisites: Java Interfaces
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Controller -> Service -> Repository, wired — Use name the main application layers as the base, then wire controller service and repository in Controller -> Service -> Repository, wired.
Stage purpose: Rehearse implementation choices that invite common follow-up questions.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Walk through a realistic API decision and defend the trade-offs.
Estimated time: 102 minutes
Prerequisites: Spring Core — IoC & Dependency Injection
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: From an empty folder to a running endpoint — Use wire controller service and repository as the base, then run a spring boot app in From an empty folder to a running endpoint.
Prerequisites: Introduction to Spring Boot
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: API Boundaries: DTOs, Validation & Errors — Use run a spring boot app as the base, then separate api and persistence shapes in API Boundaries: DTOs, Validation & Errors.
Prerequisites: Controller -> Service -> Repository, wired
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Relationships & Transactions — Use separate api and persistence shapes as the base, then map entity relationships in Relationships & Transactions.
Prerequisites: Spring Data JPA — From Object to Table
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Proving it works: Mockito & slice tests — Use map entity relationships as the base, then write a service test in Proving it works: Mockito & slice tests.
Prerequisites: Test Doubles & Mockito
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: JWT Authentication with Spring Security — Use write a service test as the base, then explain jwt verification in JWT Authentication with Spring Security.
Prerequisites: Spring Security — Basic Auth
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Real data with JPA, H2 & Lombok — Use explain jwt verification as the base, then persist data with jpa in Real data with JPA, H2 & Lombok.
Prerequisites: Spring Data JPA — From Object to Table
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: NoSQL, MongoDB & Spring Data — Use persist data with jpa as the base, then compare document and relational models in NoSQL, MongoDB & Spring Data.
Stage purpose: Prepare the operational and security details that distinguish a deeper answer.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Connect observability, persistence, and security concerns to production behavior.
Estimated time: 62 minutes
Prerequisites: Spring Data JPA — From Object to Table
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Logging in Spring Boot — Use compare document and relational models as the base, then configure useful application logs in Logging in Spring Boot.
Prerequisites: From an empty folder to a running endpoint
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Logging: SLF4J, Logback & Log4j — Use configure useful application logs as the base, then add structured logs in Logging: SLF4J, Logback & Log4j.
Prerequisites: Logging in Spring Boot
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Security: Spring Security & Basic Auth — Use add structured logs as the base, then configure a security filter chain in Security: Spring Security & Basic Auth.
Prerequisites: Spring Security — Basic Auth
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Stateless auth with JWT — Use configure a security filter chain as the base, then issue a signed token in Stateless auth with JWT.
Prerequisites: Security: Spring Security & Basic Auth
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: From requirements to a blueprint — Use issue a signed token as the base, then turn requirements into a design in From requirements to a blueprint.
Stage purpose: Combine concepts under time pressure in design and implementation prompts.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Structure a complete answer from requirements through verification.
Estimated time: 150 minutes
Prerequisites: Controller -> Service -> Repository, wired
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Design in action: blueprint to working code — Use turn requirements into a design as the base, then implement a design incrementally in Design in action: blueprint to working code.
Prerequisites: From requirements to a blueprint
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: TaskFlow Integration Sprint — Use implement a design incrementally as the base, then integrate spring boot skills in one application in TaskFlow Integration Sprint.
Prerequisites: Design in action: blueprint to working code
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Build from scratch — Use integrate spring boot skills in one application as the base, then plan an independent spring boot build in Build from scratch.
Prerequisites: TaskFlow Integration Sprint
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Spring mock round 1 — core backend fundamentals — Use plan an independent spring boot build as the base, then structure a concise spring explanation in Spring mock round 1 — core backend fundamentals.
Prerequisites: Build from scratch
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Spring mock round 2 — production trade-offs — Use structure a concise spring explanation as the base, then reason about production persistence in Spring mock round 2 — production trade-offs.
Prerequisites: Spring mock round 1 — core backend fundamentals
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Complete this path by applying these outcomes in your own project.