↵

What's your thought on design tasks for a job application?

5 years ago from Anmol Bahl, UX Designer - Feminist | Say hi@anmolbahl.com

  • Adam Fisher-CoxAdam Fisher-Cox, 5 years ago

    There is a difference between a practical interview and doing work for your company without being paid. Far too many design tasks are just "work on this project we're working on."

    If the task is a hypothetical constructed specifically for the hiring process that is of no use to the company, other than to judge your abilities, then that is fine. But it should be judging something you can't get from the portfolio, it should be specifically time and scope limited, and it should be absolutely clear that it will not benefit the company's bottom line.

    0 points
    • Aaron Wears Many HatsAaron Wears Many Hats, 5 years ago

      I agree, practical tests shouldn't be contributing to IP - though a good company would know better than that.

      At the same time I've had enough years of hiring people to know that pretty portfolios don't necessarily mean someone can complete a deliverable in a particular timeframe, or work to processes or directions. Hiring someone purely based on their portfolio - unless they have some killer references - is usually a recipe for disaster. (Of course there's always exceptions, but you know.)

      0 points
      • Adam Fisher-CoxAdam Fisher-Cox, 5 years ago

        Right, but a lot of those things you point out are what an interview is for. Ask about their process in building their portfolio pieces. Ask about timeframes, their experience with different types of management, etc. None of those things really demand a test, and I think it serves the company to be more aware of the interviewer's time and to recognize that it's unlikely that this is the only company the applicant is interested in.

        0 points