Update frontend challenge requirements by littleStudent · Pull Request #8 · getmimo/coding-challenge

littleStudent · 2026-04-21T05:39:30Z

Updates the frontend challenge description to reflect new requirements including:

Open-ended challenge approach
Focus on UX, code structure, and LLM collaboration
Self-built API requirement
Updated submission guidelines

Kliriklara

Just pointing out some typos and small things, so Christopher and I don't do them twice. Will continue with the review

Kliriklara · 2026-04-21T12:07:01Z

 ## Welcome!

-To give you an idea of how some of the work as mobile engineering team member will look and help us get an impression of how you might approach these tasks, we've put together a take-home assignment. We’re doing this asynchronously because we know that, despite our best efforts to create a laid-back atmosphere, live coding interviews can be stressful and results may not be representative of your work. We believe going through the assignment at your own pace is a more natural way to achieve this goal. We know that completing the assignment will require some time investment and we really appreciate you taking this time. We believe this is a win-win situation and we wouldn't ask you if we didn't already think you're a great fit for the role.
+To give you an idea of how some of the work as a frpmtemd engineering team member will look and help us get an impression of how you might approach these tasks, we've put together a take-home assignment. We're doing this asynchronously because we know that, despite our best efforts to create a laid-back atmosphere, live coding interviews can be stressful and results may not be representative of your work. We believe going through the assignment at your own pace is a more natural way to achieve this goal. We know that completing the assignment will require some time investment and we really appreciate you taking this time. We believe this is a win-win situation and we wouldn't ask you if we didn't already think you're a great fit for the role.


Suggested change

To give you an idea of how some of the work as a frpmtemd engineering team member will look and help us get an impression of how you might approach these tasks, we've put together a take-home assignment. We're doing this asynchronously because we know that, despite our best efforts to create a laid-back atmosphere, live coding interviews can be stressful and results may not be representative of your work. We believe going through the assignment at your own pace is a more natural way to achieve this goal. We know that completing the assignment will require some time investment and we really appreciate you taking this time. We believe this is a win-win situation and we wouldn't ask you if we didn't already think you're a great fit for the role.

To give you an idea of how some of the work as a frontend engineering team member will look and help us get an impression of how you might approach these tasks, we've put together a take-home assignment. We're doing this asynchronously because we know that, despite our best efforts to create a laid-back atmosphere, live coding interviews can be stressful and results may not be representative of your work. We believe going through the assignment at your own pace is a more natural way to achieve this goal. We know that completing the assignment will require some time investment and we really appreciate you taking this time. We believe this is a win-win situation and we wouldn't ask you if we didn't already think you're a great fit for the role.

Kliriklara · 2026-04-21T12:13:09Z

+
+## Important
+
+- **User Experience (UX):** How does the app feel to use? Consider loading states, error handling, feedback, accessibility, and the overall flow. The visual design itself is not important, but the experience is.


If this is fed into an LLM, then it would do loading states, error handling, feedback & accessibility. I would rather that people think about this themselves as part of this challenge.

So maybe we could phrase it broader:

Suggested change

- **User Experience (UX):** How does the app feel to use? Consider loading states, error handling, feedback, accessibility, and the overall flow. The visual design itself is not important, but the experience is.

- **User Experience (UX):** How does the app feel to use? Think beyond the happy path and design an experience that feels intuitive and easy to follow for new learners.

Kliriklara · 2026-04-21T12:18:26Z

+
+## What We Value
+
+- Solve the challeng by using react


Suggested change

- Solve the challeng by using react

- Solve the challenge by using react

Kliriklara · 2026-04-21T12:18:41Z

+- Solve the challeng by using react
 - Try to think about how you manage your state and how you structure it.
- You won't be judged on the visual design, the only metric is your code.
+- he main metrics for judgment are your LLM usage, your code and UX.


Suggested change

- he main metrics for judgment are your LLM usage, your code and UX.

- The main metrics for judgment are your LLM usage, your code and UX.

Kliriklara · 2026-04-21T12:18:51Z

