Healthcare Project Architect / Job Captain
for each heading. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the job description and extract sections.
Given the description includes:
- Intro: "An internationally recognized architecture and design firm is looking to hire a Project Architect/Project Manager. This position requires an expert in Revit and will focus on healthcare and civic projects. This position requires strong renovation experience, healthcare, civic, and/or correctional facilities construction design experience, and big project management experience. 70% of projects will be focused on large CA-based projects (healthcare), and 30% of projects will be working on small projects based in Seattle (i.e., assisted living facility projects). Title - Project Architect (if not licensed, the title will be a Job Captain) Pay - $43/hr. - $67/hr. (around $90k/yr. - $140k/yr.) - (Depending on Revit proficiency, strong portfolio, overall tenure, relevant industry, certifications, etc.) Schedule - Monday - Friday (Will have the last Friday off every month) Location - Seattle, WA (Hybrid: Tuesday & Wednesday on-site, Monday, Thursday & Friday Remote)"
- Then "(Summary Of Key Responsibilities)" with bullet list.
- Then "(Qualification Requirements)" with bullet list.
- Then "(Disqualifiers)" bullet list.
- Then "(Employee Value Proposition)" bullet list.
- Then "Job Type & Location This is a Contract to Hire position based out of Seattle, WA."
- Then "Pay And Benefits The pay range for this position is $43.00 - $67.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors. Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following: Medical, dental & vision Critical Illness, Accident, and Hospital 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available Life Insurance (Voluntary Life & AD&D for the employee and dependents) Short and long-term disability Health Spending Account (HSA) Transportation benefits Employee Assistance Program Time Off/Leave (PTO, Vacation or Sick Leave) Workplace Type This is a hybrid position in Seattle,WA."
- Then "Application Deadline This position is anticipated to close on Sep 28, 2026."
- Then "About Actalent ..." which is boilerplate about the company; we need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Actalent" section is likely considered boilerplate? It's not exactly EEO but it's company description. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Actalent" might be considered company overview, not necessarily boilerplate, but could be considered fluff. However we need to preserve ALL substantive information; do NOT invent or summarize away detail. The "About Actalent" includes details about the firm being a global leader, network size, etc. That might be considered substantive? But it's not about the job itself; it's about the employer. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't explicitly say to remove company overview. However earlier they said "Prefer a few substantive sections over many thin ones." The company overview might be considered not directly relevant to the job posting content (like responsibilities, qualifications, pay, schedule, benefits). It might be considered boilerplate. But it's not explicitly listed as boilerplate to remove. However typical job postings include "About the company" which is often considered not essential for the job description. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." If we remove the About Actalent section, we might be losing substantive info about the company. But is that considered substantive for the job? Possibly yes, but the instruction also says "Prefer a few substantive sections over many thin ones." Might be okay to include an "About the company" section if we have content. However the allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company" heading. So we cannot add a heading not in that list. So we must either incorporate that info into another allowed heading or drop it. Since we cannot create a heading like "About the company", we likely should drop that info, as it's not covered by allowed headings. The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not an exhaustive list? It says "e.g." meaning examples. So we could potentially use other headings if needed, but they gave a list of typical sections. Safer to stick to those.
Thus we need to extract content for:
- About the role: maybe a brief description of the role (the intro paragraphs). Could be placed under About the role.
- Responsibilities: the Summary Of Key Responsibilities list.
- Requirements: maybe the Qualification Requirements list.
- Qualifications: maybe overlapping with Requirements? But we have both Requirements and Qualifications as separate headings allowed. We need to decide what goes where. The posting has "Qualification Requirements" and "Disqualifiers". Also "Employee Value Proposition" (benefits/culture). Also "Pay And Benefits". Also "Schedule". Also "Job Type & Location". Also location/hybrid details.
We need to avoid duplication. We need to preserve all substantive info.
Let's map:
About the role: Could include the introductory paragraph(s) describing the firm, the position focus, project distribution, title note, location/hybrid? But location/hybrid maybe belongs under Schedule? Actually schedule is separate. Location could be part of About the role or maybe we can include in a short p under About the role.
Responsibilities: the bullet list under "(Summary Of Key Responsibilities)".
Requirements: maybe the "(Qualification Requirements)" list.
Qualifications: maybe the "(Disqualifiers)" list? Or we could treat Disqualifiers as part of Requirements? But we have separate headings; we could put Disqualifiers under Requirements as a list of what is not acceptable. However the instruction says "Use - for any list of duties/requirements/benefits". So we can have lists under Requirements and Qualifications.
Benefits: the list under Pay And Benefits (benefits). Also Employee Value Proposition includes benefits like employee-owned firm, awards, culture, compensation, hybrid opportunity. That overlaps with benefits and pay. We need to avoid duplication. We'll need to consolidate.
Pay: the pay range info.
Schedule: the schedule info (Monday-Friday, last Friday off each month). Also hybrid days.
We also have location/hybrid details: location Seattle, WA (Hybrid: Tuesday & Wednesday on-site, Monday, Thursday & Friday Remote). This could go under Schedule or About the role. Since schedule heading is for schedule info, we could include hybrid details there.
We also have Job Type & Location: Contract to Hire position based out of Seattle, WA. That's location and job type. Could be included in About the role or maybe a short p.
We also have Application Deadline: Sep 28, 2026. That's a minor metadata; we could fold into a short p under About the role or drop it? The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short p with that info.
We also have "About Actalent" which is company description; we might drop as not fitting headings.
We need to avoid filler/placeholder text. Ensure we don't include sections with only filler.
Now we need to output HTML fragment with
headings and appropriate
or
- .
Let's draft:
About the role
An internationally recognized architecture and design firm is seeking a Project Architect/Project Manager with expert Revit skills to focus on healthcare and civic projects. The role involves strong renovation experience and experience with healthcare, civic, and/or correctional facilities construction design, plus big project management. Approximately 70% of work will be on large California‑based healthcare projects and 30% on smaller Seattle‑based assisted‑living facility projects. The title will be Project Architect (or Job Captain if not licensed). Position is a Contract‑to‑Hire role based in Seattle, WA with a hybrid schedule (Tuesday & Wednesday on‑site, Monday, Thursday & Friday remote). Application anticipated to close September 28, 2026.
That covers intro, location, job type, deadline.
Responsibilities
- Serve as a Project Manager and Project Architect on a range of projects, overseeing scope, schedule, and budget.
- Lead design development and documentation efforts using Revit across all project phases.
- Coordinate with consultants, clients, and internal teams to ensure seamless project delivery.
- Manage project communication and maintain strong client relationships.
- Oversee production of construction documents and ensure compliance with applicable codes and regulations.
- Contribute to design vision while balancing technical, functional, and budgetary requirements.
- Support and mentor junior staff, providing guidance on design and documentation standards.
- Participate in project meetings, presentations, and stakeholder coordination.
Requirements
- 4‑8+ years of experience with Revit‑based construction document production.
- Advanced Revit proficiency (non‑negotiable).
- Complex project management experience (high preference for healthcare and correctional, but open to civic and hospitality).
- Big‑box retail or single‑home residential experience only is not a fit.
- Licensure is not required, but pursuing licensure is preferred.
- Self‑starter able to run projects with minimal oversight.
- Willingness to contribute to all phases of a project (not just design).
- Experience working on large and multi‑year timeline projects.
- Familiarity with CA and/or WA building codes and permitting processes.
Disqualifiers
- Not having advanced Revit proficiency (only AutoCAD experience will not be a fit).
- Only having big‑box retail and/or single‑family residential experience.
But
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the job description and extract sections. Given the description includes: - Intro: "An internationally recognized architecture and design firm is looking to hire a Project Architect/Project Manager. This position requires an expert in Revit and will focus on healthcare and civic projects. This position requires strong renovation experience, healthcare, civic, and/or correctional facilities construction design experience, and big project management experience. 70% of projects will be focused on large CA-based projects (healthcare), and 30% of projects will be working on small projects based in Seattle (i.e., assisted living facility projects). Title - Project Architect (if not licensed, the title will be a Job Captain) Pay - $43/hr. - $67/hr. (around $90k/yr. - $140k/yr.) - (Depending on Revit proficiency, strong portfolio, overall tenure, relevant industry, certifications, etc.) Schedule - Monday - Friday (Will have the last Friday off every month) Location - Seattle, WA (Hybrid: Tuesday & Wednesday on-site, Monday, Thursday & Friday Remote)" - Then "(Summary Of Key Responsibilities)" with bullet list. - Then "(Qualification Requirements)" with bullet list. - Then "(Disqualifiers)" bullet list. - Then "(Employee Value Proposition)" bullet list. - Then "Job Type & Location This is a Contract to Hire position based out of Seattle, WA." - Then "Pay And Benefits The pay range for this position is $43.00 - $67.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors. Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following: Medical, dental & vision Critical Illness, Accident, and Hospital 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available Life Insurance (Voluntary Life & AD&D for the employee and dependents) Short and long-term disability Health Spending Account (HSA) Transportation benefits Employee Assistance Program Time Off/Leave (PTO, Vacation or Sick Leave) Workplace Type This is a hybrid position in Seattle,WA." - Then "Application Deadline This position is anticipated to close on Sep 28, 2026." - Then "About Actalent ..." which is boilerplate about the company; we need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Actalent" section is likely considered boilerplate? It's not exactly EEO but it's company description. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Actalent" might be considered company overview, not necessarily boilerplate, but could be considered fluff. However we need to preserve ALL substantive information; do NOT invent or summarize away detail. The "About Actalent" includes details about the firm being a global leader, network size, etc. That might be considered substantive? But it's not about the job itself; it's about the employer. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't explicitly say to remove company overview. However earlier they said "Prefer a few substantive sections over many thin ones." The company overview might be considered not directly relevant to the job posting content (like responsibilities, qualifications, pay, schedule, benefits). It might be considered boilerplate. But it's not explicitly listed as boilerplate to remove. However typical job postings include "About the company" which is often considered not essential for the job description. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." If we remove the About Actalent section, we might be losing substantive info about the company. But is that considered substantive for the job? Possibly yes, but the instruction also says "Prefer a few substantive sections over many thin ones." Might be okay to include an "About the company" section if we have content. However the allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company" heading. So we cannot add a heading not in that list. So we must either incorporate that info into another allowed heading or drop it. Since we cannot create a heading like "About the company", we likely should drop that info, as it's not covered by allowed headings. The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not an exhaustive list? It says "e.g." meaning examples. So we could potentially use other headings if needed, but they gave a list of typical sections. Safer to stick to those.
Thus we need to extract content for:
- About the role: maybe a brief description of the role (the intro paragraphs). Could be placed under About the role.
- Responsibilities: the Summary Of Key Responsibilities list.
- Requirements: maybe the Qualification Requirements list.
- Qualifications: maybe overlapping with Requirements? But we have both Requirements and Qualifications as separate headings allowed. We need to decide what goes where. The posting has "Qualification Requirements" and "Disqualifiers". Also "Employee Value Proposition" (benefits/culture). Also "Pay And Benefits". Also "Schedule". Also "Job Type & Location". Also location/hybrid details.
We need to avoid duplication. We need to preserve all substantive info.
Let's map:
About the role: Could include the introductory paragraph(s) describing the firm, the position focus, project distribution, title note, location/hybrid? But location/hybrid maybe belongs under Schedule? Actually schedule is separate. Location could be part of About the role or maybe we can include in a short p under About the role.
Responsibilities: the bullet list under "(Summary Of Key Responsibilities)".
Requirements: maybe the "(Qualification Requirements)" list.
Qualifications: maybe the "(Disqualifiers)" list? Or we could treat Disqualifiers as part of Requirements? But we have separate headings; we could put Disqualifiers under Requirements as a list of what is not acceptable. However the instruction says "Use - for any list of duties/requirements/benefits". So we can have lists under Requirements and Qualifications.
Benefits: the list under Pay And Benefits (benefits). Also Employee Value Proposition includes benefits like employee-owned firm, awards, culture, compensation, hybrid opportunity. That overlaps with benefits and pay. We need to avoid duplication. We'll need to consolidate.
Pay: the pay range info.
Schedule: the schedule info (Monday-Friday, last Friday off each month). Also hybrid days.
We also have location/hybrid details: location Seattle, WA (Hybrid: Tuesday & Wednesday on-site, Monday, Thursday & Friday Remote). This could go under Schedule or About the role. Since schedule heading is for schedule info, we could include hybrid details there.
We also have Job Type & Location: Contract to Hire position based out of Seattle, WA. That's location and job type. Could be included in About the role or maybe a short p.
We also have Application Deadline: Sep 28, 2026. That's a minor metadata; we could fold into a short p under About the role or drop it? The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short p with that info.
We also have "About Actalent" which is company description; we might drop as not fitting headings.
We need to avoid filler/placeholder text. Ensure we don't include sections with only filler.
Now we need to output HTML fragment with
headings and appropriate
or
- .
Let's draft:
About the role
An internationally recognized architecture and design firm is seeking a Project Architect/Project Manager with expert Revit skills to focus on healthcare and civic projects. The role involves strong renovation experience and experience with healthcare, civic, and/or correctional facilities construction design, plus big project management. Approximately 70% of work will be on large California‑based healthcare projects and 30% on smaller Seattle‑based assisted‑living facility projects. The title will be Project Architect (or Job Captain if not licensed). Position is a Contract‑to‑Hire role based in Seattle, WA with a hybrid schedule (Tuesday & Wednesday on‑site, Monday, Thursday & Friday remote). Application anticipated to close September 28, 2026.
That covers intro, location, job type, deadline.
Responsibilities
- Serve as a Project Manager and Project Architect on a range of projects, overseeing scope, schedule, and budget.
- Lead design development and documentation efforts using Revit across all project phases.
- Coordinate with consultants, clients, and internal teams to ensure seamless project delivery.
- Manage project communication and maintain strong client relationships.
- Oversee production of construction documents and ensure compliance with applicable codes and regulations.
- Contribute to design vision while balancing technical, functional, and budgetary requirements.
- Support and mentor junior staff, providing guidance on design and documentation standards.
- Participate in project meetings, presentations, and stakeholder coordination.
Requirements
- 4‑8+ years of experience with Revit‑based construction document production.
- Advanced Revit proficiency (non‑negotiable).
- Complex project management experience (high preference for healthcare and correctional, but open to civic and hospitality).
- Big‑box retail or single‑home residential experience only is not a fit.
- Licensure is not required, but pursuing licensure is preferred.
- Self‑starter able to run projects with minimal oversight.
- Willingness to contribute to all phases of a project (not just design).
- Experience working on large and multi‑year timeline projects.
- Familiarity with CA and/or WA building codes and permitting processes.
Disqualifiers
- Not having advanced Revit proficiency (only AutoCAD experience will not be a fit).
- Only having big‑box retail and/or single‑family residential experience.
But
or drop it. So we can include a short p with that info. We also have "About Actalent" which is company description; we might drop as not fitting headings. We need to avoid filler/placeholder text. Ensure we don't include sections with only filler. Now we need to output HTML fragment with
headings and appropriate
or
- .
Let's draft:
About the role
An internationally recognized architecture and design firm is seeking a Project Architect/Project Manager with expert Revit skills to focus on healthcare and civic projects. The role involves strong renovation experience and experience with healthcare, civic, and/or correctional facilities construction design, plus big project management. Approximately 70% of work will be on large California‑based healthcare projects and 30% on smaller Seattle‑based assisted‑living facility projects. The title will be Project Architect (or Job Captain if not licensed). Position is a Contract‑to‑Hire role based in Seattle, WA with a hybrid schedule (Tuesday & Wednesday on‑site, Monday, Thursday & Friday remote). Application anticipated to close September 28, 2026.
That covers intro, location, job type, deadline.Responsibilities
- Serve as a Project Manager and Project Architect on a range of projects, overseeing scope, schedule, and budget.
- Lead design development and documentation efforts using Revit across all project phases.
- Coordinate with consultants, clients, and internal teams to ensure seamless project delivery.
- Manage project communication and maintain strong client relationships.
- Oversee production of construction documents and ensure compliance with applicable codes and regulations.
- Contribute to design vision while balancing technical, functional, and budgetary requirements.
- Support and mentor junior staff, providing guidance on design and documentation standards.
- Participate in project meetings, presentations, and stakeholder coordination.
Requirements
- 4‑8+ years of experience with Revit‑based construction document production.
- Advanced Revit proficiency (non‑negotiable).
- Complex project management experience (high preference for healthcare and correctional, but open to civic and hospitality).
- Big‑box retail or single‑home residential experience only is not a fit.
- Licensure is not required, but pursuing licensure is preferred.
- Self‑starter able to run projects with minimal oversight.
- Willingness to contribute to all phases of a project (not just design).
- Experience working on large and multi‑year timeline projects.
- Familiarity with CA and/or WA building codes and permitting processes.
Disqualifiers
- Not having advanced Revit proficiency (only AutoCAD experience will not be a fit).
- Only having big‑box retail and/or single‑family residential experience.