Landscape Architect (Fort Worth, TX)

We need to output HTML fragment with sections: Who We Are? Actually "Who We Are" is a heading? It's a section heading but not in list of allowed headings? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings if applicable. The posting includes "Who We Are" (company description). That could be considered "About the role"? Actually "About the role" is typical. But we have "Who We Are" describing company. Could map to "About the role"? Not exactly. However we can still use

for any section heading we decide, but they gave examples; we should stick to those headings if possible. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; we can also use other headings? Probably better to use those headings where content matches. Let's identify sections: - About the role / Who We Are? Could be "About the role" describing the position and company. We'll put an

About the role

and include the "Who We Are" paragraph plus the description of the role. - Responsibilities: list of essential functions (bulleted). We'll put

Responsibilities

with

• items. - Requirements: maybe education and technical skills? Could be "Qualifications" and "Skills". We have "Technical Skills", "Education", "Qualifications", "Cultural Fit". We'll need to decide. We have "Technical Skills" list: AutoCAD, Adobe Creative Suite, Revit and/or Lumion, Microsoft Office, Written and verbal communication, including technical writing. Education: Bachelor’s degree in Landscape Architecture preferred. Undergraduate degrees in related fields may be considered with completion of an accredited Master’s program and/or the required equivalent experience working under a licensed Landscape Architect. Qualifications: list of abilities. Cultural Fit: list of traits. We could combine Education and Technical Skills into "Requirements" or "Qualifications". The instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use Requirements for education and technical skills? Qualifications for abilities? Skills for technical skills? Might be overlapping. Better to map: - About the role: company description + role overview. - Responsibilities: essential functions list. - Requirements: Education + Technical Skills (maybe combined). - Qualifications: abilities list. - Skills: maybe we could put technical skills under Skills, but we already used them in Requirements. Could instead put Technical Skills under Skills, and Education under Requirements. Let's decide: Requirements: Education (Bachelor's degree etc.) Skills: Technical Skills list. Qualifications: Abilities list. Benefits: we have benefits section with many items. Pay: not specified (no compensation details). So we should NOT create Pay section. Schedule: not specified (no schedule details). So omit. We must not create sections with filler like "not specified". So omit Pay and Schedule. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes a disclaimer about AI tools and Atwell unsolicited resumes. That's likely boilerplate/legal; we should remove. Also the "RVi Benefits" heading is part of benefits; we keep that content. We need to output only HTML fragment, no /, no markdown. Let's extract substantive content: Who We Are paragraph: "At RVi, we advocate for nature, inspire creativity, tell captivating stories, and forge strong relationships to create places with staying power. We’re process-oriented and results-driven. Our design is grounded in data, inspired by culture, and committed to responsible stewardship. Through creative strategy and design, we lead integrated teams to envision the world’s next great communities, public places, campuses, and hospitality experiences." Then: "RVi is looking for a Landscape Architect to join our Fort Worth office. This is an entry-level opportunity on our landscape architecture team.In this role, you’ll work alongside project leadership to support project design, development, and documentation throughout the different phases of a project. You’ll also help prepare, coordinate, and assemble project documents as directed by project leadership." That's role overview. Essential Functions list (bulleted). Let's list each: - Use AutoCAD and related software to complete assignments on time and in line with standards outlined in the RVi Quality Assurance/Quality Control Manual. - Support the RVi standard design process. - Assist with drafting documents and computations, including opinions of probable cost. - Take ownership of design and plan sets, regardless of originator. - Coordinate with project subconsultants and clients. - Assist with the preparation of construction-related services. - Assist with agreement preparation. - Complete site visits as required. - Participate in site walks, including project closeouts and related procedures. - Communicate with the Project Manager about workload, schedules, and tasks to help meet designated chargeability goals. - Follow RVi QA/QC protocols and established standards. - Support project compliance with national, state, and local landscape architectural standards. Technical Skills list: - Experience or knowledge related to: - AutoCAD - Adobe Creative Suite - Revit and/or Lumion - Microsoft Office - Written and verbal communication, including technical writing Education: - Bachelor’s degree in Landscape Architecture preferred. - Undergraduate degrees in related fields may be considered with completion of an accredited Master’s program and/or the required equivalent experience working under a licensed Landscape Architect. Qualifications (Abilities): - Ability to apply fundamental design concepts to practical situations using your educational background and/or equivalent experience. - Ability to work independently while also collaborating closely with Project Managers. - Ability to complete and/or correct design documentation. - Ability to move about the office and project sites as needed. - Willingness to travel as required. Cultural Fit traits: - Independent yet collaborative - Dependable and flexible - Creative problem solver - Results-oriented and client-focused - Enthusiastic and natural communicator Benefits: Under "RVi Benefits" heading, we have paragraphs and lists. Let's extract benefits content: Paragraph: "To attract and retain the best professionals in the industry, we aim to provide an excellent working environment and a progressive benefits program designed to support your personal and professional needs. We will support you to be a lifelong learner. You will be encouraged to give back to your community. Meeting deadlines, budgets and project objectives is important, but of equal importance is meeting your needs through training, advancement, and mentorships." Then subheadings: Work/Life:, Compensation:, Wellness: Under Work/Life: list: - Generous Paid Time Off - Paid Parental Leave - Flexible work schedules are available for some positions - Tenure Awards — Travel Vouchers to see the world based upon your travel preferences Under Compensation: list: - Competitive Compensation packages - Annual bonuses, spot bonuses and peer recognition awards - 401K match - 1:1 up to 4% of compensation - Tuition Assistance - Student Loan Repayment - Paid Licensing / Certification Fees and Renewals - Financial Rewards for Obtaining Licensure - Employee Referrals - Annual Wellness Reimbursement for anything wellness related (gym memberships, fitness tracker, home gym equipment, etc.) - Dependent Care Match Under Wellness: list: - Medical (BC/BS), Dental (Delta), and Vision (VSP) - Family Planning & IVF Benefits - Pet Insurance - Health Savings Account & Flex Spending Account options - Employer paid LTD, STD, and life insurance - Metlife Supplemental Benefits covering accident, hospitalization, and critical illness - Member Assistance Program (MAP) with complimentary counseling sessions, legal benefits, financial consultations, and work/life referral services We should keep all that. Now we need to format with

  headings and

  • for lists,

    for prose. We must not repeat the job title as a heading. The job title is Landscape Architect; we already didn't use it as heading. We must not put Job ID/requisition numbers as headings; none present. We must remove boilerplate: the disclaimer about AI tools and Atwell unsolicited resumes. Also maybe the "RVi Benefits" heading is okay as part of benefits section; we can keep that as prose before list. We need to decide which heading to use for benefits:

    Benefits

    . Good. Now we need to decide for sections: - About the role:

    About the role

    containing the Who We Are paragraph + role overview paragraph. - Responsibilities:

    Responsibilities

    with
    • essential functions. - Requirements:

      Requirements

      containing Education paragraph (maybe as

      )? Could also include technical skills? But we have Skills section. - Skills:

      Skills

      with technical skills list. - Qualifications:

      Qualifications

      with abilities list. - Benefits:

      Benefits

      with benefits prose and lists. We must not create Pay or Schedule sections. Now ensure we preserve all substantive information. Let's verify we didn't miss any: - The "Who We Are" paragraph included. - Role overview paragraph included. - Essential functions list included all items. - Technical skills list included. - Education paragraph included. - Qualifications abilities list included. - Cultural Fit traits: we haven't placed them anywhere. Should we include them? They are substantive. Could be part of Qualifications or maybe a separate section like "Cultural Fit". But we only have allowed headings; we could include them under Qualifications as additional bullet points, or we could create a separate section but not in allowed list? The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

      for section headings (e.g ...)". It implies we should use those headings for sections; but we could also add other headings if needed? Safer to stick to those headings. We can incorporate Cultural Fit into Qualifications as additional bullet points (makes sense). So Qualifications will include abilities plus cultural fit traits. - Benefits: we have all. Check for any duplicated lines: we should avoid duplication. Ensure we didn't repeat any. Now produce HTML. We'll need to escape any special characters? Not needed. Let's craft:

      About the role

      At RVi, we advocate for nature, inspire creativity, tell captivating stories, and forge strong relationships to create places with staying power. We’re process-oriented and results-driven. Our design is grounded in data, inspired by culture, and committed to responsible stewardship. Through creative strategy and design, we lead integrated teams to envision the world’s next great communities, public places, campuses, and hospitality experiences.

      RVi is looking for a Landscape Architect to join our Fort Worth office. This is an entry-level opportunity on our landscape architecture team. In this role, you’ll work alongside project leadership to support project design, development, and documentation throughout the different phases of a project. You’ll also help prepare, coordinate, and assemble project documents as directed by project leadership.

      Responsibilities

      • Use AutoCAD and related software to complete assignments on time and in line with standards outlined in the RVi Quality Assurance/Quality Control Manual.
      • Support the RVi standard design process.
      • Assist with drafting documents and computations, including opinions of probable cost.