+- **Code Structure and Architecture:** How do you manage state? How is your code organized? We look for clean separation of concerns, maintainability, and thoughtful architectural decisions.
+- **LLM Collaboration:** You must use **OpenCode** to build this challenge. We want to see how you work with AI — share your OpenCode session link (or multiple) with your submission. We are interested in your prompts, iterations, and how you leverage LLMs in your workflow.
+- **openrouter api key:** We will provide an openrouter api key which you can use with opencode.
+- **dont invest more than 5hours:** Rather use the readme to describe what you would work on next. We do want to protect your time.


Suggested change

- **dont invest more than 5hours:** Rather use the readme to describe what you would work on next. We do want to protect your time.

- **don't invest more than 5hours:** Rather use the readme to describe what you would work on next. We do want to protect your time.

Kliriklara

The challenge looks good and exciting!

I do think the challenge is quite ambitious. People will need some time to get familiar with the domain, and come up with a lesson & lesson interaction idea before even starting to develop.

I left a comment, but I would make it clear that people can focus on what they think is most important, and add any trade-offs or scope cuts to the README. (I find those READMEs often very telling).

Kliriklara · 2026-04-21T12:36:10Z

+- **Code Structure and Architecture:** How do you manage state? How is your code organized? We look for clean separation of concerns, maintainability, and thoughtful architectural decisions.
+- **LLM Collaboration:** You must use **OpenCode** to build this challenge. We want to see how you work with AI — share your OpenCode session link (or multiple) with your submission. We are interested in your prompts, iterations, and how you leverage LLMs in your workflow.
+- **openrouter api key:** We will provide an openrouter api key which you can use with opencode.
+- **dont invest more than 5hours:** Rather use the readme to describe what you would work on next. We do want to protect your time.


The scope does seem quite ambitious. We're asking for a lot

Coming up with a lesson idea

Designing 3-5 lessons

A fairly ok design with CSS

good ux with error, loading states etc

Using openrouter (might be a slightly new tool to some)

Good architecture/separation of concerns.

API design + implementation

We could say here

Suggested change

- **dont invest more than 5hours:** Rather use the readme to describe what you would work on next. We do want to protect your time.

- **Don't invest more than 5hours:** The scope is ambitions, so focus on the topics that feel most important to you. If you need to make trade-offs or cut scope, that is absolutely fine! Use the readme to share your thinking and what you would work on next. We do want to protect your time.

Kliriklara · 2026-04-21T12:42:34Z

+- **User Experience (UX):** How does the app feel to use? Consider loading states, error handling, feedback, accessibility, and the overall flow. The visual design itself is not important, but the experience is.
+- **The learning content** Invest time into the learning content. Your job is to create a great experience for the user.
+- **Code Structure and Architecture:** How do you manage state? How is your code organized? We look for clean separation of concerns, maintainability, and thoughtful architectural decisions.
+- **LLM Collaboration:** You must use **OpenCode** to build this challenge. We want to see how you work with AI — share your OpenCode session link (or multiple) with your submission. We are interested in your prompts, iterations, and how you leverage LLMs in your workflow.


Should we set the expectation here that people should exclusively use OpenCode (e.g. no manual coding)? That's how it sounds like.

I would phrase it a bit more openly

Suggested change

- **LLM Collaboration:** You must use **OpenCode** to build this challenge. We want to see how you work with AI — share your OpenCode session link (or multiple) with your submission. We are interested in your prompts, iterations, and how you leverage LLMs in your workflow.

- **LLM Collaboration:** You must use **OpenCode** while working on this challenge. You don't need to use it exclusively but we want to see how you work with AI — please share your OpenCode session link (or multiple) with your submission. We are interested in your prompts, iterations, and how you leverage LLMs in your workflow.

Maybe we should also add a link to the opencode docs about sharing

Kliriklara · 2026-04-21T12:45:01Z

