Campaign Operations Manager - Temporary with Potential for Full-Time

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Plum", "The Opportunity", "What You'll Own", "Requirements", "Benefits". Also maybe "Temporary-to-Full-Time Opportunity". We need to use

for section headings. Do not repeat job title. No Job ID. Remove boilerplate. Keep all substantive info. We need to decide which sections to include based on content. The posting has: - About Plum (description of company) - The Opportunity (role description) - What You'll Own (detailed responsibilities) - Requirements (required and nice to have) - Benefits (benefits and pay) - Temporary-to-Full-Time Opportunity (maybe part of About? Could be its own section but it's somewhat redundant with description; but it's substantive. Could be included as a section maybe "Temporary-to-Full-Time Opportunity". However we need to avoid thin sections. It's a paragraph about temporary role potential conversion. Could be included under "About the role" or "The Opportunity". But we have "The Opportunity" already. Could merge that paragraph into The Opportunity section. However we must preserve all substantive info; we can keep it within that section. We need to use

• for any list of duties/requirements/benefits. So for responsibilities we should list bullet points. For requirements we should list bullet points. For benefits we should list bullet points. We need to use

  for prose. We must not include sections with filler like "Pay, Schedule" unless present. Pay is present: "Hourly rate is $40 - $48." Also mention compensation and bonus potential. So we can include a Pay section. Schedule not mentioned. Benefits section includes health, dental, vision, 401k, holidays, vacation, equity, etc. We need to ensure we don't create sections with no content. Thus sections: - About Plum (maybe "About the company" but heading should be like "About the role"? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings as long as they are appropriate. Probably we should use "About the role" for description of role and company? But they said "About the role" as example. However we have "About Plum" describing company. Could use "About the role" to include both company and role overview. But we also have "What You'll Own" which is responsibilities. So maybe we use "About the role" for company overview and opportunity description. Then "Responsibilities" for what you'll own. Then "Requirements" for required/nice-to-have. Then "Benefits" for benefits and pay. Could also add "Pay" separate if we want but we can include pay inside Benefits. However they said prefer few substantive sections over many thin ones. So we can combine Pay and Benefits into one Benefits section that includes pay details. Thus sections:

  About the role

  with paragraphs about Plum and the opportunity.

  Responsibilities

  with
  • list of duties from "What You'll Own".

    Requirements

    with
    • list of required and nice-to-have.

      Benefits

      with

      prose about benefits and pay. We need to ensure we don't repeat job title. No metadata. We need to strip boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to preserve all substantive info: need to include details like "temporary role with potential to transition into full-time", "hands-on experience with Instantly and SmartReach required", etc. Let's extract. About Plum paragraph: "Plum AI is an AI-powered technology company helping lenders identify opportunities, re-engage relationships, and create new pipeline through highly personalized outreach. Built by lenders for lenders, Plum combines AI, data, automation, and managed campaign execution to help financial institutions turn their existing data and new market opportunities into meaningful conversations. Our campaigns are not traditional mass email marketing. Plum uses AI and prospect-level data to create personalized, one-to-one outreach while leveraging specialized sending infrastructure and campaign technology to protect customer domains and maximize deliverability." The Opportunity: "Plum is seeking an experienced Campaign Operations Manager to join our team in a temporary role with the potential to transition into a full-time position. We need someone who can step in quickly and take hands-on ownership of campaign execution. This is not primarily a strategy or content-marketing position. You will be actively working inside Instantly and SmartReach, setting up campaigns, managing sending accounts, loading and validating contact data, monitoring deliverability, troubleshooting issues, and ensuring campaigns launch and run successfully. Because this role is designed to provide immediate operational support, prior hands-on experience with both Instantly and SmartReach is required. We are looking for someone who understands outbound campaign operations and can become productive quickly with minimal platform training. For the right person, this temporary assignment has the potential to develop into a permanent role as Plum continues to scale its campaign operations." We can combine these into About the role section. Responsibilities: list from "What You'll Own". Let's extract bullet points: - Campaign Setup & Execution - Build, configure, launch, and manage customer campaigns in Instantly and SmartReach - Manage multiple customer campaigns, sending accounts, inboxes, and sequences simultaneously - Upload, map, validate, and QA prospect lists before campaigns go live - Configure sending schedules, daily limits, inbox rotation, reply routing, sequences, and campaign settings - Manage campaigns targeting both existing customer relationships for reactivation and newly sourced prospects - Perform thorough pre-launch QA to ensure the correct audience, messaging, sending accounts, exclusions, and settings are in place - Maintain campaign calendars and keep launches moving against committed timelines - Email Infrastructure & Deliverability - Manage lookalike sending accounts and domains used to protect customers' primary email domains - Coordinate and monitor inbox warm-up before campaign launch - Manage appropriate sending ramp-up and daily sending volumes - Monitor sender reputation, bounce rates, spam signals, unsubscribes, and other deliverability indicators - Troubleshoot sending-account connections, reply routing, campaign configuration, and other platform issues - Work comfortably with Microsoft 365 and Google Workspace sending environments - Identify potential deliverability problems early and take or recommend corrective action - Contact & Data Management - Work with Plum's Data Science and Account Management teams to prepare campaign audiences - Validate contact files and identify duplicates, missing information, malformed records, or other data-quality issues - Properly manage existing contacts, newly sourced prospects, exclusion lists, blacklists, and suppression lists - Ensure contacts are assigned to the appropriate loan originator, salesperson, territory, sending account, and campaign - Coordinate contact enrichment and data corrections as needed - Maintain strong data hygiene throughout campaign execution - Personalization & Messaging QA - Translate approved customer messaging into executable campaign sequences - QA AI-generated and personalized outreach to ensure messages sound natural and appropriate for the individual recipient - Validate personalization fields, variables, and prospect-specific content before launch - Recognize messaging that could appear generic, automated, repetitive, or inappropriate given an existing customer relationship - Ensure follow-up sequences maintain the feel of genuine one-to-one communication - Campaign Monitoring & Optimization - Monitor active campaigns daily - Track sending activity, delivery, replies, meaningful responses, positive responses, bounces, unsubscribes, and other campaign indicators - Identify abnormal campaign behavior or performance trends and escalate issues quickly - Pause or adjust campaigns when deliverability, data quality, messaging, or customer concerns require intervention - Optimize sending volumes, sequencing, timing, and configuration based on campaign performance - Ensure customer replies are routed correctly to the appropriate real inbox or team member - Help distinguish meaningful business responses from automated replies, out-of-office messages, unsubscribes, and other non-actionable responses - Reporting & Customer Success Support - Provide Account Managers with accurate, timely campaign status and performance information - Maintain clear reporting on contacts loaded, contacts reached, sending volume, replies, meaningful responses, and other agreed-upon KPIs - Proactively surface campaign risks, delays, dependencies, and blockers - Document campaign setup, changes, issues, and resolutions - Support campaign performance reviews and identify opportunities for improvement - Partner closely with Account Management to ensure execution aligns with customer expectations and commitments We could group these under a single

      but maybe better to keep headings inside? The instruction: use
      • for any list of duties/requirements/benefits. It didn't forbid headings inside list. But we could just make a flat list of all responsibilities. However that would be long but okay. But we could also keep subheadings as

        or

        but they said only use

        for section headings. So we shouldn't use other headings. We could keep responsibility sections as paragraphs with bold? Not allowed? They didn't forbid . But safer to just make a flat list. Thus

        • each duty. Similarly for Requirements: list required and nice-to-have. Required / Strongly Preferred: - Hands-on experience managing outbound email campaigns - Direct experience with Instantly and SmartReach required - Strong understanding of email deliverability, domain reputation, inbox warm-up, sending limits, bounce management, and sender health - Experience managing multiple sending accounts and inboxes - Experience importing and managing large prospect/contact lists - Strong Excel/CSV skills, including filtering, validation, deduplication, and field mapping - Ability to troubleshoot campaign-platform and email-account configuration issues independently - Exceptional attention to detail and strong QA habits - Ability to manage multiple customers, campaigns, and deadlines simultaneously - Strong written communication skills and good judgment around outbound messaging Nice to Have: - Experience in financial services, commercial lending, commercial real estate, mortgage, banking, or B2B fintech - Experience with Salesforce, HubSpot, or Microsoft Dynamics 365 - Experience with CRM-integrated outreach - Experience with AI-generated or highly personalized outbound messaging - Experience working in a managed-service environment - Understanding of contact enrichment, segmentation, suppression lists, and CRM data hygiene We can combine required and nice-to-have in one list, maybe differentiate with a note? Could keep as separate

          preceding list? But we need to use

          • for any list. Could have two lists: one for Required, one for Nice to Have, each preceded by a

            heading? But headings only

            . Could use

            Required:

            then

            . That's okay. Benefits: include: - A fast-paced, collaborative startup culture with high visibility - Autonomy, flexibility, and a flat corporate structure that gives you the opportunity for your direct input to be realized and put into action. - Opportunity to make a meaningful impact in building a company and culture. - Equity in a financial technology startup. - Generous health, dental, and vision coverage for employees and family members + 401(k) - Eleven paid holidays and unlimited discretionary vacation days - Competitive compensation and bonus potential - Hourly rate is $40 - $48. The range displayed on each job posting reflects the minimum and maximum target for new hire salaries. Within the range, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education or training. Also mention "Temporary-to-Full-Time Opportunity" maybe as part of About the role. We need to ensure we don't include filler like "commensurate with experience". Not present. Now produce HTML fragment. We'll start with

            About the role