How to use the built-in note-taking tool during your exam.
The research journal is your personal workspace during the exam. It's designed to help you organize thoughts, track progress, and reference useful information without leaving the exam interface.
Use the journal to jot down initial ideas, outline solution approaches, save documentation links, and track debugging attempts. It's especially useful for multi-part problems where you need to remember your strategy across different questions.
Your journal is saved automatically but not reviewed or scored. It's purely a tool for your benefit during the exam.
Keep notes concise and organized. Use bullet points or numbered lists for clarity. Label sections by question number if working on multiple problems, so you can quickly find relevant notes later.
When researching documentation or articles, paste useful URLs into your journal with a brief note about what you found. This creates a reference library without cluttering browser tabs.
Start by writing down the problem requirements in your own words. This confirms you understand the task. Next, outline your approach step-by-step. As you code, update your notes if you discover a better approach or encounter unexpected edge cases.
If you get stuck, review your journal notes. Often, re-reading your initial thoughts sparks new ideas or reveals where your logic diverged from the requirements.
When debugging, document what you've tried and the results. This prevents wasting time re-testing the same failed approaches and helps identify patterns in errors.
After submission, your journal is archived with your exam session. While not scored, it can be a useful reference if you want to review your problem-solving process later.
Was this article helpful?