Content & Community Marketing Specialist

We need to output HTML fragment with sections: About the role? Actually the posting includes "About SwipeSimple" then "The role", "What You Will Own", "The team", "What You Bring", "Helpful But Not Required", "How To Apply", "Why You’ll Love Being Part of the Team". We need to reformat into clean semantic HTML using

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. The posting includes: - About SwipeSimple (company description) - The role (description of role) - What You Will Own (breakdown of responsibilities with percentages) - The team (reporting line) - What You Bring (requirements) - Helpful But Not Required (nice-to-have) - How To Apply (application instructions) - we need to remove application instructions per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should drop the How To Apply section. - Why You’ll Love Being Part of the Team (benefits, perks, compensation) - includes US location-neutral work environment, home-office equipment stipend, flexible PTO, employee engagement, learning & development, comprehensive health benefits, competitive compensation including salary range, bonus, stock options, remote flexibility. We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can use other headings if they match content? The instruction says: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive; we can use those headings as appropriate. Probably we should use those headings for sections we have. We have: - About SwipeSimple (company overview) could be "About the role"? Actually "About the role" is about the role description, not company. But we have a section "The role" describing what you own. That could be "About the role". Then "What You Will Own" is responsibilities (list). Could be "Responsibilities". Then "The team" maybe "Team" but not in list; maybe we can incorporate into responsibilities or omit? The instruction says prefer a few substantive sections over many thin ones. We could combine team into responsibilities or omit if not needed. But we need to preserve all substantive information; we can't drop team info. Could include under "About the role" or "Responsibilities". Perhaps we can add a section "Team" but not in the examples; but instruction says use those examples but not limited? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples; we could still use other headings if needed, but better to stick to those. We could map team info under "About the role" or "Responsibilities". The team describes reporting line and support; could be part of "About the role". We'll incorporate. "What You Bring" is requirements/qualifications/skills. Could be "Requirements" and "Qualifications" and "Skills". We have three or more years running social and content for a B2B company selling to SMBs (requirement), published work you can show us (qualification), experience running more than one social account for more than one audience (skill), willingness to reach out cold (skill/experience), experience writing for small business owners in a trade or service industry (skill/qualification), you catch the doubled word and the broken link before anyone else does (skill). Also helpful but not required: experience in payments, fintech, video production, sourcing customer stories, familiarity with reseller or channel go-to-market models. We could have sections: Requirements (mandatory), Qualifications (maybe overlapping), Skills (maybe overlapping). But to avoid thin sections, we could combine into one "Requirements & Skills" section with bullet list. However instruction says prefer a few substantive sections over many thin ones. So we could have one section "Requirements" that includes both mandatory and helpful? But helpful is separate. Could have "Requirements" for mandatory, and "Preferred Qualifications" for helpful. That's two sections. "Benefits" section: we have US location-neutral work environment, home-office equipment stipend, flexible paid time off, Employee Engagement (Lunch & Learns, team building events), Learning & Development culture, Comprehensive Health Benefits, Competitive compensation including salary range, bonus, stock options, remote flexibility and autonomy. That's benefits and pay. We could have "Benefits" for non-compensation perks, and "Pay" for salary range, bonus, stock options. Or combine into Benefits. But instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation details, so we can have Pay section. Benefits also present. So we can have both. Schedule: not mentioned; we should not create Schedule section. Thus final sections: - About the role (company description + role overview) - Responsibilities (What You Will Own breakdown) - Requirements (What You Bring mandatory) - Preferred Qualifications (Helpful But Not Required) - Benefits (non-compensation perks) - Pay (compensation details) We need to use

  for each heading. Use

  • for any list of duties/requirements/benefits. Use

    for prose. We must preserve all substantive information. Let's extract content. About SwipeSimple paragraph: "SwipeSimple helps small businesses get paid. Since 2013 we have built payment software and tools that merchants use to run their day: taking cards in person, sending invoices, collecting online, and keeping the books straight. Banks, payment processors, and resellers offer SwipeSimple to their business customers. Businesses can also sign up with us directly. We focus on SMBs, with priority given to services businesses like HVAC, plumbing, chiropractic, physical therapy, salons and barbershops, and mental health and family counseling and more. Serving these businesses well starts with understanding them. An HVAC owner and a salon owner get paid in different ways, and go to different places for information. Very few of them read marketing publications. They ask other owners, they follow the trade accounts and podcasts their industry already listens to, may go to trade shows, and they trust a recommendation from someone who has done the job over anything a vendor tells them. That is the role. Learn what these owners deal with, find where they spend their attention, speak to the problems they actually have, and earn enough trust that they recommend us to each other." Then "The role You own how SwipeSimple shows up in public: what we publish, where we take part, and whose stories we tell. The work has to be specific enough to be useful. A plumbing contractor should read something of ours and learn how to handle a deposit on a job that has not been quoted yet, not general SMB advice. You will publish for two audiences. Business owners who buy from us directly, and the banks and resellers who offer SwipeSimple to their own customers. The two do not always want the same thing from us." Then "What You Will Own These shares are estimates and will move as the work does." Then bullet list with percentages. We need to preserve that list. Let's capture each bullet: - Industry content, community, & events (roughly 35%) - Write and produce content for our priority industries: guides, posts, videos, campaign material, all of it answering a specific question about payments or operations - Run the content that goes out ahead of a sales push or an event, so an owner has heard of us before anyone reaches out - Show up in the online communities where these owners already gather, and be useful there rather than promotional - Build working relationships with creators, podcast hosts, and the people whose opinions carry weight in these trades - Plan the marketing and communications around a growing trade shows and industry events schedule: outreach beforehand, social presence during, follow-up after - Research and coordinate industry events and trade shows, manage the timeline, pre-briefing, and ensure the floor team has the presence and content they need for success - Keep up the relationships with the associations and event organizers our owners already trust - Direct-to-business channels (roughly 25%) - Run organic social and community for SwipeSimple Connect, which serves businesses that come to us without going through a bank or processor - Produce and distribute Connect campaign content - Manage the Connect social accounts day to day - Bring in reviews on TrustPilot, Capterra, and similar platforms, and respond to them - Brand and partner channels (roughly 30%) - Run the master brand SwipeSimple social handles - Create brand content, then repurpose and distribute it across channels and formats - Amplify announcements and wins from the banks and resellers who offer SwipeSimple - Work with those partners on stories worth telling publicly - Help the People team with employer brand content - Product (roughly 10%) - Produce launch content for new features and plans - Produce campaign content for the product and the App Marketplace Then "The team This role reports to the Head of Marketing, with support from our Product Marketing Manager, our Sales Enablement Manager, along with RevOps and sales support. Product Marketing and Sales enablement will seed a significant portion of what you publish." Then "What You Bring Three or more years running social and content for a B2B company selling to SMBsPublished work you can show us, in your own voice or a brand voiceExperience running more than one social account for more than one audienceWillingness to reach out cold to a creator, a podcast host, or an association, and turn that into a working relationshipExperience writing for small business owners in a trade or service industry, or a track record of learning an unfamiliar industry well enough to write for itYou catch the doubled word and the broken link before anyone else does" Note there is missing punctuation; we need to preserve as is but we can format into list. Then "Helpful But Not Required Experience in payments, fintech, or small business softwareVideo production or editingExperience sourcing and producing customer storiesFamiliarity with reseller or channel go-to-market models" Then "Why You’ll Love Being Part of the Team US location-neutral work environmentHome-office equipment stipendFlexible paid time offEmployee Engagement (Lunch & Learns, team building events)Learning & Development cultureComprehensive Health BenefitsCompetitive compensation including:Annualized Base Salary Range: $80,000 – $100,000Annualized Company Performance Bonus: $8,000 - $10,000Company Stock Options: 10,000Remote flexibility and autonomy" We need to split into benefits and pay. Benefits (non-compensation): US location-neutral work environment, Home-office