Raaha Discover · Free assessment

Tech assessment

Work on a small fictional product, then try three kinds of tech work. Explain a problem, read code, build a feature and revise your approach when the situation changes.

Try Tech, free See an example

A free Raaha account is required. Read the assessment introduction before starting the timer.

WHO IT IS FOR: Tech students exploring possible career directions
TIME: 65 + 30 minutes
FORMAT: Two sessions; complete Session 2 within seven days
PRICE: Free · Build90 purchase is not required

Step by step

What you’ll do

Get ready
A laptop or desktop. You will write in Python or JavaScript.
Do the work
Two sessions; complete Session 2 within seven days
65 + 30 minutes
See the parts
Hand in
Written answers, a code change for the debugging task, a small feature in code or pseudocode, then three role exercises.
Get back
A report built from your saved work, code checks and AI-assisted interpretation. Some parts may wait for a human review.
See an example report

What you need before starting

Use a laptop or desktop. You will read code and write answers in Python or JavaScript.
Work experience is not required. The build task accepts code or pseudocode; the debugging task asks you to change code and explain what you understand.
Reserve 65 minutes for Session 1 and 30 minutes for Session 2 within seven days. Each session’s timer continues if you close the page.

Inside the assessment

The work you will try

Get ready and understand the problem
Session 1
Try an unscored warm-up, then explain what a small product needs to do.
Read and debug
Session 1
Investigate code behaviour, propose a change and explain a test.
Build and replan
Session 1
Write a small feature or clear pseudocode, then revise your approach under a new constraint.
Work with people
Session 1
Explain a decision and reflect on the kind of work you want to explore.
Try three role exercises
Session 2
In Session 2, explore your chosen interest, a related area and a different family of tech work.

Illustrative example · Not scored

Plan a campus book-swap feature

This is a separate fictional example to show the kind of thinking involved. It is not an official assessment question or a student result.

A fictional book-swap app needs to prevent two students from reserving the same book. The team also wants a clear message when a reservation cannot be made.

Describe the information and checks the reservation needs. Write steps or pseudocode if that helps.
What would you test when two requests arrive close together, and what should each student see?

Your report

What the feedback means

The report combines saved work, available code checks and AI-assisted interpretation to explain areas worth exploring.

Missing execution evidence or an incomplete evaluation can leave part of the report pending or needing human review. A pending result is not a completed judgement of your ability.

Session 2 adds exploration evidence without changing Session 1 scores. If you complete only part of it, the report identifies what remains unexplored.

This is a career-exploration pilot. Suggestions are based on a limited work sample and do not choose a career for you or predict hiring outcomes.

Example report · Not a real student

See what you get back

This is the real Tech report layout, filled in for a fictional student. The scores and feedback are made up. Question wording and answers are hidden, so the assessment stays fair for everyone. Quoted answers and code refer to the fictional example above, not to the real assessment.

EXAMPLE RESULT

Overall task-work score

66/100

Directions worth exploring: Backend development · QA / testing

INSIDE THE REPORT

Your starting point
Directions worth exploring
How you approached the work
Your debugging work
Areas not explored yet
Your one next step

Open the full example report

Example · Not a real student

Tech report

Fictional student · Example case: Plan a campus book-swap feature

CompleteReport 1 · 12 October 2026 at 4:00 pm IST

1Your starting point

You understood what the book-swap app needed and fixed the debugging task with a clear explanation. Building software and testing it are worth exploring next.

This report is a starting point for exploring careers, based on one short assessment. It is not a test of your ability or a prediction of your future.

Product: Plan a campus book-swap feature (example)
Language: Python
Build path: Code

Session 1

Understand the problemAnswered
Read and debugAnswered
Build a small featureAnswered
ReplanPartly answered
Work with peopleAnswered

Session 2: role exercises

Backend developmentAnswered
QA / testingAnswered
Product managementPartly answered

2Directions worth exploring

Build software

Backend development: worth exploring

Build the server code that saves data and handles requests.

