Field & Events Marketing Specialist
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: "About Dialpad" (company description) but not "About the role". There's a "Your role" paragraph describing role. Could treat that as About the role? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings if present.
We have:
- About Dialpad (company overview) – not exactly "About the role". Could we treat as About the role? Probably not; but we could include "About the role" using the "Your role" paragraph. The "About Dialpad" is company description; maybe we can omit because not requested heading. The instruction: "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." It doesn't forbid other headings not listed, but says use
for section headings (e.g. About the role, Responsibilities...). Likely they expect we only output those headings if content exists. So we need to decide which sections have content.
Let's extract:
About the role: Could be the paragraph starting "Your role We are seeking a Field Marketing & Events Specialist..." That describes role. So we can put that under About the role
.
Responsibilities: The bullet list under "What You’ll Do". That's responsibilities.
Requirements: Not explicitly labeled but there is "Skills You’ll Bring" which includes experience requirements. Could treat as Requirements or Qualifications. There's also "Skills You’ll Bring" which is skills. The posting also mentions "Why Join Dialpad" (benefits/culture). There's no explicit Pay or Schedule.
Thus we can have sections: About the role, Responsibilities, Skills (or Qualifications), Benefits (maybe from Why Join Dialpad). No Pay or Schedule.
We must not create sections with filler like "not specified". So omit Pay and Schedule.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as HTML.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting includes at end: "Dialpad is an equal-opportunity employer..." That's EEO boilerplate; we should remove. Also "Don’t meet every single requirement? ..." maybe keep? That's encouragement to apply; could be considered application instruction? It's not exactly instruction to apply but encourages. Might be okay to keep? Safer to remove any encouragement to apply? The instruction: remove application instructions. That line is not exactly instruction but encourages to apply; might be considered part of EEO? I'd remove it to be safe.
Also remove duplicated lines.
We need to keep all substantive info: company description, role description, responsibilities list, skills/experience list, benefits/culture description.
Let's extract content precisely.
Company description (About Dialpad): first paragraph(s) up to "Being a Dialer". Actually there is a section "About Dialpad" then a paragraph about Dialpad being AI platform. Then "Being a Dialer At Dialpad, AI isn’t just a feature; it’s how our teams do their best work every day..." That's also company culture. We'll keep that as part of About the role? Might be better to include under About the role? But we already have About the role heading for role description. Could also include a separate "About Dialpad" but not in allowed headings. Since only allowed headings are those, we could incorporate company description into About the role section as introductory paragraph. That would preserve info.
Thus About the role section will contain: description of Dialpad (the AI platform) and "Being a Dialer" paragraph, then the role description "Your role We are seeking..." etc.
But we must not repeat job title as heading; we are not.
Now Responsibilities: list of items under "What You’ll Do". We'll convert each line to
Skills
(or Qualifications). The instruction includes Skills as a possible heading. We'll use Skills. Now Benefits: The "Why Join Dialpad" section includes: - Work at the center of the AI transformation in business communications - Build and ship agentic AI products that are redefining how companies operate - Join a team where AI amplifies every employee’s impact - Competitive salary, comprehensive benefits, and real opportunities for growth - We believe in investing in our people. Dialpad offers competitive benefits and perks, cutting-edge AI tools, and a robust training program that help you reach your full potential. - We have designed our offices to be inclusive, offering a vibrant environment to cultivate collaboration and connection. - Our exceptional culture, repeatedly recognized as a Great Place to Work, ensures that every employee feels valued and empowered to contribute to our collective success. We should put these underBenefits
. Ensure we don't include filler like "competitive salary, comprehensive benefits, and real opportunities for growth" is specific enough. We should not include Pay or Schedule sections. Now we need to output only HTML fragment, no /, no markdown fences. We'll structure:About the role
... (company description + role description)
Responsibilities
- ... ...
Skills
- ... ...
Benefits
- ... ...
tags. Probably separate paragraphs for readability. We'll output:
About the role
About Dialpad Dialpad is the AI platform for customer experience, built to resolve customer problems in real time across voice and digital. Our AI agents learn from your best human agents and improve with every interaction, helping organizations understand their customers, deliver better experiences, increase operational efficiencies, and build a lasting competitive advantage. Unlike legacy systems built to route and answer, or standalone agentic bot vendors built to deflect, Dialpad was built to resolve. Our AI agents and human agents operate on a single platform with shared context, allowing Agentic AI to resolve issues, advance deals, and eliminate busywork through automation while seamlessly handing conversations to humans when needed, with full context preserved. Market-leading brands, including Randstad, Motorola Solutions, Netflix, the San Diego Padres, the Colorado Rockies Baseball Club, and Cal Athletics, trust Dialpad. Dialpad is backed by Andreessen Horowitz, GV, ICONIQ