Architecture Internship
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse posting.
Content:
- Intro paragraph: "FSB, an affiliate of Colliers Engineering & Design, is offering a hands-on Summer Internship for Architecture students ready to see what happens when studio concepts meet real projects, real clients, and real constraints. As an intern, you’ll work alongside architects and designers while gaining experience in architectural design, visualization, documentation, coordination, and project delivery. You’ll contribute to projects across a wide variety of markets and building types while seeing how ideas move from early concepts toward built environments. This is more than a summer of shadowing. You’ll have opportunities to contribute your ideas, develop your design and technical skills, build your portfolio of professional experience, and explore what a career in a multidisciplinary architecture and engineering firm can look like."
That's about the role.
Then sections: "Design & Technical Learning" with bullet points (list). Then "Team Collaboration" with bullet points. Then "The FSB Internship Experience" with bullet points (some paragraphs). Then "Required Qualifications" with bullet points (list). Then EEO statement (to be removed). Also mention "Frankfurt-Short-Bruza Associates, P.C. provides equal employment opportunities..." remove.
We need to map to headings: About the role (intro). Responsibilities? Could be Design & Technical Learning and Team Collaboration combined as responsibilities. Could also have separate sections: Responsibilities (Design & Technical Learning, Team Collaboration). Qualifications (Required Qualifications). Skills? Could be implied but maybe not needed. Benefits? Not mentioned. Pay? Not mentioned. Schedule? Not mentioned (though says approx 40 hours per week, that's schedule info). Actually "Able to work on site in Oklahoma City for the duration of the summer internship, approximately 40 hours per week" is schedule info. So we can include Schedule section with that detail. Benefits? Not mentioned. Pay? Not mentioned.
Thus sections: About the role (intro). Responsibilities (Design & Technical Learning + Team Collaboration). Qualifications (Required Qualifications). Schedule (40 hrs/week on site). Possibly Skills? Could extract from qualifications: Strong communication, creativity, organization, problem solving, collaboration skills. Could be Skills section. But we already have qualifications includes those. Might combine.
We need to avoid thin sections. Let's decide: About the role (intro). Responsibilities (Design & Technical Learning + Team Collaboration). Qualifications (Required Qualifications). Schedule (40 hrs/week on site). That's four sections.
We need to use for each heading. 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 keep each bullet point exactly as in posting.
Let's extract bullet points:
Design & Technical Learning:
- Assist with architectural design, modeling, visualization, and documentation using Revit and other design tools
- Support development of floor plans, elevations, sections, details, renderings, and presentation materials
- Contribute to programming, design studies, material research, and design development
- Support development and coordination of construction documents and technical deliverables
- Learn how building codes, accessibility requirements, life safety considerations, and design standards influence architectural solutions
- Gain exposure to the architectural design process from programming and conceptual design through construction
Team Collaboration:
- Work alongside experienced architects and designers on active projects
- Coordinate with interior design, mechanical, electrical, structural, and fire protection teams
- Experience how design ideas evolve through multidisciplinary BIM coordination, technical problem solving, and client input
- Gain exposure to project meetings, client communication, and the day-to-day processes behind successful project delivery
The FSB Internship Experience:
- Kick off your experience with FSB 101 and an introduction to our firm, culture, people, projects, and career opportunities
- Connect with an FSB team member as a resource for questions, navigating the firm, and making connections throughout the summer
- Participate in professional development programming, including leadership and project focused panels, Lunch & Learns, design activities, and other learning opportunities
- Meet leaders and professionals from across FSB and learn about different career paths within the A/E industry
- Build relationships with fellow interns and employees through networking, community service, and intern events
- Develop your communication and presentation skills and wrap up the summer by sharing your experience, project contributions, and lessons learned through a final intern presentation
Required Qualifications:
- Actively pursuing a bachelor’s or master’s degree in architecture from an accredited architecture program
- Able to work on site in Oklahoma City for the duration of the summer internship, approximately 40 hours per week
- Basic familiarity with Revit and other architectural design, modeling, rendering, or visualization software preferred
- Strong communication, creativity, organization, problem solving, and collaboration skills
- Curiosity, initiative, and a willingness to ask questions, contribute ideas, take on new challenges, and learn from experienced professionals
Note: The second bullet includes schedule info (40 hrs/week). We might separate schedule but it's part of qualifications. However we said schedule section separate. But we could keep schedule inside qualifications; but we need schedule section only if posting actually states them. It does state approx 40 hrs/week. So we could make schedule section with that detail. But then we would duplicate info if we also keep in qualifications. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we move schedule to its own section, we must still keep it somewhere; we could remove from qualifications to avoid duplication? But that would be removing substantive info (the schedule) from qualifications. Better to keep schedule within qualifications and not create separate schedule section unless we also keep it there. However we could create schedule section and also keep the bullet in qualifications? That would duplicate. Duplication is allowed? The instruction says remove duplicated lines. So we should not duplicate. So we need to decide where to place schedule info. Since schedule is a specific piece, we could make a Schedule section and remove it from qualifications. But then we lose the "Able to work on site in Oklahoma City for the duration of the summer internship, approximately 40 hours per week" from qualifications. That is substantive; we need to preserve it somewhere. If we put it in Schedule section, we preserve it. So we can remove it from qualifications list. That's okay as long as we keep the info elsewhere. So we will have Schedule section with that sentence.
Thus qualifications list will exclude that bullet.
Now we need to ensure we don't create thin sections. We have About the role (intro paragraph). Responsibilities (two subsections? Could combine into one list? But we have two categories: Design & Technical Learning and Team Collaboration. Could we make two subheadings? Not allowed; only h3 for section headings. Could we make two separate sections: Design & Technical Learning and Team Collaboration? That would be more sections but each has substantive content. That's okay. The instruction: Prefer a few substantive sections over many thin ones. But we have enough content for each. Could combine them under Responsibilities heading with two sub-lists? But we cannot use h4; we could use
for Responsibilities and then inside we could have ? Not allowed per rules? The rules only mention using for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we stick to those headings. So we can have Responsibilities heading and inside we can have paragraphs describing each area, maybe using
for prose and
- for lists. We could have two lists under Responsibilities: one for Design & Technical Learning, one for Team Collaboration. That's fine.
Thus structure:
About the role
...
Responsibilities
Design & Technical Learning
...
Team Collaboration
...
Qualifications
...
(excluding schedule bullet)
Schedule
Able to work on site in Oklahoma City for the duration of the summer internship, approximately 40 hours per week.
We must not include Benefits, Pay, Skills sections.
Check for any other specifics: The intro paragraph includes "FSB, an affiliate of Colliers Engineering & Design, is offering a hands-on Summer Internship for Architecture students ready to see what happens when studio concepts meet real projects, real clients, and real constraints." Keep that.
Now ensure we removed boilerplate: EEO statement removed. Also remove "Frankfurt-Short-Bruza Associates, P.C. provides equal employment opportunities..." etc.
Also remove any duplicated lines: none.
Now produce HTML fragment.
Let's craft.
About the role paragraph: combine the intro sentences into one . Might be long but okay.
Responsibilities: We'll have a
for "Design & Technical Learning" then
list. Then a for "Team Collaboration" then
list.
Qualifications: list of bullets (excluding schedule). Ensure we keep the bullet about basic familiarity with Revit etc., strong communication etc., curiosity etc.
Schedule: with the sentence.
Check that we kept all substantive info: Let's list all original bullets and see if any missing.
Original bullets:
Design & Technical Learning:
1 Assist with architectural design, modeling, visualization, and documentation using Revit and other design tools
2 Support development of floor plans, elevations, sections, details, renderings, and presentation materials
3 Contribute to programming, design studies, material research, and design development
4 Support development and coordination of construction documents and technical deliverables
5 Learn how building codes, accessibility requirements, life safety considerations, and design standards influence architectural solutions
6 Gain exposure to the architectural design process from programming and conceptual design through construction
Team Collaboration:
1 Work alongside experienced architects and designers on active projects
2 Coordinate with interior design, mechanical, electrical, structural, and fire protection teams
3 Experience how design ideas evolve through multidisciplinary BIM coordination, technical problem solving, and client input
4 Gain exposure to project meetings, client communication, and the day-to-day processes behind successful project delivery
The FSB Internship Experience:
1 Kick off your experience with FSB 101 and an introduction to our firm, culture, people, projects, and career opportunities
2 Connect with an FSB team member as a resource for questions, navigating the firm, and making connections throughout the summer
3 Participate in professional development programming, including leadership and project focused panels, Lunch & Learns, design activities, and other learning opportunities
4 Meet leaders and professionals from across FSB and learn about different career paths within the A/E industry
5 Build relationships with fellow interns and employees through networking, community service, and intern events
6 Develop your communication and presentation skills and wrap up the summer by sharing your experience, project contributions, and lessons learned through a final intern presentation
Required Qualifications:
1 Actively pursuing a bachelor’s or master’s degree in architecture from an accredited architecture program
2 Able to work on site in Oklahoma City for the duration of the summer internship, approximately 40 hours per week
3 Basic familiarity with Revit and other architectural design, modeling, rendering, or visualization software preferred
4 Strong communication, creativity, organization, problem solving, and collaboration skills
5 Curiosity, initiative, and a willingness to ask questions, contribute ideas, take on new challenges, and learn from experienced professionals
We moved #2 to Schedule section. So Qualifications list will have 1,3,4,5.
Check we didn't miss any other info: The intro paragraph also includes "As an intern, you’ll work alongside architects and designers while gaining experience in architectural design, visualization, documentation, coordination, and project delivery. You’ll contribute to projects across a wide variety of markets and building types while seeing how ideas move from early concepts toward built environments. This is more
- 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 keep each bullet point exactly as in posting. Let's extract bullet points: Design & Technical Learning: - Assist with architectural design, modeling, visualization, and documentation using Revit and other design tools - Support development of floor plans, elevations, sections, details, renderings, and presentation materials - Contribute to programming, design studies, material research, and design development - Support development and coordination of construction documents and technical deliverables - Learn how building codes, accessibility requirements, life safety considerations, and design standards influence architectural solutions - Gain exposure to the architectural design process from programming and conceptual design through construction Team Collaboration: - Work alongside experienced architects and designers on active projects - Coordinate with interior design, mechanical, electrical, structural, and fire protection teams - Experience how design ideas evolve through multidisciplinary BIM coordination, technical problem solving, and client input - Gain exposure to project meetings, client communication, and the day-to-day processes behind successful project delivery The FSB Internship Experience: - Kick off your experience with FSB 101 and an introduction to our firm, culture, people, projects, and career opportunities - Connect with an FSB team member as a resource for questions, navigating the firm, and making connections throughout the summer - Participate in professional development programming, including leadership and project focused panels, Lunch & Learns, design activities, and other learning opportunities - Meet leaders and professionals from across FSB and learn about different career paths within the A/E industry - Build relationships with fellow interns and employees through networking, community service, and intern events - Develop your communication and presentation skills and wrap up the summer by sharing your experience, project contributions, and lessons learned through a final intern presentation Required Qualifications: - Actively pursuing a bachelor’s or master’s degree in architecture from an accredited architecture program - Able to work on site in Oklahoma City for the duration of the summer internship, approximately 40 hours per week - Basic familiarity with Revit and other architectural design, modeling, rendering, or visualization software preferred - Strong communication, creativity, organization, problem solving, and collaboration skills - Curiosity, initiative, and a willingness to ask questions, contribute ideas, take on new challenges, and learn from experienced professionals Note: The second bullet includes schedule info (40 hrs/week). We might separate schedule but it's part of qualifications. However we said schedule section separate. But we could keep schedule inside qualifications; but we need schedule section only if posting actually states them. It does state approx 40 hrs/week. So we could make schedule section with that detail. But then we would duplicate info if we also keep in qualifications. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we move schedule to its own section, we must still keep it somewhere; we could remove from qualifications to avoid duplication? But that would be removing substantive info (the schedule) from qualifications. Better to keep schedule within qualifications and not create separate schedule section unless we also keep it there. However we could create schedule section and also keep the bullet in qualifications? That would duplicate. Duplication is allowed? The instruction says remove duplicated lines. So we should not duplicate. So we need to decide where to place schedule info. Since schedule is a specific piece, we could make a Schedule section and remove it from qualifications. But then we lose the "Able to work on site in Oklahoma City for the duration of the summer internship, approximately 40 hours per week" from qualifications. That is substantive; we need to preserve it somewhere. If we put it in Schedule section, we preserve it. So we can remove it from qualifications list. That's okay as long as we keep the info elsewhere. So we will have Schedule section with that sentence. Thus qualifications list will exclude that bullet. Now we need to ensure we don't create thin sections. We have About the role (intro paragraph). Responsibilities (two subsections? Could combine into one list? But we have two categories: Design & Technical Learning and Team Collaboration. Could we make two subheadings? Not allowed; only h3 for section headings. Could we make two separate sections: Design & Technical Learning and Team Collaboration? That would be more sections but each has substantive content. That's okay. The instruction: Prefer a few substantive sections over many thin ones. But we have enough content for each. Could combine them under Responsibilities heading with two sub-lists? But we cannot use h4; we could use
for Responsibilities and then inside we could have
? Not allowed per rules? The rules only mention using
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we stick to those headings. So we can have Responsibilities heading and inside we can have paragraphs describing each area, maybe using
for prose and
- for lists. We could have two lists under Responsibilities: one for Design & Technical Learning, one for Team Collaboration. That's fine.
Thus structure:
About the role
...
Responsibilities
Design & Technical Learning
- ...
Team Collaboration
- ...
Qualifications
- ...
Schedule
Able to work on site in Oklahoma City for the duration of the summer internship, approximately 40 hours per week.
We must not include Benefits, Pay, Skills sections. Check for any other specifics: The intro paragraph includes "FSB, an affiliate of Colliers Engineering & Design, is offering a hands-on Summer Internship for Architecture students ready to see what happens when studio concepts meet real projects, real clients, and real constraints." Keep that. Now ensure we removed boilerplate: EEO statement removed. Also remove "Frankfurt-Short-Bruza Associates, P.C. provides equal employment opportunities..." etc. Also remove any duplicated lines: none. Now produce HTML fragment. Let's craft. About the role paragraph: combine the intro sentences into one. Might be long but okay. Responsibilities: We'll have a
for "Design & Technical Learning" then
- list. Then a
for "Team Collaboration" then
- list.
Qualifications: list of bullets (excluding schedule). Ensure we keep the bullet about basic familiarity with Revit etc., strong communication etc., curiosity etc.
Schedule:
with the sentence. Check that we kept all substantive info: Let's list all original bullets and see if any missing. Original bullets: Design & Technical Learning: 1 Assist with architectural design, modeling, visualization, and documentation using Revit and other design tools 2 Support development of floor plans, elevations, sections, details, renderings, and presentation materials 3 Contribute to programming, design studies, material research, and design development 4 Support development and coordination of construction documents and technical deliverables 5 Learn how building codes, accessibility requirements, life safety considerations, and design standards influence architectural solutions 6 Gain exposure to the architectural design process from programming and conceptual design through construction Team Collaboration: 1 Work alongside experienced architects and designers on active projects 2 Coordinate with interior design, mechanical, electrical, structural, and fire protection teams 3 Experience how design ideas evolve through multidisciplinary BIM coordination, technical problem solving, and client input 4 Gain exposure to project meetings, client communication, and the day-to-day processes behind successful project delivery The FSB Internship Experience: 1 Kick off your experience with FSB 101 and an introduction to our firm, culture, people, projects, and career opportunities 2 Connect with an FSB team member as a resource for questions, navigating the firm, and making connections throughout the summer 3 Participate in professional development programming, including leadership and project focused panels, Lunch & Learns, design activities, and other learning opportunities 4 Meet leaders and professionals from across FSB and learn about different career paths within the A/E industry 5 Build relationships with fellow interns and employees through networking, community service, and intern events 6 Develop your communication and presentation skills and wrap up the summer by sharing your experience, project contributions, and lessons learned through a final intern presentation Required Qualifications: 1 Actively pursuing a bachelor’s or master’s degree in architecture from an accredited architecture program 2 Able to work on site in Oklahoma City for the duration of the summer internship, approximately 40 hours per week 3 Basic familiarity with Revit and other architectural design, modeling, rendering, or visualization software preferred 4 Strong communication, creativity, organization, problem solving, and collaboration skills 5 Curiosity, initiative, and a willingness to ask questions, contribute ideas, take on new challenges, and learn from experienced professionals We moved #2 to Schedule section. So Qualifications list will have 1,3,4,5. Check we didn't miss any other info: The intro paragraph also includes "As an intern, you’ll work alongside architects and designers while gaining experience in architectural design, visualization, documentation, coordination, and project delivery. You’ll contribute to projects across a wide variety of markets and building types while seeing how ideas move from early concepts toward built environments. This is more
- for lists. We could have two lists under Responsibilities: one for Design & Technical Learning, one for Team Collaboration. That's fine.
Thus structure: