What Is The Purpose Of An Architecture Portfolio?
/
Disclaimer: As an Amazon Associate I earn from qualifying purchases. There are affiliate links in this post. This means that at no cost to you, I will receive a commission if you purchase through my link. I will only ever promote the products and services that I trust and 100% recommend. You may read my full disclosure policy for more information. Thank you for supporting my business in this way.
There are many different reasons why you would want to create an architecture portfolio. From graduate school and internships to scholarships and fellowships.
The primary focus for this post is getting a job at an architecture office — either large or small.
To help you with your architecture job search, I've created a mega-pack of free resources that includes architecture resumes, cover letters, and an extensive collection of application documents.
The main reason for creating an application portfolio is to share your work, experience and talents in a compact package that can be easily understood by the hiring manager.
Regardless of your strengths and weaknesses your goal with a portfolio is to effectively communicate what you can bring to the office.
Defining your work
Defining your work can be successfully done in any number of ways. For example, you may want to emphasize how you solved a particular problem in a project or how you creatively developed a particular design idea.
There are no wrong answers, but it is the poor, unclear execution of those answers is what you want to avoid. Before including anything in your portfolio ask yourself the question, "what am I trying to convey with this?".
For instance, a building site image. Are you showing the photo to explain how you learned about the construction materials and methods? If so, then clearly explain yourself.
A casual observer might just see the image and not understand its role in your portfolio. This can be easily achieved through text in an application portfolio or verbally at the interview. While this sounds obvious, it is often overlooked by job applicants.
Can you have a look at this?
You often know your own work so intimately that it can be difficult to prepare it for someone who knows nothing of you work.
One way to overcome this issue is to have a someone edit your application documents, not just as an proofreader but as a third-party observer. If you can explain your work to them, it is likely the hiring manager will be able to understand your projects.
Know your audience
The key to a successful portfolio submission and ultimately landing the job you want is knowing your audience. In this case it is the architecture office that you are applying.
The more information you can collect on your selected target the better.
What type and scale are their typical projects? Do they do local or international work? What software do they use?
For instance, you many need to take classes to improve your abilities with a particular program.
Once you have collected this data it becomes much easier for you to tailor your portfolio to the firm. You may even discover this is not somewhere you want to work because it doesn't align with your career or personal goals.
For this reason you should try to meet with current employees to get their honest feedback. Keep in mind that many people are negative about their employment situation, but don't let that derail your goals. Disneyland is paradise for some and hell for others.
How does the hiring process work? Who will be reviewing my portfolio? What format do you prefer?
If you were looking to hire and someone called with these genuine questions would you be put off by their subsequent application? Of course not, quite the opposite.
If you are looking to make a career change into architecture or even within a different sector you may have to find creative ways to build those skills. One option is to pursue the projects you wish to work on full time either through freelance work or design competitions. This is certainly no easy task but if you want something bad enough you will find the time.
Don't be afraid to contact the office directly and ask what they are looking for in an applicant.
To include or not to include
Perhaps just as important as knowing what to include in your portfolios is what not to include. While some people may try, it is not a record of your entire academic and working career. Not only is your time finite but so is the person's time you will be asking to review it.
Back when portfolios were simply mailed hard copies there was a built-in limiter — the printing budget. No one wanted so spend thousands of dollars on printing in the hopes of landing an interview.
However, now that restriction has been lifted with the advent of digital portfolios. This has been both a blessing and a curse. The portfolio length, formatting and design options are infinite, creating an overwhelming challenge.
See also: Should You Use An Online Architecture Portfolio?
Rule #1 (There is no Rule #2)
Regardless of which stage you are on one rule remains true: your portfolio is a collection of your most intriguing and relevant work.
See also: 5 Reasons Why You Need Multiple Architecture Portfolios
Also keep in mind that your application portfolio will have to clearly describe your projects via text, diagrams or other easily comprehensible methods. On the other hand your interview portfolio will not have to be as self explanatory since you will be there to provide commentary.
Organization
I recommend, depending on your experience that you organize your portfolio by project typologies. There is no benefit to organizing by firm or chronologically.
For example, would it matter that the most relevant project you have worked on was from two years ago?
No, that would be the project you would want to start the discussion with. This is why it is important to know all of you previous projects inside and out.
The order of importance for portfolio presentation:
1. A project relevant to the role you are applying AND shows your most valuable skills and attributes
2. A project that shows your most valuable skills and attributes
3. A project relevant to the firm's typology or expertise you are applying
4. A project relevant to the person interviewing you (remember people love to talk about themselves)
5. A particularly interesting project for discussion
You are better off presenting a potentially less glamorous project you know more intimately than a project that is impressive but you only spent a few weeks on or had a lesser role.
Want to find your dream architecture job?
Check out The Architect's Guide Resources.
To help you with your architecture job search, I've created a mega-pack of free resources that includes architecture resumes, cover letters, and an extensive collection of application documents.
Thanks for reading, see also my posts on:
3 Tips to Get An Architecture Job With No Experience
Where To Apply For Architecture Jobs Online
The Two Page Architecture Portfolio
Good luck!
Brandon Hubbard, AIA, NCARB, LEED AP BD+C
Have a suggestion for a future blog post? Please let me know in the comments below.
