Architect - Federal

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove application instructions. So we need to parse the posting and extract relevant content. Let's read the posting: First paragraph: "At Jacobs, we're challenging today to reinvent tomorrow by solving the world's most critical problems for thriving cities, resilient environments, mission-critical outcomes, operational advancement, scientific discovery and cutting-edge manufacturing, turning abstract ideas into realities that transform the world for good." This is about the company. Could be "About the role"? Actually "About the role" maybe about the job. But we have a "Position Summary" later. So we could have "About the role" as a short description of the role? The posting includes "Your impact Jacobs is a leading design firm..." That's more about company. Might be considered "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include sections that have content. We need to decide which sections to include based on content present. Let's identify sections: - About the role: Could be the introductory paragraphs describing the role and impact. The posting includes: "Your impact Jacobs is a leading design firm...". Also "We are seeking an Architect who brings a natural curiosity...". Also "Position Summary". So we can combine into About the role. - Responsibilities: The posting includes many bullet-like sentences under "As a Project Architect on our team, you’ll be responsible for..." and then a list of responsibilities. Also "Team Development Responsibilities". So we can create Responsibilities section with

• . - Requirements: The posting includes "Here's what you'll need" with bullet list: U.S. Citizenship, Bachelor’s degree..., at least 2 years..., Overseas & US based travel may be required, Proficiency in REVIT, Proficiency in standard Office Suite products, Ideally, you’ll also have Registered Architect (RA), Previous DoD experience..., NCARB Accreditation, Design Build experience and DBIA certification, Clearance or ability to secure a clearance, A desire to be actively engaged... So that's requirements/qualifications. Could split into Requirements and Qualifications but we can combine or separate. The instruction says we can have both Requirements and Qualifications sections if content. We have both: "Here's what you'll need" seems like requirements/qualifications. Also there is "Registered Architect (RA)" etc. Might be qualifications. But we can just put them under Requirements or Qualifications. To be safe, we can have Requirements (citizenship, degree, experience, travel, proficiency) and Qualifications (RA, DoD experience, NCARB, DBIA, clearance, community engagement). Or we could combine. The instruction: prefer a few substantive sections over many thin ones. So maybe combine into one "Requirements" section covering all. But we have also "Skills" section: Could list Revit, Office Suite, etc. But those are also skills. Could separate Skills. However we have proficiency in REVIT, Office Suite. Also maybe "Registered Architect" is a qualification. The instruction says we can have Skills section if posting actually states them. It does mention proficiency in REVIT and Office Suite. So we could have Skills. - Benefits: The posting includes "Our health and welfare benefits are designed to invest in you..." with medical, dental, vision, basic life insurance, 401(k), ability to purchase company stock at a discount, deferred compensation plan, Executive Deferral Plan, unlimited U.S. Personalized Paid Time Off (PPTO) policy, seven paid holidays, caregiver leave, possible additional rewards: merit increases, performance discretionary bonus, stock. So we have benefits content. - Pay: The posting includes "The base salary range for this position is $69,500.00 to $121,500.00." So we have Pay. - Schedule: The posting includes "The position is hybrid with a minimum Jacobs Atlanta office attendance of two days per week in the office, but more days are encouraged to become more engrained with the culture of Jacobs." Also later: "We empower employees with our hybrid working policy, allowing them to split their work week between Jacobs offices/projects and remote locations enabling them to deliver their best work." So we have schedule/hybrid info. So we can include Schedule. Thus we can include sections: About the role, Responsibilities, Requirements (or Requirements & Qualifications), Skills, Benefits, Pay, Schedule. We must not include filler like "commensurate with experience". Not present. We must not include boilerplate like EEO etc. At end there is "All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability or protected veteran status." That's EEO boilerplate; must remove. Also "Job posted on September 27, 2026. This position will be open for at least 3 days." That's metadata; we can drop or fold into short p? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we could drop that line entirely or put in a short p at end maybe. But better to drop as it's not substantive. Also "We value collaboration and believe that in-person interactions are crucial for both our culture and client delivery. We empower employees with our hybrid working policy, allowing them to split their work week between Jacobs offices/projects and remote locations enabling them to deliver their best work." That's schedule/hybrid content; we already captured. Also "Your application experience is important to us, and we’re keen to adapt to make every interaction even better. If you require further support or reasonable adjustments with regards to the recruitment process (for example, you require the application form in a different format), please contact the team via Careers Support." That's application instructions; must remove. Thus we need to output HTML fragment with sections. We need to use

  for section headings. Use

  • for any list of duties/requirements/benefits. Use

    for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep details exactly as written, but we can format into lists. We need to be careful not to lose any detail. Let's extract content for each section. About the role: Could combine the introductory paragraphs before "Position Summary". Let's capture: "At Jacobs, we're challenging today to reinvent tomorrow by solving the world's most critical problems for thriving cities, resilient environments, mission-critical outcomes, operational advancement, scientific discovery and cutting-edge manufacturing, turning abstract ideas into realities that transform the world for good. Your impact Jacobs is a leading design firm in the Government, Commercial, Healthcare, Data Center and University sectors. We provide award winning architectural and engineering services in all phases of building design and construction. Our collaborative approach allows us to successfully deliver fully integrated professional services for a broad range of clients and project types worldwide. At Jacobs, we help prepare people for new opportunities and challenges. With positions at every level, openings in multiple disciplines, expertise in a range of markets and offices around the globe, we create an environment where you can learn, grow, and thrive. From our competitive benefits program to our Health and Safety initiative of Beyond Zero workplace injuries, we believe that you'll find a flourishing career here at Jacobs. We are seeking an Architect who brings a natural curiosity and growth mindset, continuously seeking new ideas, technologies, and design approaches that elevate project outcomes, team performance, and overall practice. The candidate will be excited by the opportunity to contribute beyond project delivery by helping to develop other staff, improve processes, and strengthen our architectural practice." Then "Position Summary The Project Architect is responsible for the coordination, development, and production of deliverables in support of the overall scope of architectural design. The Project Architect will take ownership of the completeness, accuracy and timeliness of the work assigned and within the agreed project budget. Individuals in this position must demonstrate the ability to lead a design effort as a member of a multi-disciplinary team to include electrical, structural, mechanical, civil, interiors, and fire protection engineers. We are looking for a self-motivated personality with the ability to work collaboratively and independently as appropriate in studio or remote environments. The position is in the Federal Buildings Business Unit, and the project type is majority US Federal Government facilities that are contracted by Department of Defense clients (USACE, NAVFAC, etc.) as well as Federal Civilian clients to include NASA, FAA, GSA, OBO and Intelligence Community amongst many others. As a Project Architect on our team, you’ll be responsible for managing projects for environments that enhance organizational performance and achieve the client’s business objectives utilizing best practices. Our goal is to develop innovative architectural design concepts which are practical, aesthetic, safe, and conducive to intended purpose and function, reflect client goals and are within project budget and schedule." That seems like a mix of about role and responsibilities. But we can treat "Position Summary" as part of About the role. Then responsibilities separate. Better: About the role: include the introductory paragraphs up to "We are seeking an Architect..." maybe plus Position Summary? But Position Summary includes responsibilities. However we can still keep it in About the role if we want, but then Responsibilities would duplicate. To avoid duplication, we should split: About the role: company description and role seeking. Responsibilities: the detailed list after "As a Project Architect on our team, you’ll be responsible for..." and also "Team Development Responsibilities". Also the earlier Position Summary includes some responsibilities but we can incorporate them into Responsibilities. Let's parse responsibilities: From "As a Project Architect on our team, you’ll be responsible for managing projects for environments that enhance organizational performance and achieve the client’s business objectives utilizing best practices. Our goal is to develop innovative architectural design concepts which are practical, aesthetic, safe, and conducive to intended purpose and function, reflect client goals and are within project budget and schedule." Then bullet list (actually sentences) starting with "Type of Work Works in a fast-paced environment under tight deadlines, while maintaining high quality standardsActs as the Designer of Record (DOR) for architectural design projects including schedule, budget, delegation of work to junior staff, quality control and sealing/stamping construction drawings and specificationsGather information, interview stakeholders, make studies, and prepare original rough layouts and sketches as required Responsible for technical resolution and coordination for a defined portion of a projectDevelops specifications and is responsible for coordination of drawings and specificationsWorks to implement the overall strategy for producing contract documents and participates in organizing the sheets planned for each stage of the work. This includes defining how data will be organized into files and which elements will be incorporated in a Building Information Model (BIM)Fosters and maintains a collaborative professional working relationship with the entire Project TeamPerform construction administration and field investigation tasks for assigned projects including document management and processing RFI's and Submittals" Then "Team Development Responsibilities Provide staffing development and mentoring for junior staff to include ensuring quality delivery of products completed by all supervised by Project Architect Provide project quality control reviews at project milestones and continuous “over-the-shoulder” discipline checks" We need to split into list items. The text is run together without punctuation. We need to separate logically. We can create list items based on the phrases separated by capital letters or verbs. But we must preserve all substantive information; we can reformat into

  • items but must not lose any detail. We can break them into sensible items. Let's extract each responsibility: - Works in a fast-paced environment under tight deadlines, while maintaining high quality standards - Acts as the Designer of Record (DOR) for architectural design projects including schedule, budget, delegation of work to junior staff, quality control and sealing/stamping construction drawings and specifications - Gather information, interview stakeholders, make studies, and prepare original rough layouts and sketches as required - Responsible for technical resolution and coordination