Technical Support Specialist
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. So we can have sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also "About the role" could be a brief summary from first paragraphs? The first paragraphs are about culture, not specific role. Might be considered "About the role" but it's more about company. The instruction says do NOT repeat job title as heading; we can still have About the role as a short paragraph summarizing role. But we have "WHAT YOU’LL DO" which is responsibilities. So we could have a short About the role paragraph before responsibilities, using prose
. Then Responsibilities
- . Then Requirements
- .
WHAT YOU HAVE (requirements/qualifications):
- 2–3 years of experience supporting technical products, ideally in SaaS or mobile application environments.
- A degree from an accredited college or university, a technical boot camp certification, or equivalent practical experience.
- Proficiency with case management tools (e.g., Salesforce, Zendesk) for efficient inquiry management and resolution.
- Hands-on experience with HTML, CSS, APIs, and/or SQL
- Experience with tools such as Postman, Snowflake, and/or Kibana is a plus.
- Domain knowledge of two or more: SaaS, Mobile Technology, APIs, Marketing Automation, Direct Marketing, Marketing Analytics, and/or basic programming.
- Strong written and verbal communication skills in English
We could split into Requirements (experience, education) and Qualifications (technical skills). But instructions allow using those headings. Let's make:
Requirements: 2–3 years experience, degree or equivalent.
Qualifications: proficiency with case management tools, hands-on experience with HTML/CSS/APIs/SQL, experience with Postman/Snowflake/Kibana (plus), domain knowledge of two or more areas, strong written/verbal communication.
But we could also combine. However we need to avoid thin sections. Let's make Requirements (experience + education) and Qualifications (technical skills + domain knowledge + communication). That seems reasonable.
WHO YOU ARE (skills/attributes):
- An excellent communicator with a customer-centric attitude with the ability to translate complex concepts into clear, understandable language for diverse audiences.
- Analytical, curious, and resourceful with strong troubleshooting and problem-solving capabilities
- Passionate about helping customers and resolving issues efficiently and effectively.
- Skilled at managing and prioritizing a high volume of inquiries and escalations; resilient and calm under pressure in fast-paced, time-sensitive situations.
- Able to synthesize complex technical concepts and communicate them clearly to diverse audiences (somewhat duplicate of first)
- Adaptable to fast-paced, high-volume environments with shifting priorities while being able to multitask and maintain performance under pressure.
- A proactive problem solver with a strong sense of intellectual curiosity, who thrives in collaborative team settings to tackle challenges.
We can deduplicate similar points but must preserve all substantive information; we can keep both but maybe combine similar? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should not remove details that are substantive. However we can combine if they are essentially same? The first and fifth are similar: both about communicating complex concepts. Might be considered duplicate; but they are separate sentences. Safer to keep both as separate list items? Could be considered duplicated lines; instruction says remove duplicated lines. So we should remove duplicate lines. The first and fifth are similar but not identical; first: "An excellent communicator with a customer-centric attitude with the ability to translate complex concepts into clear, understandable language for diverse audiences." Fifth: "Able to synthesize complex technical concepts and communicate them clearly to diverse audiences". They are similar but not identical; still convey same skill. Might be considered duplicate. Safer to keep only one? But risk losing nuance. I'd keep both but maybe rephrase to avoid duplication? The instruction: remove duplicated lines. If they are not exact duplicates, maybe okay. I'd keep both.
Pay section: "For candidates based in the United States, the pay range for this position at the start of employment is expected to be between $57,000 and $90,000/year, with an expected On Target Earnings (OTE) between $64,000 and $101,000/year (including bonus or commission). Your exact offer may vary depending on multiple individualized factors, including market location, job-related knowledge, skills, and experience. In addition to cash compensation, this role qualifies for a comprehensive Total Rewards package that includes equity grants of restricted stock (RSUs) so that you will own a piece of our company."
We need Pay section heading
Pay
and thenwith that text. Benefits section: "WHAT WE OFFER Braze benefits vary by location, and we encourage you to review our specific benefits offerings for each country here. More details on benefits plans will be provided if you receive an offer of employment.From offering comprehensive benefits to fostering hybrid ways of working, we’ve got you covered so you can prioritize work-life harmony. Braze offers benefits such as:Competitive compensation that may include equityRetirement and Employee Stock Purchase PlansFlexible paid time offComprehensive benefit plans covering medical, dental, vision, life, and disabilityFamily services that include fertility benefits and equal paid parental leaveProfessional development supported by formal career pathing, learning platforms, and a yearly learning stipendA curated in-office employee experience, designed to foster community, team connections, and innovationOpportunities to give back to your community, including an annual company-wide Volunteer Week and donation matching Employee Resource Groups that provide supportive communities within BrazeCollaborative, transparent, and fun culture recognized as a Great Place to Work®" We need to format as
- items. The text after colon is a list but not separated by punctuation. We need to split into items based on the list. Let's parse: - Competitive compensation that may include equity - Retirement and Employee Stock Purchase Plans - Flexible paid time off - Comprehensive benefit plans covering medical, dental, vision, life, and disability - Family services that include fertility benefits and equal paid parental leave - Professional development supported by formal career pathing, learning platforms, and a yearly learning stipend - A curated in-office employee experience, designed to foster community, team connections, and innovation - Opportunities to give back to your community, including an annual company-wide Volunteer Week and donation matching - Employee Resource Groups that provide supportive communities within Braze - Collaborative, transparent, and fun culture recognized as a Great Place to Work® Note there is also "Braze offers benefits such as:" then list. We'll output each as
- .
We also have earlier sentence about benefits vary by location etc. That can be a
before the list. Now About the role: maybe we can include a short paragraph summarizing role from first paragraphs? The first paragraphs are about company culture, not role. Could skip About the role section. But we could include a brief "About the role" paragraph using the first sentences: "At Braze, we have found our people..." but that's company. Might be considered filler. Safer to omit About the role heading if no specific role summary. The instructions: include a section ONLY when the posting has real, specific content for it. So we can omit About the role. Thus sections: Responsibilities, Requirements, Qualifications, Skills, Pay, Benefits. Now produce HTML. We need to wrap each section in
heading then content. For lists:
- ...
...
Make sure not to include any extra markdown. Let's craft. Responsibilities:- Owning customer inquiries end-to-end (how-to questions, technical break-fix issues, integration/configuration help, and best practice guidance), providing timely, insightful, and technically sound resolutions and suggestions.
- Becoming a trusted product expert—mastering the dashboard, integrations, troubleshooting steps, and best practices
- Driving increased product adoption by enabling customers to effectively utilize the platform and achieve their desired outcomes.
- Collaborating effectively with your own team members, Customer Success, Account Managers, Product and Engineering, and other cross-functional teams to deliver seamless customer experiences.
- Proactively identifying opportunities to enhance customer satisfaction and drive product adoption.
- Contributing to process improvements and internal enablement while actively documenting and sharing knowledge to elevate teammates and customers.
- 2–3 years of experience supporting technical products, ideally in SaaS or mobile application environments.
- A degree from an accredited college or university, a technical boot camp certification, or equivalent practical experience.
- Proficiency with case management tools (e.g., Salesforce, Zendesk) for efficient inquiry management and resolution.
- Hands-on experience with HTML, CSS, APIs, and/or SQL
- Experience with tools such as Postman, Snowflake, and/or Kibana is a plus.
- Domain knowledge of two or more: SaaS, Mobile Technology, APIs, Marketing Automation, Direct Marketing, Marketing Analytics, and/or basic programming.
- Strong written and verbal communication skills in English
- An excellent communicator with a customer-centric attitude with the ability to translate complex concepts into clear, understandable language for diverse audiences.
- Analytical, curious, and resourceful with strong troubleshooting and problem-solving capabilities
- (education/experience). Then Qualifications
- maybe for technical skills? Or combine. The posting has "WHAT YOU HAVE" includes experience, degree, proficiency with tools, hands-on experience, experience with tools plus, domain knowledge, communication skills. That's qualifications. Then "WHO YOU ARE" includes skills/attributes: communication, analytical, passionate, etc. That's Skills. Then Pay section: includes pay range and OTE. Benefits section: includes list of benefits. Schedule not mentioned, so omit.
We must not include boilerplate like EEO, AI recruitment process, etc. Also remove duplicated lines. Also remove "Please note this job description does not cover every duty..." maybe that's boilerplate? It's a note but could be considered filler; but it's substantive? It's a disclaimer; maybe we can drop as it's not specific duty. Safer to omit.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from WHAT YOU’LL DO, WHAT YOU HAVE, WHO YOU ARE, pay, benefits.
We need to format as HTML fragment only.
Let's extract details.
WHAT YOU’LL DO (responsibilities):
- Owning customer inquiries end-to-end (how-to questions, technical break-fix issues, integration/configuration help, and best practice guidance), providing timely, insightful, and technically sound resolutions and suggestions.
- Becoming a trusted product expert—mastering the dashboard, integrations, troubleshooting steps, and best practices
- Driving increased product adoption by enabling customers to effectively utilize the platform and achieve their desired outcomes.
- Collaborating effectively with your own team members, Customer Success, Account Managers, Product and Engineering, and other cross-functional teams to deliver seamless customer experiences.
- Proactively identifying opportunities to enhance customer satisfaction and drive product adoption.
- Contributing to process improvements and internal enablement while actively documenting and sharing knowledge to elevate teammates and customers.
We should keep each as