nimblehq.co

Recruitment Challenges

Hero image for Recruitment Challenges

Upon passing the first interview, applicants need to work on a challenge which relates to the position they have applied for i.e. Ruby, Elixir, Golang or JavaScript test for web developers, Android or iOS test for mobile developers, Product test for Product Managers, UX/UI test for designers, etc. The team has dedicated challenges for each position they advertise 🤓

Any applicant gets one week to complete the assignment from the comfort of their home. Commitment-wise, each applicant should allocate between 4-8 hours, but it varies greatly based on their own aptitude and workflows.

The challenge allows the team to assess “real world” skills that interviews cannot deliver. It is also a chance for the applicant to collaborate with their members, and thus experience how they actually work. The submissions will never be used for commercial purposes.

Developers

The challenge requires building a small application from scratch with a single feature. Applicants have the opportunity to show how they can architect a small application from scratch using the best practices of software development encompassing code structure, maintainability, security, and testing.

All code must be submitted via a public git-based code versioning platform such as GitHub, Bitbucket, and GitLab. Upon submitting the link to the code repository, applicants need to make sure that the issue tracker is enabled on the repository so that the team can submit their code review feedback.

Upon reception of the submission by email, the team usually takes anywhere between 1-3 days to do a complete code review. As previously mentioned, they open issues to provide their feedback that usually fits into the following types:

  • Questions regarding implementation details. Often raised when the team needs clarifications on a technical choice taken by the applicant, e.g., design pattern, non-standard third-party library (or not known to them). The purpose is for applicants to explain the reasons for their decision.
  • Recommendation to change the implementations. The team might recommend some of its best practices and other ways to implement the same feature.
  • Bugs. Upon testing the small application, the team encountered technical issues or a feature did not work as expected.

Applicants are invited to interact with the team by replying directly to the open issues and also have the opportunity to fix or change the code following the code review comments. So the code challenge is really a participative process, not a submission-and-waiting-and-praying-everything-goes-well step. The main goal is to find developers the team would love to work with, so show them how awesome you are in the code review đź’Ş

Product Managers

The challenge requires reviewing one of the team’s current or past products. Applicants are expected to:

  • Provide recommendations on improving existing features.
  • Provide recommendations on potential new features.
  • Find, report, and classify any kind of bugs/issues in the product.

Applicants are free to choose the format in which they want to submit their report e.g. test document, presentation, spreadsheet, website, blog article, etc.

Upon reception of the submission by email, the team usually takes anywhere between 3-5 days to do a complete review. The team puts great emphasis on the following:

  • Care and attention to detail in the way to present the report.
  • The business value of recommendations.
  • Clarity of the content.

The team’s review will be emailed back to the applicant.

UX/UI Designers

The challenge is broken down into two tasks:

  1. UX

Applicants need to create a UX flow for a specific feature for a fictive company in a specific industry e.g. eCommerce checkout flow for a job board, payment flow for a bank, etc. Only the main screens are expected in order to make the task smaller in scope.

The UX flow must be submitted in PDF format.

  1. UI

Applicants need to create a single screen for a fictive company in a specific industry, e.g., the homepage for a music application, the checkout page for an online grocery store, etc. The UI must be a single page and be responsive if the assignment is for a web application.

The challenge leaves lots of room for applicants to show the team their personality since there are no constraints on colors, fonts, images, or illustrations.

The design must be submitted as a single PNG file along with the original source on Figma.

Upon reception of the submission by email, the team usually takes anywhere between 3-5 days to do a complete review.

The team’s review will be emailed back to the applicant.

Talent Acquisition and People Operations

The challenge requires providing recommendations on multiple aspects of Talent Acquisition or People Operations, including high-level strategy and tactics.

Applicants are expected to provide recommendations relevant to the company specifically (geography, industry, and team size).

Applicants are free to choose the format in which they want to submit their report, e.g., test document, presentation, or others…

Upon reception of the submission by email, the team usually takes anywhere between 3-5 days to do a complete review. The team puts great emphasis on the following:

  • Care and attention to detail in the way to present the report.
  • Business value and implementation feasibility of recommendations.

The team’s review will be emailed back to the applicant.