Senior Solutions Engineer - Upmarket West
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content accordingly. The instructions: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should only include those headings if there is real content. We must not repeat job title as heading. Also we must not include Pay/Schedule/Benefits unless posting actually states them. The posting includes salary range (Minimum Salary Range or On Target Earnings: $146,000.00 Maximum $319,400.00). That's Pay info. Also includes Benefits section. There's no explicit schedule (like remote/hybrid) but there is "Ways of Working Our structured hybrid approach...". That could be considered Schedule? The instruction says include Pay/Schedule/Benefits sections only if posting actually states them. The posting does mention hybrid approach, which is a work style. Could be considered Schedule. But we need to decide if we include a Schedule section. The posting says "Ways of Working Our structured hybrid approach is centered around our offices and remote work environments. The work style of each role, Hybrid, Remote, or In-Person is indicated in the job description/posting." That's schedule info. So we could include a Schedule section with that content.
We also need Requirements, Qualifications, Skills sections. The posting includes "What We're Looking For" which contains experience, knowledge, proficiency, passion, rapport-builder. That could be split into Requirements (experience), Qualifications (knowledge), Skills (proficiency, passion, rapport). But we must not invent headings with filler. We need to ensure each heading has substantive content.
We can structure:
About the role
with intro paragraph(s) from "What You Can Expect" and maybe "About The Team". Actually "About The Team" could be part of About the role. We'll combine.
Responsibilities
with list from Responsibilities bullet points.
Requirements
with "8+ years of solutions engineering experience supporting enterprise-level customers in technical pre-sales, with a strong understanding of the sales cycle and ability to drive urgency at the right moments."
Qualifications
with "Strong working knowledge across the full UCaaS stack—SaaS collaboration, cloud voice, contact center, video, and unified communications—with ability to hit the ground running; generalist profile strongly preferred over narrow specialization."
Skills
with "Highly proficient in presenting complex technical solutions, from traditional voice systems to modern cloud platforms, with hands-on familiarity with API integrations, networking protocols, security best practices, and cloud infrastructure (AWS, Azure, GCP). A genuine passion for AI: not just awareness of the trends, but real use cases, hands-on experience, and the ability to speak to its impact on the modern workforce with conviction. Natural rapport-builder with strong business acumen and executive presence: effective with AEs, executives, and technical stakeholders at every level."
Benefits
with paragraph from Benefits section.
Pay
with salary range paragraph.
Schedule
with hybrid work description.
We must not include any boilerplate like EEO, application instructions, etc. Also remove duplicated lines.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact text? Probably we can keep the substance but can rephrase slightly? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the information as is, maybe copy sentences. We can keep them as paragraphs or list items.
We need to use - for any list of duties/requirements/benefits. So for Responsibilities we should make a list. For Requirements, Qualifications, Skills maybe also list if they are multiple items. But they are each a single paragraph with multiple clauses; could still be a list but not required. The instruction says use
- for any list of duties/requirements/benefits. If we have multiple items, we should list them. For Responsibilities we have multiple bullet points; we will make a list.
For Requirements, Qualifications, Skills each could be a single item list or just paragraph. Safer to make them as
maybe. But the instruction says use
- for any list of duties/requirements/benefits. If it's not a list, we can use
. We'll decide.
Let's extract exact text:
Intro: "What You Can Expect You will serve as the lead technical advocate for our customers, helping them understand and leverage Zoom's architectural advantages while partnering closely with our Upmarket Enterprise and Majors AE teams across the West. This is a role for a well-rounded, technically credible SE who brings broad knowledge across the full UCaaS stack, not just a single product line. This is a high-visibility, high-impact role supporting some of the most complex accounts in the country: enterprise-scale technology companies that demand sophisticated, multi-product solution design. This role is for a forward-thinking UCaaS generalist with a passion for technology, a customer-first mindset, and a genuine drive to deliver happiness through transformative AI solutions."
About The Team: "Supporting Upmarket West accounts, our Solutions Engineering team acts as the strategic and technical backbone for complex enterprise deal cycles. We partner closely with Account Executives to architect full-platform solutions, articulate Zoom’s competitive advantages, and deliver happiness to our clients."
We can combine.
Responsibilities bullet points:
- Partner closely with Enterprise and Majors AEs to drive technical sales engagements across the full Zoom platform—including Meetings, Phone, Contact Center, Rooms, and AI-powered solutions.
- Lead technical discovery, solution design, custom demos, and proofs of concept (POCs) tailored to address complex enterprise collaboration challenges.
- Serve as the primary technical advocate for our clients, translating customer requirements into product recommendations and driving feature requests internally with Product and Engineering.
- Articulate Zoom’s architectural advantages, enterprise AI use cases, and broader vision to decision-makers ranging from technical practitioners to executive leadership.
- Gather market intelligence and competitive insights from field engagements to help refine sales strategies and inform internal roadmaps.
- Collaborate cross-functionally with AEs, product managers, and specialists to manage RFPs/RFQs, remove technical blockers, and accelerate deal cycles.
What We're Looking For paragraphs:
"8+ years of solutions engineering experience supporting enterprise-level customers in technical pre-sales, with a strong understanding of the sales cycle and ability to drive urgency at the right moments."
"Strong working knowledge across the full UCaaS stack—SaaS collaboration, cloud voice, contact center, video, and unified communications—with ability to hit the ground running; generalist profile strongly preferred over narrow specialization."
"Highly proficient in presenting complex technical solutions, from traditional voice systems to modern cloud platforms, with hands-on familiarity with API integrations, networking protocols, security best practices, and cloud infrastructure (AWS, Azure, GCP)."
"A genuine passion for AI: not just awareness of the trends, but real use cases, hands-on experience, and the ability to speak to its impact on the modern workforce with conviction."
"Natural rapport-builder with strong business acumen and executive presence: effective with AEs, executives, and technical stakeholders at every level."
Minimum Salary Range or On Target Earnings: "$146,000.00 Maximum $319,400.00 In addition to the base salary and/or OTE listed Zoom has a Total Direct Compensation philosophy that takes into consideration; base salary, bonus and equity value. Note: Starting pay will be based on a number of factors and commensurate with qualifications & experience. We also have a location based compensation structure; there may be a different range for candidates in this and other locations"
Benefits: "As part of our award-winning workplace culture and commitment to delivering happiness, our benefits program offers a variety of perks, benefits, and options to help employees maintain their physical, mental, emotional, and financial health; support work-life balance; and contribute to their community in meaningful ways. Click Learn for more information."
Ways of Working: "Our structured hybrid approach is centered around our offices and remote work environments. The work style of each role, Hybrid, Remote, or In-Person is indicated in the job description/posting."
About Us: "Zoomies help people stay connected so they can get more done together. We set out to build the best collaboration platform for the enterprise, and today help people communicate better with products like Zoom Contact Center, Zoom Phone, Zoom Events, Zoom Apps, Zoom Rooms, and Zoom Webinars. We’re problem-solvers, working at a fast pace to design solutions with our customers and users in mind. Find room to grow with opportunities to stretch your skills and advance your career in a collaborative, growth-focused environment."
Our Commitment: "At Zoom, we believe great work happens when people feel supported and empowered. We’re committed to fair hiring practices that ensure every candidate is evaluated based on skills, experience, and potential. If you require an accommodation during the hiring process, let us know—we’re here to support you at every step. If you need assistance navigating the interview process due to a medical disability, please submit an Accommodations Request Form and someone from our team will reach out soon. This form is solely for applicants who require an accommodation due to a qualifying medical disability. Non-accommodation-related requests, such as application follow-ups or technical issues, will not be addressed. Our interviews are supported by BrightHire, a tool that helps us create a consistent and thoughtful interview experience and may include recordings. Please refer to our candidate privacy statement for more information of how we use your data."
We need to remove boilerplate like EEO, legal, etc. The "Our Commitment" includes accommodation info; that's not boilerplate? It's about accommodations; maybe keep? It's not EEO but it's about accommodations. Might be okay to keep. However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Our Commitment" includes accommodation request; that's not EEO but it's about accommodations; could be considered part of EEO? Might be borderline. Safer to keep? The instruction says remove EEO/equal-opportunity boilerplate. The accommodation request is related to equal opportunity; might be considered EEO. I'd remove the entire "Our Commitment" section to be safe. Also remove "About Us"? That's not boilerplate; it's company description. Could keep. But the instruction says we should include sections only when posting has real, specific content. About Us is specific content; we could include as a section but not one of the prescribed headings. The prescribed headings list does not include About Us. We could either omit it or incorporate into About the role. Probably better to omit About Us and Our Commitment as they are not required headings and could be considered boilerplate-ish. The instruction: "Prefer a few substantive sections over many thin ones." So we can stick to the core sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Thus we will not include About Us or Our Commitment.
Now craft HTML.
We'll have:
About the role
What You Can Expect You will serve as the lead technical advocate for our customers, helping them understand and leverage Zoom's architectural advantages while partnering closely with our Upmarket Enterprise and Majors AE teams across the West. This is a role for a well-rounded, technically
About the role
with intro paragraph(s) from "What You Can Expect" and maybe "About The Team". Actually "About The Team" could be part of About the role. We'll combine.Responsibilities
with list from Responsibilities bullet points.Requirements
with "8+ years of solutions engineering experience supporting enterprise-level customers in technical pre-sales, with a strong understanding of the sales cycle and ability to drive urgency at the right moments."Qualifications
with "Strong working knowledge across the full UCaaS stack—SaaS collaboration, cloud voice, contact center, video, and unified communications—with ability to hit the ground running; generalist profile strongly preferred over narrow specialization."Skills
with "Highly proficient in presenting complex technical solutions, from traditional voice systems to modern cloud platforms, with hands-on familiarity with API integrations, networking protocols, security best practices, and cloud infrastructure (AWS, Azure, GCP). A genuine passion for AI: not just awareness of the trends, but real use cases, hands-on experience, and the ability to speak to its impact on the modern workforce with conviction. Natural rapport-builder with strong business acumen and executive presence: effective with AEs, executives, and technical stakeholders at every level."Benefits
with paragraph from Benefits section.Pay
with salary range paragraph.Schedule
with hybrid work description. We must not include any boilerplate like EEO, application instructions, etc. Also remove duplicated lines. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact text? Probably we can keep the substance but can rephrase slightly? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the information as is, maybe copy sentences. We can keep them as paragraphs or list items. We need to use- for any list of duties/requirements/benefits. So for Responsibilities we should make a list. For Requirements, Qualifications, Skills maybe also list if they are multiple items. But they are each a single paragraph with multiple clauses; could still be a list but not required. The instruction says use
- for any list of duties/requirements/benefits. If we have multiple items, we should list them. For Responsibilities we have multiple bullet points; we will make a list.
For Requirements, Qualifications, Skills each could be a single item list or just paragraph. Safer to make them as
maybe. But the instruction says use
- for any list of duties/requirements/benefits. If it's not a list, we can use
. We'll decide. Let's extract exact text: Intro: "What You Can Expect You will serve as the lead technical advocate for our customers, helping them understand and leverage Zoom's architectural advantages while partnering closely with our Upmarket Enterprise and Majors AE teams across the West. This is a role for a well-rounded, technically credible SE who brings broad knowledge across the full UCaaS stack, not just a single product line. This is a high-visibility, high-impact role supporting some of the most complex accounts in the country: enterprise-scale technology companies that demand sophisticated, multi-product solution design. This role is for a forward-thinking UCaaS generalist with a passion for technology, a customer-first mindset, and a genuine drive to deliver happiness through transformative AI solutions." About The Team: "Supporting Upmarket West accounts, our Solutions Engineering team acts as the strategic and technical backbone for complex enterprise deal cycles. We partner closely with Account Executives to architect full-platform solutions, articulate Zoom’s competitive advantages, and deliver happiness to our clients." We can combine. Responsibilities bullet points: - Partner closely with Enterprise and Majors AEs to drive technical sales engagements across the full Zoom platform—including Meetings, Phone, Contact Center, Rooms, and AI-powered solutions. - Lead technical discovery, solution design, custom demos, and proofs of concept (POCs) tailored to address complex enterprise collaboration challenges. - Serve as the primary technical advocate for our clients, translating customer requirements into product recommendations and driving feature requests internally with Product and Engineering. - Articulate Zoom’s architectural advantages, enterprise AI use cases, and broader vision to decision-makers ranging from technical practitioners to executive leadership. - Gather market intelligence and competitive insights from field engagements to help refine sales strategies and inform internal roadmaps. - Collaborate cross-functionally with AEs, product managers, and specialists to manage RFPs/RFQs, remove technical blockers, and accelerate deal cycles. What We're Looking For paragraphs: "8+ years of solutions engineering experience supporting enterprise-level customers in technical pre-sales, with a strong understanding of the sales cycle and ability to drive urgency at the right moments." "Strong working knowledge across the full UCaaS stack—SaaS collaboration, cloud voice, contact center, video, and unified communications—with ability to hit the ground running; generalist profile strongly preferred over narrow specialization." "Highly proficient in presenting complex technical solutions, from traditional voice systems to modern cloud platforms, with hands-on familiarity with API integrations, networking protocols, security best practices, and cloud infrastructure (AWS, Azure, GCP)." "A genuine passion for AI: not just awareness of the trends, but real use cases, hands-on experience, and the ability to speak to its impact on the modern workforce with conviction." "Natural rapport-builder with strong business acumen and executive presence: effective with AEs, executives, and technical stakeholders at every level." Minimum Salary Range or On Target Earnings: "$146,000.00 Maximum $319,400.00 In addition to the base salary and/or OTE listed Zoom has a Total Direct Compensation philosophy that takes into consideration; base salary, bonus and equity value. Note: Starting pay will be based on a number of factors and commensurate with qualifications & experience. We also have a location based compensation structure; there may be a different range for candidates in this and other locations" Benefits: "As part of our award-winning workplace culture and commitment to delivering happiness, our benefits program offers a variety of perks, benefits, and options to help employees maintain their physical, mental, emotional, and financial health; support work-life balance; and contribute to their community in meaningful ways. Click Learn for more information." Ways of Working: "Our structured hybrid approach is centered around our offices and remote work environments. The work style of each role, Hybrid, Remote, or In-Person is indicated in the job description/posting." About Us: "Zoomies help people stay connected so they can get more done together. We set out to build the best collaboration platform for the enterprise, and today help people communicate better with products like Zoom Contact Center, Zoom Phone, Zoom Events, Zoom Apps, Zoom Rooms, and Zoom Webinars. We’re problem-solvers, working at a fast pace to design solutions with our customers and users in mind. Find room to grow with opportunities to stretch your skills and advance your career in a collaborative, growth-focused environment." Our Commitment: "At Zoom, we believe great work happens when people feel supported and empowered. We’re committed to fair hiring practices that ensure every candidate is evaluated based on skills, experience, and potential. If you require an accommodation during the hiring process, let us know—we’re here to support you at every step. If you need assistance navigating the interview process due to a medical disability, please submit an Accommodations Request Form and someone from our team will reach out soon. This form is solely for applicants who require an accommodation due to a qualifying medical disability. Non-accommodation-related requests, such as application follow-ups or technical issues, will not be addressed. Our interviews are supported by BrightHire, a tool that helps us create a consistent and thoughtful interview experience and may include recordings. Please refer to our candidate privacy statement for more information of how we use your data." We need to remove boilerplate like EEO, legal, etc. The "Our Commitment" includes accommodation info; that's not boilerplate? It's about accommodations; maybe keep? It's not EEO but it's about accommodations. Might be okay to keep. However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Our Commitment" includes accommodation request; that's not EEO but it's about accommodations; could be considered part of EEO? Might be borderline. Safer to keep? The instruction says remove EEO/equal-opportunity boilerplate. The accommodation request is related to equal opportunity; might be considered EEO. I'd remove the entire "Our Commitment" section to be safe. Also remove "About Us"? That's not boilerplate; it's company description. Could keep. But the instruction says we should include sections only when posting has real, specific content. About Us is specific content; we could include as a section but not one of the prescribed headings. The prescribed headings list does not include About Us. We could either omit it or incorporate into About the role. Probably better to omit About Us and Our Commitment as they are not required headings and could be considered boilerplate-ish. The instruction: "Prefer a few substantive sections over many thin ones." So we can stick to the core sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Thus we will not include About Us or Our Commitment. Now craft HTML. We'll have:
About the role
What You Can Expect You will serve as the lead technical advocate for our customers, helping them understand and leverage Zoom's architectural advantages while partnering closely with our Upmarket Enterprise and Majors AE teams across the West. This is a role for a well-rounded, technically
- for any list of duties/requirements/benefits. If it's not a list, we can use
- for any list of duties/requirements/benefits. If we have multiple items, we should list them. For Responsibilities we have multiple bullet points; we will make a list.
For Requirements, Qualifications, Skills each could be a single item list or just paragraph. Safer to make them as