BONUS: 5‌ CHECKPOINTS AWARDED WORTH ‌$100‌ EACH

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to the  Synergy - Campus Recruitment Web Application - Part 2 Design Challenge.

This is a follow-up design challenge, we recently completed a design challenge for part of the Campus Recruitment app, which focused on just a few user types. We now have several more user types that we need to design. We have wireframes for all of the remaining users and the UI designs from the previous challenge. We just need to complete the remaining user types and match the current UI designs.

About the Application:
As part of automation of 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 online and makes the overall process simple.

Very excited to see your designs for this challenge!

Round 1

Submit your initial design refinements for Checkpoint Feedback
A. National Campus Manager (NCM)
B. Campus Head (CH)
C. Campus Staffing Manager (CSM)
D. Campus Program Manager (CPM)

You must upload your submission to MarvelApp so we can provide direct feedback on your designs.
Feel free to add any other additional screens which are necessary to explain your concept.
Notes.jpg: Please note any comments about your design for the Client
Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03)

Round 2

Your Final designs for all the required designs with all Checkpoint Feedback implemented.
A. National Campus Manager (NCM)
B. Campus Head (CH)
C. Campus Staffing Manager (CSM)
D. Campus Program Manager (CPM)
E. Campus Operation Executive (COE)
F. Campus Admin (CA)
G. Tech Panel User
H. HR Panel User
I. Campus Auditor

You must upload your submission to MarvelApp, for the final submission - you can reuse the prototype that you shared for checkpoint
Feel free to add any other additional screens which are necessary to explain your concept.
Notes.jpg: Please note any comments about your design for the Client
Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03)

For this challenge we are providing you the wireframes which will act as a reference for the content and we are looking for your help to improve user experience wherever possible. It is also required that your designs align with the existing designs!

Design Considerations:
- Clean and streamlined design and user flow
- Looking for a fresh user-experience!
- We have provided wireframes that were created for the provided requirements, use these as reference for content.
- We are providing designs from previous challenge, need to make sure you are following them and your design is inline with them. Existing designs are based on the branding guidelines provided here - feel free to use any icons from this: https://drive.google.com/file/d/0B6kvOdxpqnKMRlJYY3JiMzV6Y28/view
- It looks like a lot of user types, but a lot of the screens are very similar to what was already designed in the first UI challenge. You should be reusing UI elements and page layouts as much as possible to keep a consistent experience
- Improve the overall user experience and flow of entire application as you see fit.
- You are free to suggest any feature that you think would help with the user experience.
- Design your screens focussing Desktop, so have the resolution as 1366px width and height as required.

Required Screens/ Functionality
We need below concepts in your designs, feel free to add any pages that you think is necessary to show the flow!

A. National Campus Manager (NCM)
01 NCM Dashboard:
Wireframe Reference: ncm_user.html
- Please see 06-01_Dashboard_LCM.png in existing designs and design something similar to keep it consistent.
- This shows the statistics along with the list of colleges, events and master job codes
- Provide a way for the user to change the status of colleges
- Clicking on College name will reveal additional details about the college, how do you think it needs to be shown?
- Please include drop-down styles for the drop-downs in college table.

Event List
- Events created by the LCM will need to be approved or rejected by NCM
- View list of events waiting for approval.
- Should be able to filter the list of events.
- Should be able to see the list of candidates registered for the event, think on how to show the link to view candidates and also how the list of candidates be shown?

02 Master Job Code (MJC):
Reference: master_job.html
- Should be able to view a list of job codes!
- Should be able to search, filter, sort the list of job codes.
- Approve / reject the list of job codes approved by Campus Head.

02 1 View Master Job Code Details:
Reference: master_job_details.html
- On clicking on “Process” button on a job code in the list will show the details.
- The NCM should be able to create Regional Job Code (RJC) to further divide the requirement region wise / think on how this can be done, please see wireframes for reference.
- NCM should be able to allocate how many candidates to be recruited for every region ( North, east, west, Andhra Pradesh, Karnataka, Tamil Nadu, Kerala).
- NCM will select respective LCM (multiple LCM’s can be selected).
- User will have ability to change the status of the job to either “Approved or Rejected” status, also provide a way to enter comments and click on Submit button

03 Event Details:
Reference: event_details_1.html
- Will have ability to view the details of the event and have options to choose as “NCM Event Approved or NCM Event Rejected”, also provide a way to enter comments and click on Submit button.

