INSIDE STRIVE / THE WORK EXPERIENCE

There's a task.
You're the
engineer.

A virtual company. AI teammates. Code you write and run. See what happens when you step into the work.

Inspect your first task ₹499 · 2 weeks · Virtual

THE WORK, FROM START TO FINISH

01Understand the job.02Get the context.03Write it. Run it.04Explain your decisions.

The company and in-product team are simulated. The work is yours to do.

01 / UNDERSTAND THE JOB

A payout file.
A missing check.
Your starting point.

In the fictional incident, a payout run was restarted and some riders were paid twice. Your assignment is to write the missing check in the payments service.

The current task asks you to identify repeated rider IDs. You start with an existing codebase and an empty JavaScript function.

SAMPLE TASKSIMULATED PAYMENTS TEAM

Build a duplicate-
payout check.

Read the service that calls your function. Work out the expected result. Then implement the check.

src/services/dedupe.jsJavaScript
function findDuplicates(rows) {
  // Your implementation starts here.
}

Simplified preview of the task's starting point. The editor and tests are inside the experience.

See a small example

Here are three illustrative payout rows:

Illustrative rows with a repeated rider ID
RowRider ID
1rider_042
2rider_108
3rider_042

rider_042 appears twice. Inside the task, you'll turn that observation into a function and check its behavior with sample data.

An explanatory example, not a scored assessment.

02 / GET THE CONTEXT

Ask a question.
Follow the situation.

Speak with AI characters playing the team. Read messages and reference material. Figure out what you need to know before you write.

STRIVE / TEAM CALLACTUAL PRODUCT PREVIEW
Strive's call interface with Tara, the AI senior-engineer character, a participant tile, and the Join the call control.
Tara is an AI teammate represented by a character portrait and voice interaction.View full size ↗
THE CONVERSATION

Get oriented to the work.

Ask for context, listen to the situation, and explain how you're approaching it.

THE MATERIAL

Read what the team has.

The ticket, source files and supporting material give you something concrete to investigate.

03 / WRITE IT. RUN IT.

Your code executes.
You inspect the result.

Use the editor to write your approach and implement the function. Run the available tests, examine the result, and refine your work.

STRIVE / WORKSPACEACTUAL PRODUCT PREVIEW
Actual Strive editor showing the file tree, an empty spec.md approach document, terminal instructions, and Tara's AI call panel.
The workspace before the student's approach is written. Code editing is paused while this call is open.View full size ↗
01

An approach in writing

Explain what you're building and the assumptions behind your implementation.

02

A function you wrote

Implement the missing check in the JavaScript workspace.

03

Results you can inspect

Run against the available sample cases. Use the output to check your understanding.

04 / EXPLAIN YOUR DECISIONS

Give your work
a clear handover.

Close the task with a written explanation and a conversation with AI Tara. Practise describing your approach, the evidence you have, and the limits of your answer.

These are useful questions to rehearse with your own work:

  • What was the problem?
  • What did you implement?
  • How did you test it?
  • What would you investigate next?
HANDOVER / EXAMPLE STRUCTURE

My engineering read

THE SITUATION

A payout file may contain repeated rider IDs.

MY IMPLEMENTATION

Explain how your function identifies them and returns the expected result.

MY EVIDENCE

Describe the sample cases you ran and what the results show.

MY LIMITS

State what you have not checked and what you would do next.

Illustrative prompts. Your handover should describe your actual work and results.

Vaibhav Vashishta, Strive co-founderTHE HUMAN CLOSING SESSION

A HUMAN CONVERSATION, TOO

Close the two weeks
with Vaibhav.

Vaibhav Vashishta

Strive co-founder · 15+ years in software engineering

A one-hour live group session on what engineers look for when hiring for their teams, followed by questions from the group.

Format
Live group session
Duration
One hour
Focus
Hiring perspectives and group Q&A

This session is separate from the AI teammates and case feedback inside the product. Individual human code review and daily one-to-one mentorship are not part of this description.

View Vaibhav's background

WORK YOU CAN DESCRIBE TRUTHFULLY

A resume line
with work behind it.

Use the experience to discuss something specific you completed. Keep the virtual or simulated context clear.

The example here describes a completed task. Adapt it to your own implementation, tests and result.

EXAMPLE AFTER COMPLETING THE WORK

Strive — Virtual software
work experience

Two weeks · Simulated company project

  • Implemented a JavaScript check for repeated rider IDs in a simulated payout workflow.
  • Tested it with sample data and documented the approach and limitations.

Use only claims you can explain and support. This experience is not employment, an external-company internship, or a guaranteed hiring outcome.

A FEW USEFUL DISTINCTIONS

Know what
you're joining.

What makes this different from a video course?

The core activity is working through a situation: reading source material, asking questions, writing code, running it and explaining your decisions. The task gives those actions a context.

Are these screenshots student results?

These are previews of the actual product interface. The handover and resume examples are illustrative. They do not represent a verified student's result or completed work.

Is the work used by a real company?

The company and incident are fictional. Your code runs in the simulated workflow. Do not claim that it was deployed to a real employer's payment system or produced real business impact.

Who is this experience for?

Engineering students and freshers looking for a first software-work story. Basic programming knowledge helps. The shown task uses JavaScript; plan to use a laptop or desktop for the coding work.

How much time should I plan for?

The existing two-week offer asks you to plan for 6–8 focused hours each week. The work is asynchronous; the human group closing session is live. Session arrangements are shared with participants.

GET WORK EXPERIENCE. EVEN WITHOUT AN INTERNSHIP.

Ready to take
on the task?

₹499 · Two weeks · Virtual software work experience

Try the short work check

Share your name and WhatsApp number first. Then choose checkout or a conversation with Strive.