Related Posts
S&P Global Hey IHS markit S&P global people's, what should be the designation for yoe :5 , tech stack .net developer with angular They offered level 6, Software Engineer designation at Markit India services pvt Ltd Is it good or designation is regarded Current designation in Capgemini is Associate Consultant IHS Markit S&P Global
More Posts
Additional Posts in Architecture, Engineering, and Construction
New to Fishbowl?
unlock all discussions on Fishbowl.



Are your long term career goals to be in Construction Management or to do this while you work on getting your stamp?
Are you looking to get in to residential or commercial?
A recent grad with a B Arch going on a traditional path to Architecture license doesn’t have enough experience to jump right into a management position.
see reply, didn't want to crowd the reply section with long paragraphs
ditto what others say, you'll be too young to go straight into management, but it's awesome that you're ambitious. get a job working for a big firm like HKS, AECOM, HoK, those guys. You will need to know Revit but for high level stuff I think those guys use a lot of Sketchup to do early sketchups. and of COURSE the entire industry uses Bluebeam Revu that's very important.
In architect leadership you need to know your way through IBC, and how it affects stuff like what changes the buildings occupancy and how many stories you can make the building if you do x or y. Not my area of expertise but I've worked for some deadly architects and briefly witnessed what they do in the front end of projects.
in addition to getting your architects license (don't waste any time), look at the steps to getting a PMP certification, that takes a few years of actual project management experience. tell employer you want to go in that direction to get a PMP and a good manager will put you on that path, if you're truly cut out for leadership.
However, to reiterate you will not start out as a manager out of college. As someone who made my way into leadership in the A/E industry relatively quickly here's what I'd suggest: take in the work coming to you, and gain an understand the balance between high-level tasks and low-level tasks. high level is when the decisions seem small but are tremendously costly and require someone experienced who understands how these things work. low-level tasks are not as costly per decision and can be figured out by someone less experienced but the challenge is in NUMBERS this is why a project manager needs a team of architects working on these tasks.
What I did, is show that you know the difference and spend the first few years taking as many low-level tasks off of your leaders plate as possible to give them more time to deal with high-level decisions. basically surround yourself with good architect leaders and be their lackey, water boy 💪 (to avoid using vulgar terms) And meanwhile you're learning from them and getting put on tough projects. you need to master the low level before it's time for high level.
AND ELECTRICAL ROOM DOORS OPEN OUT. NEC ARTICLE 110.26.