Career Resources • Assessments

How to Prepare for Online Assessments

Online assessments vary by employer, but preparation can still be structured. The goal is to improve fundamentals, speed and test-day reliability—not to memorize leaked questions.

Start with the assessment format

Use the employer's invitation, careers page or candidate guide to understand the sections, duration, proctoring rules and allowed tools. Do not assume every software role uses the same test.

A simple preparation plan

  1. List the sections.
    Separate aptitude, coding, SQL, communication or domain sections instead of preparing everything equally.
  2. Review fundamentals first.
    For coding roles, focus on language syntax, arrays/strings, complexity and common data structures. For analytics roles, include SQL and data interpretation.
  3. Practise under time limits.
    Accuracy without time pressure can create false confidence. Use short timed sets and review mistakes.
  4. Prepare your environment.
    Check browser, webcam, power, internet and quiet space before the test if proctoring is involved.
  5. Read instructions before solving.
    Negative marking, multiple correct answers, hidden tests and output formats can change how you should answer.
  6. Do not chase leaked questions.
    They may be outdated, inaccurate or violate employer rules. Strong fundamentals transfer across tests.

For coding assessments

Practise writing complete solutions without depending on IDE autocomplete. Test edge cases, empty input, duplicates, integer limits and expected output format. If the employer provides sample tests, use those to understand the platform rather than predicting exact questions.

After the test: record which topics slowed you down. That creates a useful study plan for the next assessment even when you do not receive an employer score breakdown.

Three practice exercises with explanations

1. Coding: find two numbers that sum to a target

Prompt: Given [2, 7, 11, 15] and a target of 9, return the two indices. An efficient approach uses a hash map to remember previously seen values: at each position, check whether target minus current value has appeared. In this example, 2 at index 0 is remembered and 7 at index 1 completes the pair, so the result is (0, 1).

What to review: duplicate values, no-match behavior, whether indices or numbers are requested, and O(n) expected time using O(n) additional memory. Confirm the problem's exact return contract before coding.

2. SQL: identify duplicate email values

Prompt: Find email addresses appearing more than once in a table called candidates. One portable query is SELECT email, COUNT(*) AS copies FROM candidates GROUP BY email HAVING COUNT(*) > 1;. Explain why WHERE cannot filter the result of COUNT() in this grouped query and how NULL values are handled by your database.

What to review: GROUP BY, HAVING, joins, DISTINCT, NULL, basic window functions and query output formatting.

3. Aptitude: percentage changes

Prompt: A value rises from 80 to 100. Percentage increase is (100 − 80) / 80 × 100 = 25%. A later decrease of 20% from 100 returns it to 80. The increase and decrease percentages use different base values, so they need not cancel numerically in general.

What to review: base values, ratios, time limits and estimation.

A seven-day preparation cycle

  1. Day 1: find the official test format and complete a short diagnostic. Record errors by topic.
  2. Day 2: practise language fundamentals, arrays, strings and dry runs for coding tests.
  3. Day 3: work through SQL filters, joins, grouping and one problem involving duplicates or missing data.
  4. Day 4: practise ratios, percentages, reasoning and reading questions carefully.
  5. Day 5: take a timed mock with a similar mix of questions and no unapproved assistance.
  6. Day 6: review every incorrect answer; explain the correct solution without looking at notes.
  7. Day 7: perform the technical test-day checks and do light revision rather than cramming.

Test-day decision checklist

Confirm the assessment invitation, start time and time zone, allowed browser, identification requirements, permitted notes and calculator policy. Test network, battery and camera permissions if the employer requires proctoring. If an assessment platform fails, capture the permitted error details and contact the employer's official support route rather than using an unsolicited troubleshooting link.

Afterward: keep a personal error log with columns for topic, mistake, corrected approach and next practice date. This helps with future applications without claiming knowledge of an employer's confidential question bank.