I'm making a resume and I'm looking for any helpful advice on what to include, specifically for those looking for an entry level job in architecture. Thoughts?
Non Sequitur
Jun 1, 18 11:44 am
Whatever you do, don't add a graph or chart showing your software skills.
nabrU
Jun 2, 18 3:34 pm
I wish this site had a like button. I agree.
nabrU
Jun 2, 18 3:46 pm
Also don’t layout portfolio pages as if they are competition boards with extreme restrictions on number of boards/pages. White space does not add to file size.
somewhat_concerned
Jun 5, 18 11:49 am
Ha...I do have that in my current one. Why do you think that shouldn't be included? Is it because it would be a biased assessment of my skills since I'm making it?
somewhat_concerned
Jun 5, 18 11:51 am
True! I heard white space is always a good thing
Non Sequitur
Jun 5, 18 11:57 am
Get rid of it. Everyone thinks they are software wizards right out of school because they can press the render button. oooooh 9/10 in revit? how modest of you.
somewhat_concerned
Jun 5, 18 12:33 pm
Should I just list the softwares I feel most comfortable/proficient using?
Non Sequitur
Jun 5, 18 12:36 pm
Yes. List the software without making a big deal of your self-evaluated skills. Make proficient and working knowledge columns if you must split them.
thatsthat
Jun 1, 18 11:53 am
Don't make it too cheesy or try to puff yourself up like you have a lot of experience if you don't. Be honest about your experience and your past roles in projects if you have any. Portray yourself as someone eager to learn and wanting to pitch in and do your part to help on a team. If you're applying for entry level, it's assumed that you know little to nothing so do not try to portray yourself as an expert of anything, including software.
My resume matches my portfolio, as do my personal business cards, and my website.
I can't say for sure that it's the graphic consistency, but I seem to get more callbacks / interviews than with my old black serif on white layout. Ours is a design profession, and it's good to remember that that extends beyond your specifically architectural projects.
somewhat_concerned
Jun 5, 18 11:52 am
Thanks! That's a good thing to think about.
BulgarBlogger
Jun 5, 18 12:21 pm
you know what is impressive?
Seeing resumes that are:
1. Clear in terms of longevity of employment and the roles you played there.
2. Increasing responsibility/seniority of title
3. Longevity of employment (no hopping around ever year)
4. Clarity of project type and budget
All of this supplemented by a good portfolio and professional presenation of content.
Oh and last but not least- honesty. If you used rhino 8 years ago, but havnt touched it since- dont put on your resume that your are proficient. You are rusty at best.
whistler
Jun 6, 18 7:50 pm
List of skills and how you will make the firm money! If you aren't an asset your a liability!
I'm making a resume and I'm looking for any helpful advice on what to include, specifically for those looking for an entry level job in architecture. Thoughts?
Whatever you do, don't add a graph or chart showing your software skills.
I wish this site had a like button. I agree.
Also don’t layout portfolio pages as if they are competition boards with extreme restrictions on number of boards/pages. White space does not add to file size.
Ha...I do have that in my current one. Why do you think that shouldn't be included? Is it because it would be a biased assessment of my skills since I'm making it?
True! I heard white space is always a good thing
Get rid of it. Everyone thinks they are software wizards right out of school because they can press the render button. oooooh 9/10 in revit? how modest of you.
Should I just list the softwares I feel most comfortable/proficient using?
Yes. List the software without making a big deal of your self-evaluated skills. Make proficient and working knowledge columns if you must split them.
Don't make it too cheesy or try to puff yourself up like you have a lot of experience if you don't. Be honest about your experience and your past roles in projects if you have any. Portray yourself as someone eager to learn and wanting to pitch in and do your part to help on a team. If you're applying for entry level, it's assumed that you know little to nothing so do not try to portray yourself as an expert of anything, including software.
Check this article we published a few years back:
Architecture and Design Graduates – How to Secure Your First Position – Part 1: Writing Your CV, Writing a Cover Letter
Thank you!
My resume matches my portfolio, as do my personal business cards, and my website.
I can't say for sure that it's the graphic consistency, but I seem to get more callbacks / interviews than with my old black serif on white layout. Ours is a design profession, and it's good to remember that that extends beyond your specifically architectural projects.
Thanks! That's a good thing to think about.
you know what is impressive?
Seeing resumes that are:
1. Clear in terms of longevity of employment and the roles you played there.
2. Increasing responsibility/seniority of title
3. Longevity of employment (no hopping around ever year)
4. Clarity of project type and budget
All of this supplemented by a good portfolio and professional presenation of content.
Oh and last but not least- honesty. If you used rhino 8 years ago, but havnt touched it since- dont put on your resume that your are proficient. You are rusty at best.
List of skills and how you will make the firm money! If you aren't an asset your a liability!