Customer Success Lead

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes "About The Role" (which is essentially description). Then "What You Will Build At Zip Security" (responsibilities). Then "What We’re Looking For" (requirements/qualifications/skills). Then "Who You’ll Work With" (maybe not needed). Then "What we offer" (benefits). No explicit Pay or Schedule specifics; they mention "Competitive compensation, equity, and comprehensive health benefits starting on day one 401(k) plan ... Flexible hybrid work environment (2-3 days in office! You decide what is best for you!) Monthly wellness benefits ... Comprehensive family-building, fertility, and hormonal health benefits ... High ownership, autonomy ... Fully stocked office ...". So we have benefits details. No explicit pay numbers, so we should not create Pay section. Schedule: they mention flexible hybrid work environment (2-3 days in office). That's schedule info. So we can include Schedule section with that detail. Also maybe include "About the role" section: we have "About The Role" paragraph. Should we include that as a section? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role heading. Then Responsibilities heading (from "What You Will Build At Zip Security"). Then Requirements/Qualifications/Skills maybe combined? The posting has "What We’re Looking For" which includes experience, technical aptitude, project-management, track record, etc. Could split into Requirements (experience), Qualifications (maybe same), Skills (technical aptitude). But we should avoid thin sections. Perhaps combine into one Requirements section that includes experience, technical aptitude, project-management, etc. Or we could have Requirements and Skills separate if content distinct. Let's see: The list includes: - 5+ years of experience in Customer Success, implementation, customer experience, or another highly customer-facing role at a B2B technology company. - Experience owning complex customer implementations where success requires driving customer action, coordinating multiple stakeholders, and keeping projects moving — not simply configuring a product. - Strong technical aptitude and the ability to quickly become credible with customers on topics such as device management, identity, endpoint security, email security, SSO, and integrations. - Exceptional project-management skills with the ability to manage multiple customer deployments simultaneously, identify blockers early, and proactively drive customers toward action. - A track record of building strong customer relationships while being comfortable pushing customers when necessary to keep implementations and adoption on track. - Experience building playbooks, processes, and programs from scratch rather than only operating within an established Customer Success organization. - Strong judgment around whether a recurring customer problem should be solved through service, process, documentation, automation, or improvements to the product. - Comfort working directly with Product and Engineering on technical customer problems and translating customer feedback into clear, actionable insights. These could be considered Requirements (experience) and Skills (technical aptitude, project-management, judgment, comfort). Qualifications maybe similar. To avoid many thin sections, we could have a single "Requirements" section that includes all bullet points. Or we could have "Requirements" for experience, "Skills" for technical aptitude etc. But the instruction: Prefer a few substantive sections over many thin ones. So better to have one Requirements section covering all. Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule. We must not repeat job title as heading. Not include Job ID etc. We must preserve all substantive information. Need to include details from "About Zip Security" maybe? That's company overview; could be part of About the role? The instruction: About the role section heading for e.g. About the role. The posting includes an "About Zip Security" paragraph before About The Role. Should we include that? It's not about the role but company overview. The instruction says use headings for section headings (e.g. About the role, Responsibilities...). It doesn't forbid adding other sections like "About the company". But they gave examples; we should stick to those headings. However we need to preserve ALL substantive information; we cannot omit company overview. Could we include it within About the role section as a preamble? The About the role section could include both company overview and role description. That would preserve info. So we can put the company overview paragraph(s) inside the About the role section. Thus:

About the role

Zip Security Cybersecurity for growing businesses is broken — even enterprises spend heavily across hundreds of disconnected tools for marginal real-world benefit. For startups and mid-sized firms, this gap often means forgoing security entirely, or cobbling together a solution that leaves them vulnerable in other ways. At Zip Security, we build solutions that make enterprise cybersecurity effective and doable for growing businesses of all kinds, whether or not they have a security team in house. Our product is a complete security program that automates device management, endpoint security, identity and access management, compliance, and managed IT and security operations to keep teams of all kinds protected. We help our customers pick their right security frameworks, correctly deploy the tools, policies, and controls they need, and keep everything enforced over time, so their business is protected and compliant, 24/7. Zip is at the cutting edge of what’s possible in cybersecurity, and dedicated to delivering value for our customers. It’s a big part of why we’re backed by Ballistic Ventures. Major platforms are opening APIs that enable automated management at scale, new government initiatives are surfacing global threat data, and we're positioned to be the first to properly integrate all of it. We're looking for driven, talented people to help us get there. If this resonates with you, we invite you to consider building alongside our team.

