Coding Assessments — Candidate Guide
This guide covers everything you need to know about taking XEtest coding assessments on XeCubes.
What Is XEtest?
XEtest is XeCubes' technical assessment platform. You'll write code in a browser-based editor, run it against test cases, and submit your solutions — all within a secure, proctored environment.
Assessment Format
A typical assessment includes:
| Component | Description |
|---|---|
| MCQ Questions | Multiple-choice questions testing conceptual knowledge |
| Coding Problems | Write code to solve algorithmic challenges |
| System Design | Draw or describe system architectures (for senior roles) |
| Time Limit | Typically 30-120 minutes depending on the role |
Supported Languages
XEtest supports 20+ programming languages:
Python, TypeScript, JavaScript, Go, Java, C++, C, Rust, Ruby, PHP, SQL (PostgreSQL/MySQL), Kotlin, Swift, Scala, R, Dart, Perl, Haskell, and more.
Choose the language you're most comfortable with unless the assessment restricts language options.
The Code Editor
- Monaco Editor (same as VS Code) with syntax highlighting and autocomplete.
- Run Code: Click "Run" to execute against sample test cases and see output.
- Submit: Finalize your solution. It's tested against hidden edge-case suites.
- Test Results: See which test cases passed/failed with expected vs actual output.
Proctoring Rules
Be aware of the following monitoring during assessments:
| Rule | What Happens |
|---|---|
| Webcam | Periodic snapshots verify you're the only person present. |
| Tab Switching | Switching to other tabs is logged. Excessive switches may trigger warnings or auto-submission. |
| Copy/Paste | Pasting large text blocks into the editor is flagged. |
| Full Screen | You may be required to stay in full-screen mode. |
| Time Tracking | Time spent per question is recorded. |
⚠️ Important: Violating proctoring rules may result in your assessment being flagged or invalidated. Play fair.
Tips for Success
- Read the problem carefully — understand constraints, edge cases, and expected output format.
- Start with brute force — get a working solution first, then optimize.
- Test with edge cases — empty input, single element, max size, negative numbers.
- Manage your time — don't spend too long on one problem. Move on and come back.
- Use the Run button — test frequently instead of trying to write perfect code in one go.
- Comment your code — brief comments showing your approach can earn partial credit.
Troubleshooting
| Issue | Solution |
|---|---|
| Code won't compile | Check syntax errors. Verify language selection matches your code. |
| Runtime error | Check for null/undefined access, array out of bounds, or infinite loops. |
| Time limit exceeded | Optimize your algorithm. Consider different data structures. |
| Page frozen | Refresh the browser. Your code is auto-saved. |
| Can't paste | Copy-paste may be restricted. Type your code manually. |
For urgent technical issues: 📞 +44 7471 530754 | 💬 WhatsApp