Synergy - Campus Recruitment Web Application Wireframe Challenge

Welcome to Synergy - Campus Recruitment Web Application Wireframe Challenge. In this challenge, we are looking for your help to come up with a new user experience for an existing application.

Client of this challenge is looking to automate their Hiring Module for Campus Graduates, the change is to enable the entire process from end to end to automate the hiring for Engineering & Non engineering graduates in campus/colleges. By automation of the requirements - all the approvals are done online and makes the overall process simple.

There are multiple users in this application, in this challenge we are looking to handle the flow for 3 users.

At the end of this challenge, we are looking to see intuitive and easy to use "wireframe concepts" that will help us design and build UI/UX in the next phase of this project!
Be creative in your wireframes!

Round 1

Submit your initial wireframes for checkpoint review.
A. Campus Placement Coordinator (CPC)
B. Location Campus Manager (LCM)

Feel free to add any screens which are necessary to explain your concept.

Round 2

Submit your initial wireframes for checkpoint review.
A. Campus Placement Coordinator (CPC)
B. Location Campus Manager (LCM)
C. Candidate
?
Feel free to add any screens which are necessary to explain your concept.

Task of this challenge is to come up with wireframes for the below provided use-cases.

Design Problem:
Current process of hiring Module for Campus Graduates requires lot of approvals and these offline transaction makes things complex. Allocation of resources were not accurate and tracking becomes was not an easy job.

We also have an existing application which looks very complex in-terms of design as well as the functionality / overall flow of the application looks complicated. Through this wireframe challenge we are looking for your help to improve the overall user experience and flow of entire application as you see fit.

IMPORTANT:
- We have provided screenshots from the existing application which looks very complex, so please make sure you are NOT copying the screens and flow from that.
- Improve the overall user experience and flow of entire application as you see fit.
- Most of functionalities will be similar among users (like approving or rejecting something, etc)..so make sure to have the same user experience for all users.
- You are free to suggest any feature that you think would help with the user experience.
- Existing application can be referred for content that will be required in your wireframes
- We are not wireframing/ designing every screen in the document. We are just pulling out key screens that we can then use to build a UI kit for development

Wireframe Considerations:
- Provide us with your interaction and click-path thoughts and suggestions
- 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 you create your solution for the layout and flow information.
- You MUST cover all requirements mentioned in challenge details below.

Suggested Screens:
There are multiple users in this application, we are looking for your help to improve the overall flow and user experience of this application.
NOTE: You are not limited to the screens listed below, feel free to add any screens that are required to show the flow of your concepts.

General (All Users):
00 Login:
- All users will be required to login into their account
- To login they will enter their username and password
- What else do you think need to be shown in this page?

01 Dashboard:
- Once logged in, they will be taken to the dashboard with a welcome message.
- Should have a way to view the list of notifications.
- For some users, dashboard need to show the list of items that need to be approved / rejected.
- How should the navigation be shown?

A. Campus Placement Coordinator (CPC)
02 College Registration:
Reference: Page 3
- Will have ability to enter details about the college (add new college)
- Details that will be entered are “Type of College, Institute Name, Authorized Personnel, Address, State, City, contact information“
- Once all details Submit the Details about the college
- On Successful registration, we need to show the success message!
- This college that was registered will need to be approved by LCM (see below) after which CPC user will move onto the next step which involves entering detailed information about college in the empanelment form.

03 Empanelment Form:
Reference: Page 4 to 8
- Once logged in, user will need to enter details in empanelment form.
- This form includes the following sections “Institute profile, Quantitative Details, Faculty Details, Students details, Placement history”
- Each of these sections will have specific details that need to be entered by the user.
- Looking forward to your thoughts on how the progress in each of the sections can be shown / how will the user know the section they are entering details for.

B. Location Campus Manager (LCM):
- Provides a way to send / resend Campus Registration Link to all the CPC.

04 Approve / Reject College:
Reference: Page 9
- Should be able to view list of colleges waiting for approval!
- Should be able to search, filter, sort the list of colleges.
- Approve / reject the list of colleges entered by CPC.
- They will have option to select a college and assign status as Pre-approved / Pre-rejected, also provide a way to enter comments and click on Submit button.

