eQuest Job Posting Dashboard
From specifications team Nyantek designed a dashboard for eQuest's applicant tracking system which aggregates job boards from across the web. The dashboard allows users to create their job listing once and submit it to job boards all over the web. This SaaS product is meant to be used on desktop and is for trained professionals.
Role: UI designer with UX sensibilities
Teammates: Nate McMillin, Jason Hsu
Timeline: Three weeks
Teammates: Nate McMillin, Jason Hsu
Timeline: Three weeks
Once the user has signed into their account or entered as a guest, they'll find a list of popular job boards, or boards that were accessed in the past. There are three "views" for board-posting layout, on the left is the list view and on the right the small card view (yes, some of the board info is duplicate, but this is a prototype). The home page has filters and search, and selected boards are added to a visible cart that can be edited at any time. Favorite boards can be managed from profile preferences.
I provided designs for login screens and profile preferences which were then translated into code by the dev. team.
To ensure my login-screen prototype would be user friendly I studied how other teams created a great experience and borrowed ideas. I didn't want to leave something important out.
To ensure my login-screen prototype would be user friendly I studied how other teams created a great experience and borrowed ideas. I didn't want to leave something important out.
Posting a job has a long list of input fields, way too many to put into one screen, so we broke them down into smaller more manageable chunks. Below are steps one and two.
Below are screens I designed for payment confirmation and job posting details.
The screen-flow ensured that job-boards could be selected as well as removed from a cart that was always up to date, that the user always knew what page they were on, and received confirmation that their actions were registered by the system.
The screen-flow ensured that job-boards could be selected as well as removed from a cart that was always up to date, that the user always knew what page they were on, and received confirmation that their actions were registered by the system.
Final Thoughts
As the design process continued we discussed the interface deeper and obtained stakeholder feedback, this led us to make direct changes and find solutions to this complicated product. My goal is to seek many possible use cases in flat pixel prototypes so that functional errors are caught before going into production. What are the edge cases? What catastrophic errors can we prevent? Sadly I was taken off of this project for another higher priority one and never got to implement the changes that would make this project shine.
Allotting time for iterations leads to a better design.
Allotting time for iterations leads to a better design.
Next Project