B. Campus Head (CH):
04 CH Dashboard:
Reference: ch_user.html
- Same as other dashboards, it just has the list of colleges and master job codes
- View list of colleges with an option to send a mail and a way to approve / reject (please follow existing designs 06-01_Dashboard_LCM.png)
- Approve / reject the list of colleges entered.
- They will have option to select a college and assign status as Approve / Reject, also provide a way to enter comments and click on Submit button.

05 Master Job Code list:
Reference: master_job_1.html
- This is same as NCM, just include a version for this user.

05 1 Master Job Code Details:
Reference: master_job_details_1.html
- This is same as NCM but they won’t have option to assign LCM.

C. Campus Staffing Manager (CSM):
06 CSM Dashboard:
Reference: csm_user.html
- This shows the list of master job codes (MJC’s).
- In the list, only those that were rejected will have an edit option / rest of them shows edit as disabled.
- Clicking on “Create New Onboarding Allocation Matrix” will show a modal window..think on how to design them!
- User will have option to create a new master job code

07 View Master Job Code Details:
Reference: master_job_details_2.html
- User will be able to view the master job code details in this page
- Provide way to edit and delete a master job code
- Clicking on “Re-submit” will show a modal window / look to include them as per the existing design style.

07 1 Create New Master Job Code (MJC):
Reference: create_new_master_job_code.html
- User will have the ability to create new master job code.
- Capture all the details from the wireframe
- Include a design for the date picker

D. Campus Program Manager (CPM):
08 CPM Landing Page:
08 1 Nominations:
Reference: cpm_user.html

- Shows nominations for list of events
- User will be able to nominate (accept) or withdraw from the nomination, how to show these in your designs.

08 2 Dockets:
Reference: docket.html

- This shows list of events with option to view docket details

08 2 1 Docket Details:
Reference: docket_details.html
- This shows the docket details
- User will be able to select their attendance information by clicking on the checkbox and be able to submit them!

08 3 Event Sign off:
Reference: event_sign-off.html

- This shows a list of all events that were completed
- Provide a way for the user to select multiple events and click on sign off.

E. Campus Operation Executive (COE):
09 Panel Mobilization:
Reference: coe_user.html
- This shows list of events that can be selected for panel nomination

09 1 Panel:
Reference: panel.html
- Chosen events from the previous step are shown here
- User will be able to search, filter employees and assign / submit the list as a part of the panel for the event

10 Manage Panel Master:
Reference: manage_panel_master.html
- User will be able to view list of panelist and provide a way to search, filter
- Provide options to edit, delete a panelist.
- User will be able add a new panelist

10 1 Add New Panel:
Reference: add_new_panel.html
- User will be able to add a new panelist by entering the details as shown in the wireframes

11 Candidate Audit:
Reference: candidate_audit.html
- This shows the list of candidates with their offers
- User will have option to view more details about the candidate

11 1 Candidate Details:
Reference: campus_candidate_audit_details.html
- This shows the details about the candidate
- User will have option to approve or reject and submit it!

12 Onboarding Allocation Matrix:
- This shows a list of steps to assign a candidate to a training location.
- We need to include a progress bar, please see how the progress bar is designed in the existing designs and look to include them!

Step 1: Onboarding_allocation_matrix:
Reference: onboarding_allocation_matrix.html
- This shows the 1st step in the three step process in assigning Training location for the candidates that were hired.
- This shows the list of batches (list of candidates) grouped by hiring domain
- User will choose a particular batch to move to step 2

Step 2: Stream Allocation:
Reference: stream_allocation.html
- In this step, user will be able to view the list of streams and the required number of hires for each city.
- User will select a particular stream to move forward

Step 3: List of Candidates:
Reference: candidate_details.html
- User will be able to choose the list of candidates and have option to assign them to a particular city for training.

F. Campus Admin (CA):
13 CA Dashboard:
Reference: ca_user.html
- This allows user to upload vendor master, user will be able to upload candidate details for each of the event.
- User will choose “Upload” in the event for which details need to be uploaded.
- Provide ability to “Re-assign Event Status” and “Re-assign Candidate Domain”, should have ability to “Upload Turbo/STAR Hiring internship candidate” - think on how to show these!