05 View Event / Event Details:
Reference: Page 9, 10
- Should be able to view list of events
- Allow user to search for events based on Event ID or Event Name
- User should be able to view click on an event and view more details
- Provide a way for the user to modify the event (please see page 16, 17, 18)
- Event Sign-off: Once the event has been completed at the campus, LCM will be responsible for signing off the event (Reference: Page 24, 25)

06 Event Creation:
Reference: Page 10 to 16
- User will be able to create a event for off-campus or on-campus (single or group event).
- To create an event user will first see the list of MJC (job codes), from that they will be able to choose job code for which the event need to be created.
- They will need to choose the category (Engineering or Non-engineering), and Two Types of Campus Events can be created (Single Campus Event Type or Group Campus Event Type)
- Based on the Event type selected appropriate details need to be entered / chosen (see below).
- Event start date should be greater than the current date and Registration end date should not be greater than the event dates and Registration end date should not be less than system date

Single Campus Event:
- Event will take place only in the selected college and the candidate of that college only will participate in the event.
- Select the Campus Event Type as “Single”.
- Multiple Hiring Domains can be selected
- Provide a way to assign multiple CPM’s, user will be able to search and assign CPM’s, they will be able to search using Employee ID or Email ID
- If 1 CPM is selected during event creation, that CPM will be the CPM for that event. If multiple CPM’s are selected during event creation then nomination accepted CPM will be the CPM
for that event.
- Please see screenshots for the all the details that need to be entered.

Group Campus Event:
- Master college is considered as the Venue for the Event, candidates from two or more college will participate in the event.
- Select the Campus Event Type as “Group”.
- Multiple Hiring Domains can be selected.
- Should be able to select the master college (by default it will be college for which event is being created) and sub-colleges that will participate in the event.
- Please see screenshots for the details to be entered.

07 View Registered Candidates / Initial Screening:
Reference: Page 18, 19, 20
- User should be able to view all the registered candidates along with basic information like name, marks, event id, 10th , 12th, UG/ PG score, degree & branches, etc.
- LCM should be filter based on various parameters like Graduation branch, year , score% etc
- LCM should be able to select or reject the candidates based on the filter results.
- Based on the score LCM should be able to categorize toppers and non topper (page 19)
- LCM will decide the hiring workflow for toppers and non toppers. Ex: All topper candidates will directly goto written test and non toppers will go to group discussion if applicable.
- Information on selected, rejected candidate data should be available to LCMs
- If GD is applicable, group discussion batch assignment should be done automatically by the system (admin should be given an option to set the parameter for batch assignment).
- Boarding pass with a QR code should be generated for the toppers and non toppers and the info should be passed on to onboarding portal.
- The boarding pass with a QR code should be sent to the candidates through a mail/ SMS (page 33)
- Rejected candidates should be communicated.

08 Trigger LOI:
Reference: Page 20 to 24
- User should be able to search candidates who cleared all rounds of interview by "event name, event id, event type, event from, to dates and reference no.
- Provide an option to preview the LOI before triggering or re-triggering the LOI to the candidates.
- From the list of the candidate's, user will be able to select the candidates to whom LOI should trigger and Click on “Send LOI” button.
- Once LOI is sent, they should be able to able to see the list of candidates to whom LOI is already sent.
- Also provide option to resend/re-trigger the LOI.

C: Candidate:
09 Candidate Registration
Reference: Page 26, 27
- Candidate can register for the event themselves using the URL that was sent to the candidate in the mail
- Candidate will be required to enter all the required details and click Register.

10 Candidate Login:
- Candidate should be able to log in via a social network ID or create a separate user ID and password on onboarding portal.
- The candidate should be able to enter his aadhar no. (this is a Unique Identification number assigned to each individual in India, Example format: XXXX-XXXX-XXXX) and system should be able to extract basic information from that.
- Candidate should be asked to enter his mobile no. & primary email address and it should be verified immediately with OTP.
- Show a success message and allow them to login with their login details. Candidate should also be confirmed through email & SMS that his login details has been successfully created.