Why: You explained how the app should store and check a reservation, and you enjoyed this exercise.
Basis: A role exercise from this area that you completed.
Your work: Role exercise: Backend development
“Each reservation needs the book, the student and the time, so we can tell who asked first.”
Your reaction: Enjoyment of “Role exercise: Backend development”: 4 out of 5. More work like this: Yes.
Not tested yet: Working with a real database or another person’s code.
Try next: Build a small order API, about 120 minutes.
Use starter code to create and read an order.
Handle a missing item and an invalid quantity.
Show three requests and explain their results.
Raaha provides: A starter project in Python or JavaScript.
A short API guide (how programs exchange requests).
Sample orders, expected results and a checklist.

Quality and reliability

QA / testing: worth exploring

Check whether a product works, including unusual situations.

Why: You listed the cases to check before calling the feature finished.
Basis: A role exercise from this area that you completed.
Your work: Role exercise: QA / testing
“I would test a free book, a reserved book and a book that was just returned.”
Your reaction: Enjoyment of “Role exercise: QA / testing”: 5 out of 5. More work like this: Yes.
Not tested yet: Testing a full app or writing automated tests.
Try next: Write and run a small test plan, about 75 minutes.
Write checks for a small login feature.
Run the checks on a supplied practice app.
Report a failure with steps, expected result and actual result.
Raaha provides: A practice app with fictional accounts.
A short feature specification.
A test-plan template and example report.

Your mentor shares the “try next” tasks. They are not available in the app yet.

3How you approached the work

Overall task-work score: 66 / 100

All five parts of your work were scored.

You wrote code for the build task. Private checks on your final code: 3 of 4 passed.

The score describes your work on these tasks only.

Problem understanding

75 / 100

How you worked out what the product needed and what mattered most.

Your work: Get ready and understand the problem
“The app must stop two students reserving one book, and tell the second student clearly what happened.”
What this shows: You named the main rule and the person it affects.
Practise next: Before you start, write the rule in one sentence and list who it affects.

Code and debugging

75 / 100

How you traced a problem in code and made a change that works.

Your work: Read and debug
return "This book is already reserved. Please try again later."
What this shows: Your change fixed the blank message, and you explained why it was blank.
Practise next: Write one test for the case you fixed before you change the code.

Design and tradeoffs

50 / 100

How you chose an approach and explained its limits.

Your work: Build and replan
“I kept the first version simple: one list of books and one reservation per book.”
What this shows: You chose a simple approach but did not say what it cannot handle.
Practise next: After each design choice, add one line on what it does not cover.
Why it matters: Teams decide faster when the limits of a plan are written down.

Adapting the plan

50 / 100

How you changed earlier work when the situation changed.

Your work: Build and replan
“When the library asked for a waiting list, I added it as a separate step.”
What this shows: You kept your earlier work and added the new request on top.
Practise next: When plans change, list what you keep, what you drop and why.
Why it matters: Requirements often change after work has started.

Communication and teamwork

75 / 100

How you explained your work and handled other people’s requests.

Your work: Work with people
“I told the team which case is not handled yet, so nobody assumes it is finished.”
What this shows: You told your team clearly what was not finished.
Practise next: End each update with what is done, what is not and what you need.

4Your debugging work

Your submitted code · Python

def reservation_message(book, student):
    if book.reserved_by is None:
        return f"Reserved for {student.name}."
    # Before: nothing was returned here, so the page stayed blank.
    return "This book is already reserved. Please try again later."

What a working fix changes: A working fix gives the student a clear message when the book is not available.
Your explanation: “When the book was taken, the function returned nothing, so the page stayed blank. Now it says why.”
Checks on your final code: Checks on your final code: 5 of 6 passed. Samples: 2 of 2. Private checks: 3 of 4.
Sample: A free book is reservedPassed
Sample: A taken book shows a messagePassed

5Areas not explored yet

Build software: Frontend development, Full-stack development, Embedded / IoT

Work with data: Data analysis, ML / AI

