RAFAEL MACIEL

FULL STACK DEVELOPER WEBSITE

Alexandre Bispo

Alexandre Bispo is a full stack developer from Rio de Janeiro.

Challenge

To open new opportunities for Alexandre Bispo in the website development market.

My role

Stakeholder interviews, user reasearch, and user interface design.

KPIS

How to measure success?

Increase job opportunities.

Increase mentions of the website over the web.

01

Meeting the user

PERSONA

"I'm afraid to hire the wrong developer."

ABOUT

Age: 40
Income: High
Technology Proficiency: High
Favorite Brands: Apple, Google.

CORE NEEDS

I want to have a talented team and I must trust them.

Members of my team have to be passionate about their work.

I have to understand what is my team weakness.

Recruiting new members shouldn’t be so painful.

USER PSYCHOLOGY

MOTIVATION . BELONGING “I'm proud of the talented team that I work with."

USER INTERVIEW

SWIPE TO VIEW THE FULL TABLE

PAIN X SOLUTION
Developers apply for a job that they are not qualified to. It's a waste of time and frustrating for both sides.	To show clearly what is the level of knowledge Alexandre has in each set of skills.
Some developers aren't good communicators, don't understand design process and are weak strategists (giving wrong deadlines, not helping designers understanding what's possible or how to keep things simple).	To show some of Alexandre's soft skills. He worked for some time side by side with designers, and some of them were print designers, he has experience in explaining how things work, bringing simple solutions and warning about solutions with high effort for few ROI. He has some basic knowledge in design tools too. To have a blog with content that confirms these soft and technical skills.
When you see a portfolio it is difficult to know what the person did in the project or even how it was made.	Every portfolio case has exactly what he did: programming language, frameworks used etc. and a sample, so the recruiter is able to check the right version he developed.

Developers apply for a job that they are not qualified to. It's a waste of time and frustrating for both sides.

To show clearly what is the level of knowledge Alexandre has in each set of skills.

Some developers aren't good communicators, don't understand design process and are weak strategists (giving wrong deadlines, not helping designers understanding what's possible or how to keep things simple).

To show some of Alexandre's soft skills. He worked for some time side by side with designers, and some of them were print designers, he has experience in explaining how things work, bringing simple solutions and warning about solutions with high effort for few ROI. He has some basic knowledge in design tools too.

To have a blog with content that confirms these soft and technical skills.

When you see a portfolio it is difficult to know what the person did in the project or even how it was made.

Every portfolio case has exactly what he did: programming language, frameworks used etc. and a sample, so the recruiter is able to check the right version he developed.

02

User Interface

HOME

EXPANDED MENU

IA AND STRATEGY

01. The developer role
Recruiters can see exactly what Alexandre did in the project: technologies, frameworks and a sample of the version that he actually coded. Therefore, they can feel more comfortable when deciding to hire him.

02. Years of experience
As an experienced developer, showing years of experience is an advantage for him.

03. Skill level
This information is very important, because it avoids any misunderstanding or frustrations when hiring him and recruiters know exactly what to expect from his work.

04. Blog
I’ve encouraged him to start a blog. Besides showing passion about his career, he can learn more, spread his knowledge and engage with the dev community.

STYLE GUIDE

Colors

Interface color palette

TYPOGRAPHY

ELEMENTS

Navigation Items

Form Items

OTHER

ICONS

03

Final Words

Since I know many designers and developers, who are often hiring developers, it was never so easy to recruit users for testing the website :). In the end, the main objective, that even before launching the site I managed to fulfill, was to encourage Alexandre to start writing, be engaged with the dev community and put more focus on his career.