11 Candidate Onboarding Portal:
Reference: Page 28 to 32
- Candidates will be required to fill their details and should be able to save his progress.
- Once the user has registered for the event, they should be able to login and upload their resume.

Candidate Application Manual (CAM):
- They should be able to UPDATE their resume at any time till they report for the campus interview.
- The basic candidate details should be parsed, extracted and auto populated in the registration form from candidate resume where possible automatically.
- Candidate should be able verify and edit (if required) the auto populated registration form details. Form filling progress should be saved automatically (like OneNote).
- He should also be able to fill in missing details and submit the form once finished. Without filling all the basic details he should not be able to submit the form.
- Candidates should be confirmed that their information has been successfully uploaded via portal, email & SMS.
- The candidate should be able to cancel and opt out of the recruitment process at any point of time.

12 Boarding Pass:
Reference: Page 32
- Once the candidate send their details (CAM), and on approval, boarding pass will be generated (which they will be carrying to attend the event)
- Candidate should be able to view their boarding pass

Below use-cases / functionalities are shown once the candidate has cleared the interview and on accepting LOI.

13 Unified Form / Uploading of Docs:
- Candidates who received the LOI (letter of intent - page 33) will be required to upload the docs for background verification (BGV).
- Users will be able to upload their docs and data are automatically captured in the unified form
- Candidate will be responsible for filling out any details that are missing.
- Users will be able to save the progress of their upload and send it at a later time.

14 Offer Acceptance / Rejection:
Reference: page 34 to 36
- User will be able to see their offer letter once the BGV is completed, candidate should receive a notification once they receive the offer letter.
- Candidate should be able to view, accept or reject the offer letter on candidate portal
- In case of rejection, candidate would be dropped from the process.

15 Campus Onboarding Flow:
Reference: Page 37, 38
- Once candidate is added to the onboarding pool, a variety of contents, notifications, articles should be displayed on onboarding portal.
- The candidate should be able to select his seat based on his preference for location, DOJ, stream & BU.
- Candidate should be able to postpone DOJ to a later date. Candidate should also have an option to mark against a particular opening as favorite. System should notify the candidate when ever similar opening is available and be given first priority.
- Notifications should be sent to candidates on allocations
- Once selected seat has been confirmed by the portal, the candidate should be added to list of candidates joining .
- Candidates who reject should be alerted that offer would be cancelled and on confirmation necessary notifications should be sent.
- In case the candidate has taken no action, he should be able to view next month's matrix when released and select a seat if he is ready.
- In case the candidate has selected a seat and later cancels, he should be asked for the reason.
- If the reason for cancellation is candidate is unable to join as per the seat selected, but he is still interested in joining the company; then his reservation should be cancelled & he should be added to the last batch pool which should be allowed the last for reservation.
- If the reason for cancellation is candidate is no longer interested in joining the company, then the offer should be withdrawn and he should get out of the process.
- If the candidate has not reserved any seat for multiple rounds, CPM should be able to contact the candidate and prompt him to join.
- Joining information like DOJ, venue, contact person should be displayed on candidate portal

16 Candidate Feedback:
- Feedback form will be enabled for offer and To-offer candidates after event sign-off.
- Candidates should be able to provide feedback on how the event was conducted, etc.
- They will be able to choose rating as "Excellent, Very Good, Good, Average, Not good" and also have ability to provide comments for each of the question.
- Should be able to provide an overall comment.

17 Candidate Helpdesk:
- Throughout the process, the candidate should be able to raise a helpline request in case he needs help.
- Following details need to be entered while raising a request “reference no, contact details, module, topic, comments”
- The manager campus team should be able to see and resolve the request.

Target Audience
- University / College Admin, prospective students, HR

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

Judging Criteria
- User Experience of the application/portal
- Completeness and accuracy of your wireframes
- 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
Wireframes should be built in HTML or Axure

Source Files
All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file.

Final Fixes
As part of the final fixes phase you may be asked to modify content or user click paths.