Bookings & Sales Manager, Los Angeles

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate. We need to parse the posting. Content: - Role: Bookings & Sales Manager, Lumos Experiences - Reports to: Head of Regional Events, South California - Contract Type: Full time (Hybrid role 3:2) - Location: The office is in South L.A Company Overview: paragraph. Role Overview: paragraph. What Success Looks Like: bullet? Actually paragraph. Key Responsibilities: list of bullet points (each with subheadings? Actually they have headings like Venue Sourcing & Outreach:, etc. We need to output as

• for any list of duties/requirements/benefits. So we need to convert each bullet into
• . The headings within bullet maybe part of text. We need sections: About the role (maybe combine Company Overview + Role Overview?), Responsibilities (Key Responsibilities), Requirements (maybe "Who We’re Looking For"), Qualifications (maybe not separate?), Skills (maybe part of Who We’re Looking For?), Benefits (What We Offer), Pay (maybe not explicit? They say "A competitive salary with flexibility based on your experience and skills." That's pay info. So we can include Pay section with that sentence. Schedule: they mention hybrid role 3:2, flexible hybrid-working policy 3 days in office and 2 at home. That's schedule info. We must not create sections with filler like "commensurate with experience". The pay sentence is specific enough: "A competitive salary with flexibility based on your experience and skills." That's okay. Schedule: "Full time (Hybrid role 3:2)" and "flexible hybrid-working policy 3 days in the office and 2 at home". That's schedule. Benefits: list of benefits. We need to avoid duplication. Let's extract sections: About the role: Could combine Company Overview and Role Overview and What Success Looks Like? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include. We have content for: - About the role: Could be Company Overview + Role Overview + What Success Looks Like. That's substantive. - Responsibilities: Key Responsibilities. - Requirements: Who We’re Looking For (list of attributes). Could be Requirements. - Qualifications: maybe not separate; but we could treat "Experience in venue sourcing, bookings, events or partnerships is strongly preferred" as qualification. But we can also include under Requirements. Since we prefer few substantive sections, we could combine Requirements and Qualifications into one? But instruction says use headings for those categories if content exists. We have content for Requirements (Who We’re Looking For). Qualifications maybe not distinct; we could omit Qualifications heading if no specific content beyond what's in Requirements. Similarly Skills maybe part of Who We’re Looking For. But we could still include Skills if we have explicit skills list: "Excellent negotiation and interpersonal skills", "Comfortable with Google Suite and team collaboration tools", "Process-driven with strong administrative skills". Those are skills. Could make Skills section. But we need to avoid thin sections. Let's see: we have enough for Skills. Pay: we have sentence. Schedule: we have hybrid info. Benefits: we have list. Thus we can include sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Possibly Qualifications omitted. Now we need to format. About the role: combine Company Overview paragraph, Role Overview paragraph, What Success Looks Like paragraph. Ensure we preserve all info. Let's extract exact text: Company Overview: "Curate Group is a dynamic events and experiences company, creating unforgettable moments that bring people together. We specialise in unique, high-quality live events - from large scale festivals, immersive concerts, cultural experiences and corporate events partnering with some of the world’s most exciting brands. One of our core event brands, Lumos Experiences, is one of the most distinctive live entertainment concepts, creating atmospheric candlelit concerts that transform unexpected spaces into something genuinely magical. We're growing fast, running multiple shows per week across new cities and countries and we're looking for a highly motivated Bookings & Sales Manager to drive our venue expansion strategy and support the continued growth of Lumos across the region of South California." Role Overview: "As a Bookings & Sales Manager, you will own our event pipeline from end to end, sourcing and securing high-quality venues across the South California region, managing the full bookings process and ensuring each confirmed show is seamlessly handed over to the teams responsible for delivery. This is a high-output, process-driven role that rewards people who are organised, proactive and take real pride in accuracy. If you're someone who enjoys owning a system, hitting targets and building relationships and seeing your work come to life, you'll thrive in this role." What Success Looks Like: "Success in this role will be measured by venue acquisition, confirmed bookings, show sell-through performance, pipeline health, and accuracy of internal records." We can combine into About the role section with paragraphs. Now Responsibilities: list each bullet. Key Responsibilities bullet points: - Venue Sourcing & Outreach: Deliver high-volume, targeted outreach using our approved Target Location Hit List, prioritising venues that meet our brand and commercial criteria. Use approved AI tools, templates and brand assets to generate interest and secure responses efficiently. - Bookings & Calendar Management: Secure venues and schedule shows in line with monthly targets. Maintain an accurate bookings calendar, ensure all shows go on sale within required lead times and keep master location records complete and up to date. - Promotion: Grow organic promotion to reduce reliance on paid advertisement. - Confirmation & Processing: Ensure every booking is fully confirmed, documented and financially processed on time, with event pages created accurately across ticketing and social platforms. - Venue Coordination: Liaise with venues to ensure co-hosting and visibility requirements are met, maintaining a strong working relationship from booking through to show day. - Internal Handover: Provide timely, accurate handover of all booking details to musicians, staffing, content and ads teams with clean internal records that require minimal follow-up. - Reporting & Pipeline Visibility: Provide regular, clear updates on booking progress, pipeline health and upcoming targets to the wider team. We need to output each as

  . The heading within each bullet (e.g., "Venue Sourcing & Outreach:") can be part of the li text. Now Requirements: "Who We’re Looking For" bullet list: - Highly organised, detail-oriented and reliable, taking real ownership of your systems and deadlines - A natural self-starter who builds momentum and doesn't need to be chased - Confident communicating with venues and external stakeholders, naturally building rapport with local venues potentially unfamiliar with Lumos scale - Process-driven with strong administrative skills and the ability to manage multiple bookings simultaneously - Experience in venue sourcing, bookings, events or partnerships is strongly preferred - Excellent negotiation and interpersonal skills - Comfortable with Google Suite and team collaboration tools - Flexibility to travel to and attend shows as needed We can output as

  • . Now Skills: maybe we can extract skills from the above: "Excellent negotiation and interpersonal skills", "Comfortable with Google Suite and team collaboration tools", "Process-driven with strong administrative skills". Also "Highly organised, detail-oriented and reliable" etc. But to avoid duplication, we could make Skills section separate from Requirements. However the instruction: prefer a few substantive sections over many thin ones. If we split Requirements and Skills, we might have thin sections. Better to combine Requirements and Skills into one section called Requirements (or Skills). But we already have Requirements heading. Could we rename Requirements to "Requirements & Skills"? Not allowed; headings must be from list. But we could include both Requirements and Skills sections if they have substantive content. Let's see if Skills section would be thin: we could list skills: "Excellent negotiation and interpersonal skills", "Comfortable with Google Suite and team collaboration tools", "Process-driven with strong administrative skills", "Highly organised, detail-oriented and reliable", "Natural self-starter", "Confident communicator", "Flexibility to travel". That's many items, not thin. So we could have Skills section separate from Requirements (which could focus on experience/qualifications). But Requirements currently includes experience and some attributes. Could split: Requirements: "Experience in venue sourcing, bookings, events or partnerships is strongly preferred". Skills: list of soft skills and technical skills. However the instruction says prefer few substantive sections over many thin ones. Having both may be okay if each is substantive. Let's decide: We'll have Requirements (experience) and Skills (attributes). But we need to ensure we don't duplicate content. Extract experience line: "Experience in venue sourcing, bookings, events or partnerships is strongly preferred". That's the only explicit qualification/experience line. Skills: the rest: Highly organised, detail-oriented and reliable, taking real ownership of your systems and deadlines; A natural self-starter who builds momentum and doesn't need to be chased; Confident communicating with venues and external stakeholders, naturally building rapport with local venues potentially unfamiliar with Lumos scale; Process-driven with strong administrative skills and the ability to manage multiple bookings simultaneously; Excellent negotiation and interpersonal skills; Comfortable with Google Suite and team collaboration tools; Flexibility to travel to and attend shows as needed. That's substantive. Now Benefits: list from "What We Offer": - A competitive salary with flexibility based on your experience and skills. (but we will move salary to Pay section; maybe we keep salary in Benefits? Better to move to Pay.) - Access to our discretionary annual bonus based on performance - Covered travel expenses to shows - 11 days PTO plus federal holidays and extra days off at Christmas - An extra day of annual leave gifted for each year of service (up to an additional 3 days) - Your Birthday off - Health insurance - 401k - Maternity and paternity leave policy - A flexible hybrid-working policy 3 days in the office and 2 at home - Significant opportunities for personal growth and career progression as the business scales - Complimentary access to our full range of events and concerts for family and friends We need to separate Pay and Schedule. Pay: "A competitive salary with flexibility based on your experience and skills." plus maybe "Access to our discretionary annual bonus based on performance" could be considered bonus, but that's part of benefits. We'll keep bonus in Benefits. Schedule: "Full time (Hybrid role 3:2)" and "A flexible hybrid-working policy 3 days in the office and 2 at home". Also maybe "flexibility to travel to and attend shows as needed" is not schedule but requirement. Thus Schedule section: combine those two statements. Now Benefits section: all other benefits except salary and hybrid policy. Let's list benefits: - Access to our discretionary annual bonus based on performance - Covered travel expenses to shows - 11 days PTO plus federal holidays and extra days off at Christmas - An extra day of annual leave gifted for each year of service (up to an additional 3 days) - Your Birthday off - Health insurance - 401k - Maternity and paternity leave policy - Significant opportunities for personal growth and career progression as the business scales - Complimentary access to our full range of events and concerts for family and friends Now we need to output HTML with

    headings and

    for prose,

    • for lists. We must not include any extra text like markdown. Let's craft. First, About the role: combine three paragraphs into maybe two

      elements? Could be one

      containing all? Better to separate paragraphs for readability but still valid. We'll output

      for each paragraph. Paragraph1: Company Overview. Paragraph2: Role Overview. Paragraph3: What Success Looks Like. Now Responsibilities: