Senior Project Architect - Retail
for each section heading.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from posting. That's a lot. We need to capture all responsibilities bullet points.
Let's extract responsibilities list from posting:
- Set the technical direction on assigned projects of moderate to large complexity.
- Determine the overall strategy for producing the documents, identify the drawings and related documents each phase of the work requires, and make sure the design intent from Performance Based Design survives into the detailed documentation.
- Produce and modify construction documents on the firm's most complicated work.
- Work in Revit, AutoCAD, SketchUp, and BSD SpecLink, execute document modifications in situations with no clean precedent, and answer RFIs during bidding and construction to Progressive standards.
- Develop project specifications that agree with the drawings.
- Write and coordinate the specs alongside the drawing set for accuracy and completeness, with industry standards and sustainability guidelines built in rather than added at the end.
- Resolve code and technical issues with the authorities having jurisdiction.
- Work directly with the AHJ, supply the documentation they ask for, and settle code-related questions before they hold up a project.
- Own quality assurance and quality control for the Architecture discipline.
- Review the work of other architectural staff for accuracy and completeness before anything is submitted, and give feedback on code compliance, constructability, and systems integration while contract documents are still in production.
- Resolve field issues and contract document disputes during construction.
- Attend site visits, work through errors or disagreements arising from the contract documents, and keep the project team current on changes to design, scope, schedule, and budget as they happen.
- Act as the subject matter expert other teams bring their specialized systems questions to.
- Lead product research and selection with the project team, attend vendor meetings, and make sure the materials chosen hold up against the design intent.
- Mentor architectural staff and raise the technical floor of the team.
- Coach staff and project teams through design and documentation problems as they come up, and lead Lessons Learned sessions so what one project figured out reaches the next one.
Also earlier paragraphs: "you will be the lead technical voice on projects ranging from moderate to large complexity, from conceptual design through the last field question. You will decide how a building gets documented, carry the design intent from our Performance Based Design process into the detailed set, and serve as the subject matter expert on specialized building systems. Project managers, other architects, and outside consultants will come to you for the technical call, and you will work directly with the director and department head on technical solutions and product strategy. The autonomy here is real. You will set the documentation approach, review the discipline's work before it leaves the office, and mentor the architects coming up behind you, which is the usual path toward senior technical and department leadership roles."
These are also responsibilities but overlapping.
We need to preserve all substantive information, not just bullet list. Could combine into a cohesive list but ensure we don't lose any detail.
We'll create a
with - items each representing a distinct responsibility. We'll try to capture all unique points.
Let's list unique responsibilities:
1. Be the lead technical voice on projects ranging from moderate to large complexity, from conceptual design through the last field question.
2. Decide how a building gets documented.
3. Carry the design intent from the Performance Based Design process into the detailed set.
4. Serve as the subject matter expert on specialized building systems.
5. Project managers, other architects, and outside consultants will come to you for the technical call.
6. Work directly with the director and department head on technical solutions and product strategy.
7. Set the documentation approach.
8. Review the discipline's work before it leaves the office.
9. Mentor the architects coming up behind you (path toward senior technical and department leadership roles).
10. Set the technical direction on assigned projects of moderate to large complexity.
11. Determine the overall strategy for producing the documents, identify the drawings and related documents each phase of the work requires, and make sure the design intent from Performance Based Design survives into the detailed documentation.
12. Produce and modify construction documents on the firm's most complicated work.
13. Work in Revit, AutoCAD, SketchUp, and BSD SpecLink, execute document modifications in situations with no clean precedent, and answer RFIs during bidding and construction to Progressive standards.
14. Develop project specifications that agree with the drawings.
15. Write and coordinate the specs alongside the drawing set for accuracy and completeness, with industry standards and sustainability guidelines built in rather than added at the end.
16. Resolve code and technical issues with the authorities having jurisdiction.
17. Work directly with the AHJ, supply the documentation they ask for, and settle code-related questions before they hold up a project.
18. Own quality assurance and quality control for the Architecture discipline.
19. Review the work of other architectural staff for accuracy and completeness before anything is submitted, and give feedback on code compliance, constructability, and systems integration while contract documents are still in production.
20. Resolve field issues and contract document disputes during construction.
21. Attend site visits, work through errors or disagreements arising from the contract documents, and keep the project team current on changes to design, scope, schedule, and budget as they happen.
22. Act as the subject matter expert other teams bring their specialized systems questions to.
23. Lead product research and selection with the project team, attend vendor meetings, and make sure the materials chosen hold up against the design intent.
24. Mentor architectural staff and raise the technical floor of the team.
25. Coach staff and project teams through design and documentation problems as they come up, and lead Lessons Learned sessions so what one project figured out reaches the next one.
Also earlier: "Certification and continuing education are provided." That's a benefit.
Also benefits: "comprehensive benefits including an award-winning wellness program, hybrid work schedule, summer hours, profit-sharing, and employee stock ownership plan (ESOP)." Also "paid service-learning hours available to every employee and corporate sponsorship for a wide range of community organizations and activities." Also "continuing education, mentorship, growth opportunities."
Also schedule: hybrid work schedule, summer hours.
Thus Benefits section: list: award-winning wellness program, hybrid work schedule, summer hours, profit-sharing, ESOP, paid service-learning hours, continuing education, mentorship, growth opportunities, corporate sponsorship for community organizations.
We need to avoid duplication: hybrid work schedule appears both in Benefits and Schedule; but we can keep in Benefits and also mention in Schedule maybe as part of schedule details. However we should not repeat same info unnecessarily? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include hybrid work schedule somewhere. Could be in Benefits and also Schedule but that repeats. Might be okay but better to avoid duplication? The instruction didn't forbid duplication but said remove duplicated lines. So we should avoid duplicate lines. So we need to decide where to place hybrid work schedule: either Benefits or Schedule, not both. Since schedule section is for schedule specifics, we can put hybrid work schedule and summer hours there. Benefits can list other benefits: award-winning wellness program, profit-sharing, ESOP, paid service-learning hours, continuing education, mentorship, growth opportunities, corporate sponsorship.
Thus Benefits section excludes hybrid work schedule and summer hours.
Schedule section: hybrid work schedule, summer hours.
Now Skills section: list technical skills: Revit, AutoCAD, SketchUp, BSD SpecLink; specification writing; code coordination; QA/QC; mentorship; product research and selection; vendor meetings; Lessons Learned facilitation. But many of these are responsibilities. Might be better to not have Skills section and just have Responsibilities covering all. However we need to decide sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe we just have About the role, Responsibilities, Benefits, Schedule. That's four sections. That seems good.
We need About the role: a short paragraph summarizing the role. We can craft from the description: "As an Architectural Staff III, you will be the lead technical voice on projects ranging from moderate to large complexity, from conceptual design through the last field question. You will decide how a building gets documented, carry the design intent from our Performance Based Design process into the detailed set, and serve as the subject matter expert on specialized building systems. Project managers, other architects, and outside consultants will come to you for the technical call, and you will work directly with the director and department head on technical solutions and product strategy. The autonomy here is real. You will set the documentation approach, review the discipline's work before it leaves the office, and mentor the architects coming up behind you, which is the usual path toward senior technical and department leadership roles."
That's a good summary.
Now Responsibilities: we need to list all distinct responsibilities as
- . Ensure we don't miss any.
Let's compile final list, ensuring we cover all points from the posting without duplication.
I'll go through the posting again and extract each distinct responsibility sentence.
Paragraph 1: "As an Architectural Staff III, you will be the lead technical voice on projects ranging
for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from posting. That's a lot. We need to capture all responsibilities bullet points. Let's extract responsibilities list from posting: - Set the technical direction on assigned projects of moderate to large complexity. - Determine the overall strategy for producing the documents, identify the drawings and related documents each phase of the work requires, and make sure the design intent from Performance Based Design survives into the detailed documentation. - Produce and modify construction documents on the firm's most complicated work. - Work in Revit, AutoCAD, SketchUp, and BSD SpecLink, execute document modifications in situations with no clean precedent, and answer RFIs during bidding and construction to Progressive standards. - Develop project specifications that agree with the drawings. - Write and coordinate the specs alongside the drawing set for accuracy and completeness, with industry standards and sustainability guidelines built in rather than added at the end. - Resolve code and technical issues with the authorities having jurisdiction. - Work directly with the AHJ, supply the documentation they ask for, and settle code-related questions before they hold up a project. - Own quality assurance and quality control for the Architecture discipline. - Review the work of other architectural staff for accuracy and completeness before anything is submitted, and give feedback on code compliance, constructability, and systems integration while contract documents are still in production. - Resolve field issues and contract document disputes during construction. - Attend site visits, work through errors or disagreements arising from the contract documents, and keep the project team current on changes to design, scope, schedule, and budget as they happen. - Act as the subject matter expert other teams bring their specialized systems questions to. - Lead product research and selection with the project team, attend vendor meetings, and make sure the materials chosen hold up against the design intent. - Mentor architectural staff and raise the technical floor of the team. - Coach staff and project teams through design and documentation problems as they come up, and lead Lessons Learned sessions so what one project figured out reaches the next one. Also earlier paragraphs: "you will be the lead technical voice on projects ranging from moderate to large complexity, from conceptual design through the last field question. You will decide how a building gets documented, carry the design intent from our Performance Based Design process into the detailed set, and serve as the subject matter expert on specialized building systems. Project managers, other architects, and outside consultants will come to you for the technical call, and you will work directly with the director and department head on technical solutions and product strategy. The autonomy here is real. You will set the documentation approach, review the discipline's work before it leaves the office, and mentor the architects coming up behind you, which is the usual path toward senior technical and department leadership roles." These are also responsibilities but overlapping. We need to preserve all substantive information, not just bullet list. Could combine into a cohesive list but ensure we don't lose any detail. We'll create a
- with
- items each representing a distinct responsibility. We'll try to capture all unique points. Let's list unique responsibilities: 1. Be the lead technical voice on projects ranging from moderate to large complexity, from conceptual design through the last field question. 2. Decide how a building gets documented. 3. Carry the design intent from the Performance Based Design process into the detailed set. 4. Serve as the subject matter expert on specialized building systems. 5. Project managers, other architects, and outside consultants will come to you for the technical call. 6. Work directly with the director and department head on technical solutions and product strategy. 7. Set the documentation approach. 8. Review the discipline's work before it leaves the office. 9. Mentor the architects coming up behind you (path toward senior technical and department leadership roles). 10. Set the technical direction on assigned projects of moderate to large complexity. 11. Determine the overall strategy for producing the documents, identify the drawings and related documents each phase of the work requires, and make sure the design intent from Performance Based Design survives into the detailed documentation. 12. Produce and modify construction documents on the firm's most complicated work. 13. Work in Revit, AutoCAD, SketchUp, and BSD SpecLink, execute document modifications in situations with no clean precedent, and answer RFIs during bidding and construction to Progressive standards. 14. Develop project specifications that agree with the drawings. 15. Write and coordinate the specs alongside the drawing set for accuracy and completeness, with industry standards and sustainability guidelines built in rather than added at the end. 16. Resolve code and technical issues with the authorities having jurisdiction. 17. Work directly with the AHJ, supply the documentation they ask for, and settle code-related questions before they hold up a project. 18. Own quality assurance and quality control for the Architecture discipline. 19. Review the work of other architectural staff for accuracy and completeness before anything is submitted, and give feedback on code compliance, constructability, and systems integration while contract documents are still in production. 20. Resolve field issues and contract document disputes during construction. 21. Attend site visits, work through errors or disagreements arising from the contract documents, and keep the project team current on changes to design, scope, schedule, and budget as they happen. 22. Act as the subject matter expert other teams bring their specialized systems questions to. 23. Lead product research and selection with the project team, attend vendor meetings, and make sure the materials chosen hold up against the design intent. 24. Mentor architectural staff and raise the technical floor of the team. 25. Coach staff and project teams through design and documentation problems as they come up, and lead Lessons Learned sessions so what one project figured out reaches the next one. Also earlier: "Certification and continuing education are provided." That's a benefit. Also benefits: "comprehensive benefits including an award-winning wellness program, hybrid work schedule, summer hours, profit-sharing, and employee stock ownership plan (ESOP)." Also "paid service-learning hours available to every employee and corporate sponsorship for a wide range of community organizations and activities." Also "continuing education, mentorship, growth opportunities." Also schedule: hybrid work schedule, summer hours. Thus Benefits section: list: award-winning wellness program, hybrid work schedule, summer hours, profit-sharing, ESOP, paid service-learning hours, continuing education, mentorship, growth opportunities, corporate sponsorship for community organizations. We need to avoid duplication: hybrid work schedule appears both in Benefits and Schedule; but we can keep in Benefits and also mention in Schedule maybe as part of schedule details. However we should not repeat same info unnecessarily? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include hybrid work schedule somewhere. Could be in Benefits and also Schedule but that repeats. Might be okay but better to avoid duplication? The instruction didn't forbid duplication but said remove duplicated lines. So we should avoid duplicate lines. So we need to decide where to place hybrid work schedule: either Benefits or Schedule, not both. Since schedule section is for schedule specifics, we can put hybrid work schedule and summer hours there. Benefits can list other benefits: award-winning wellness program, profit-sharing, ESOP, paid service-learning hours, continuing education, mentorship, growth opportunities, corporate sponsorship. Thus Benefits section excludes hybrid work schedule and summer hours. Schedule section: hybrid work schedule, summer hours. Now Skills section: list technical skills: Revit, AutoCAD, SketchUp, BSD SpecLink; specification writing; code coordination; QA/QC; mentorship; product research and selection; vendor meetings; Lessons Learned facilitation. But many of these are responsibilities. Might be better to not have Skills section and just have Responsibilities covering all. However we need to decide sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe we just have About the role, Responsibilities, Benefits, Schedule. That's four sections. That seems good. We need About the role: a short paragraph summarizing the role. We can craft from the description: "As an Architectural Staff III, you will be the lead technical voice on projects ranging from moderate to large complexity, from conceptual design through the last field question. You will decide how a building gets documented, carry the design intent from our Performance Based Design process into the detailed set, and serve as the subject matter expert on specialized building systems. Project managers, other architects, and outside consultants will come to you for the technical call, and you will work directly with the director and department head on technical solutions and product strategy. The autonomy here is real. You will set the documentation approach, review the discipline's work before it leaves the office, and mentor the architects coming up behind you, which is the usual path toward senior technical and department leadership roles." That's a good summary. Now Responsibilities: we need to list all distinct responsibilities as
- . Ensure we don't miss any. Let's compile final list, ensuring we cover all points from the posting without duplication. I'll go through the posting again and extract each distinct responsibility sentence. Paragraph 1: "As an Architectural Staff III, you will be the lead technical voice on projects ranging