Land Solutions, Right of Way Acquisition Specialist (Solar) – Ohio

Responsibilities

• each. - Requirements: The posting has "Qualifications" section which includes required qualifications. We'll treat as Requirements? The spec says we can have Requirements heading. We'll put required qualifications under

  Requirements

  maybe as
  . The "Qualifications" list includes: Active Ohio Real Estate License (Salesperson or Broker) required Prior right of way, land acquisition, easement acquisition, renewable energy leasing, or landowner negotiation experience required. Experience supporting solar energy, renewable energy, utility, electric transmission, pipeline, or other large-scale infrastructure projects preferred. Strong communication, negotiation, documentation, and relationship-building skills. Ability to work independently in rural communities, agricultural areas, and field-based project environments. Comfortable coordinating with landowners, project teams, title resources, document teams, and client stakeholders. Working knowledge of property ownership research, land rights, deeds, easements, option agreements, lease agreements, purchase agreements, and real estate documentation. Strong organizational skills and attention to detail. Ability to maintain accurate parcel files, acquisition records, and landowner communication logs. Active Notary Public commission preferred, or ability to obtain quickly. Willingness to travel throughout assigned Midwest project areas as project needs require. We'll put these as list items. - Preferred Backgrounds: Could be under "Qualifications" or "Skills"? The spec includes Skills heading. We could put "Preferred Backgrounds" under Skills? But we have a separate "Skills" heading. The "Preferred Backgrounds" list includes many items like Utility-scale solar energy projects, Renewable energy land acquisition, etc. We could treat as Skills. However we already have skills listed in Qualifications. Might combine. But spec says prefer few substantive sections over many thin ones. We could merge Preferred Backgrounds into Skills or Qualifications. Since Qualifications already includes required and preferred items, we could keep Qualifications as required and maybe add a Skills section for preferred backgrounds. But we need to avoid thin sections. Let's decide: We'll have Requirements (required qualifications) and Skills (preferred/skill-based). That seems reasonable. Thus:

  Requirements

  with required items (those marked required). Which items are required? The list: Active Ohio Real Estate License required; Prior right of way, land acquisition, easement acquisition, renewable energy leasing, or landowner negotiation experience required. The rest are preferred or skills. So we separate. Thus Requirements: - Active Ohio Real Estate License (Salesperson or Broker) required - Prior right of way, land acquisition, easement acquisition, renewable energy leasing, or landowner negotiation experience required. Maybe also "Willingness to travel throughout assigned Midwest project areas as project needs require." That's a requirement? It says willingness to travel... not marked required but likely required. We'll keep as requirement? It's not explicitly required but we can include in Requirements as it's a condition. However spec says preserve all substantive info; we can put it under Requirements as it's a condition. But to avoid thin sections, we could include it under Requirements as well. But we also have "Active Notary Public commission preferred, or ability to obtain quickly." That's preferred. Thus Requirements list: - Active Ohio Real Estate License (Salesperson or Broker) required - Prior right of way, land acquisition, easement acquisition, renewable energy leasing, or landowner negotiation experience required. - Willingness to travel throughout assigned Midwest project areas as project needs require. Now Skills: include the rest: strong communication, negotiation, documentation, relationship-building skills; ability to work independently in rural communities; comfortable coordinating; working knowledge of property ownership research...; strong organizational skills and attention to detail; ability to maintain accurate parcel files, acquisition records, and landowner communication logs; Active Notary Public commission preferred, or ability to obtain quickly; plus the Preferred Backgrounds list. We'll combine Skills and Preferred Backgrounds into a Skills section. Thus Skills list items: - Strong communication, negotiation, documentation, and relationship-building skills. - Ability to work independently in rural communities, agricultural areas, and field-based project environments. - Comfortable coordinating with landowners, project teams, title resources, document teams, and client stakeholders. - Working knowledge of property ownership research, land rights, deeds, easements, option agreements, lease agreements, purchase agreements, and real estate documentation. - Strong organizational skills and attention to detail. - Ability to maintain accurate parcel files, acquisition records, and landowner communication logs. - Active Notary Public commission preferred, or ability to obtain quickly. - Experience supporting solar energy, renewable energy, utility, electric transmission, pipeline, or other large-scale infrastructure projects (preferred). - Utility-scale solar energy projects. - Renewable energy land acquisition. - Solar lease, purchase, easement, option, and right-of-entry agreements. - Agricultural landowner negotiations. - Competitor research and land control research. - Surface title, courthouse research, deed review, and parcel documentation. - GIS/online mapping coordination. - Utility, electric transmission, pipeline, or other infrastructure projects. - Rural community engagement and stakeholder coordination. - Document execution, recording, and project close-out support. We could also include "While AI tools may support your application process..." but that's not a skill; it's a note. We can ignore as boilerplate? It's not cookie/navigation/legal/EEO etc. It's a statement about AI tools. Might be considered substantive? It's not a requirement. Probably we can omit as it's not a qualification. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not exactly those but could be considered application instructions? It's a note about AI tools. Safer to omit. Now Benefits: we have a Benefits section with many items. We'll create

  Benefits

  with
  • each. List from "Atwell Benefits:": Work/Life: - Generous Paid Time Off - Paid Parental Leave - Flexible work schedules are available for some positions - Tenure Awards — Travel Vouchers to see the world based on your travel preferences Compensation: - 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 ‘Atwell’ness: - 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'll flatten into a single list. Pay: we have "Pay Range : $35 USD - $40 USD". We'll create

    Pay

    with

    $35 USD - $40 USD

    . Schedule: not mentioned. No schedule info. So we omit Schedule section. Also we might include About the company? The "Who We Are" section could be considered About the role? But spec says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Who We Are" is about company, not role. Could we put under About the role? Might be okay to include as part of About the role? But About the role should describe the role. The "Who We Are" is company overview. Could we create a separate heading? Not in allowed list. The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should stick to those headings. It didn't forbid other headings, but says use those for section headings. Likely they expect only those headings. So we should not add a heading for Who We Are. We can incorporate that info into About the role? Might be okay to include as part of About the role? But About the role should be about the role, not company. However we could treat "Who We Are" as part of About the role? Might be considered filler. Better to omit it? But we must preserve ALL substantive information. The Who We Are is substantive about company. If we cannot add a heading not in list, maybe we can incorporate it into About the role as a preamble? The spec 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 those for section headings. It might be okay to add other headings if needed, but they gave examples. Safer to stick to those headings and incorporate company info into About the role? Could be considered not accurate but we need to preserve info. Perhaps we can create a heading "About the company" but not in list; risk. I'd incorporate into About the