Hi, thanks for your interest in ACM's backend development team! Your task is to write a design doc for a "quest system" that integrates into the membership portal and then schedule an interview that'll be some mix of design review, technical, and behavioral.
First you'll need to understand how the portal works at the API and database layers—the portal doesn't currently have a service layer—and then design appropriate API and database changes for the required functionality. Your priority should be a working design, not a clever one; bonus points if you explain why yours is definitively the best or if you consider multiple designs and explain the tradeoffs of each. There's no right answer and this is an exercise intended to see how you approach some functionality you'd reasonably be expected to implement as a backend developer for ACM—there's no limit to how deep your changes to the portal can go. The portal's being completely rewritten so don't worry about any current constraints (e.g. what