Skip to content

Latest commit

 

History

History
64 lines (49 loc) · 2.21 KB

File metadata and controls

64 lines (49 loc) · 2.21 KB

ShiMart Coding Test Preparation Guide

Required Tools

Git (Required for all environments)

  • Git: Version control system for cloning and working with the repository

What to Prepare

For C# Development

  • .NET SDK: .NET Core 8.0 or compatible version
  • IDE: Visual Studio, Visual Studio Code, JetBrains Rider, or any editor of your choice

For Python Development

  • Python: Version 3.6 or higher
  • Editor/IDE: PyCharm, VS Code, or any Python editor of your choice

For Java Development

  • Java JDK: Version 8 or higher (supports up to 21 LTS)
  • Build Tools: Maven or Gradle (both are supported in the project)
  • IDE: Any Java IDE of your choice (IntelliJ IDEA, Eclipse, VS Code, etc.)

For TypeScript Development

  • Node.js: Latest LTS version recommended
  • npm: Comes with Node.js
  • TypeScript: Will be installed via npm
  • Editor/IDE: VS Code, WebStorm, or any TypeScript-capable editor of your choice

Allowed Tools and Resources

ALLOWED

  • Any IDE or Code Editor of your choice
  • Google and Online Documentation (official language docs, Stack Overflow, etc.)
  • Standard IDE Features:
    • Syntax highlighting
    • Auto-completion for language syntax
    • Code formatting
    • Refactoring tools (rename, extract method, etc.)
    • Debugging tools
    • Unit test runners
  • Package managers (npm, pip, NuGet, Maven, etc.)

NOT ALLOWED

  • AI-powered coding assistants (GitHub Copilot, Amazon CodeWhisperer, etc.)
    • While we do allow (and provide) AI tools in our day to day work environment, we're looking to see your own problem solving skills here
  • AI auto-completion tools
  • ChatGPT, Claude, or any other AI chatbots
  • Pre-written code from previous projects (except standard boilerplate)

Interview Timeline

The interview is 1.5 hours total, structured as follows:

  • ~15 minutes: Introductions and repository setup
  • ~50-60 minutes: Coding exercise
  • ~15-20 minutes: Discussion and code review

Tips for Success

  • Be prepared with your language and environment
  • Focus on understanding the existing code first
  • Implement the new feature correctly
  • Ensure existing functionality isn't broken
  • Ask clarifying questions if needed