Technical Assignment

Recruiting developers over the past few weeks has been a busy process. Even when candidates perform well during interviews, many struggle with the technical assignments. This is why I want to focus on technical assignments today.

There are three main aspects of technical assignments:

1. Preparation
2. Assignment
3. Delivery

Let's dive into each of them.

1. Preparation

Before diving into the assignment, it’s crucial to clearly understand its requirements. Ask yourself:

• What is the primary goal of the task?
• What should be the top priority?

Typically, you’ll be given a few tasks to complete within a limited time frame. If you’re asked to spend more than three hours on the assignment, it may be closer to a complete project, which I believe should be paid.

During this phase, clarify the requirements and ensure you know who the point of contact is for any questions. Never start an assignment without a clear understanding of the expected outcome. However, avoid asking how to complete the task – it is your responsibility.

It’s also worth noting that no one expects you to complete 100% of the assignment. Focus on the most important tasks and be prepared to deprioritize less critical aspects.

2. Assignment Execution

The goal here is to deliver a working code and ensure that your results are meaningful and meet the objectives.

Some key points to keep in mind:

• Clean Code: Ensure your code is well-structured and follows coding standards. Remove any commented-out debugging code like var_dump(), die(), or exit().
• Documentation: Include proper documentation, such as PHPDOC, and exclude irrelevant files.
• Coding Standards & Design Patterns: Follow standard practices and design patterns. Use the specified versions of frameworks and languages; if not specified, opt for the most maintainable, scalable, and performant options.
• Version Compatibility: Use the correct version of languages or frameworks specified in the assignment. If none are specified, choose versions that support long-term maintenance and scalability.

Remember, you may be asked to explain your technical decisions during the following interview.

3. Delivery of the Assignment

Many developers make mistakes by overlooking the packaging and delivery process. Here are some crucial points:

• File Packaging: When submitting your work, ensure the package is clean and doesn't contain unnecessary files. For example, MacOS developers often include hidden files that become visible when extracted on Linux systems. Avoid this by double-checking your archive.
• README.MD: Always include a README.MD file that provides essential information:
  • How to install and run the project.
  • Are any additional configurations or steps required?
• Generated Files: If you were asked to generate specific files, ensure they are included.
• Database Migrations: If migrations are part of the assignment, include only necessary migrations. Avoid situations where old database structures are referenced, leading to failures during execution.

The key is to deliver the assignment at the highest level possible, ensuring the reviewer can test or check it without spending extra time fixing configuration issues.

I hope this guide helps you succeed in your technical assignments. If you have any questions or comments, please use the contact form to reach out.