State Government Relations Director - Montana
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and 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 decide which sections to include based on content.
We have:
- Position Summary (could be "About the role"): includes description of role, reporting line.
- Responsibilities: list of duties.
- Qualifications: Bachelor's degree required, at least 5 years experience...
- Knowledge, Skills And Abilities: list of skills.
- Title, Position Location, Full Time, Position Grade & Compensation, Reports To: these are metadata; we can fold into a short
maybe under "About the role" or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a paragraph with Title, Location, Full Time, Grade, Compensation, Reports To.
- Who We Are: includes mission statement, benefits description. Benefits: they list benefits package. So we can have a Benefits section.
- Pay: they gave salary range $85,000 – $95,000. So we can have Pay section.
- Schedule: they gave Full Time: Based on 37.5 hours per week. Also mention ability to work some evenings and weekends as needed, travel up to 60%. So we can have Schedule section.
We must not create sections with filler. All these have real content.
We need to use
for each section heading.
We need to use - for any list of duties/requirements/benefits.
We need to use
for prose.
We must not repeat the job title as a heading. So we will not have an
for "Montana Government Relations Director". We'll include title in metadata paragraph.
We must not include boilerplate like EEO etc. The "Who Are" includes mission statement and benefits; we need to keep mission statement? It's substantive. The EEO statement at end is boilerplate; we should remove it. Also the "Read on to learn more..." etc is promotional; maybe we can keep mission statement but remove the EEO and the "Please click HERE for more information." and the "Full time employees (37.5 hours/week), will enjoy all of the above plus an annual School Visitation Day and an Elder Care Facility Day of their choosing." Actually that is part of benefits description; we can keep that.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the mission statement sentences, the $100 million investment, etc. That's part of Who We Are.
We need to remove duplicated lines. There's no duplication apparent.
We need to remove application instructions: "Please click HERE for more information." and "Read on to learn more about the role, then visit our website www.alz.org/jobs to explore who we are and why we've been recognized as a Best Place to Work for the last twelve years in a row." That's promotional but maybe considered application instruction? It's not exactly instruction to apply, but it's a call to visit website. Might be considered boilerplate; safer to remove it. Also "At the Alzheimer's Association®, we believe that diverse perspectives are critical..." that's part of EEO/diversity statement; might be considered boilerplate but it's about commitment to diversity; could be considered substantive? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So we should remove the diversity statement as well. Also the final paragraph about equal employment opportunities is definitely EEO boilerplate; remove.
Thus we keep:
- Position Summary (About the role)
- Responsibilities (list)
- Qualifications (list? It's a couple sentences; could be
or
. It's not a list but we can keep as .
- Knowledge, Skills And Abilities (list)
- Metadata paragraph (Title, Location, Full Time, Position Grade & Compensation, Reports To)
- Pay section (salary range)
- Schedule section (hours, evenings/weekends, travel)
- Benefits section (benefits package description)
- Who We Are (mission, investment, employee count, etc.) maybe as About the organization? Could be a section "About the Association". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use "About the role" for summary, and maybe "About the Association" not in list but we could still use
with custom heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we can use other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where appropriate. We can also add other headings if needed, but better to stick to those. For mission statement we could put under "About the role"? No, that's about the role. Could put under "About the Association" but not in list; maybe we can incorporate into "About the role" as a brief description? But the mission statement is about the organization, not the role. However we could treat it as part of "About the role" as context. But we risk losing detail. The instruction says preserve ALL substantive information; we must keep mission statement etc. So we need a section for it. Could use "About the Association" as heading; not in examples but likely acceptable. The instruction didn't forbid other headings; just gave examples. So we can add About the Association
.
Similarly, we might need a section for "Requirements"? We have Qualifications and Knowledge, Skills And Abilities; we could combine them into Requirements? But better to keep Qualifications and Skills separate as per examples.
Thus sections:
- About the role (Position Summary)
- Responsibilities
- Qualifications
- Skills (Knowledge, Skills And Abilities)
- About the Association (mission, investment, employee count, etc.)
- Benefits
- Pay
- Schedule
We also need to include metadata like Title, Location, Full Time, Grade, Reports To. Could be placed in a
under About the role or separate
before sections. Probably best to put after About the role as a short paragraph.
We must not repeat the job title as a heading; we can include it in that paragraph.
Now craft HTML.
We'll start with
About the role
then containing the position summary plus metadata.
Position Summary text: "The Montana Government Relations Director serves as the principal staff for state government affairs and chief lobbyist in Montana, representing the Alzheimer’s Association before Montana’s legislature, governor, relevant state agencies, coalitions and community partners, and on statewide task forces and work groups. This position serves as a registered lobbyist with the state and is responsible for developing and executing a strategy to implement the Alzheimer’s Association’s coordinated nationwide state policy priorities including issues related to insurance coverage, Medicaid, long-term care, training standards, workforce issues, aging policy, and other related issues. The State Government Relations Director reports to the Territory Government Relations Director."
We also need to include Title, Location, Full Time, Position Grade & Compensation, Reports To. Title: Montana Government Relations Director. Position Location: Helena, MT. Full Time: Based on 37.5 hours per week. Position Grade & Compensation: Grade 109 The Alzheimer's Association’s good faith expectation for the salary range for this role is between $85,000 – $95,000. Reports To: Territory State Government Relations Director.
Note that salary range also appears in Pay section; we might duplicate if we include in metadata. Better to not duplicate; we can keep salary range only in Pay section. So in metadata we can omit salary range. So metadata paragraph: Title: Montana Government Relations Director. Position Location: Helena, MT. Full Time: Based on 37.5 hours per week. Position Grade: Grade 109. Reports To: Territory State Government Relations Director.
Now Responsibilities: list each duty as
- . We need to capture all responsibilities bullet points.
Responsibilities list from posting:
- Plan and execute a multi-year state legislative and regulatory agenda with a focus on implementation of the Association's state policy priorities, in collaboration with the National Public Policy Office.
- Draft bills and regulatory language and secure bill sponsors.
- Testify regularly before state legislative committees and train volunteer advocates and other Association staff to provide testimony on behalf of the Association as needed.
- Develop and grow relationships with legislators, state government officials and community stakeholders, ensuring the Association is represented on relevant statewide task forces, workgroups, committees and coalitions.
- Track state legislation utilizing the Association’s approved tracking system and monitor committee meetings and legislative action.
- Report lobbying activities as required and ensure compliance with the Association’s approved lobbying compliance vendor and internal tracking system.
- Collaborate with the local Grassroots Advocacy Manager to plan and execute the Association’s annual State Advocacy Day event at the state capitol.
- Identify opportunities for grassroots engagement on state issues and assist as needed in the execution of state-level advocacy activities, including coordinating office visits, correspondence, and other activities.
- Provide regular updates to the state Chapter Executive and other functional leaders; prepare reports and presentations for Chapter Board meetings and community events as requested.
- Collaborate with Association staff across the state chapter regularly to advance mission priorities and provide policy expertise.
- Participate in major events hosted by the state Chapter including Walk, galas, etc.
We'll put each as
- .
Qualifications: "Bachelor’s degree required. At least 5 years experience working in state government affairs setting; as a state legislative staff person; or as policy staff in the governor’s office or relevant state agency, preferably in Montana."
We can keep as
or
. Since it's two sentences, we can .
Skills (Knowledge, Skills And Abilities): list each bullet.
- Has current contacts within the state legislature and executive branch, and with potential partners and collaborators in Montana.
- Understands, and has experience with the legislative, regulatory, and budget process in Montana.
- Familiar with Medicaid, aging, health, drug coverage, and long-term care issues.
- Demonstrates the ability to anticipate, identify, organize, and analyze public policy opportunities.
- Possess excellent written and oral communications skills.
- Detail-oriented, adaptable, organized and able to successfully manage multiple projects and tasks.
- Proven self-starter with excellent judgment and careful attention to detail.
- Strong negotiation skills.
- Ability to work effectively with diverse populations with a high level of integrity, diplomacy and initiative.
- Ability and willingness to travel up to 6
for prose. Do NOT repeat the job title as a heading (the page already shows it) and 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 decide which sections to include based on content. We have: - Position Summary (could be "About the role"): includes description of role, reporting line. - Responsibilities: list of duties. - Qualifications: Bachelor's degree required, at least 5 years experience... - Knowledge, Skills And Abilities: list of skills. - Title, Position Location, Full Time, Position Grade & Compensation, Reports To: these are metadata; we can fold into a short
maybe under "About the role" or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a paragraph with Title, Location, Full Time, Grade, Compensation, Reports To. - Who We Are: includes mission statement, benefits description. Benefits: they list benefits package. So we can have a Benefits section. - Pay: they gave salary range $85,000 – $95,000. So we can have Pay section. - Schedule: they gave Full Time: Based on 37.5 hours per week. Also mention ability to work some evenings and weekends as needed, travel up to 60%. So we can have Schedule section. We must not create sections with filler. All these have real content. We need to use
for each section heading.
We need to use - for any list of duties/requirements/benefits.
We need to use
for prose.
We must not repeat the job title as a heading. So we will not have an
for "Montana Government Relations Director". We'll include title in metadata paragraph.
We must not include boilerplate like EEO etc. The "Who Are" includes mission statement and benefits; we need to keep mission statement? It's substantive. The EEO statement at end is boilerplate; we should remove it. Also the "Read on to learn more..." etc is promotional; maybe we can keep mission statement but remove the EEO and the "Please click HERE for more information." and the "Full time employees (37.5 hours/week), will enjoy all of the above plus an annual School Visitation Day and an Elder Care Facility Day of their choosing." Actually that is part of benefits description; we can keep that.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the mission statement sentences, the $100 million investment, etc. That's part of Who We Are.
We need to remove duplicated lines. There's no duplication apparent.
We need to remove application instructions: "Please click HERE for more information." and "Read on to learn more about the role, then visit our website www.alz.org/jobs to explore who we are and why we've been recognized as a Best Place to Work for the last twelve years in a row." That's promotional but maybe considered application instruction? It's not exactly instruction to apply, but it's a call to visit website. Might be considered boilerplate; safer to remove it. Also "At the Alzheimer's Association®, we believe that diverse perspectives are critical..." that's part of EEO/diversity statement; might be considered boilerplate but it's about commitment to diversity; could be considered substantive? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So we should remove the diversity statement as well. Also the final paragraph about equal employment opportunities is definitely EEO boilerplate; remove.
Thus we keep:
- Position Summary (About the role)
- Responsibilities (list)
- Qualifications (list? It's a couple sentences; could be
or
. It's not a list but we can keep as .
- Knowledge, Skills And Abilities (list)
- Metadata paragraph (Title, Location, Full Time, Position Grade & Compensation, Reports To)
- Pay section (salary range)
- Schedule section (hours, evenings/weekends, travel)
- Benefits section (benefits package description)
- Who We Are (mission, investment, employee count, etc.) maybe as About the organization? Could be a section "About the Association". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use "About the role" for summary, and maybe "About the Association" not in list but we could still use
with custom heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we can use other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where appropriate. We can also add other headings if needed, but better to stick to those. For mission statement we could put under "About the role"? No, that's about the role. Could put under "About the Association" but not in list; maybe we can incorporate into "About the role" as a brief description? But the mission statement is about the organization, not the role. However we could treat it as part of "About the role" as context. But we risk losing detail. The instruction says preserve ALL substantive information; we must keep mission statement etc. So we need a section for it. Could use "About the Association" as heading; not in examples but likely acceptable. The instruction didn't forbid other headings; just gave examples. So we can add About the Association
.
Similarly, we might need a section for "Requirements"? We have Qualifications and Knowledge, Skills And Abilities; we could combine them into Requirements? But better to keep Qualifications and Skills separate as per examples.
Thus sections:
- About the role (Position Summary)
- Responsibilities
- Qualifications
- Skills (Knowledge, Skills And Abilities)
- About the Association (mission, investment, employee count, etc.)
- Benefits
- Pay
- Schedule
We also need to include metadata like Title, Location, Full Time, Grade, Reports To. Could be placed in a
under About the role or separate
before sections. Probably best to put after About the role as a short paragraph.
We must not repeat the job title as a heading; we can include it in that paragraph.
Now craft HTML.
We'll start with
About the role
then containing the position summary plus metadata.
Position Summary text: "The Montana Government Relations Director serves as the principal staff for state government affairs and chief lobbyist in Montana, representing the Alzheimer’s Association before Montana’s legislature, governor, relevant state agencies, coalitions and community partners, and on statewide task forces and work groups. This position serves as a registered lobbyist with the state and is responsible for developing and executing a strategy to implement the Alzheimer’s Association’s coordinated nationwide state policy priorities including issues related to insurance coverage, Medicaid, long-term care, training standards, workforce issues, aging policy, and other related issues. The State Government Relations Director reports to the Territory Government Relations Director."
We also need to include Title, Location, Full Time, Position Grade & Compensation, Reports To. Title: Montana Government Relations Director. Position Location: Helena, MT. Full Time: Based on 37.5 hours per week. Position Grade & Compensation: Grade 109 The Alzheimer's Association’s good faith expectation for the salary range for this role is between $85,000 – $95,000. Reports To: Territory State Government Relations Director.
Note that salary range also appears in Pay section; we might duplicate if we include in metadata. Better to not duplicate; we can keep salary range only in Pay section. So in metadata we can omit salary range. So metadata paragraph: Title: Montana Government Relations Director. Position Location: Helena, MT. Full Time: Based on 37.5 hours per week. Position Grade: Grade 109. Reports To: Territory State Government Relations Director.
Now Responsibilities: list each duty as
- . We need to capture all responsibilities bullet points.
Responsibilities list from posting:
- Plan and execute a multi-year state legislative and regulatory agenda with a focus on implementation of the Association's state policy priorities, in collaboration with the National Public Policy Office.
- Draft bills and regulatory language and secure bill sponsors.
- Testify regularly before state legislative committees and train volunteer advocates and other Association staff to provide testimony on behalf of the Association as needed.
- Develop and grow relationships with legislators, state government officials and community stakeholders, ensuring the Association is represented on relevant statewide task forces, workgroups, committees and coalitions.
- Track state legislation utilizing the Association’s approved tracking system and monitor committee meetings and legislative action.
- Report lobbying activities as required and ensure compliance with the Association’s approved lobbying compliance vendor and internal tracking system.
- Collaborate with the local Grassroots Advocacy Manager to plan and execute the Association’s annual State Advocacy Day event at the state capitol.
- Identify opportunities for grassroots engagement on state issues and assist as needed in the execution of state-level advocacy activities, including coordinating office visits, correspondence, and other activities.
- Provide regular updates to the state Chapter Executive and other functional leaders; prepare reports and presentations for Chapter Board meetings and community events as requested.
- Collaborate with Association staff across the state chapter regularly to advance mission priorities and provide policy expertise.
- Participate in major events hosted by the state Chapter including Walk, galas, etc.
We'll put each as
- .
Qualifications: "Bachelor’s degree required. At least 5 years experience working in state government affairs setting; as a state legislative staff person; or as policy staff in the governor’s office or relevant state agency, preferably in Montana."
We can keep as
or
. Since it's two sentences, we can .
Skills (Knowledge, Skills And Abilities): list each bullet.
- Has current contacts within the state legislature and executive branch, and with potential partners and collaborators in Montana.
- Understands, and has experience with the legislative, regulatory, and budget process in Montana.
- Familiar with Medicaid, aging, health, drug coverage, and long-term care issues.
- Demonstrates the ability to anticipate, identify, organize, and analyze public policy opportunities.
- Possess excellent written and oral communications skills.
- Detail-oriented, adaptable, organized and able to successfully manage multiple projects and tasks.
- Proven self-starter with excellent judgment and careful attention to detail.
- Strong negotiation skills.
- Ability to work effectively with diverse populations with a high level of integrity, diplomacy and initiative.
- Ability and willingness to travel up to 6
for prose. We must not repeat the job title as a heading. So we will not have an
for "Montana Government Relations Director". We'll include title in metadata paragraph. We must not include boilerplate like EEO etc. The "Who Are" includes mission statement and benefits; we need to keep mission statement? It's substantive. The EEO statement at end is boilerplate; we should remove it. Also the "Read on to learn more..." etc is promotional; maybe we can keep mission statement but remove the EEO and the "Please click HERE for more information." and the "Full time employees (37.5 hours/week), will enjoy all of the above plus an annual School Visitation Day and an Elder Care Facility Day of their choosing." Actually that is part of benefits description; we can keep that. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the mission statement sentences, the $100 million investment, etc. That's part of Who We Are. We need to remove duplicated lines. There's no duplication apparent. We need to remove application instructions: "Please click HERE for more information." and "Read on to learn more about the role, then visit our website www.alz.org/jobs to explore who we are and why we've been recognized as a Best Place to Work for the last twelve years in a row." That's promotional but maybe considered application instruction? It's not exactly instruction to apply, but it's a call to visit website. Might be considered boilerplate; safer to remove it. Also "At the Alzheimer's Association®, we believe that diverse perspectives are critical..." that's part of EEO/diversity statement; might be considered boilerplate but it's about commitment to diversity; could be considered substantive? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So we should remove the diversity statement as well. Also the final paragraph about equal employment opportunities is definitely EEO boilerplate; remove. Thus we keep: - Position Summary (About the role) - Responsibilities (list) - Qualifications (list? It's a couple sentences; could be
or
- . It's not a list but we can keep as
- . We need to capture all responsibilities bullet points. Responsibilities list from posting: - Plan and execute a multi-year state legislative and regulatory agenda with a focus on implementation of the Association's state policy priorities, in collaboration with the National Public Policy Office. - Draft bills and regulatory language and secure bill sponsors. - Testify regularly before state legislative committees and train volunteer advocates and other Association staff to provide testimony on behalf of the Association as needed. - Develop and grow relationships with legislators, state government officials and community stakeholders, ensuring the Association is represented on relevant statewide task forces, workgroups, committees and coalitions. - Track state legislation utilizing the Association’s approved tracking system and monitor committee meetings and legislative action. - Report lobbying activities as required and ensure compliance with the Association’s approved lobbying compliance vendor and internal tracking system. - Collaborate with the local Grassroots Advocacy Manager to plan and execute the Association’s annual State Advocacy Day event at the state capitol. - Identify opportunities for grassroots engagement on state issues and assist as needed in the execution of state-level advocacy activities, including coordinating office visits, correspondence, and other activities. - Provide regular updates to the state Chapter Executive and other functional leaders; prepare reports and presentations for Chapter Board meetings and community events as requested. - Collaborate with Association staff across the state chapter regularly to advance mission priorities and provide policy expertise. - Participate in major events hosted by the state Chapter including Walk, galas, etc. We'll put each as
- .
Qualifications: "Bachelor’s degree required. At least 5 years experience working in state government affairs setting; as a state legislative staff person; or as policy staff in the governor’s office or relevant state agency, preferably in Montana."
We can keep as
or
- . Since it's two sentences, we can
. Skills (Knowledge, Skills And Abilities): list each bullet. - Has current contacts within the state legislature and executive branch, and with potential partners and collaborators in Montana. - Understands, and has experience with the legislative, regulatory, and budget process in Montana. - Familiar with Medicaid, aging, health, drug coverage, and long-term care issues. - Demonstrates the ability to anticipate, identify, organize, and analyze public policy opportunities. - Possess excellent written and oral communications skills. - Detail-oriented, adaptable, organized and able to successfully manage multiple projects and tasks. - Proven self-starter with excellent judgment and careful attention to detail. - Strong negotiation skills. - Ability to work effectively with diverse populations with a high level of integrity, diplomacy and initiative. - Ability and willingness to travel up to 6
. - Knowledge, Skills And Abilities (list) - Metadata paragraph (Title, Location, Full Time, Position Grade & Compensation, Reports To) - Pay section (salary range) - Schedule section (hours, evenings/weekends, travel) - Benefits section (benefits package description) - Who We Are (mission, investment, employee count, etc.) maybe as About the organization? Could be a section "About the Association". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use "About the role" for summary, and maybe "About the Association" not in list but we could still use
with custom heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we can use other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where appropriate. We can also add other headings if needed, but better to stick to those. For mission statement we could put under "About the role"? No, that's about the role. Could put under "About the Association" but not in list; maybe we can incorporate into "About the role" as a brief description? But the mission statement is about the organization, not the role. However we could treat it as part of "About the role" as context. But we risk losing detail. The instruction says preserve ALL substantive information; we must keep mission statement etc. So we need a section for it. Could use "About the Association" as heading; not in examples but likely acceptable. The instruction didn't forbid other headings; just gave examples. So we can add About the Association
.
Similarly, we might need a section for "Requirements"? We have Qualifications and Knowledge, Skills And Abilities; we could combine them into Requirements? But better to keep Qualifications and Skills separate as per examples.
Thus sections:
- About the role (Position Summary)
- Responsibilities
- Qualifications
- Skills (Knowledge, Skills And Abilities)
- About the Association (mission, investment, employee count, etc.)
- Benefits
- Pay
- Schedule
We also need to include metadata like Title, Location, Full Time, Grade, Reports To. Could be placed in a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where appropriate. We can also add other headings if needed, but better to stick to those. For mission statement we could put under "About the role"? No, that's about the role. Could put under "About the Association" but not in list; maybe we can incorporate into "About the role" as a brief description? But the mission statement is about the organization, not the role. However we could treat it as part of "About the role" as context. But we risk losing detail. The instruction says preserve ALL substantive information; we must keep mission statement etc. So we need a section for it. Could use "About the Association" as heading; not in examples but likely acceptable. The instruction didn't forbid other headings; just gave examples. So we can add About the Association
.
Similarly, we might need a section for "Requirements"? We have Qualifications and Knowledge, Skills And Abilities; we could combine them into Requirements? But better to keep Qualifications and Skills separate as per examples.
Thus sections:
- About the role (Position Summary)
- Responsibilities
- Qualifications
- Skills (Knowledge, Skills And Abilities)
- About the Association (mission, investment, employee count, etc.)
- Benefits
- Pay
- Schedule
We also need to include metadata like Title, Location, Full Time, Grade, Reports To. Could be placed in a
under About the role or separate
before sections. Probably best to put after About the role as a short paragraph. We must not repeat the job title as a heading; we can include it in that paragraph. Now craft HTML. We'll start with
About the role
thencontaining the position summary plus metadata. Position Summary text: "The Montana Government Relations Director serves as the principal staff for state government affairs and chief lobbyist in Montana, representing the Alzheimer’s Association before Montana’s legislature, governor, relevant state agencies, coalitions and community partners, and on statewide task forces and work groups. This position serves as a registered lobbyist with the state and is responsible for developing and executing a strategy to implement the Alzheimer’s Association’s coordinated nationwide state policy priorities including issues related to insurance coverage, Medicaid, long-term care, training standards, workforce issues, aging policy, and other related issues. The State Government Relations Director reports to the Territory Government Relations Director." We also need to include Title, Location, Full Time, Position Grade & Compensation, Reports To. Title: Montana Government Relations Director. Position Location: Helena, MT. Full Time: Based on 37.5 hours per week. Position Grade & Compensation: Grade 109 The Alzheimer's Association’s good faith expectation for the salary range for this role is between $85,000 – $95,000. Reports To: Territory State Government Relations Director. Note that salary range also appears in Pay section; we might duplicate if we include in metadata. Better to not duplicate; we can keep salary range only in Pay section. So in metadata we can omit salary range. So metadata paragraph: Title: Montana Government Relations Director. Position Location: Helena, MT. Full Time: Based on 37.5 hours per week. Position Grade: Grade 109. Reports To: Territory State Government Relations Director. Now Responsibilities: list each duty as