Digital Marketing Account Manager (US)
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.
Thus we need to decide which sections to include based on content.
We have:
- Who We Are (company description) – could be "About the role"? Actually "About the role" is a heading for role description. But we have "Who We Are" describing company. Could map to "About the role"? Not exactly. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if appropriate. We have content for "About the role" maybe we can put company description under "About the role"? Or we could create a custom heading? The instruction says use those headings for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings? It says use for section headings (e.g. About the role, Responsibilities...). Likely they expect us to use those standard headings where applicable. We can also add other headings if needed? Probably better to stick to those.
We have:
- Responsibilities: "What You’ll Be Doing" list.
- Requirements/Qualifications/Skills: "What We’re Looking For" list of traits.
- Benefits: Not explicitly listed besides maybe "Why You’ll Love It Here" which is more about culture, not benefits. No explicit benefits like health insurance etc. So we should not create Benefits section unless posting actually states them. It does not. So skip Benefits.
- Pay: Salary range given: "$50,000 – $60,000 (depending on experience)". So we can create Pay section.
- Schedule: Not given besides full-time. Could we infer schedule? Not explicit. So skip Schedule.
- About the role: Could include "Who We Are" and maybe "The Role: Account Executive" summary. But we already have Responsibilities etc. The "About the role" could be a brief description of the role. We have "The Role: Account Executive" paragraph describing it's not a back-office role etc. That could go under About the role.
- Qualifications: Could be same as Requirements? Might combine.
We need to preserve all substantive information. So we need to include company description, role description, responsibilities list, what we're looking for list, mission, why you'll love it here (maybe as a section like "Why You’ll Love It Here" but not in standard list; we could treat as a section with heading maybe "Why You’ll Love It Here" but instruction says use those headings (e.g., About the role, Responsibilities...). It doesn't forbid other headings but says use for section headings (e.g. About the role, Responsibilities...). Could interpret that we should use those headings for sections; but we can also add other headings if needed? Safer to map content to those headings.
We have "Why You’ll Love It Here" which is about culture/benefits; could be placed under Benefits? But Benefits section is for tangible benefits; but we could still put it under Benefits if we want to include it. However instruction says never create Benefits section unless posting actually states them. It does not state benefits like health insurance etc. But "Why You’ll Love It Here" is not a benefit per se but more about culture. Might be considered a benefit? The instruction ambiguous. Safer to not create a Benefits section if no explicit benefits. But we could include that content under "About the role" or as a separate section with a custom heading? Might risk violating instruction.
We also have "Your Mission" which could be part of Responsibilities or a separate section like "Mission". Not in list.
We have "Ready to Apply?" which is application instructions; we must remove application instructions. So drop that.
We have location and salary: location is "Full-time, based in our Celebration, Florida office". That's schedule/location; we could put location under Pay? Or maybe under Schedule? Since schedule not given, we could put location under Pay section as a note? Or we could create a short
for metadata (location) as allowed: "fold minor metadata into a short
or drop it." So we can include location in a short
maybe after Pay section.
Thus plan:
-
About the role
: include company description (Who We Are) and role overview (The Role: Account Executive paragraph). Could be two elements.
-
Responsibilities
: - list each bullet from "What You’ll Be Doing".
-
Requirements
: maybe combine "What We’re Looking For" and "Your Mission"? Actually "What We’re Looking For" is list of traits; that fits Requirements. "Your Mission" is more about mission/duties; could be part of Responsibilities but it's separate. Could include under Requirements as well? Might be better to have a separate section for "Mission"? Not in list. Could put under Responsibilities as additional bullet? But it's more about mission. Could treat as part of Responsibilities.
We need to preserve all substantive information. So we need to include "Your Mission" content somewhere. Could add a Mission
but not in allowed headings. Might be okay if we treat as a subsection under Responsibilities? But then we might lose heading.
Alternatively, we could create a Qualifications
for "What We’re Looking For". And keep Responsibilities as is. Then we could add a About the role
for company description and role overview. Then we could add a Pay
for salary. Then we could add a for location.
We must not create sections with filler. So we need to ensure each heading has real content.
Thus:
About the role
Who We Are At Paul Gough Media, we’re not your typical marketing agency—we’re a growth engine for private healthcare clinics around the world. Founded by Paul Gough—best-selling author, podcast host, international speaker, and a leading voice in the private healthcare space—we’ve helped over 2,500 clinics turn their marketing into consistent patient-generating systems. From our energetic HQ in Hartlepool to our sunny base in Orlando, our team builds high-performing funnels, ad campaigns, AI tools, and sales systems that help clinic owners scale with confidence. When clinic owners are serious about growth, they come to us.
The Role: Account Executive We’re looking for a full-time Account Executive to join our fast-growing, high-performance team. This isn’t a back-office role. You’ll work directly with ambitious business owners, helping them maximise results from their digital marketing. If you enjoy marketing, love building real relationships, and want to play a meaningful role in helping businesses grow, this could be one of the most rewarding opportunities you’ll find.
Responsibilities
- Managing a portfolio of around 20 client accounts as their primary point of contact
- Building strong, long-term relationships based on trust (relationships matter just as much as results)
- Helping clients get the most from their digital marketing—ads, funnels, and content
- Leading bi-weekly review calls to discuss performance and next steps
- Analysing campaign data (including Google Ads and Facebook Ads) ahead of client meetings
- Translating PPC performance into clear, actionable insights
- Creating and managing Facebook lead generation and retargeting campaigns
- Working closely with creative and marketing teams to ensure campaigns launch on time
- Identifying client needs and developing strategic, creative solutions
- Supporting content creation (ad angles, hooks, messaging, and social ideas)
- Helping clients generate consistent leads and sales to grow their businesses and impact more lives
Requirements
- Are passionate about marketing, sales, and business growth
- Are highly organised and detail-oriented
- Can confidently manage multiple clients and projects
- Take initiative and make things happen
- Are driven to learn, improve, and make a meaningful impact
Mission
maybe not allowed. Could incorporate mission into Responsibilities as an extra bullet? But we already have responsibilities list; mission is more about delivering world-class client experience etc. Could add as a bullet under Responsibilities? But that would mix. Better to add a separate section maybe "Your Mission" but not in allowed headings. However instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say you cannot use other headings, but gives examples. It might be okay to use other headings if needed, but they said "Prefer a few substantive sections over many thin ones." So maybe we can incorporate mission into Responsibilities as a bullet? Let's see mission content:
"Your Mission Your mission is to deliver a world-class client experience that drives retention, loyalty, and results. You’ll help clients generate predictable leads and strong ROI through well-managed campaigns across Meta, Google, and other platforms. You’ll ensure smooth project delivery by coordinating timelines, assets, and internal teams, while turning client goals into clear, actionable marketing strategies. You’ll also support and mentor your marketing assistant, contributing to a culture where everyone continues to grow and perform at a higher level."
This is substantive; we should include it. Could be placed under Responsibilities as additional bullets, but it's more about mission. Could create a Mission
but not in list; risk. However maybe they expect us to use "Qualifications" for skills, "Responsibilities" for duties, and "About the role" for description, and then "Pay" for salary. Mission could be considered part of Responsibilities (since it's about what you'll do). Actually many of those mission items overlap with responsibilities: delivering client experience, generating leads, coordinating timelines, supporting mentor. Some are already covered: Helping clients get the most from digital marketing, leading bi-weekly review calls, analyzing campaign data, translating PPC performance, creating/managing FB campaigns, working with creative team, identifying needs, supporting content creation, helping generate leads. The mission adds: deliver world-class client experience driving retention, loyalty, results; help clients generate predictable leads and strong ROI through well-managed campaigns across Meta, Google, other platforms
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. Thus we need to decide which sections to include based on content. We have: - Who We Are (company description) – could be "About the role"? Actually "About the role" is a heading for role description. But we have "Who We Are" describing company. Could map to "About the role"? Not exactly. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if appropriate. We have content for "About the role" maybe we can put company description under "About the role"? Or we could create a custom heading? The instruction says use those headings for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings? It says use for section headings (e.g. About the role, Responsibilities...). Likely they expect us to use those standard headings where applicable. We can also add other headings if needed? Probably better to stick to those.
We have:
- Responsibilities: "What You’ll Be Doing" list.
- Requirements/Qualifications/Skills: "What We’re Looking For" list of traits.
- Benefits: Not explicitly listed besides maybe "Why You’ll Love It Here" which is more about culture, not benefits. No explicit benefits like health insurance etc. So we should not create Benefits section unless posting actually states them. It does not. So skip Benefits.
- Pay: Salary range given: "$50,000 – $60,000 (depending on experience)". So we can create Pay section.
- Schedule: Not given besides full-time. Could we infer schedule? Not explicit. So skip Schedule.
- About the role: Could include "Who We Are" and maybe "The Role: Account Executive" summary. But we already have Responsibilities etc. The "About the role" could be a brief description of the role. We have "The Role: Account Executive" paragraph describing it's not a back-office role etc. That could go under About the role.
- Qualifications: Could be same as Requirements? Might combine.
We need to preserve all substantive information. So we need to include company description, role description, responsibilities list, what we're looking for list, mission, why you'll love it here (maybe as a section like "Why You’ll Love It Here" but not in standard list; we could treat as a section with heading maybe "Why You’ll Love It Here" but instruction says use those headings (e.g., About the role, Responsibilities...). It doesn't forbid other headings but says use for section headings (e.g. About the role, Responsibilities...). Could interpret that we should use those headings for sections; but we can also add other headings if needed? Safer to map content to those headings.
We have "Why You’ll Love It Here" which is about culture/benefits; could be placed under Benefits? But Benefits section is for tangible benefits; but we could still put it under Benefits if we want to include it. However instruction says never create Benefits section unless posting actually states them. It does not state benefits like health insurance etc. But "Why You’ll Love It Here" is not a benefit per se but more about culture. Might be considered a benefit? The instruction ambiguous. Safer to not create a Benefits section if no explicit benefits. But we could include that content under "About the role" or as a separate section with a custom heading? Might risk violating instruction.
We also have "Your Mission" which could be part of Responsibilities or a separate section like "Mission". Not in list.
We have "Ready to Apply?" which is application instructions; we must remove application instructions. So drop that.
We have location and salary: location is "Full-time, based in our Celebration, Florida office". That's schedule/location; we could put location under Pay? Or maybe under Schedule? Since schedule not given, we could put location under Pay section as a note? Or we could create a short
for section headings (e.g. About the role, Responsibilities...). Could interpret that we should use those headings for sections; but we can also add other headings if needed? Safer to map content to those headings. We have "Why You’ll Love It Here" which is about culture/benefits; could be placed under Benefits? But Benefits section is for tangible benefits; but we could still put it under Benefits if we want to include it. However instruction says never create Benefits section unless posting actually states them. It does not state benefits like health insurance etc. But "Why You’ll Love It Here" is not a benefit per se but more about culture. Might be considered a benefit? The instruction ambiguous. Safer to not create a Benefits section if no explicit benefits. But we could include that content under "About the role" or as a separate section with a custom heading? Might risk violating instruction. We also have "Your Mission" which could be part of Responsibilities or a separate section like "Mission". Not in list. We have "Ready to Apply?" which is application instructions; we must remove application instructions. So drop that. We have location and salary: location is "Full-time, based in our Celebration, Florida office". That's schedule/location; we could put location under Pay? Or maybe under Schedule? Since schedule not given, we could put location under Pay section as a note? Or we could create a short
for metadata (location) as allowed: "fold minor metadata into a short
or drop it." So we can include location in a short
maybe after Pay section. Thus plan: -
About the role
: include company description (Who We Are) and role overview (The Role: Account Executive paragraph). Could be twoelements. -
Responsibilities
:- list each bullet from "What You’ll Be Doing".
-
Requirements
: maybe combine "What We’re Looking For" and "Your Mission"? Actually "What We’re Looking For" is list of traits; that fits Requirements. "Your Mission" is more about mission/duties; could be part of Responsibilities but it's separate. Could include under Requirements as well? Might be better to have a separate section for "Mission"? Not in list. Could put under Responsibilities as additional bullet? But it's more about mission. Could treat as part of Responsibilities. We need to preserve all substantive information. So we need to include "Your Mission" content somewhere. Could add aMission
but not in allowed headings. Might be okay if we treat as a subsection under Responsibilities? But then we might lose heading. Alternatively, we could create aQualifications
for "What We’re Looking For". And keep Responsibilities as is. Then we could add aAbout the role
for company description and role overview. Then we could add aPay
for salary. Then we could add afor location. We must not create sections with filler. So we need to ensure each heading has real content. Thus:
About the role
Who We Are At Paul Gough Media, we’re not your typical marketing agency—we’re a growth engine for private healthcare clinics around the world. Founded by Paul Gough—best-selling author, podcast host, international speaker, and a leading voice in the private healthcare space—we’ve helped over 2,500 clinics turn their marketing into consistent patient-generating systems. From our energetic HQ in Hartlepool to our sunny base in Orlando, our team builds high-performing funnels, ad campaigns, AI tools, and sales systems that help clinic owners scale with confidence. When clinic owners are serious about growth, they come to us.
The Role: Account Executive We’re looking for a full-time Account Executive to join our fast-growing, high-performance team. This isn’t a back-office role. You’ll work directly with ambitious business owners, helping them maximise results from their digital marketing. If you enjoy marketing, love building real relationships, and want to play a meaningful role in helping businesses grow, this could be one of the most rewarding opportunities you’ll find.
Responsibilities
- Managing a portfolio of around 20 client accounts as their primary point of contact
- Building strong, long-term relationships based on trust (relationships matter just as much as results)
- Helping clients get the most from their digital marketing—ads, funnels, and content
- Leading bi-weekly review calls to discuss performance and next steps
- Analysing campaign data (including Google Ads and Facebook Ads) ahead of client meetings
- Translating PPC performance into clear, actionable insights
- Creating and managing Facebook lead generation and retargeting campaigns
- Working closely with creative and marketing teams to ensure campaigns launch on time
- Identifying client needs and developing strategic, creative solutions
- Supporting content creation (ad angles, hooks, messaging, and social ideas)
- Helping clients generate consistent leads and sales to grow their businesses and impact more lives
Requirements
- Are passionate about marketing, sales, and business growth
- Are highly organised and detail-oriented
- Can confidently manage multiple clients and projects
- Take initiative and make things happen
- Are driven to learn, improve, and make a meaningful impact
Mission
maybe not allowed. Could incorporate mission into Responsibilities as an extra bullet? But we already have responsibilities list; mission is more about delivering world-class client experience etc. Could add as a bullet under Responsibilities? But that would mix. Better to add a separate section maybe "Your Mission" but not in allowed headings. However instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say you cannot use other headings, but gives examples. It might be okay to use other headings if needed, but they said "Prefer a few substantive sections over many thin ones." So maybe we can incorporate mission into Responsibilities as a bullet? Let's see mission content: "Your Mission Your mission is to deliver a world-class client experience that drives retention, loyalty, and results. You’ll help clients generate predictable leads and strong ROI through well-managed campaigns across Meta, Google, and other platforms. You’ll ensure smooth project delivery by coordinating timelines, assets, and internal teams, while turning client goals into clear, actionable marketing strategies. You’ll also support and mentor your marketing assistant, contributing to a culture where everyone continues to grow and perform at a higher level." This is substantive; we should include it. Could be placed under Responsibilities as additional bullets, but it's more about mission. Could create a
Mission
but not in list; risk. However maybe they expect us to use "Qualifications" for skills, "Responsibilities" for duties, and "About the role" for description, and then "Pay" for salary. Mission could be considered part of Responsibilities (since it's about what you'll do). Actually many of those mission items overlap with responsibilities: delivering client experience, generating leads, coordinating timelines, supporting mentor. Some are already covered: Helping clients get the most from digital marketing, leading bi-weekly review calls, analyzing campaign data, translating PPC performance, creating/managing FB campaigns, working with creative team, identifying needs, supporting content creation, helping generate leads. The mission adds: deliver world-class client experience driving retention, loyalty, results; help clients generate predictable leads and strong ROI through well-managed campaigns across Meta, Google, other platforms