tag:blogger.com,1999:blog-7685608788672533401.post647320077915432886..comments2022-04-05T03:02:08.815-06:00Comments on Intern 101: A quick word on resumes (or, please don't try this at home)Lulu Brownhttp://www.blogger.com/profile/14713133001416080918noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-7685608788672533401.post-12084799100089300892010-08-14T20:38:59.029-06:002010-08-14T20:38:59.029-06:00As one of three principals of a growing architectu...As one of three principals of a growing architectural practice, I take issue with this post. Normally your info is quite good, but this one falls into the heading of 'What is Wrong with the Architecture Profession'.<br /><br />Like you, I have about 10 years of experience. Seven of those years were before the 3rd year of a 4+2 MArch degree. I have two more exams to become licensed thanks to the new early testing rules.<br /><br />So tell me, is your experience more valuable than mine? Is your list of accomplishments more relevant because you are licensed and I am not?<br /><br />I know plenty of Principal and Senior Associate people who, had they passed a two page resume to you, would have been denied review because they are unlicensed.<br /><br />Lastly, we need to set the record straight. You have been an architect for four years, not 10. An architect is someone who has passed the ARE and received a license to practice architecture, something that happened 4 years ago.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7685608788672533401.post-32579445201295467412010-08-12T21:43:16.850-06:002010-08-12T21:43:16.850-06:00Thanks it would be interesting to hear those views...Thanks it would be interesting to hear those views on how they perceive us. I've run a previous version by a small handful of people before and generally the first reaction is "This looks long", then the next reaction while reading it is "You've had great experience so I don't think I'd change it much". It ends up being a dilemma. The first reaction says that it might not get looked at when someone opens the envelope or the PDF. The second reaction is based on me sitting across from them and they are more obligated to look. When they read it, they value it. Sooooo, it can be easy to wonder what really happens out in the ether!JDnoreply@blogger.comtag:blogger.com,1999:blog-7685608788672533401.post-50403660186920758812010-08-12T20:28:31.556-06:002010-08-12T20:28:31.556-06:00JD: Good question, and a valid one for those who a...JD: Good question, and a valid one for those who are getting into architecture as a second or third career. My initial reaction is this: unless your past career involved being one of the guys that discovered a vaccine for cancer or involved pulling Saddam Hussein out of his spider hole, you still need to keep it to one page. Regardless of what your career used to be, architecture is what it is now, so anything you highlight from that/those previous careers should be selective and relate strongly to architecture or to how your past experience can benefit a firm. Save more in-depth details for the interview.<br /><br />I think your question deserves more discussion, and I'd like to pass our question on to some of my licensed colleagues who do hiring at other firms.Lulu Brownhttps://www.blogger.com/profile/14713133001416080918noreply@blogger.comtag:blogger.com,1999:blog-7685608788672533401.post-13722098153816953622010-08-11T11:31:22.910-06:002010-08-11T11:31:22.910-06:00So, I think I asked something about this awhile ba...So, I think I asked something about this awhile back...The one page rule seems to make sense for the 20/early 30 something intern with one to maybe three architecture related jobs. How about the late 30/midlife intern with career experience in two or three careers? I agree it needs to be filtered and every livid detail of the sales numbers generated, % productivity gained or the projects completed doesn't need to be logged. There does seem to be difference between the business oriented "Knock em Dead" approach (you must state results, results, results!!)and the architecture resume, particularly for interns.<br /><br />However, still listing the job(s) and the filtered architecture/business/client competent summary can still take 3-8 lines. As a result, I've gone the functional resume route but still find it tough to get to a page and a half. I've considered an 8 1/2 x 14 with a fold over to 8.5 x 11. Works nice as a delivered piece, but violates the "you're never sure how it will be copied or printed out of email" principle. I also attempted something similar to the combined letter idea where I had a sidebar summary and objective and more bulleted resume section. I agree, it just seemed even more "dense" and harder to read. <br /><br />So... current thought is first page has the summary, architecture related experience and possibly the firms. The second page will be the other career skills and those companies. Thoughts?JDnoreply@blogger.com