Challenge Summary

Welcome to IBM - SiBM Blueview Interview Helper Mobile Wireframe Challenge!

Our application is designed to digitize the process for capturing feedback during the interview on a mobile device. Following the interview, data can easily be sent to HR to analyze and track candidates.

Round 1

Submit your wireframe for a Checkpoint feedback:
Please submit your initial wireframe designs for:
1. HR User.
2. Interviewer User.
- Any notes for client.

Round 2

Final wireframe plus any Checkpoint feedback:
1. HR User.
2. Interviewer User.
- Any notes for client.


Challenge Details:
The goal of this mobile application is to help IBM interviewers capture candidate’s information during the interview process. This will help the interviewers do their job easily and the data captured can be sent directly to HR to analyze and track.

We are looking for wireframe (Axure) solutions based on requirements below. We’re also looking to the community to come up with interesting ideas for the workflow - we’re absolutely open to creative solutions!

At the end of this wireframe challenge, we are looking to have a complete solution for the user experience and flow of the application.

Wireframe Expectations:
- Produce HTML click through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The website must be very easy to use and intuitive. Keep that in mind when designing your solution.
- You MUST cover all screens mentioned in required new sections below, if any requirement is missing in final submission the client will not take a look at it, so make a checklist for the required screens to make sure you designed all of them.
- Please show us your proposal as a movie or series of wireframes that communicate the user’s intended interaction with your proposed solution.
- You MUST use wireframes note pane in every single page you design to explain what items are addressed in that page from the documentation, what things you added/changed/removed, use it to make your idea clearer and help the client to give you constructive feedback.

Notes:
- Your solution need use Responsive Design Solution when viewed on Portrait and Landscape view of Mobile device.
- We would like you to pay attention to the IBM Design Language: http://www.ibm.com/design/language/
- Your wireframe submission needs to drill down to provide views of all pages
- Show your wireframe solution on Portrait View. Use this screen size (375px x 663px)
- Feel free to suggest any tools/function that can bring good User Experience for this Mobile Application.

User story:
A) User: HR (Human Resources)
1. Login to app on a web page.
2. Selection of Geographic Region for interview (e.g., New York, Massachusetts, Connecticut).
3. Selection of Geographic Location for interview (e.g., Somers, Yorktown Heights, White Plains, for New York).
4. Selection of Competency for interviewee (e.g., Java programmer, Mobile developer, Quality Engineer, Release Engineer).
5. Upload interviewee resume.
6. Select the people who will do the interviews (1-3), and pick the date / time of each interview(s).

The HR person will also use the app in the following ways:
- After the interview(s), the HR person should see a list of people who have been interviewed, and read the notes of the interview.
- They also need a view of all the interviewees, and who the interviewers are.
- They will also need a view of the dates and times of interviews (can be multiple, if the person has two or more rounds of interviews).
- Ability to edit (e.g., if an interview is not accepted, and another candidate needs to be picked).
- HR person can add/remove/edit the list of interviewers per location / competency.
- The interviewer will be emailed the notes of interviews as well as receive a notification in the mobile app when they login.

B) User: Interviewer
1. Login to app on the tablet.
2. Option to view notifications--allotted time and date with the details of HR who has triggered that.
3. Will be assigned candidates for interview--the interviewer will have list of candidates assigned to them for the interview. The interviewer can accept or deny the interview (two buttons (a) ACCEPT (b) DECLINE) -- If the interviewer can not take the interview, they can add some information about why -- that information is sent back to HR person.
4. Select “ACCEPT” option: (Once this is done, the status of the candidate will change to “In Progress”).
- Here, the screen should be divided into two: ie one side with evaluation criteria and other side with candidate profile (note: you should not be visually dividing the screen in half; think in terms of tabs or toggles that allow users to switch views quickly. Looking for your ideas on how this can function!)
--- Select the competency -- (note -- there can be more than one competency for an applicant).
--- Based on the competencies selected, appropriate evaluation criteria will be listed.
--- Interviewer can start the interview and at the same time he can mark scores against the listed skills.
- Once complete, interviewer can click on the "CALCULATE" button, this will automatically calculate the final score of the interview, followed by allowing the interviewer to give and edit comments on the interviewee.
- Interviewer will press "ACCEPT / DECLINE" button which triggers email and app notification to HR. There should be option to add additional form fields to the email response. Interviewers can add and save additional fields within the app.
- Notification for the selected candidate should be in the format of:                                           
--- Interviewer Name:
--- Candidate Name:
--- Employee ID:
--- Notes ID:
--- Candidate Feedback:
--- JRSS (this means job role: some examples are Java, Mobile, Analytics, Mainframe, SAP); note that there can be subcategories, as well -- such as Java.ejb, Java. Spring -- and this can be a very large list:
--- Role Suggested:
- Based on interview rating calculation and interviewer comments, HR can decide whether the selected candidate is selected for next round. If yes, repeat the same process for the second round. (Different person, interviewing the same candidate, with same criteria selection).

Here is some sample data to use for the kinds of questions someone would need to figure out about an applicant:

Knowledge of Java language, OOP basics, Javascript, EJB, Communication skills, Servlets, XML, Webservices, Tools
Each of these might have subcategories, such as for Tools: IDEs, Build tools, Testing frameworks, Logging frameworks

 

Learn Axure:
New to Axure? Here are some quick tutorials to help you get started.
http://www.axure.com/learn

Target Users:
The app will be used from 2 main users:
- IBM HR.
- IBM Interviewer.

Judging Criteria:
- User Experience of Blueview Interviewer Helper App.
- Completeness and accuracy of the wireframe as defined in the spec requirements.
- How well your wireframes provide a consistent user flow.

Submission & Source Files:
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.

Submission File
Generated HTML files with all the requested contest requirements stated above.

Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.

Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.

Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.

Stock Photography

Stock photography is not allowed in this challenge. All submitted elements must be designed solely by you. See this page for more details.

How To Submit

  • New to Studio? ‌Learn how to compete here
  • Upload your submission in three parts (Learn more here). Your design should be finalized and should contain only a single design concept (do not include multiple designs in a single submission).
  • If your submission wins, your source files must be correct and “Final Fixes” (if applicable) must be completed before payment can be released.
  • You may submit as many times as you'd like during the submission phase, but only the number of files listed above in the Submission Limit that you rank the highest will be considered. You can change the order of your submissions at any time during the submission phase. If you make revisions to your design, please delete submissions you are replacing.

Winner Selection

Submissions are viewable to the client as they are entered into the challenge. Winners are selected by the client and are chosen solely at the client's discretion.

Challenge links

Screening Scorecard

Submission format

Your Design Files:

  1. Look for instructions in this challenge regarding what files to provide.
  2. Place your submission files into a "Submission.zip" file.
  3. Place all of your source files into a "Source.zip" file.
  4. Declare your fonts, stock photos, and icons in a "Declaration.txt" file.
  5. Create a JPG preview file.
  6. Place the 4 files you just created into a single zip file. This will be what you upload.

Trouble formatting your submission or want to learn more? ‌Read the FAQ.

Fonts, Stock Photos, and Icons:

All fonts, stock photos, and icons within your design must be declared when you submit. DO NOT include any 3rd party files in your submission or source files. Read about the policy.

Screening:

All submissions are screened for eligibility before the challenge holder picks winners. Don't let your hard work go to waste. Learn more about how to  pass screening.

Challenge links

Questions? ‌Ask in the Challenge Discussion Forums.

Source files

  • HTML
  • RP file created with Axure

You must include all source files with your submission.

Submission limit

5 submissions

ID: 30051010