Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create mockups for Assessment SPA #2

Open
bsemot opened this issue Dec 26, 2018 · 5 comments
Open

Create mockups for Assessment SPA #2

bsemot opened this issue Dec 26, 2018 · 5 comments
Assignees

Comments

@bsemot
Copy link

bsemot commented Dec 26, 2018

Following the Material design concept and Material UI components, we need to have mockups for assessment application UX

  • Mockups for the candidate login screen
  • Mockups for assessment starting, infographic and section screens
  • Mockups for question screens (cover each question type)
  • Mockups for result screen
@bsemot
Copy link
Author

bsemot commented Dec 28, 2018

Candidate Login Screen Mockup

assessment app - candidate login

@koraytaylan koraytaylan transferred this issue from EmakinaTR/makina Dec 30, 2018
@tolgaevcimen
Copy link

tolgaevcimen commented Jan 8, 2019

I think we need few clarifications before moving forward with the mockups. Maybe we already have answers to below ambiguities, but I'm unaware of them as I couldn't find them written anywhere.

  • Question types needs to be defined, few I can think of are:
    • multiple choice-single selection (generilised version for true-false questions too)
    • multiple choice-multi selection
    • open answer questions
    • coding expected questions (i think it would be nice to have an input field that only accepts code snippets - maybe even highlighted according to the language)
    • any other types? any not wanted types among above suggestions?
  • I and @mahsumdemir remember we talked that the candidate login screen is going to be accessed via a url like assessment.emakina.com.tr (a generic url), not through an invitation link, so we don't know the name or assesment type of the candidate in the first screen. Sure we can show those information in the second screen no problem. But let's clarify this as it affects the first screens mockups.
  • What level of result will there be on the result screen?
    • Overall score?
    • Score for each section?
    • All questions with the wrong/correct feedback?
    • No result, just "we'll call you" message?

@bsemot , @koraytaylan can you provide some input on this?

@tolgaevcimen
Copy link

tolgaevcimen commented Jan 9, 2019

Here is the mockup for generic question screen (https://www.figma.com/file/gIC5qGUSTcaom4Zj3mgtwd19/Candidate-Test-Screen?node-id=0%3A1)

questionscreentemplate-v1

Note: Tried to attach the fig file but git does not support it in the comments. If any one needs it, let me know.

@bsemot
Copy link
Author

bsemot commented Jan 11, 2019

@tolgaevcimen below my answers to your questions,

First of all, please not only consider items only as questions but informations or polls. So here are the possible rendering types inside a section;

Types

  • Radio ( multiple choice, single selection. Number of choices are not limited. 2 or more.)
  • Boolean (True or False question may be we can ignore this while the Radio option also covers it)
  • Number (Expecting a numeric "int, double, float" input) for calculation / math questions
  • String (obvious but we might need to choose single line text input or a textarea)
  • Rating (it might not be a question but collecting feedback about assessment. Or a question like "please rate your frontend capabilities between 0 to 10" )
  • Code (given a problem and ask for a code, or given a code to fix the problems on it)
  • Checkbox (multiple choice multiple selection like "select the 2 correct ones from below 5 statements")
  • Information (nothing for candidate but just giving a message, it has no effect on final result calculation)
  • Comment (given a pull request kind of code block and ask the candidate to review it with multiple
    comments on different lines)

Accessing the assessment
Candidate can only access the assessment via the link over mail. This link will contain a hash code which will give us the opportunity to recognize the candidate, the expiration of the assessment and also the profile of the assessment. We will not ask candidates to reach the url and try to register. They will have a 4-5 digit authentication token to enter which is also shared in that mail invitation.

Scoring
We will not share any result score with the candidate. Only an information about timings can be shared. Because at the stage of candidate finishing his/her assessment, there will be many answers waiting for Emakina review (open ended questions, code reviews etc) that will effect the final result. We will send a detailed report to candidate later on like "You took the n'th position between the candidates took the same assessment ,etc."

@tolgaevcimen
Copy link

tolgaevcimen commented Jan 11, 2019

@bsemot answers are taken. Thanks for the clarifications.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants