Do you want to join Quave as a developer? Great. Read this document and then submit your solution. Good luck.

• Install Node.js
  • Use nvm to install Node.js
• Install Meteor

If you're new to Meteor, we recommend this tutorial to get familiar with it.

This project uses Meteor 3 with Node.js 20. It's in the final release candidates as of June 29, 2024.

Use the Meteor 3 docs as a reference: https://v3-docs.meteor.com/

The Quave ESLint plugin is configured to throw errors if you use the old Meteor API. We recommend using the new Meteor 3 API on the server, which is typically async.

• Use this git repository as your starting point.
• Once completed, remember to push your changes.
• Submit this challenge via a GitHub Classroom assignment (read more below).

meteor npm install

meteor npm start

A mini-application that allows event hosts to check people into an event.

The home page should show:

• An event selector displaying each event's name. By default, it should display Select an event (communities collection).
• A list of people registered in the selected event (people collection).

The list of people should allow the event host to:

• See the full name (first and last name together), company name, title, check-in date, and check-out date in the MM/DD/YYYY, HH:mm format or as N/A.
• Check people into the event by clicking the Check-in {person firstName and lastName} button.
• If the user was checked in over five seconds ago, show a Check-out {person firstName and lastName} button.

Between the event selector and the list of people, display a summary like this:

• People in the event right now: 10
• People by company in the event right now: Green Group (10), Hoppe Group (5)
• People not checked in: 200

The page needs to be reactive -- no refresh should be needed to display the latest data.

• Use Meteor as the builder and runner, React as the view layer, and MongoDB as the data layer.
• Use MongoDB embedded in Meteor; don't configure the project to access a different MongoDB URL.
• Style the application using TailwindCSS.
• Do not insert new documents into the communities or people collections.
• Do not change initial-data.js.
• You can add new dependencies.

• We encourage the use of AI tools to generate code, but the developer needs to understand all the code generated and be able to: a) explain the code and b) explain why it's the best choice for the use case. If during the interview we realize you don't understand any part of the code you used in your solution, you will be eliminated from the process. The same applies to any question we ask during the video interview.
• An automatic process will check your solution. Follow the requirements closely; only submissions that pass the tests will be considered.
• We will not answer any questions about this challenge to ensure all submissions are fairly compared.

• Complete this challenge via a GitHub Classroom assignment.
• Is your solution ready for review? Respond to this form.
• Our team will review your submission and provide feedback via PR or email within 15 work days.