Roundiva
Sample roadmap: mid-level coding interview prep
Use this public sample to see how Roundiva thinks about coding preparation for mid-level software engineer loops. It is intentionally generic—your diagnostic will prioritize patterns that match your target company and time left.
Weekly shape (about 3–4 weeks)
If you have roughly a month, split time between pattern fluency, timed mocks and explanation quality.
- Week 1: Core patterns — two-pointers, sliding window, BFS/DFS, hashing. End each day explaining one solution aloud.
- Week 2: Medium difficulty under 30–40 minute timers. Track where you stall (modeling vs implementation vs edge cases).
- Week 3: Company-flavored problems (APIs, data transforms, concurrency basics if relevant to the role).
- Week 4: Two full mocks, then light revision of missed patterns only.
Daily practice habit
Consistency beats volume. A useful mid-level session is one problem done well, not five skimmed.
- Clarify inputs/outputs and constraints before coding.
- State the approach and complexity before typing.
- After solving, write one sentence on what you would improve next time.
Readiness signals
You are closer to ready when timed mediums feel repeatable and you can narrate trade-offs without freezing.