About The Role We’re looking for our first dedicated Customer Success Lead to own the customer experience from Closed Won through successful deployment and ongoing adoption. This is a hands-on, high-ownership role. You’ll work directly with customers to get them live on Zip, make sure they’re continuously getting value from the platform, and proactively step in when adoption stalls. At the same time, you’ll build the playbooks, metrics, processes, and programs that become the foundation of Customer Success at Zip. You’ll work closely across Sales, Account Management, Provisioning, Product, and Engineering. As our customer base grows, you’ll have the opportunity to help shape and eventually build the broader Customer Success function.

But we might duplicate "About The Role" heading inside; we already have heading. Could combine. Better: After heading, include the company overview paragraph then the role description paragraph. Now Responsibilities: from "What You Will Build At Zip Security". We'll list bullet points. Responsibilities section:

Responsibilities

• Own customer onboarding and deployment from Closed Won to successful adoption.
• Drive customers through required setup, coordinate closely with our Provisioning team, guide integrations such as SSO and device management, and ensure customers consistently reach 80%+ device enrollment.
• Drive ongoing adoption and customer value. Monitor customer health, proactively identify accounts that are stalled or underutilizing Zip, help customers adopt new products and features, and provide technical enablement when additional guidance is needed.
• Build a repeatable customer lifecycle. Define clear milestones, owners, handoffs, and success metrics across onboarding, deployment, adoption, and ongoing engagement so no customer gets stuck because ownership is unclear.
• Create the operating system for Customer Success. Establish metrics around deployment, adoption, customer health, retention, and expansion, and build the playbooks and processes needed to manage a growing customer base.
• Turn recurring customer needs into scalable solutions. Build customer-facing documentation, education, communications, and enablement programs while identifying when recurring problems should be solved through better process, automation, service, or product.
• Be the voice of the customer internally. Partner closely with Product and Engineering to deliver structured, high-quality feedback and help the team understand where customers are succeeding, struggling, or finding opportunities for additional value.
• Help build the future Customer Success team. As Zip grows, help define the structure of the function and hire, onboard, and develop future Customer Success team members.

Now Requirements: combine all bullet points from "What We’re Looking For". Also maybe include "Who You’ll Work With" as not needed. Requirements section:

Requirements

• 5+ years of experience in Customer Success, implementation, customer experience, or another highly customer-facing role at a B2B technology company.
• Experience owning complex customer implementations where success requires driving customer action, coordinating multiple stakeholders, and keeping projects moving — not simply configuring a product.
• Strong technical aptitude and the ability to quickly become credible with customers on topics such as device management, identity, endpoint security, email security, SSO, and integrations.
• Exceptional project-management skills with the ability to manage multiple customer deployments simultaneously, identify blockers early, and proactively drive customers toward action.
• A track record of building strong customer relationships while being comfortable pushing customers when necessary to keep implementations and adoption on track.
• Experience building playbooks, processes, and programs from scratch rather than only operating within an established Customer Success organization.
• Strong judgment around whether a recurring customer problem should be solved through service, process, documentation, automation, or improvements to the product.
• Comfort working directly with Product and Engineering on technical customer problems and translating customer feedback into clear, actionable insights.

Now Benefits: from "What we offer". Need to list bullet points. Benefits section:

Benefits

• Competitive compensation, equity, and comprehensive health benefits starting on day one
• 401(k) plan to help you invest in your future
• Flexible hybrid work environment (2-3 days in office! You decide what is best for you!)
• Monthly wellness benefits to help you stay active, healthy, and balanced in whatever way works best for you
• Comprehensive family-building, fertility, and hormonal health benefits to support you through every stage of life
• High ownership, autonomy, and the opportunity to shape a rapidly growing company
• Fully stocked office with endless snacks, coffee, and tea, plus Zip swag and team outings

Now Schedule: we have flexible hybrid work environment already in benefits; but schedule could be separate: "Flexible hybrid work environment (2-3 days in office! You decide what is best for you!)". Since it's already in benefits, we could still make a Schedule section with that detail. However we risk duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put schedule info only in Benefits, it's still preserved. But they asked to include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can have Schedule section with that specific content. But we already have that content in Benefits; duplication might be okay but maybe better to avoid duplication. However we could move that bullet from Benefits to Schedule and keep Benefits without that bullet. Let's see: Benefits list includes many items; we could keep the flexible hybrid work environment under Schedule instead. That would avoid duplication. Let's do that. Thus Benefits section excludes the flexible hybrid work environment bullet. Schedule section includes that bullet. Now Benefits list: - Competitive compensation, equity, and comprehensive health benefits starting on day one - 401(k) plan to help you invest in your future - Monthly wellness benefits to help you stay active, healthy, and balanced in whatever way works best for you - Comprehensive family-building, fertility, and hormonal health benefits to support you through every stage of life - High ownership, autonomy