A website showcasing UX design works, resume and blog posts
ROLE: UX Designer, Logo/Graphic Designer, Developer
PORTFOLIO is indispensable and irreplaceable for UX Designers to showcase equipped skills, helping recruiters make a better choice on a qualified candidate.
At the stage of looking for jobs, recruiters are the primary users, even thought I am using portfolio as a tool to sell myself.
If considered from the big picture view, as keeping updating portfolio encourages retrospection, which brings many benefits on the way of learning stuff, I will be the main user.
Blog readers and designers
Since I have no ambitions to be a blog influencer, I wouldn’t target this group, but I do feel cheerful if someone gets inspiration from thoughts I shared.
As a recruiter, I want to find a candidate whose skill sets match the job duties and responsibilities, so that we are more likely to issue an offer letter after interviews.
As a recruiter, I want to know a candidate from different perspectives, so that I can reckon that they will fit in the new working environment and get along with colleagues.
As a recruiter, I want to find information in a portfolio as quickly as possible, so that it largely improves my work efficiency.
As a Recruiter, I want to get in touch with the candidate, so that we can discuss the position or arrange an interview.
When: During working hours
Where: Office, Home(WFH), On the move
Device: Desktop(most likely), Mobile phone, None(hard copy document)
Different formats of portfolio:
Ideate & prioritise
Enable users to interact with content displayed with text, illustrations, videos, or animations.
Easy to get access, navigate and share
Users don’t need to download and store documents in a local folder, and documents can be shared with only one click. With well-designed information architecture, users can find right information and return back to where they were quickly.
Consider from my own (one of target users) perspective, I choose website for two personal reasons:
Since I would like to make the website not only a portfolio for UX works but also a journal, taking thoughts that occur to me when learning things. By doing so, tangled ideas could be sorted out through retrospection and reflection. By posting on the website, ideas could be shared, which, hopefully, can inspire someone.
Learning and practicing coding
Though I don’t expect to work as a programmer at my next position, coding my own website is a rare opportunity to make use of those languages I learned, which can raise a sense of accomplishment. Also, if choosing from one of the themes or templates already there, that means it won’t be personalized and well-design, but I believe that portfolio should have its position in one’s design works.
Efficiency is important when recruiters are dealing with a large number of applications, so a portfolio should display information in a way that they can capture useful information while scanning a page. Also, details should be ready for them to dive into.
Information that recruiters are most likely to look for includes:
Actions they might take when browsing:
Environmental factors should be taken into consideration when users are getting access through a mobile phone:
What you see is the Version 1.0, changes made will be updated soon.
To be Evaluated
Feedback is on the way…
Feel free to drop me an email, if you would like to have your say 😀
Finally, it’s time to wrap up, which means this website is almost done and going to play a role. I feel exhilarated and a little bit worried. The sense of accomplishment is even intensive, as it’s no longer completed for an assignment at Uni. Instead, it’s essential for the customer(it’s me) to start a career. Worries come from endless bugs that I’ve been solved. That’s one of the risks that I had to take when choosing to develop the website without using any online templates and plugins. Ok, enough for the web development.
Speaking of the design process, an interesting question haunted me for a while, “Who’s the user of a portfolio website? Recruiters or job seekers? What if it’s just a hard copy of their resume?”
It’s easy to understand that customers sometimes are not the users. For example, Moms buy books for their kids. Moms are customers, while kids are users. If it’s a resume or portfolio, the line seems not clear, since applicants do interact with their documents a lot during the preparation, and from their perspective, they are using those documents to launch a job. That’s where I was confused.
Now I got two ideas to disentangle these thoughts. It might be helpful when targeting user groups next time. Firstly, consider where the final interaction happens. Think job hunters as a customer with others preparing their resume or portfolio for them, then the final interaction becomes more clear. Also, if it’s a portfolio website, recruiters are those who will be browsing content, click on a button, and navigate between pages on your website. Secondly, consider if your users have their target users of this product. Similar to the way of looking for interactions. Take the mom buying books for her kids as an example. Her kids are targets for reading those books.