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: 65 minutes
Prerequisites: OOPs Concepts
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Sorting — Comparable & Comparator — Carry the object contract into ordering so collections can compare values predictably.
Prerequisites: Object Class, equals/hashCode & SOLID
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Low Level Design — OOP & UML — Use explicit ordering as one more boundary in a coherent object design.
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: 80 minutes
Prerequisites: Object Class, equals/hashCode & SOLID, OOPs Concepts
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: SOLID Principles — ISP, DIP & LSP — Pressure-test the class boundaries against dependency and substitution failures.
Prerequisites: Low Level Design — OOP & UML
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Factory Method Pattern — Move from principles to a pattern that isolates object creation and variation.
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: 70 minutes
Prerequisites: SOLID Principles — ISP, DIP & LSP
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Creational Design Patterns — Compare factory method with builder and singleton before choosing a creational pattern.
Prerequisites: Factory Method Pattern
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: 22 minutes
Prerequisites: OOPs Concepts
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Sorting — Comparable & Comparator — Move from equality to the Comparable versus Comparator trade-off interviewers probe.
Prerequisites: Object Class, equals/hashCode & SOLID
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Low Level Design — OOP & UML — Apply ordering decisions inside a low-level design conversation next.
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: 27 minutes
Prerequisites: Object Class, equals/hashCode & SOLID, OOPs Concepts
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: SOLID Principles — ISP, DIP & LSP — Use the design sketch as the setup for an SOLID trade-off discussion.
Prerequisites: Low Level Design — OOP & UML
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Factory Method Pattern — Translate SOLID into a factory answer with a concrete extension point.
Stage purpose: Prepare the details that distinguish a deeper answer.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Connect the concept to reliability, complexity, or production behavior.
Estimated time: 27 minutes
Prerequisites: SOLID Principles — ISP, DIP & LSP
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Creational Design Patterns — Round out the pattern answer by comparing three creational choices.
Prerequisites: Factory Method Pattern
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.