Job Captain - Education

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, legal, etc. Also remove application instructions (like "We strongly encourage you to apply..." maybe that's not boilerplate but it's encouragement; but it's not a specific section; we can keep as part of About the role? Probably we can keep it as prose. We need to preserve all substantive information. So we need to extract content. Let's parse the posting: First paragraph: "Do you thrive in an imaginative and inventive environment? Are you someone who flourishes when part of a cohesive team where collaboration and ideas flow freely? Want to work for a firm that is taking concrete actions towards Equity, Diversity, and Inclusion? We’re looking for an experienced Job Captain to join our Education team in our Sacramento office. The Education team works on various projects from K-12 to higher education. An ideal candidate has a thorough understanding of building systems, codes, and standards as they relate to their assigned projects and assists in collaborating with internal staff and studio and firm management as well as external contacts. This individual has experience with projects ranging in size and complexity in the Education market. We are looking for a stellar individual who wants to change the world, one project at a time. Sound like you? As the Job Captain, you will…" Then bullet list of responsibilities (starting with "Monitor the production..."). Then "The Must-Haves" list. Then "The Like-to-Haves" list. Then "Why You’ll Love Lionakis…" with bullet points (actually sentences). Then "Salary Range: $90,100-$119,200 annually. Compensation and level DOE." Then the encouragement paragraph about underrepresented individuals. We need sections: About the role (intro paragraph maybe), Responsibilities (list), Requirements (maybe Must-Haves?), Qualifications (maybe Like-to-Haves?), Skills (maybe technical skills?), Benefits (Why You’ll Love Lionakis... includes benefits), Pay (salary range), Schedule (maybe hybrid work flexibility, every-other-Friday off options). The posting mentions "Hybrid work flexibility, every-other-Friday off options". That's schedule info. We must not create sections with filler like "commensurate with experience". We have actual content. Thus sections: - About the role: intro paragraph up to "Sound like you? As the Job Captain, you will…" maybe we include that as prose. - Responsibilities: list of duties after that. - Requirements: Must-Haves list. - Qualifications: Like-to-Haves list (LEED accreditation). Could also be Skills but we have Skills maybe from Must-Haves includes BIM/Revit etc. But we can treat Must-Haves as Requirements, Like-to-Haves as Qualifications, and maybe Skills separate? However we must not create thin sections. Could combine Skills into Requirements? But we need to follow instruction: use headings only when posting has real specific content for it. We have content for Responsibilities, Requirements (Must-Haves), Qualifications (Like-to-Haves), Benefits (Why You’ll Love Lionakis...), Pay (salary range), Schedule (hybrid work flexibility, every-other-Friday off). Also About the role (intro). That's six sections. We should not include Skills if not distinct; but we could include Skills as part of Requirements. However we have separate heading for Skills; we could omit if not enough distinct content. The posting includes "Excellent ability to collaborate..., time management..., Proficient with BIM/Revit..., MS Office Suite, Bluebeam, Created presentation materials..., Complete and maintain code review...". Those are skills. Could be placed under Skills section. But we already have Requirements (Must-Haves) which includes those. Might be redundant. Better to follow typical sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Omit Skills. Now we need to output HTML fragment: use

for each heading, then content:

for prose,

• for lists. We must not include markdown fences. Let's craft. About the role: combine intro paragraphs before responsibilities. Include the initial motivational sentences and description of team, ideal candidate, etc. Also include "Sound like you? As the Job Captain, you will…" maybe as part of intro? Actually that leads into responsibilities. We'll keep it as part of About the role. Thus About the role

  containing: "Do you thrive in an imaginative and inventive environment? Are you someone who flourishes when part of a cohesive team where collaboration and ideas flow freely? Want to work for a firm that is taking concrete actions towards Equity, Diversity, and Inclusion? We’re looking for an experienced Job Captain to join our Education team in our Sacramento office. The Education team works on various projects from K-12 to higher education. An ideal candidate has a thorough understanding of building systems, codes, and standards as they relate to their assigned projects and assists in collaborating with internal staff and studio and firm management as well as external contacts. This individual has experience with projects ranging in size and complexity in the Education market. We are looking for a stellar individual who wants to change the world, one project at a time. Sound like you? As the Job Captain, you will…" But the "As the Job Captain, you will…" is a lead-in to list; we could keep it as part of About the role but maybe better to end before list. We'll keep it. Now Responsibilities

  • each duty. List items from posting: - Monitor the production and coordination of drawings and specifications, including overseeing consultant coordination of projects - Collaborate with project leaders to develop solutions for basic design problems, including program compliance, code and agency compliance, product research, schedule commitments, and agency interface - Provide technical oversight and coordinate project activities with clients, consultants, contractors, and staff - Assist project leads in developing project documents for bidding and construction and help with construction administration tasks for projects - Work with project leaders to develop and adhere to plans, address, and find solutions for basic project-related issues. Inform project leaders of potential client and consultant requested changes to the scope of work; assess the impact on the project budget and schedule - Produce accurate work and perform complete quality control reviews as a part of a coordinated project team - Delegate tasks to production staff and support their professional development through coaching. Assist the project team and market/studio leadership with any additional duties that may be assigned - Participate in all phases of the design and project documentation processes and manage multiple projects simultaneously - Uphold The Lionakis Way standards for design, quality control, and production Make each as
  • . Now Requirements (Must-Haves) list: - Bachelor’s degree in architecture or equivalent and a minimum of 6 years architectural project experience - Excellent ability to collaborate with a variety of individuals, time management and organizational skills, complete tasks accurately and on schedule and take initiative to seek out guidance or additional tasks - Experience identifying and addressing issues affecting project budget, construction costs, schedule, and risk management for the Firm - Proficient with BIM/Revit software programs, MS Office Suite, Bluebeam - Created presentation materials to support the project team's design and marketing efforts - Complete and maintain code review and analysis through the completion of the projects - Prior experience with Education projects (DSA experience a huge plus) Now Qualifications (Like-to-Haves) list: - LEED accreditation Now Benefits (Why You’ll Love Lionakis…) content: It's a paragraph with bullet-like sentences. We'll convert to
    • maybe. The text: "At Lionakis, people and design come first. You’ll find: A collaborative, design-forward culture that values creativity, mentorship, and shared successThe chance to shape stories that impact real communitiesHybrid work flexibility, every-other-Friday off options, and a comprehensive benefits package (bonus plan, 401(k) with match, health/dental/vision, generous PTO)A workplace deeply committed to Equity, Diversity, and Inclusion – in our projects, our people, and our culture Join us and help bring our design vision to life—one story at a time." We need to split into sensible items. Could keep as

      for prose and then

      • for list items. But we have no explicit list; we can treat each sentence after colon as list items. Let's parse: - A collaborative, design-forward culture that values creativity, mentorship, and shared success - The chance to shape stories that impact real communities - Hybrid work flexibility, every-other-Friday off options, and a comprehensive benefits package (bonus plan, 401(k) with match, health/dental/vision, generous PTO) - A workplace deeply committed to Equity, Diversity, and Inclusion – in our projects, our people, and our culture - Join us and help bring our design vision to life—one story at a time. But the first sentence "At Lionakis, people and design come first. You’ll find:" could be intro

        . Then list. Thus Benefits section:

        At Lionakis, people and design come first. You’ll find:

        then
        • ... etc. Now Pay section: Salary Range: $90,100-$119,200 annually. Compensation and level DOE. We'll put in

          . Now Schedule section: Hybrid work flexibility, every-other-Friday off options. That's from Benefits but we could also put under Schedule. However we already used hybrid work flexibility in Benefits list. Might duplicate. Better to keep schedule separate: The posting mentions "Hybrid work flexibility, every-other-Friday off options". We'll put that as

          Hybrid work flexibility, every-other-Friday off options.

          But we already used that phrase in Benefits list; we could remove from Benefits to avoid duplication. However the instruction says preserve ALL substantive information; we can't remove it. We could keep it in both sections but that duplicates. Better to keep it only under Schedule and not duplicate in Benefits. But then we lose that benefit from Benefits section. However the benefit description includes that phrase as part of comprehensive benefits package. It's okay to mention it there as well; duplication may be okay but we risk being considered filler? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not removing info, it's preserving. It's okay to have it in both sections. However we might want to avoid redundancy but not required. I'd keep it in Benefits as part of the list, and also have Schedule section with same info. That's duplication but preserves info. Might be considered redundant but not violating. However they said "Prefer a few substantive sections over many thin ones." Duplication may create thin sections but still okay. Alternatively we could move hybrid work flexibility to Schedule and keep Benefits list without that phrase, but then we lose that detail from Benefits. But we could keep it in Benefits as part of the phrase "Hybrid work flexibility, every-other-Friday off options, and a comprehensive benefits package..." If we remove it from Benefits, we lose that detail. So better to keep it in Benefits and also have Schedule section. Thus Benefits list items: - A collaborative, design-forward culture that values creativity, mentorship, and shared success - The chance to shape stories that impact real communities - Hybrid work flexibility, every-other-Friday off options, and a comprehensive benefits package (bonus plan, 401(k) with match, health/dental/vision, generous PTO) - A workplace deeply committed to Equity, Diversity, and Inclusion – in our projects, our people, and our culture - Join us and help bring our design vision to life—one story at a time. Now Schedule section:

          Hybrid work flexibility, every-other-Friday off options.

          Now we need to ensure we didn't include boilerplate: EEO, legal, etc. We removed