Customer Success Manager

under Pay section. Schedule: hybrid role in NYC office. We'll put that as

under Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, equal opportunity, scam warning, etc. Also remove navigation/cookie/legal. The posting includes EEO statement at end; we must remove that. Also remove "Visa sponsorship for this role is currently not available." That's not a benefit but maybe we keep as note? It's not needed? It's not a benefit; maybe we can drop as it's not substantive? It's a detail about visa sponsorship; could be considered relevant but not a benefit. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Visa sponsorship is not exactly those; but it's a detail about eligibility. Might keep? However it's not a benefit; could be placed under Requirements? Not really. Might be okay to keep as a short p under a generic "Notes" but we don't have a section for that. Safer to drop it as it's not explicitly requested. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Visa sponsorship is substantive. But we have no section for it; we could include it under Benefits? Not appropriate. Could add a

after Benefits maybe as a note. But we must only include sections when posting has real, specific content for it. We could add a section "Additional Information" but not in allowed headings list. The allowed headings are only those listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We shouldn't add other headings. So we need to fit visa sponsorship somewhere else, maybe under Benefits as a note? But it's not a benefit. Could be under Requirements? Not appropriate. Could be under About the role? Not appropriate. Maybe we can treat visa sponsorship as part of "Benefits" as a negative? Not ideal. However the instruction says preserve ALL substantive information; we cannot drop it. So we need to include it somewhere within allowed sections. Perhaps we can include it in the Benefits section as a bullet point: "Visa sponsorship for this role is currently not available." That is a statement about sponsorship, not a benefit but still a detail about the offer. It's okay to include there. Similarly, the EEO statement must be removed as boilerplate. Now, we need to avoid filler like "commensurate with experience", "not specified", etc. Not present. Now construct HTML. We'll have:

About the role

At monday.com, we help teams get more work done. We are the best AI work platform that empowers teams to automate, build, and scale their impact end-to-end with tools that actually execute the work for you. With over $1B in ARR, 250,000+ customers, and a global team, we’re serious about building a product people love to use and giving our employees the same ownership and flexibility to shape the way the world works. The Customer Success Team is the trusted advisor for building relationships, driving product adoption, and empowering teams to fulfill their goals. By being experts of the monday.com platform, we are able to provide a unique level of consultation and inspiration to our customers. We are an energetic, empathetic and passionate team that enjoys collaboration, taking on new challenges, and “failing forward” together in this dynamic environment. Please note this is a hybrid role in our New York City office.

for section headings (e.g. About the role, Responsibilities...). The posting already has a heading "About the role:" in the text. So we should treat that as the About the role section content. The content after that heading includes the role description (starting with "As a Technical CSM, you’ll go beyond just managing accounts..."). So we should put that as About the role content. The earlier introductory paragraphs about monday.com and Customer Success Team could be considered general company description; maybe we could put them under About the role as well? But the heading "About the role:" appears after that intro. So likely the About the role section should be the content after that heading. The earlier paragraphs could be considered company overview; but we have no section for company overview. We could include them in About the role as well, but that would duplicate heading? Not duplicate; we just have one About the role section. We could include all content before the responsibilities list as About the role prose. That includes the intro about monday.com, Customer Success Team, and then the role description sentences. However the role description includes bullet-like responsibilities; we need to separate those into list items under Responsibilities. So we need to parse: After "About the role:" we have: "As a Technical CSM, you’ll go beyond just managing accounts, and become the architect of digital evolution. You will bridge the gap between business goals and technical execution, acting as a strategic consultant for our most ambitious B2B clients. Your core mission is to move customers beyond "tool adoption" and into "business transformation" by consulting on how to power mission critical workflows with monday.com’s AI platform." Then a list of responsibilities each starting with bolded phrase. So we can treat the first three sentences as prose in About the role, and the bullet list as Responsibilities. Thus About the role section will contain those three sentences as

. Now Responsibilities section will contain the bullet list items. Now Requirements section will contain list. Now Benefits section will contain list. Now Pay section will contain prose. Now Schedule section will contain hybrid note. Now we need to ensure we don't include any boilerplate like EEO etc. Let's extract details. First, get the intro before "About the role:": "At monday.com, we help teams get more work done. We are the best AI work platform that empowers teams to automate, build, and scale their impact end-to-end with tools that actually execute the work for you. With over $1B in ARR, 250,000+ customers, and a global team, we’re serious about building a product people love to use and giving our employees the same ownership and flexibility to shape the way the world works. The Customer Success Team is the trusted advisor for building relationships, driving product adoption, and empowering teams to fulfill their goals. By being experts of the monday.com platform, we are able to provide a unique level of consultation and inspiration to our customers. We are an energetic, empathetic and passionate team that enjoys collaboration, taking on new challenges, and “failing forward” together in this dynamic environment." We could keep that as About the role prose, but note that the heading "About the role:" already indicates that the following is about the role. However the instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid having extra prose before the list. So we can include that as About the role content. Now after "About the role:" we have: "As a Technical CSM, you’ll go beyond just managing accounts, and become the architect of digital evolution. You will bridge the gap between business goals and technical execution, acting as a strategic consultant for our most ambitious B2B clients. Your core mission is to move customers beyond "tool adoption" and into "business transformation" by consulting on how to power mission critical workflows with monday.com’s AI platform." Then the list: - Champion AI-Led Transformation: Act as the primary advisor on how clients can leverage our AI suite to automate manual workflows, generate insights, and scale their internal operations. - AI Consulting: Develop a deep sense of client trust and problem-solving first through technical aptitude and thorough, in-and-out knowledge of monday’s platform, reducing the barrier and uncertainty about how AI can exponentially improve the client’s ability to achieve their designated outcomes. - Strategic Architecture: Empower customers to connect complex business challenges with sophisticated, automated solutions within the platform. - Drive Organizational Change: Navigate client organizations to uncover high-impact opportunities for digital transformation and AI adoption. - Data-Driven Growth: Leverage behavioral data and product usage insights to develop communication strategies that drive expansion and technical maturity at scale. - High-Level Technical Enablement: Lead deep-dive consultations and technical workshops that move beyond "how-to" and focus on "how-to-scale." - Voice of the Future: Represent the technical voice of the customer to our Product and Engineering teams, influencing the roadmap for AI and integration features. - Cross-Functional Partnership: Collaborate with Consulting and Product teams to identify upsell and expansion opportunities rooted in technical solutioning. Now Requirements: "Requirements: 3+ years of experience in B2B SaaS Customer Success, Technical Account Management, or Implementation Consulting. Technical Literacy: You understand how APIs work, how data flows between systems, and how to troubleshoot integration logic. AI Curiosity: A deep interest in the generative AI landscape and a proven ability to translate AI capabilities into tangible business value. Change Management DNA: Experience guiding large organizations through software transitions or process overhauls (Transformation Management). Executive Presence: Superb communication skills with the ability to establish technical credibility with stakeholders and C-suite executives. Analytical Mindset: You enjoy using data to segment business books and identify the next "big win" for your clients. Adaptability: A positive, high-energy attitude with the ability to thrive in a fast-paced, evolving technical environment. Bonus: Prior experience in strategy consulting or a background in business process mapping." We'll list each as

. The "Bonus:" line could be a separate bullet