How you describe your work is as important as opening your portfolio in a graphic design interview. Don't turn the conversation into just a list of programs you use. Be prepared to clearly explain what problem you saw in a project, how you made your decision, and how you evaluated the outcome.
Describe a project in four steps
First explain the brief and target audience. Then specify constraints such as time, content, or production. In step three, justify two important decisions you made. Finally, share the result and the point you would improve if you revisited it today. This order makes it easier for the other person to understand not only the image but also your contribution.
For example, instead of saying "I made it more modern" in the catalog project, you can explain that you put the feature fields in the same order to facilitate product comparison. Don't claim to increase sales if you haven't measured the impact. Maintain distinction between observation, user feedback, and measured result.
What questions can you prepare for?
- What was the first problem you tried to solve in this design?
- Do you have an alternative that was rejected, why was it eliminated?
- Which decision did you change with the feedback you received?
- How did you prepare the file for production or developer?
- Which part of the team did you take on?
These questions are preparation suggestions; It is not the actual interview question list of a particular company. Instead of memorizing your answers, work in a way that you can show evidence from your own project. Acknowledging the area that is lacking and explaining how you will improve it is a more reliable narrative than owning up to the work that hasn't been done.
Discuss scope in design essay
If a test run is requested, clarify the goal, expected output, and time to allocate. Discuss the difference between extensive production to be used in the real campaign and limited practice to understand the skill. Ask about any uncertainties such as terms of use and pricing in writing before delivery; These are not carried out the same way in every institution.
Evaluate your working order too
Who will give feedback, how many jobs will be executed simultaneously, who will control the production file? Try to understand the daily tasks as well as the title of the posting. Working areas of graphic design graduates reserves these questions for the agency, brand team and freelance model.
I am Selçuk Aker, a graduate of Marmara University, Faculty of Fine Arts, Graphic Design. My focus in this article on the transition from education to business life is to present one's design decisions in an understandable way. If you haven't chosen your samples yet, you can start from first portfolio guide.
What do you document when preparing a presentation for a design competition?
When applying for a web design contest or awards program, don't just create impressive screenshots. The purpose of the project, your role, the constraints encountered, and the problem solved should be clear. Clarify the scope of sharing with the customer; Do not disclose confidential data or access to anyone.
You can prepare a brief project summary, examples of different screens, and verifiable information about actual use of the work. Don't make up a success rate if there is no outcome data. Application calendar, categories and rules may differ in each organization; Check the organization's official announcement rather than accepting the terms on an old blog as current. This section is not a claim to have won a prize or current entry guide for the particular contest.
Frequently asked questions
In what order should I describe the project during the design interview?
Explain the problem and goal first, then the constraints, design decisions, and outcome. If it is a team effort, make your own contribution; Do not present an unmeasured impact as a percentage of success.
How can I defend a criticized design in my portfolio?
Instead of getting into a debate about taste, explain the goal and conditions on which your decision is based. If the critique indicates a new usage problem, acknowledge it and explain what change you will try.