Protect systems: Cybersecurity

Design for users: UI / UX design

Quality and reliability: Cloud / DevOps

People-facing tech: Product management, Technical support, Presales / tech consulting

Talk to your mentor if any of these interest you.

6Your one next step

Try the QA / testing task: write and run a small test plan.

Raaha provides: A practice app with fictional accounts. A short feature specification. A test-plan template and example report. Your mentor shares these tasks. They are not available in the app yet.
Time: About 75 minutes

Make the work your own

Use only the supplied case and the tools permitted in its instructions. Do not use AI assistants, web searches, prepared answers or another person’s help during the official assessment.

Answers save as you work. Check the save status, because only work received before a deadline can count. Closing the page does not pause the timer, and submitted or expired stages lock.

The account and assessment introduction explain any verification requirements before you begin. Completed assessment versions may not be available to retake.

Turn the result into a next step

Use one suggested area to choose a small follow-up project. Keep the code or design decisions, explain your tests and note what you still need to learn before deciding on a longer track.

Open the free assessment

What you’ll do

Get ready

A laptop or desktop. You will write in Python or JavaScript.

Do the work

Two sessions; complete Session 2 within seven days

65 + 30 minutes

See the parts

Hand in

Written answers, a code change for the debugging task, a small feature in code or pseudocode, then three role exercises.

Get back

A report built from your saved work, code checks and AI-assisted interpretation. Some parts may wait for a human review.

See an example report

What you need before starting

Use a laptop or desktop. You will read code and write answers in Python or JavaScript.

Work experience is not required. The build task accepts code or pseudocode; the debugging task asks you to change code and explain what you understand.

Reserve 65 minutes for Session 1 and 30 minutes for Session 2 within seven days. Each session’s timer continues if you close the page.

Plan a campus book-swap feature

This is a separate fictional example to show the kind of thinking involved. It is not an official assessment question or a student result.

A fictional book-swap app needs to prevent two students from reserving the same book. The team also wants a clear message when a reservation cannot be made.

Describe the information and checks the reservation needs. Write steps or pseudocode if that helps.

What would you test when two requests arrive close together, and what should each student see?

def reservation_message(book, student): if book.reserved_by is None: return f"Reserved for {student.name}." # Before: nothing was returned here, so the page stayed blank. return "This book is already reserved. Please try again later."

Make the work your own

Use only the supplied case and the tools permitted in its instructions. Do not use AI assistants, web searches, prepared answers or another person’s help during the official assessment.

Answers save as you work. Check the save status, because only work received before a deadline can count. Closing the page does not pause the timer, and submitted or expired stages lock.

The account and assessment introduction explain any verification requirements before you begin. Completed assessment versions may not be available to retake.

What you’ll do

01Get ready

02Do the work

03Hand in

04Get back

What you need before starting

The work you will try

Get ready and understand the problem

Read and debug

Build and replan

Work with people

Try three role exercises

Plan a campus book-swap feature

What the feedback means

See what you get back

1Your starting point

2Directions worth exploring

Backend development: worth exploring

QA / testing: worth exploring

3How you approached the work

Problem understanding

Code and debugging

Design and tradeoffs

Adapting the plan

Communication and teamwork

4Your debugging work

5Areas not explored yet

6Your one next step

Make the work your own

Turn the result into a next step

What you’ll do

01Get ready

02Do the work

03Hand in

04Get back

What you need before starting

The work you will try

Get ready and understand the problem

Read and debug

Build and replan

Work with people

Try three role exercises

Plan a campus book-swap feature

What the feedback means

See what you get back

1Your starting point

2Directions worth exploring

Backend development: worth exploring

QA / testing: worth exploring

3How you approached the work

Problem understanding

Code and debugging

Design and tradeoffs

Adapting the plan

Communication and teamwork

4Your debugging work

5Areas not explored yet

6Your one next step

Make the work your own

Turn the result into a next step

Get ready

Do the work

Hand in

Get back

Get ready

Do the work

Hand in

Get back