Project Architect

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes: About Mkthink (company description) maybe not needed as heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we can have sections: About the role (maybe summarizing role description), Responsibilities, Requirements, Qualifications, Skills, Benefits? There's no explicit Benefits, Pay, Schedule content. The posting does not mention benefits, pay, schedule. So we should not include those sections. Also we need to include About Mkthink? Possibly as "About the role" includes description of role and maybe company? The instruction: "About the role" heading is for role description. We can put the role overview there. Then Responsibilities: list of primary responsibilities. Requirements: maybe required qualifications? Qualifications: maybe preferred? But we need to avoid duplication. Let's parse content. Sections present: - About Mkthink (company intro) - could be placed under "About the role"? Might be separate but not required. Could include as a brief paragraph under About the role. - THE ROLE: description of role, ideal candidate, experience 7-10 years, etc. This could be under About the role. - Who This Role Is For: bullet list of traits. - Primary Responsibilities: bullet list. - Construction Administration Support: bullet list. - Code Compliance & Technical Coordination: bullet list. - BIM / Revit Coordination: bullet list. - Team Collaboration & Mentorship: bullet list. - Qualifications: Required list. - Preferred: list. - LOCATION: location info. - How To Apply: application instructions (should be removed per instruction: remove application instructions). So we drop that. We must remove boilerplate, navigation, legal, EEO, etc. Not present. We must not include Pay/Benefits/Schedule sections because not stated. We need to use

• for any list of duties/requirements/benefits. So each bullet list becomes
  • ...
  . For prose, use

  . We must not repeat job title as heading. So no heading for "Project Architect". Good. We need to decide headings: About the role, Responsibilities, Requirements, Qualifications, Skills? The posting includes "Qualifications Required" and "Preferred". Could combine into Requirements (required) and Qualifications (preferred) or Skills. But we have both Required and Preferred. Could make "Requirements" for required qualifications, and "Qualifications" for preferred? Or "Skills" for technical skills? Let's think. The instruction list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: - About the role: company + role overview + who this role is for. - Responsibilities: all responsibility bullet lists (Project Coordination & Technical Delivery, Construction Administration Support, Code Compliance & Technical Coordination, BIM/Revit Coordination, Team Collaboration & Mentorship). Could combine into one responsibilities list. - Requirements: required qualifications (Bachelor/Master, 7-10 years experience, strong experience producing docs, advanced Revit proficiency, etc.) - Qualifications: preferred qualifications (registration, experience in CA/HI, DSA/HCAI, LEED, etc.) Could also include "Skills" for technical skills like Rhino, Sketchup, etc. But we already have skills in required/preferred. Maybe we separate: Requirements = required experience/education; Qualifications = preferred; Skills = software/tools. But we must not create thin sections. Let's see if we have enough content for each. We have: - About the role: company description + role overview + who this role is for (bullet list). Good. - Responsibilities: multiple bullet lists (maybe combine). Good. - Requirements: required qualifications list (maybe 8 items). Good. - Qualifications: preferred qualifications list (maybe 7 items). Good. - Skills: maybe list of software proficiencies: Rhino, Sketchup, Rendering software such as Enscape, Bluebeam, Adobe software, hand sketching, parametric tools Dynamo and Grasshopper, curiosity about AI integration. Also maybe "Spec writing experience", "Interest in strategic and contextual analysis". Those could be skills. But we already have many items in qualifications. Might be okay to have Skills section for software/tools. We must not create sections with filler like "not specified". We have real content. Thus output:

  About the role

  ... company description and role overview ...

  • ... who this role is for bullet items ...

  Responsibilities

  • ... each responsibility bullet ...

  Requirements

  • ... each required qualification ...

  Qualifications

  • ... each preferred qualification ...

  Skills

  • ... each skill/tool ...
  We must not include location or how to apply. Now we need to preserve all substantive information. Let's extract. Company description: "About Mkthink MKThink is a future-forward design firm grounded in spatial intelligence and dedicated to “build less, solve more.” Our data-informed solutions improve human performance at less operational, environmental, and capital costs than conventional approaches. Founded in 2000, MKThink practices from the Pacific Edge of San Francisco to the Oceanic Edge of O'ahu. At MKThink, we believe that we can play a role in helping create a better and more sustainable future by creating intelligent spaces that improve the quality of life. Our greatest resource is our staff and their ability to contribute fully as teammates and individuals. We bring together thinkers from various disciplines to solve problems at the nexus of architecture, culture, and the environment. Our people have the interdisciplinary skills to contribute to this mission within and across the domains of architecture, strategies, and innovation." We can put that as prose. Role overview: "The ROLE MKThink is seeking a highly motivated and technically skilled Project Architect to support the development and delivery of architectural projects across a diverse range of sectors, including commercial, civic, education, healthcare, multi-family residential, and mixed-use developments. This role is ideal for an architect who thrives in a collaborative, interdisciplinary environment and is passionate about delivering thoughtful, high-quality technical documentation and project coordination from concept through construction. We are seeking a candidate with 7-10 years of architectural experience. The Project Architect will serve as a key technical team member, collaborating closely with team members, consultants, and clients to support successful project execution in alignment with MKThink's design standards, client expectations, schedules, and budget goals. This position requires strong technical proficiency in construction documentation, consultant coordination, BIM/Revit workflows, and construction administration support, as well as the ability to mentor and guide junior staff. The ideal candidate is proactive, detail-oriented, organized, and comfortable managing multiple responsibilities in a fast-paced environment. Experience working with California, Hawaii, and Pacific Island jurisdictions, public agencies, DSA and/or HCAI processes, and multidisciplinary consultant teams is highly valued." We can include that as prose under About the role. Who This Role Is For bullet list: - Are seeking to move beyond traditional design delivery and into a practice that excels in strategy and advisory work - Are curious about how space influences performance, behavior, and outcomes - Want to work across disciplines—integrating design, data, and systems thinking - Are motivated to have broader impact at organizational or societal scales - Have strong technical problem-solving abilities - Are self-motivated and adaptable in a dynamic project environment - Show commitment to design excellence, innovation, and continuous learning - Ability to work independently, prioritize effectively, and seek support when needed Now Responsibilities: we have several subheadings with bullet lists. Let's extract each bullet. Project Coordination & Technical Delivery: - Lead the production of comprehensive architectural construction documents across all project phases. - Collaborate closely with other team members to support project planning, technical execution, scheduling, and delivery strategies. - Coordinate work produced by internal design teams, engineering consultants, specialty consultants, and contractors. - Assist with drawing organization, technical detailing, constructability coordination, and document consistency. - Participate in project meetings with clients, consultants, contractors, and agency representatives. - Help maintain project schedules and deliverables to support successful project execution. Construction Administration Support: - Support construction administration activities, including: - Shop drawing review - Submittal review - RFI review and response - Field observations and site visits - Coordination with contractors and consultants - Punch list development and closeout support - Assist in resolving technical and construction-related issues during the construction phase. - Help ensure project documentation accurately reflects field conditions, revisions, and approved changes. But note the sub-bullets under "Support construction administration activities, including:" The main bullet includes a colon then list. We could treat each as separate