-  }
-}
-```
+Your goal is to write a small app that teaches a user **how to add a button to a homepage** through a series of interactive lessons. Assume your users are full beginners and understand nearly nothing about coding. You decide how many lessons to include (we suggest 3–5) and how to structure them.


Suggested change

Your goal is to write a small app that teaches a user **how to add a button to a homepage** through a series of interactive lessons. Assume your users are full beginners and understand nearly nothing about coding. You decide how many lessons to include (we suggest 3–5) and how to structure them.

Your goal is to write a small web app that teaches a user **how to add a button to a homepage** through a series of interactive lessons. Assume your users are full beginners and understand nearly nothing about coding. You decide how many lessons to include (we suggest 3–5) and how to structure them.

Just to avoid any confusion 😅

Kliriklara · 2026-04-21T12:47:16Z


+1. A link to your private GitHub repository.
+2. Your **OpenCode session link** so we can review how you collaborated with AI during the challenge.
+3. A README with instructions on how to run both the app and the API locally.


Suggested change

3. A README with instructions on how to run both the app and the API locally.

3. A README with instructions on how to run both the app and the API locally, plus a short note on any trade-offs you made and what you would work on next.

I find those READMEs often very telling, so I would quite like if people add their thoughts and trade-offs to it.

Update frontend challenge requirements

ebdc653

littleStudent requested review from Kliriklara and simerlec April 21, 2026 11:58

Kliriklara reviewed Apr 21, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update frontend challenge requirements#8

Update frontend challenge requirements#8
littleStudent wants to merge 1 commit intomasterfrom
update-frontend-challenge-requirements

littleStudent commented Apr 21, 2026

Uh oh!

Kliriklara left a comment

Uh oh!

Kliriklara Apr 21, 2026

Uh oh!

Kliriklara Apr 21, 2026

Uh oh!

Kliriklara Apr 21, 2026

Uh oh!

Kliriklara Apr 21, 2026

Uh oh!

Kliriklara Apr 21, 2026

Uh oh!

Kliriklara left a comment

Uh oh!

Kliriklara Apr 21, 2026

Uh oh!

Kliriklara Apr 21, 2026 •

edited

Loading

Uh oh!

simerlec Apr 21, 2026

Uh oh!

Kliriklara Apr 21, 2026

Uh oh!

Kliriklara Apr 21, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants


		## Important

		- User Experience (UX): How does the app feel to use? Consider loading states, error handling, feedback, accessibility, and the overall flow. The visual design itself is not important, but the experience is.

	- Solve the challeng by using react
	- Solve the challenge by using react

	- he main metrics for judgment are your LLM usage, your code and UX.
	- The main metrics for judgment are your LLM usage, your code and UX.

	- dont invest more than 5hours: Rather use the readme to describe what you would work on next. We do want to protect your time.
	- don't invest more than 5hours: Rather use the readme to describe what you would work on next. We do want to protect your time.

	- dont invest more than 5hours: Rather use the readme to describe what you would work on next. We do want to protect your time.
	- Don't invest more than 5hours: The scope is ambitions, so focus on the topics that feel most important to you. If you need to make trade-offs or cut scope, that is absolutely fine! Use the readme to share your thinking and what you would work on next. We do want to protect your time.

	- LLM Collaboration: You must use OpenCode to build this challenge. We want to see how you work with AI — share your OpenCode session link (or multiple) with your submission. We are interested in your prompts, iterations, and how you leverage LLMs in your workflow.
	- LLM Collaboration: You must use OpenCode while working on this challenge. You don't need to use it exclusively but we want to see how you work with AI — please share your OpenCode session link (or multiple) with your submission. We are interested in your prompts, iterations, and how you leverage LLMs in your workflow.

	Your goal is to write a small app that teaches a user how to add a button to a homepage through a series of interactive lessons. Assume your users are full beginners and understand nearly nothing about coding. You decide how many lessons to include (we suggest 3–5) and how to structure them.
	Your goal is to write a small web app that teaches a user how to add a button to a homepage through a series of interactive lessons. Assume your users are full beginners and understand nearly nothing about coding. You decide how many lessons to include (we suggest 3–5) and how to structure them.

	3. A README with instructions on how to run both the app and the API locally.
	3. A README with instructions on how to run both the app and the API locally, plus a short note on any trade-offs you made and what you would work on next.

Conversation

littleStudent commented Apr 21, 2026

Uh oh!

Kliriklara left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Kliriklara left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Kliriklara Apr 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Kliriklara Apr 21, 2026 •

edited

Loading