4 Quick Thoughts on Test Projects for Design Jobs
I pay for Squarespace and thoughtfully design my portfolio. I update my resume. I thoroughly answer the application’s questions. I get the follow-up email asking if I’d like to set up a video interview.
“Of course,” I respond.
During the interview, the hiring manager asks if I can complete a test project. A signal that I’ve survived the 1st phase of the hiring process.
“Of course”, I respond again.
The test project is something I hadn’t experienced before entering the design profession. Whenever I used to apply for jobs, the employer only seemed to care about my professional experience, social skills, and goals.
To be honest, I hated the 1st time I had to do a test project. I thought, “Isn’t my portfolio enough? Why drag the hiring process out? Maybe my smile isn’t white enough.”
But things have changed.
Now I actually appreciate test projects. Here’s why. #
- You get to learn about new users and their problems. These might be different from those you currently design for.
- You get to pitch ideas that could potentially make a big impact on the company you’d be working for.
- You get a taste of what’d it be like to design for the company on a daily basis. This helps validate the assumption that you’d actually enjoy showing up every morning.
- You get extra practice. Designing new ideas and concepts is something you probably do during free hours anyways. So you don’t have to view it as a waste of time. The skills have to stay sharp no matter what.
The Benefits are Mutual #
I’m in the middle of a test project for a brand I’ve admired for a few years. That’s why I’m thinking through this stuff.
Yeah, I guess it would be nice if this particular employer only looked at my portfolio and then handed me a salary with benefits. But ultimately, I don’t think that’d be helpful to either party.
The test project experience can be just as useful to the candidate as it is to the employer.