kreas / dayone Goto Github PK

As a user, I can create and update my developer profile.

Acceptance Criteria

1. Users can create a developer profile
2. Users can update their profile until DayOne approves the profile.
   1. When a profile is approved, it becomes publicly available along with a share link
   2. Personal information such as email and phone number are redacted from the public profile.
   3. The developer can edit the profile after it has been approved, but doing so will send a request back to DayOne for approval.

As a developer, I can complete the interview process with DayOne, so that I can apply for multiple jobs with out needing to go through the interview process each time.

Acceptance Criteria

As a user, I can register for DayOne so that I can create a profile for my role.

Acceptance Criteria

1. Users can register using MemberStack
2. When a user registers for MemberStack:
   1. They receive an email confirming their account was created
   2. They are added to the newsletter mailing list.
3. A record is created in AirTable
4. A record is created in WebflowCMS
5. The user is redirected to the profile creation page

As a Developer, when I create a profile, I am prompted to complete a code challenge.

1. Once a developer creates their profile, a link is sent to them that contains the code challenge.
   1. We capture when the code challenge was started and when they completed it.
   2. The code challenge is 2-3 questions with a definitive answer.
   3. Once the code challenge is complete, the code they used to complete the challenge is also captured.
2. Once the code challenge is accepted, DayOne staff can request an interview.
   1. Requesting an interview with the developer sends an email to the user with a link to the interviews calendar.
   2. The email links to a WebFlow page with information about the interviewer and their calendar.
   3. The developer is also given a guide showing what to expect during the interview process.
   4. A Coda doc is created to help conduct the interview.
3. If the code challenge is rejected, The user receives a rejection email
   1. An a email is sent to the developer detailing why the challenge was rejected
   2. They are invited to retake the challenge.
   3. If they are rejected a second time, they will be unable to take the code challenge again for 3 months.
      1. An email is sent detailing why they failed and when they will be eligible to try again.