• . For simplicity, we can flatten: list each item. Thus: - Shop drawing review - Submittal review - RFI review and response - Field observations and site visits - Coordination with contractors and consultants - Punch list development and closeout support - Assist in resolving technical and construction-related issues during the construction phase. - Help ensure project documentation accurately reflects field conditions, revisions, and approved changes. Code Compliance & Technical Coordination: - Assist with building code analysis and compliance reviews, including accessibility, life safety, and jurisdictional requirements. - Maintain working knowledge of applicable California and/or Hawaii building codes, ADA requirements, accessibility standards, and local agency review processes. - Apply knowledge of building systems, construction methods, materials, detailing, and industry standards. - Support permitting and agency coordination efforts, including DSA and/or HCAI review processes where applicable. BIM / Revit Coordination: - Utilize Revit with a high level of technical proficiency for documentation, coordination, and model development. - Support implementation and adherence to office BIM standards and workflows. - Coordinate BIM deliverables with internal teams and external consultants. - Assist in troubleshooting technical modeling and documentation issues. Team Collaboration & Mentorship: - Collaborate with and support junior architectural staff and emerging professionals. - Foster a collaborative and inclusive studio environment focused on growth, accountability, and continuous improvement. - Provide peer support related to technical documentation, project workflows, and production coordination. - Participate in team coordination and project resource discussions as needed. - Demonstrates kindness and actively supports colleagues. Now Requirements (required qualifications): List from "Qualifications Required": - Bachelor or Master's Degree in Architecture from an accredited program. - Minimum 7-10 years of architectural experience - Strong experience producing and coordinating construction documents. - Advanced proficiency in Revit within a professional architectural environment. - Working knowledge of construction administration processes and procedures. - Strong understanding of building codes, accessibility requirements, construction methods, and building systems. - Excellent verbal, written, and organizational communication skills. - Ability to manage multiple priorities and work collaboratively in a team environment. - Experience coordinating multidisciplinary consultant teams. - Ability to iterate and test novel ideas - Familiarity with campus design, urban design, and landscape architecture - Strong interest in stakeholder engagement and experience - Strong interest in data and database management as a component of the design process - Strong interest in environmental controls, sustainability and supply chain - Spec writing experience - Interest in strategic and contextual analysis in architectural design processes. That's many items. We'll keep them. Now Qualifications (preferred): List from "Preferred": - California or Hawaii Architectural Registration or active progress toward licensure. - Experience working on projects in California, Hawaii, and/or the Pacific Islands. - Experience with public agency jurisdictions and permitting processes. - DSA and/or HCAI project experience. - LEED Accredited Professional and/or WELL Accreditation. - Experience with sustainable