Land Solutions, Right of Way Acquisition Specialist – Washington State
for each heading only if content exists. We must not repeat job title. We need to preserve all substantive info, remove boilerplate.
We need to decide which sections to include.
Content:
- Who We Are: description of company, awards. Could be "About the role"? Actually "About the role" is about the job, not company. But we have no explicit "About the role". Could we put "Who We Are" under "About the role"? The instruction: 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 appropriate. "Who We Are" could go under "About the role"? Might be considered company overview, not role. But we could still include as "About the role" maybe not ideal. However we must include a section only when posting has real specific content for it. We have content about company; we could put under "About the role" but that might be misleading. Perhaps we can omit "About the role" if not directly about role. But we have "Job Description" which describes role. Could map that to "About the role". The "Job Description" paragraph: "Atwell is seeking Right of Way Specialists...". That's about the role. So we can put that under About the role
.
Then Responsibilities: we have a list.
Requirements vs Qualifications vs Skills: The posting has "Qualifications" list with many items. Could split into Requirements (maybe mandatory) and Qualifications (preferred) and Skills (maybe). But we need to follow instruction: only include sections when posting has real specific content. We have a qualifications list; we could treat that as Qualifications. Could also treat some as Requirements (Active Washington State Real Estate License, etc.) but they are all in qualifications. To avoid thin sections, we could combine into one Qualifications section. Or we could have Requirements (license, experience) and Qualifications (certifications, etc.) but risk creating thin sections. Better to have a single Qualifications section with all items.
Skills: maybe not separate; we could omit if not distinct.
Benefits: we have benefits details.
Pay: we have Pay Range: $35 USD - $40 USD.
Schedule: not mentioned; we should not include Schedule section.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay.
We need to use - for any list of duties/requirements/benefits. For prose, use
.
We need to preserve all substantive information: include company description, awards, job description paragraph, responsibilities list, qualifications list, benefits list, pay range.
We must remove boilerplate: disclaimer about AI tools, unsolicited resumes, etc. Also remove "Atwell Benefits: To attract..." maybe keep as part of benefits but we need to keep the list.
We need to format benefits as list items.
Let's extract details.
Who We Are paragraph:
"Atwell, LLC is a bold leader in the consulting, engineering, and construction services industry, delivering a broad range of creative solutions to clients in the real estate & land development, and energy markets. We have a strong national presence and a diverse, award-winning project portfolio. Atwell is a privately owned company, with 2,000+ passionate team members across 75+ locations and growing!Atwell, LLC is a proud recipient of the following 2025 awards:Ten consecutive years in a row as a “Best Place to Work” by Zweig Group (#11)Recognized as #70 in the ENR Top 500 Design Firms, ranked in every regionRecognized in Crain's “Fast 50” as one of the fastest-growing companies (#14)Recognized as the 2025 ENR Design Firm of the year for the Southeastern US"
We need to preserve that. Might need to add spaces/punctuation for readability but must not invent. We'll keep as is but maybe add line breaks.
Job Description paragraph:
"Atwell is seeking Right of Way Specialists to support utility infrastructure projects throughout Washington State. This opportunity will initially support a distribution line relocation project involving parcel acquisition activities and offers the potential to transition into a long-term utility program supporting electric transmission, electric distribution, and natural gas infrastructure projects across the region.We are looking for professionals ranging from emerging acquisition agents to highly experienced ROW specialists with utility and title experience."
Responsibilities list:
- Acquire easements, rights of way, permits, and other land rights needed for utility infrastructure projects
- Meet with landowners, explain project requirements, and negotiate agreements
- Maintain positive relationships with property owners, public agencies, attorneys, and project stakeholders
- Review title reports, ownership information, and property records as needed
- Coordinate with project managers, surveyors, engineers, environmental teams, and document specialists
- Track acquisition progress and maintain accurate project documentation
- Prepare status reports and communicate project updates to leadership and clients
- Support electric transmission, electric distribution, and natural gas projects as assigned
Qualifications list (as given):
- Active Washington State Real Estate License in good standing
- Experience in right of way, land acquisition, real estate, title, utility, energy, transportation, or related industries
- Knowledge of easement acquisition, property rights, and landowner negotiations
- Strong communication, negotiation, and relationship-building skills
- Ability to work independently in a field-based environment
- Ability to travel throughout Washington State as needed
- Experience supporting electric transmission, electric distribution, pipeline, renewable energy, or other utility infrastructure projects
- Working knowledge of title research, ownership verification, and property records
- Experience acquiring easements, fee acquisitions, licenses, permits, and other land rights
- Washington utility and/or infrastructure project experience
- IRWA certification or related industry certifications
Benefits list (from "Atwell Benefits:" section). Let's parse:
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 need to output as
- items. Could group under headings? Not required; just list.
Pay: "$35 USD - $40 USD". We'll put in
.
We must not include schedule.
Now produce HTML fragment:
About the role
Atwell is seeking Right of Way Specialists to support utility infrastructure projects throughout Washington State. This opportunity will initially support a distribution line relocation project involving parcel acquisition activities and offers the potential to transition into a long-term utility program supporting electric transmission, electric distribution, and natural gas infrastructure projects across the region. We are looking for professionals ranging from emerging acquisition agents to highly experienced ROW specialists with utility and title experience.
But we also need company description? Where to put? Could be part of About the role? Might be better to have a separate section like "About the company" but not allowed headings. Could we incorporate company description into About the role? Might be odd but we need to preserve all substantive info. Perhaps we can add a preceding about company before the role description within About the role section. That would still be under About the role heading but include company info. That's acceptable? The heading is About the role, but we can include company overview as part of role context. It's not ideal but we must include all info. Alternatively we could omit About the role heading and instead use no heading? But instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't say we must use those exact headings; they are examples. We could use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those examples. So we need to map content to those headings. Where does company description fit? Possibly under "About the role" as part of role context. We'll do that.
Thus About the role section will contain two paragraphs: company description and job description.
Now Responsibilities section with .
Qualifications section with .
Benefits section with .
Pay section with .
Make sure no extra boilerplate.
Let's craft.
Need to ensure we don't include duplicated lines. Remove "Atwell Benefits: 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." That's prose; we could keep as introductory sentence before list? It's substantive? It's a description of benefits program. Could keep as
before list. But we must not invent. It's okay to keep.
Similarly for Compensation and Work/Life headings inside benefits; those are not headings we should output as
because they'd be extra sections not in allowed list. But we could keep them as plain text inside
or ? The instruction: use for prose. So we could keep those headings as part of prose. Eg
Work/Life: ...
then list. But we must not create extra headings. We'll keep them as plain text.
Thus Benefits section: maybe a describing benefits program then
list.
Let's extract benefits list items exactly as given.
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 output as a single list.
Now Pay: "Pay Range : $35 USD - $40 USD". We'll output as Pay Range: $35 USD - $40 USD
.
Now produce final HTML.
Check no extra whitespace issues.
About the role
. Then Responsibilities: we have a list. Requirements vs Qualifications vs Skills: The posting has "Qualifications" list with many items. Could split into Requirements (maybe mandatory) and Qualifications (preferred) and Skills (maybe). But we need to follow instruction: only include sections when posting has real specific content. We have a qualifications list; we could treat that as Qualifications. Could also treat some as Requirements (Active Washington State Real Estate License, etc.) but they are all in qualifications. To avoid thin sections, we could combine into one Qualifications section. Or we could have Requirements (license, experience) and Qualifications (certifications, etc.) but risk creating thin sections. Better to have a single Qualifications section with all items. Skills: maybe not separate; we could omit if not distinct. Benefits: we have benefits details. Pay: we have Pay Range: $35 USD - $40 USD. Schedule: not mentioned; we should not include Schedule section. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to use- for any list of duties/requirements/benefits. For prose, use
. We need to preserve all substantive information: include company description, awards, job description paragraph, responsibilities list, qualifications list, benefits list, pay range. We must remove boilerplate: disclaimer about AI tools, unsolicited resumes, etc. Also remove "Atwell Benefits: To attract..." maybe keep as part of benefits but we need to keep the list. We need to format benefits as list items. Let's extract details. Who We Are paragraph: "Atwell, LLC is a bold leader in the consulting, engineering, and construction services industry, delivering a broad range of creative solutions to clients in the real estate & land development, and energy markets. We have a strong national presence and a diverse, award-winning project portfolio. Atwell is a privately owned company, with 2,000+ passionate team members across 75+ locations and growing!Atwell, LLC is a proud recipient of the following 2025 awards:Ten consecutive years in a row as a “Best Place to Work” by Zweig Group (#11)Recognized as #70 in the ENR Top 500 Design Firms, ranked in every regionRecognized in Crain's “Fast 50” as one of the fastest-growing companies (#14)Recognized as the 2025 ENR Design Firm of the year for the Southeastern US" We need to preserve that. Might need to add spaces/punctuation for readability but must not invent. We'll keep as is but maybe add line breaks. Job Description paragraph: "Atwell is seeking Right of Way Specialists to support utility infrastructure projects throughout Washington State. This opportunity will initially support a distribution line relocation project involving parcel acquisition activities and offers the potential to transition into a long-term utility program supporting electric transmission, electric distribution, and natural gas infrastructure projects across the region.We are looking for professionals ranging from emerging acquisition agents to highly experienced ROW specialists with utility and title experience." Responsibilities list: - Acquire easements, rights of way, permits, and other land rights needed for utility infrastructure projects - Meet with landowners, explain project requirements, and negotiate agreements - Maintain positive relationships with property owners, public agencies, attorneys, and project stakeholders - Review title reports, ownership information, and property records as needed - Coordinate with project managers, surveyors, engineers, environmental teams, and document specialists - Track acquisition progress and maintain accurate project documentation - Prepare status reports and communicate project updates to leadership and clients - Support electric transmission, electric distribution, and natural gas projects as assigned Qualifications list (as given): - Active Washington State Real Estate License in good standing - Experience in right of way, land acquisition, real estate, title, utility, energy, transportation, or related industries - Knowledge of easement acquisition, property rights, and landowner negotiations - Strong communication, negotiation, and relationship-building skills - Ability to work independently in a field-based environment - Ability to travel throughout Washington State as needed - Experience supporting electric transmission, electric distribution, pipeline, renewable energy, or other utility infrastructure projects - Working knowledge of title research, ownership verification, and property records - Experience acquiring easements, fee acquisitions, licenses, permits, and other land rights - Washington utility and/or infrastructure project experience - IRWA certification or related industry certifications Benefits list (from "Atwell Benefits:" section). Let's parse: 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 need to output as
- items. Could group under headings? Not required; just list.
Pay: "$35 USD - $40 USD". We'll put in
. We must not include schedule. Now produce HTML fragment:
About the role
Atwell is seeking Right of Way Specialists to support utility infrastructure projects throughout Washington State. This opportunity will initially support a distribution line relocation project involving parcel acquisition activities and offers the potential to transition into a long-term utility program supporting electric transmission, electric distribution, and natural gas infrastructure projects across the region. We are looking for professionals ranging from emerging acquisition agents to highly experienced ROW specialists with utility and title experience.
But we also need company description? Where to put? Could be part of About the role? Might be better to have a separate section like "About the company" but not allowed headings. Could we incorporate company description into About the role? Might be odd but we need to preserve all substantive info. Perhaps we can add a precedingabout company before the role description within About the role section. That would still be under About the role heading but include company info. That's acceptable? The heading is About the role, but we can include company overview as part of role context. It's not ideal but we must include all info. Alternatively we could omit About the role heading and instead use no heading? But instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't say we must use those exact headings; they are examples. We could use other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those examples. So we need to map content to those headings. Where does company description fit? Possibly under "About the role" as part of role context. We'll do that. Thus About the role section will contain two paragraphs: company description and job description. Now Responsibilities section with
- .
Qualifications section with
- .
Benefits section with
- .
Pay section with
. Make sure no extra boilerplate. Let's craft. Need to ensure we don't include duplicated lines. Remove "Atwell Benefits: 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." That's prose; we could keep as introductory sentence before list? It's substantive? It's a description of benefits program. Could keep as
before list. But we must not invent. It's okay to keep. Similarly for Compensation and Work/Life headings inside benefits; those are not headings we should output as
because they'd be extra sections not in allowed list. But we could keep them as plain text inside
or ? The instruction: use
for prose. So we could keep those headings as part of prose. Eg
Work/Life: ...
then list. But we must not create extra headings. We'll keep them as plain text. Thus Benefits section: maybe adescribing benefits program then
- list.
Let's extract benefits list items exactly as given.
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 output as a single list.
Now Pay: "Pay Range : $35 USD - $40 USD". We'll output as
Pay Range: $35 USD - $40 USD
. Now produce final HTML. Check no extra whitespace issues.
- items. Could group under headings? Not required; just list.
Pay: "$35 USD - $40 USD". We'll put in