<aside> ⚠️

AI Use Policy

• You're allowed to use AI tools, but careless or excessive use will disqualify your submission.
• Any signs of low-effort or AI-generated content (AI slop) will lead to immediate disqualification.
• As the process goes on, AI usage is only allowed if explicitly stated for that stage.
• If you use outside help, like AI assistants, and don’t say so, that’s a breach of our Terms of Service. You’ll be disqualified and subject to whatever actions are outlined in the terms. </aside>

This briefing is to give you information to be as successful as possible in Strider Technical Assessment. The STA is a take-home coding test that you can do on your own computer at a time you find best.

<aside> 💡

The results of your assessment will be visible to multiple companies and are very important for your profile evaluation. The solution you design, implement, and deliver works as a sample of your work, so a really good opportunity to show off your skills.

</aside>

Keep in mind that you may need multiple hours to finish the assessment, but your results are valid for multiple opportunities. That said, you can be very efficient if delivering a great job.

Here are some tips to help you be successful:

• Keep your focus on addressing the challenge (remember you have time constraints)
• Don't ignore the importance of non-code artifacts (e.g written content, organization, decisions reasoning comments, diagrams, etc)
• Make sure you followed every single instruction carefully and ask for clarification if you need help (please refer to the FAQ section)
• Make sure you take some time to think about how you're delivering the results (e.g make sure it doesn't only work on your machine, and you're providing proper instructions and resources)

Instructions

• Suggested time to complete the test is located in the test itself. The number of suggested hours ranges from 4-8hrs depending on the test. This does not include the time to set up your environment.
• Do not post this test anywhere on the public internet (including Github, Gitlab, etc.)
• We recommend using the programming language and frameworks you are most familiar with to solve the problem
• Make sure to include instructions in the README for the reviewer to be able to set up your project in his or her local environment.
• Reviewers will only see what is in your ZIP file, so make sure that any comments that you want to make about the project are left in the README.
• Write your name towards the top of your README; this helps us identify solutions after unzipping more easily
• The code you write should be as production-ready as possible given the time constraints.
• Use git during your development process and commit regularly and intelligently. Use it as you would use it in a production project (don’t just dump everything into one commit). We will read your commit messages and evaluate how you use git.