Wordle Coding Exercise

Wordle Coding Exercise

Review the game Wordle at https://www.nytimes.com/games/wordle/index.html

If you’ve never played, Wordle is a game where you have 6 guesses to guess the word of the day. Each guess must be a valid 5-letter word. A guess is submitted by using the enter key. After each guess, the color of the letter tiles will change to show how close your guess was to the word.

1. Green – the letter is in the word and in the correct spot
2. Yellow – the letter is in the word but in the wrong spot
3. Grey – the letter is not in the word

Here’s an example of a completed game:

You can see the game provides feedback in two ways. First, on the letter tyles of each guess on the guess board. Second, on the keyboard. On the keyboard, you see the letters not yet used in guesses and the same colors for those letters used in previous guesses (green, yellow, dark grey).

The game provides simple feedback when you guess correctly or when you run out of guesses.

The Challenge

Now it’s your turn. Build your own version of Wordle. Take it as far as you’d like given the amount of time you have between when you receive this challenge and your interview.

It is a coding challenge, so we want to walk through some code for sure. However, we also want to talk through your design and approach. Why you made certain decisions, assumptions, approaches to components, services, etc.

Front-end Focus

If you assume the word of the comes from a service, how would you approach the front-end. What’s done client-side vs server-side. What are you expecting to be done by the back end.

Back-end Focus

As a back-end developer, the service layer is your responsibility. Design an appropriate API that you envision being needed to allow the front-end to just focus on making the game look good. Show us your design and some of the services you anticipate delivering.

Intent

We want to review your code and style, how you approach things, etc. We also want to review how you make decisions of what to tackle given the constraints you face. So, even if you have other examples of your code out there in public repositories, we want to review a fresh repo that is specific to this challenge. Here’s some general rules:

DO	Do Not
Think for yourself. Give the challenge a go. Google for assistance on things that will help – things how to know when keys are pressed.	Look for exiting solutions to the challenge on the internet. This would be considered cheating and would disqualify you as a candidate!!!
Create a private repo and invite us to it. You’ll have our email address when the interview email is sent out.	Create a public repo for others to find.

It’s not important that you finish, it’s important for you to try. It’s important that what we review is a true reflection of you and your craftsmanship.