13 1 Re-assign Event Status:
Reference: reassign_event.html
- User will be able to view list of candidates with option to choose the event for each of the candidates.

13 2 Re-assign Candidate Domain:
Reference: reassign_candidate_domain.html
- User will be able to see a list of candidates and have ability to change the domain for each of them.
- Also have an option to upload the turbo /star Hiring internship candidate details - should have ability to drag & drop the file, click on the drag & drag area to see a file getting added..think on how to design this experience!

14 Manage LCM:
14 1 List of LCM:
Reference: manage_lcm.html
- User will be able to view list of LCM, follow the content from wireframe and follow the design from the existing designs.
- User will have option to “Map LCM to Event”, and options to edit and delete a LCM
- Provide option to add new LCM.

14 2 Add New LCM:
Reference: add_new_lcm.html

- User will be able to add a new LCM, follow the details in wireframes

14 3 Map LCM to event:
Reference: map_lcm_to_event.html

- User will be able to map LCM to an event by just click on the “map to this event” button in the appropriate event.

15 Manage CPM Master:
Reference: manage_cpm_master.html
- This is same as “10 Manage Panel Master” mentioned above but only difference is we will have option to “Upload CPM master”

G. Tech Panel User:
16 Tech Panel User Landing Page:
Reference: tech_panel_user.html
- We show the list of New events the user has been nominated as a panelist
- User will be able to Accept or Reject them by entering a comment
- For the existing / ongoing event, user will see the list of candidates that have been selected for Group Discussion (GD) Round / they will select the candidates and click proceed to move to GD Results page.

16 1 GD Results:
Reference: gd_results.html
- This shows the GD Details.
- Show list of participating candidates in that particular GD.
- User will be able to select or reject a particular candidate.

17 Fill Interview Assessment Form:
Reference: techical_assessment.html
- User will be able to search, filter and view list of candidates as shown in the wireframes
- User will have option to view candidate's resume and fill the assessment form.

17 1 Assessment Form:
Reference: techical_assessment.html

- This shows details about the candidate and provides way for the user to assess the candidate
- At the bottom, you can see option to specify whether the candidate is selected or rejected.
- Please see wireframes, looking forward to your thoughts on how this can be designed!

18 Feedback:
Reference: feedback_1.html
- This shows the list of the events that the user attended
- They will have a way to provide feedback for each and every event

18 1 Feedback Form:
Reference: feedback_form.html

- This page allows the user to provide feedback for the event
- Please see the list of fields required in the wireframe
- Show us how this page can be designed.

H. HR Panel User:
19 HR Panel User Landing Page:
Reference: assessment_form_-_non_eng.html
- This is same as 17 1 Assessment Form (techical_assessment.html) but we have few changes in the form, please look to capture them

I. Campus Auditor:
20 Campus Auditor Landing Page:
Reference: campus_auditor_user.html
- This shows the list of candidate
- User will be able to assign a status to the candidate (s).

20 1 Candidate Clarification:
Reference: clarification.html

- This shows the list of candidates who had status as RED and had provided clarification
- User will be able to view further details about the candidate

20 1 1 Candidate Audit Details:
Reference: campus_candidate_audit_details_1.html

- This page allows the user to review and change the status of the candidate along with a comment.

20 2 Cleared:
Reference: cleared.html

- This shows the list of candidates who were cleared by the auditor.

20 3 Candidate Clarification:
Reference: rejected.html

- This shows the list of candidates who were rejected by the auditor.

Judging Criteria
Your submission will be judged on the following criteria:
- Overall idea and execution of concepts
- How well does your design align with the objectives of the challenge
- Execution and thoughtfulness put into the solving the problem
- Overall design and user experience
- Cleanliness of screen design and user flow

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

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
Submit JPG/PNG for your submission files.

Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop and saved as a layered PSD file, or Adobe Illustrator as a layered AI file or Sketch!

Final Fixes
As part of the final fixes phase, you may be asked to modify your graphics (sizes or colors) or modify overall colors. We may ask you to update your design or graphics based on checkpoint feedback.

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.

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.

ELIGIBLE EVENTS:

2018 Topcoder(R) Open

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

  • Layered PSD files created in Adobe Photoshop or similar
  • AI files created in Adobe Illustrator or similar

You must include all source files with your submission.

Submission limit

5 submissions

ID: 30059752