Membership Specialist
Bluetooth SIG · Kirkland, WA · 3 wk ago
$69k–$77k/yrFull-time
We need to output HTML fragment with sections: About the role (maybe from description), Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Must include only sections with real specific content. No placeholder. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate.
We need to parse the posting.
Key info:
- Status: Full-time, employee
- Job function: Customer Service/Program Coordinator
- Relevant work experience: 3-6 years of relevant, customer-facing work experience
- Career level: Experienced
- Office location: Kirkland, WA
- Workplace type: Hybrid (a mix of work from home or in office)
- Salary Range: $69,000 - $77,000
- Benefits: list (many repeated)
- The role description: Bluetooth SIG looking for Membership Specialist...
- Roles And Responsibilities: bullet list under headings: Member Support & Operations, Data & Reporting, Foundational Applied AI Skills, Up to 10% Domestic or International travel
- Skills And Requirements: list of skills
- Preferred Skills: list
- Who We Are: description (maybe "About the role"? Actually "Who We Are" is about company, could be "About the role"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need sections: About the role (maybe from "The role Bluetooth SIG..." paragraph), Responsibilities (from Roles And Responsibilities), Requirements (maybe from Skills And Requirements? Actually "Skills And Requirements" could be Skills, but we also have "Preferred Skills". Could combine Skills section for required skills, and maybe Qualifications for experience? But we have "Relevant work experience: 3-6 years". Could put under Requirements. Also "Career level: Experienced". Could be part of Requirements.
We need to avoid filler like "commensurate with experience". Not present.
We need to include Pay section: Salary Range: $69,000 - $77,000.
Schedule: Not explicitly given. There's workplace type Hybrid, but schedule not given. Could we infer? Not given. So we should not create Schedule section unless posting actually states them. It does not state schedule (like hours). So omit Schedule.
Benefits: we have a long list; need to deduplicate repeated items. Provide bullet list.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include each benefit item exactly as stated, but we can deduplicate duplicates (they appear twice). Should we keep duplicates? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Removing duplicates could be considered summarizing away detail? But duplicates are redundant; removing them is not losing substantive info, just removing redundancy. Likely acceptable. We'll deduplicate.
List benefits:
- Fully paid medical, dental, and vision insurance for employees and eligible dependents
- Qualified high deductible health plan/Health Savings Account/FSA
- Employee assistance program (appears twice)
- Prescription drug benefits (appears twice)
- AFLAC
- Long-term care reimbursement
- WPFLM reimbursement
- Employer-paid short-term and long-term disability (appears twice)
- Employer-paid life and AD&D
- 401(k) plan with company matching and no vesting period
- Net-employer 401(k) contribution
- Bi-annual bonus program
- Minimum 15 vacation days per year
- 12 company holidays
- Personal volunteer time
- 20 days of maternity/paternity leave
- 7 sick days per year
Also "Employee assistance program" appears twice; we keep one.
Now About the role: The paragraph starting "The role Bluetooth Special Interest Group (SIG), the global organization that manages one of the most recognizable international wireless brands, is looking for a Membership Specialist to manage and support the global Bluetooth SIG membership base." Continue until maybe before "Roles And Responsibilities". We'll capture that as About the role.
Responsibilities: Under "Roles And Responsibilities" we have subheadings: Member Support & Operations, Data & Reporting, Foundational Applied AI Skills, Up to 10% Domestic or International travel. Each has bullet points. We'll need to output as
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need sections: About the role (maybe from "The role Bluetooth SIG..." paragraph), Responsibilities (from Roles And Responsibilities), Requirements (maybe from Skills And Requirements? Actually "Skills And Requirements" could be Skills, but we also have "Preferred Skills". Could combine Skills section for required skills, and maybe Qualifications for experience? But we have "Relevant work experience: 3-6 years". Could put under Requirements. Also "Career level: Experienced". Could be part of Requirements.
We need to avoid filler like "commensurate with experience". Not present.
We need to include Pay section: Salary Range: $69,000 - $77,000.
Schedule: Not explicitly given. There's workplace type Hybrid, but schedule not given. Could we infer? Not given. So we should not create Schedule section unless posting actually states them. It does not state schedule (like hours). So omit Schedule.
Benefits: we have a long list; need to deduplicate repeated items. Provide bullet list.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include each benefit item exactly as stated, but we can deduplicate duplicates (they appear twice). Should we keep duplicates? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Removing duplicates could be considered summarizing away detail? But duplicates are redundant; removing them is not losing substantive info, just removing redundancy. Likely acceptable. We'll deduplicate.
List benefits:
- Fully paid medical, dental, and vision insurance for employees and eligible dependents
- Qualified high deductible health plan/Health Savings Account/FSA
- Employee assistance program (appears twice)
- Prescription drug benefits (appears twice)
- AFLAC
- Long-term care reimbursement
- WPFLM reimbursement
- Employer-paid short-term and long-term disability (appears twice)
- Employer-paid life and AD&D
- 401(k) plan with company matching and no vesting period
- Net-employer 401(k) contribution
- Bi-annual bonus program
- Minimum 15 vacation days per year
- 12 company holidays
- Personal volunteer time
- 20 days of maternity/paternity leave
- 7 sick days per year
Also "Employee assistance program" appears twice; we keep one.
Now About the role: The paragraph starting "The role Bluetooth Special Interest Group (SIG), the global organization that manages one of the most recognizable international wireless brands, is looking for a Membership Specialist to manage and support the global Bluetooth SIG membership base." Continue until maybe before "Roles And Responsibilities". We'll capture that as About the role.
Responsibilities: Under "Roles And Responsibilities" we have subheadings: Member Support & Operations, Data & Reporting, Foundational Applied AI Skills, Up to 10% Domestic or International travel. Each has bullet points. We'll need to output as - for each duty. Could group under subheadings? The instruction only says use
for section headings, and - for any list of duties/requirements/benefits. It doesn't forbid inner headings, but we should keep simple: just list all responsibilities as li. However we might lose subheading nuance. But we can keep subheadings as plain text inside li? Better to keep as
- and maybe include the subheading as part of li text. Eg: "
- Member Support & Operations: Provide support for member questions and issues via support tools, email, phone, and in-person ..." etc. That preserves detail.
Similarly for Skills And Requirements: list each skill as li.
Preferred Skills: could be included under Skills section? But we have separate "Preferred Skills". Could create a Skills section that includes both required and preferred? The instruction: use headings like Skills, Requirements, Qualifications. We have both Skills And Requirements and Preferred Skills. Could treat Skills And Requirements as Skills (required) and Preferred Skills as additional Skills (maybe under same heading). But we might split: Skills (required) and Preferred Skills (optional). However the instruction only gave examples; we can add extra headings if needed, but better to follow given examples. We could have Skills section containing both required and preferred, but we need to differentiate? Not required. We'll just put all skills under Skills heading, maybe note "Preferred" in text.
But we must not lose info: Preferred Skills list includes: Experience with customer support and knowledge base articles in Zendesk or Hubspot; Experience using AI tools in a professional setting; Experience with reporting and CRM account management in Hubspot.
We'll include those as li.
Now Requirements: we have "Relevant work experience: 3-6 years of relevant, customer-facing work experience", "Career level: Experienced", maybe also "At least 3 years’ experience working with customers/members". That's similar. Also "Highly proficient in Excel working with formulas/pivot tables". Also "Strong verbal and written communication skills...". Actually those are skills. We'll separate.
Better: Requirements heading for experience and career level etc. Skills heading for skill list.
Let's extract:
Experience/Requirements:
- 3-6 years of relevant, customer-facing work experience
- Career level: Experienced
- At least 3 years’ experience working with customers/members (maybe redundant)
- Experience with customer support and CRM tools (maybe skill)
- Experience working within a multi-national company
- Strong ability to step back and see the bigger picture (skill)
- Exercise good judgment and decision making skills, particularly in narrow time-frames (skill)
- Highly proficient in Excel working with formulas/pivot tables (skill)
- Accountable team player with demonstrated propensity for self-starting (skill)
But many of these are skills. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements for experience, career level, maybe qualifications. Skills for abilities.
We'll decide:
- Requirements: list items that are about experience, career level, location? Actually location is separate but not a heading. Could be included in About the role? Might be better to put location in About the role paragraph? The location is given as Office location: Kirkland, WA; Workplace type: Hybrid. Could be included in About the role or maybe a separate section like "Location". But not in allowed headings. Could fold into About the role paragraph as a sentence.
We'll include location and workplace type in About the role paragraph after the description.
Thus About the role will contain: description of role, location, workplace type.
Now Responsibilities: list all duties.
Now Requirements: list experience items: "3-6 years of relevant, customer-facing work experience", "Career level: Experienced", "At least 3 years’ experience working with customers/members". Might be redundant but we keep both? Might be considered summarizing away detail if we drop one. We'll keep both but note they are similar; but we can keep both as separate li.
Now Skills: list all skill items from Skills And Requirements and Preferred Skills.
Now Benefits: list deduplicated benefits.
Now Pay: Salary Range.
Now we must not include Schedule.
Now output HTML fragment.
Let's craft.
We'll start with About the role
...
Inside p we can include multiple sentences.
Let's compose About the role paragraph:
"The Bluetooth Special Interest Group (SIG), the global organization that manages one of the most recognizable international wireless brands, is seeking a Membership Specialist to manage and support the global Bluetooth SIG membership base. In this role you will support Bluetooth SIG members from all regions of the world, performing membership operations such as supporting renewals, member onboarding, account updates, processing tier 1 support requests, and triaging tier 2 support. You will act as a subject matter expert in membership policies and processes, help members adhere to policies, and identify and advocate for improvements in member experience with internal teams. You will also contribute to global membership projects, cross‑team initiatives, and regional campaigns to help reach the goals of the Bluetooth SIG. The position is based in Kirkland, WA with a hybrid workplace arrangement (mix of work from home and in‑office)."
That captures all.
Now Responsibilities Responsibilities
- ...
We need to extract each duty from the Roles And Responsibilities section.
Original text:
Roles And Responsibilities
Member Support & Operations
Provide support for member questions and issues via support tools, email, phone, and in-person
Develop and maintain an in-depth understanding of organizational services, processes, and policies to support more complex problem resolution
Create and maintain process and policy documents
Support the membership renewal process and initiatives for driving retention
Drive continuous improvement of the program and support content by identifying trends, recommending enhancements, and sharing insights with the broader team
Data & Reporting
Create weekly, monthly, and ad-hoc reporting for management and project teams
Use AI-assisted tools to summarize member feedback and support trends for team review
Foundational Applied AI Skills
Use approved AI tools to draft first-pass responses, summarize documents or tickets, and speed up content creation
Follow company guidelines on responsible and accurate use of AI tools in member communications
Operate collaboratively to support projects and service initiatives, including establishing Membership requirements for project and tools implementation
Up to 10% Domestic or International travel
We'll make each bullet a li. Could combine subheading as bold.
Let's create li items:
- Member Support & Operations: Provide support for member questions and issues via support tools, email, phone, and in-person
- Member Support & Operations: Develop and maintain an in-depth understanding of organizational services, processes, and policies to support more complex problem resolution
- Member Support & Operations: Create and maintain process and policy documents
- Member Support & Operations: Support the membership renewal process and initiatives for driving retention
- Member Support & Operations: Drive continuous improvement of the program and support content by identifying trends, recommending enhancements, and sharing insights with the broader team
- Data & Reporting: Create weekly, monthly, and ad-hoc reporting for management and project teams
- Data & Reporting: Use AI-assisted tools to summarize member feedback and support trends for team review
- Foundational Applied AI Skills: Use approved AI tools to draft first-pass responses, summarize documents or tickets, and speed up content creation
- Foundational Applied AI Skills: Follow company guidelines on responsible
for section headings, and - for any list of duties/requirements/benefits. It doesn't forbid inner headings, but we should keep simple: just list all responsibilities as li. However we might lose subheading nuance. But we can keep subheadings as plain text inside li? Better to keep as
- and maybe include the subheading as part of li text. Eg: "
- Member Support & Operations: Provide support for member questions and issues via support tools, email, phone, and in-person ..." etc. That preserves detail.
Similarly for Skills And Requirements: list each skill as li.
Preferred Skills: could be included under Skills section? But we have separate "Preferred Skills". Could create a Skills section that includes both required and preferred? The instruction: use headings like Skills, Requirements, Qualifications. We have both Skills And Requirements and Preferred Skills. Could treat Skills And Requirements as Skills (required) and Preferred Skills as additional Skills (maybe under same heading). But we might split: Skills (required) and Preferred Skills (optional). However the instruction only gave examples; we can add extra headings if needed, but better to follow given examples. We could have Skills section containing both required and preferred, but we need to differentiate? Not required. We'll just put all skills under Skills heading, maybe note "Preferred" in text.
But we must not lose info: Preferred Skills list includes: Experience with customer support and knowledge base articles in Zendesk or Hubspot; Experience using AI tools in a professional setting; Experience with reporting and CRM account management in Hubspot.
We'll include those as li.
Now Requirements: we have "Relevant work experience: 3-6 years of relevant, customer-facing work experience", "Career level: Experienced", maybe also "At least 3 years’ experience working with customers/members". That's similar. Also "Highly proficient in Excel working with formulas/pivot tables". Also "Strong verbal and written communication skills...". Actually those are skills. We'll separate.
Better: Requirements heading for experience and career level etc. Skills heading for skill list.
Let's extract:
Experience/Requirements:
- 3-6 years of relevant, customer-facing work experience
- Career level: Experienced
- At least 3 years’ experience working with customers/members (maybe redundant)
- Experience with customer support and CRM tools (maybe skill)
- Experience working within a multi-national company
- Strong ability to step back and see the bigger picture (skill)
- Exercise good judgment and decision making skills, particularly in narrow time-frames (skill)
- Highly proficient in Excel working with formulas/pivot tables (skill)
- Accountable team player with demonstrated propensity for self-starting (skill)
But many of these are skills. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements for experience, career level, maybe qualifications. Skills for abilities.
We'll decide:
- Requirements: list items that are about experience, career level, location? Actually location is separate but not a heading. Could be included in About the role? Might be better to put location in About the role paragraph? The location is given as Office location: Kirkland, WA; Workplace type: Hybrid. Could be included in About the role or maybe a separate section like "Location". But not in allowed headings. Could fold into About the role paragraph as a sentence.
We'll include location and workplace type in About the role paragraph after the description.
Thus About the role will contain: description of role, location, workplace type.
Now Responsibilities: list all duties.
Now Requirements: list experience items: "3-6 years of relevant, customer-facing work experience", "Career level: Experienced", "At least 3 years’ experience working with customers/members". Might be redundant but we keep both? Might be considered summarizing away detail if we drop one. We'll keep both but note they are similar; but we can keep both as separate li.
Now Skills: list all skill items from Skills And Requirements and Preferred Skills.
Now Benefits: list deduplicated benefits.
Now Pay: Salary Range.
Now we must not include Schedule.
Now output HTML fragment.
Let's craft.
We'll start with About the role
...
Inside p we can include multiple sentences.
Let's compose About the role paragraph:
"The Bluetooth Special Interest Group (SIG), the global organization that manages one of the most recognizable international wireless brands, is seeking a Membership Specialist to manage and support the global Bluetooth SIG membership base. In this role you will support Bluetooth SIG members from all regions of the world, performing membership operations such as supporting renewals, member onboarding, account updates, processing tier 1 support requests, and triaging tier 2 support. You will act as a subject matter expert in membership policies and processes, help members adhere to policies, and identify and advocate for improvements in member experience with internal teams. You will also contribute to global membership projects, cross‑team initiatives, and regional campaigns to help reach the goals of the Bluetooth SIG. The position is based in Kirkland, WA with a hybrid workplace arrangement (mix of work from home and in‑office)."
That captures all.
Now Responsibilities Responsibilities
- ...
We need to extract each duty from the Roles And Responsibilities section.
Original text:
Roles And Responsibilities
Member Support & Operations
Provide support for member questions and issues via support tools, email, phone, and in-person
Develop and maintain an in-depth understanding of organizational services, processes, and policies to support more complex problem resolution
Create and maintain process and policy documents
Support the membership renewal process and initiatives for driving retention
Drive continuous improvement of the program and support content by identifying trends, recommending enhancements, and sharing insights with the broader team
Data & Reporting
Create weekly, monthly, and ad-hoc reporting for management and project teams
Use AI-assisted tools to summarize member feedback and support trends for team review
Foundational Applied AI Skills
Use approved AI tools to draft first-pass responses, summarize documents or tickets, and speed up content creation
Follow company guidelines on responsible and accurate use of AI tools in member communications
Operate collaboratively to support projects and service initiatives, including establishing Membership requirements for project and tools implementation
Up to 10% Domestic or International travel
We'll make each bullet a li. Could combine subheading as bold.
Let's create li items:
- Member Support & Operations: Provide support for member questions and issues via support tools, email, phone, and in-person
- Member Support & Operations: Develop and maintain an in-depth understanding of organizational services, processes, and policies to support more complex problem resolution
- Member Support & Operations: Create and maintain process and policy documents
- Member Support & Operations: Support the membership renewal process and initiatives for driving retention
- Member Support & Operations: Drive continuous improvement of the program and support content by identifying trends, recommending enhancements, and sharing insights with the broader team
- Data & Reporting: Create weekly, monthly, and ad-hoc reporting for management and project teams
- Data & Reporting: Use AI-assisted tools to summarize member feedback and support trends for team review
- Foundational Applied AI Skills: Use approved AI tools to draft first-pass responses, summarize documents or tickets, and speed up content creation
- Foundational Applied AI Skills: Follow company guidelines on responsible
- and maybe include the subheading as part of li text. Eg: "
- Member Support & Operations: Provide support for member questions and issues via support tools, email, phone, and in-person ..." etc. That preserves detail.
Similarly for Skills And Requirements: list each skill as li.
Preferred Skills: could be included under Skills section? But we have separate "Preferred Skills". Could create a Skills section that includes both required and preferred? The instruction: use headings like Skills, Requirements, Qualifications. We have both Skills And Requirements and Preferred Skills. Could treat Skills And Requirements as Skills (required) and Preferred Skills as additional Skills (maybe under same heading). But we might split: Skills (required) and Preferred Skills (optional). However the instruction only gave examples; we can add extra headings if needed, but better to follow given examples. We could have Skills section containing both required and preferred, but we need to differentiate? Not required. We'll just put all skills under Skills heading, maybe note "Preferred" in text.
But we must not lose info: Preferred Skills list includes: Experience with customer support and knowledge base articles in Zendesk or Hubspot; Experience using AI tools in a professional setting; Experience with reporting and CRM account management in Hubspot.
We'll include those as li.
Now Requirements: we have "Relevant work experience: 3-6 years of relevant, customer-facing work experience", "Career level: Experienced", maybe also "At least 3 years’ experience working with customers/members". That's similar. Also "Highly proficient in Excel working with formulas/pivot tables". Also "Strong verbal and written communication skills...". Actually those are skills. We'll separate.
Better: Requirements heading for experience and career level etc. Skills heading for skill list.
Let's extract:
Experience/Requirements:
- 3-6 years of relevant, customer-facing work experience
- Career level: Experienced
- At least 3 years’ experience working with customers/members (maybe redundant)
- Experience with customer support and CRM tools (maybe skill)
- Experience working within a multi-national company
- Strong ability to step back and see the bigger picture (skill)
- Exercise good judgment and decision making skills, particularly in narrow time-frames (skill)
- Highly proficient in Excel working with formulas/pivot tables (skill)
- Accountable team player with demonstrated propensity for self-starting (skill)
But many of these are skills. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements for experience, career level, maybe qualifications. Skills for abilities. We'll decide: - Requirements: list items that are about experience, career level, location? Actually location is separate but not a heading. Could be included in About the role? Might be better to put location in About the role paragraph? The location is given as Office location: Kirkland, WA; Workplace type: Hybrid. Could be included in About the role or maybe a separate section like "Location". But not in allowed headings. Could fold into About the role paragraph as a sentence. We'll include location and workplace type in About the role paragraph after the description. Thus About the role will contain: description of role, location, workplace type. Now Responsibilities: list all duties. Now Requirements: list experience items: "3-6 years of relevant, customer-facing work experience", "Career level: Experienced", "At least 3 years’ experience working with customers/members". Might be redundant but we keep both? Might be considered summarizing away detail if we drop one. We'll keep both but note they are similar; but we can keep both as separate li. Now Skills: list all skill items from Skills And Requirements and Preferred Skills. Now Benefits: list deduplicated benefits. Now Pay: Salary Range. Now we must not include Schedule. Now output HTML fragment. Let's craft. We'll start with
About the role
...
Inside p we can include multiple sentences. Let's compose About the role paragraph: "The Bluetooth Special Interest Group (SIG), the global organization that manages one of the most recognizable international wireless brands, is seeking a Membership Specialist to manage and support the global Bluetooth SIG membership base. In this role you will support Bluetooth SIG members from all regions of the world, performing membership operations such as supporting renewals, member onboarding, account updates, processing tier 1 support requests, and triaging tier 2 support. You will act as a subject matter expert in membership policies and processes, help members adhere to policies, and identify and advocate for improvements in member experience with internal teams. You will also contribute to global membership projects, cross‑team initiatives, and regional campaigns to help reach the goals of the Bluetooth SIG. The position is based in Kirkland, WA with a hybrid workplace arrangement (mix of work from home and in‑office)." That captures all. Now ResponsibilitiesResponsibilities
- ...