Email Project Manager
Vertex Communication Group · United States · 1 mo ago
RemoteRemoteProject Management$80k–$105k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like recruiting process etc. Must preserve substantive info.
We need to parse the posting.
Key sections:
- About the role: description of role: "You will be the point person for a single, high-volume client account, owning every email request from intake through deployment..." etc. Also "WHAT YOU WILL DO" list of duties.
- Responsibilities: could be the list under "WHAT YOU WILL DO". Could also be separate.
- Requirements: "WHAT YOU NEED TO HAVE" must-have list.
- Qualifications: maybe nice-to-have? Could be separate.
- Skills: maybe combine.
- Benefits: "WHAT WE OFFER" includes compensation, bonus, etc.
- Pay: compensation range.
- Schedule: maybe "WHAT YOU’LL NEED" includes availability: Full-time dedication from 9:00 AM to 5:00 PM Central (EST), Monday through Friday.
We need to ensure we don't include filler like "commensurate with experience" in Pay section? Actually Pay section should include the compensation range; we can include that. The phrase "commensurate with experience" is okay as part of description but not as placeholder. It's fine.
We must not include sections with only filler. So we need to ensure each heading has substantive content.
Let's extract:
About the role: paragraph(s) describing role and company? The "THE ROLE" section includes description. Also "HOW WE WORK" maybe about company culture but could be part of About the role? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe includes company description and role overview). Responsibilities (list of duties). Requirements (must-have). Qualifications (nice-to-have). Skills (maybe combine must-have and nice-to-have? but we can separate). Benefits (what we offer). Pay (compensation). Schedule (availability/hours).
We must not repeat job title.
We must output only HTML fragment, no /, no markdown.
Let's craft.
First, About the role: combine Vertex Communication Group description and role overview.
Paragraph: "Vertex Communication Group is a B2B email marketing firm with 23 years of experience running complex, high-volume programs. We own the full stack: strategy, production, ESP and CRM management, data operations, deliverability, and reporting. Our deepest specialty is trade associations, professional societies, and membership organizations, and we also run programs for commercial and other B2B clients. In aggregate our programs reach more than 30 million members and subscribers. We are fully remote, deliberately lean, and genuinely invested in doing the work well. We are also running AI-assisted production workflows in production today, not as an experiment, and we are expanding that layer aggressively."
Then role overview: "You will be the point person for a single, high-volume client account, owning every email request from intake through deployment. You will work alongside a small team of fellow program managers who share this account, plus the builders and reviewers who bring each job to life. When a request is incomplete, when a timeline is tight, when the client wants one more change past the point that is fair to the production queue, that is you. Your job is to make sure the work goes out complete, correct, and on time, and to protect the process (review rounds, turnaround windows, and scope boundaries) that keeps this account running smoothly job after job. Success looks like this: jobs move cleanly from intake to deployment without anyone chasing you, the project tracker reflects reality, and the client trusts you to tell them the truth about timeline and scope, even when it is not what they want to hear."
That's substantive.
Responsibilities: list from "WHAT YOU WILL DO". Each bullet.
Let's extract bullet points:
- Own intake and production: Monitor incoming requests, confirm completeness (content, audience, send date, approval chain) before work begins, and route each job to the right builder. Log and maintain every job in the project tracker so status is never a guessing game.
- Run the review gate: Coordinate build, in-house review, edits, and proof rounds. Confirm every requested change was actually applied, links are live, audience and suppression lists are correct, and subject line and preview text are final before anything is scheduled.
- Own your QA round: You are one of three QA rounds this account runs before a send goes out, the checkpoint that catches whatever the earlier rounds missed before it reaches the client or deploys.
- Own scheduling and deployment: Schedule and deploy sends directly in Salesforce Marketing Cloud or a similar ESP. Confirm sends are correctly staged and scheduled, monitor for platform errors or alerts, and close out completed jobs.
- Protect scope and timeline: Hold the client to the agreed review rounds and standard turnaround window. When an incomplete intake, a late content change, or a past-review-round revision threatens the schedule, you are the one who explains the impact, and whether it triggers a rebuild or additional review.
- Manage capacity: Balance concurrent jobs during high-volume stretches or planned reduced-availability periods without letting any of them slip.
- Communicate constantly: Keep the requester, builders, and leadership aligned on where every job stands. Deliver hard news (a delay, a fee, a scope boundary) clearly and without drama.
- Escalate what is not yours to decide: Flag anything touching pricing, contract terms, or a live platform write that needs sign-off above your level.
- Keep the team's knowledge current: Document naming conventions, known issues, and client-specific quirks so the team runs on shared standards, not memory.
That's a good list.
Requirements: Must-have list from "WHAT YOU NEED TO HAVE Must-have:":
- 3 to 5 years of client-facing project management, ideally in email production, marketing operations, or agency project management.
- Experience coordinating production work with multiple handoffs and multiple stakeholders, at real volume.
- Familiarity with a work-management tool such as Wrike, Asana, or Monday.com.
- Able to schedule and deploy a send in Salesforce Marketing Cloud or a similar ESP. You can independently confirm a job is staged, scheduled, and correct, not just watch someone else do it.
- Comfortable owning a queue of concurrent jobs at different stages without losing track of any of them.
- Sharp attention to detail. Broken links, wrong subject lines, and stale segment logic get caught before send, not after.
- Strong written communication. You document decisions clearly and deliver difficult updates (a delay, a scope boundary, a fee) in a way that keeps the client relationship intact.
- Comfort holding a line on process and scope, even when a client pushes back.
- Remote discipline. You manage your own time and deadlines without close supervision.
- Attention to detail in everything. For example, if you have read this far, we would love for you to tell us in your video answer what 32,311 x 5,672 is. (This is a bit quirky but it's a requirement? It's more of a fun test; but it's still part of must-have? It says "Attention to detail in everything. For example, if you have read this far, we would love for you to tell us in your video answer what 32,311 x 5,672 is." That's a specific request; we can include as a bullet maybe.)
We'll include that as a bullet.
Qualifications: Nice-to-have list:
- Comfortable making small edits directly in the platform (fixing a broken link, a minor copy tweak) to keep a job moving without waiting on a builder.
- Hands-on experience with Salesforce Marketing Cloud or iPost specifically.
- Basic comfort with AI tools (ChatGPT, Claude, Copilot, or similar), or genuine enjoyment of using them to work faster and catch errors. You do not need to be a power user, just curious and willing.
- Background in B2B associations, membership organizations, or trade publishers.
Skills: Could combine some overlapping but we can maybe list skills like: Project management, Client communication, ESP operation (Salesforce Marketing Cloud), QA, Scope management, Documentation, Remote work discipline, Attention to detail, Written communication, AI tool familiarity.
But we must not create thin sections; we need substantive content. We could put skills as a list derived from both must-have and nice-to-have. That's okay.
Benefits: from "WHAT WE OFFER". Let's extract:
- Compensation: $80,000 – $105,000 base (full-time equivalent), commensurate with experience, plus full benefits.
- Annual bonus eligibility starts in year two alongside the rest of the senior team.
- Type of Contract: W-2 employment, 100% remote. Full-time with full benefits from day one.
- Health, Dental & Vision: Full employee health coverage paid by the company
- Home office setup: Laptop, mouse, keyboard, monitor.
- 401(k) with Company Contribution: Safe harbor plan with company contributions whether you contribute or not
- Unlimited PTO: Take the time you need, when you need it
- Fully Remote: Work from anywhere in the US, no return-to-office hidden agenda
- Team Meet-Ups: Periodic in-person gatherings throughout the year to connect, plan, and have fun
- Real Impact, Small Team: Your work is visible from day one and shapes how we operate
We should not include "commensurate with experience" as filler? It's okay.
Pay: we could just put the compensation range. But we already have compensation in Benefits. However the instruction says include Pay section only if posting actually states them. It does state compensation range. So we can have Pay section with the range.
Schedule: from "WHAT YOU’LL NEED": Availability: Full-time dedication from 9:00 AM to 5:00 PM Central (EST), Monday through Friday. Work Setup: Access to reliable high-speed internet, and a dedicated quiet workspace suitable for focused work and client video calls.
We can include schedule as the hours.
Now we need to output HTML with
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe includes company description and role overview). Responsibilities (list of duties). Requirements (must-have). Qualifications (nice-to-have). Skills (maybe combine must-have and nice-to-have? but we can separate). Benefits (what we offer). Pay (compensation). Schedule (availability/hours).
We must not repeat job title.
We must output only HTML fragment, no /, no markdown.
Let's craft.
First, About the role: combine Vertex Communication Group description and role overview.
Paragraph: "Vertex Communication Group is a B2B email marketing firm with 23 years of experience running complex, high-volume programs. We own the full stack: strategy, production, ESP and CRM management, data operations, deliverability, and reporting. Our deepest specialty is trade associations, professional societies, and membership organizations, and we also run programs for commercial and other B2B clients. In aggregate our programs reach more than 30 million members and subscribers. We are fully remote, deliberately lean, and genuinely invested in doing the work well. We are also running AI-assisted production workflows in production today, not as an experiment, and we are expanding that layer aggressively."
Then role overview: "You will be the point person for a single, high-volume client account, owning every email request from intake through deployment. You will work alongside a small team of fellow program managers who share this account, plus the builders and reviewers who bring each job to life. When a request is incomplete, when a timeline is tight, when the client wants one more change past the point that is fair to the production queue, that is you. Your job is to make sure the work goes out complete, correct, and on time, and to protect the process (review rounds, turnaround windows, and scope boundaries) that keeps this account running smoothly job after job. Success looks like this: jobs move cleanly from intake to deployment without anyone chasing you, the project tracker reflects reality, and the client trusts you to tell them the truth about timeline and scope, even when it is not what they want to hear."
That's substantive.
Responsibilities: list from "WHAT YOU WILL DO". Each bullet.
Let's extract bullet points:
- Own intake and production: Monitor incoming requests, confirm completeness (content, audience, send date, approval chain) before work begins, and route each job to the right builder. Log and maintain every job in the project tracker so status is never a guessing game.
- Run the review gate: Coordinate build, in-house review, edits, and proof rounds. Confirm every requested change was actually applied, links are live, audience and suppression lists are correct, and subject line and preview text are final before anything is scheduled.
- Own your QA round: You are one of three QA rounds this account runs before a send goes out, the checkpoint that catches whatever the earlier rounds missed before it reaches the client or deploys.
- Own scheduling and deployment: Schedule and deploy sends directly in Salesforce Marketing Cloud or a similar ESP. Confirm sends are correctly staged and scheduled, monitor for platform errors or alerts, and close out completed jobs.
- Protect scope and timeline: Hold the client to the agreed review rounds and standard turnaround window. When an incomplete intake, a late content change, or a past-review-round revision threatens the schedule, you are the one who explains the impact, and whether it triggers a rebuild or additional review.
- Manage capacity: Balance concurrent jobs during high-volume stretches or planned reduced-availability periods without letting any of them slip.
- Communicate constantly: Keep the requester, builders, and leadership aligned on where every job stands. Deliver hard news (a delay, a fee, a scope boundary) clearly and without drama.
- Escalate what is not yours to decide: Flag anything touching pricing, contract terms, or a live platform write that needs sign-off above your level.
- Keep the team's knowledge current: Document naming conventions, known issues, and client-specific quirks so the team runs on shared standards, not memory.
That's a good list.
Requirements: Must-have list from "WHAT YOU NEED TO HAVE Must-have:":
- 3 to 5 years of client-facing project management, ideally in email production, marketing operations, or agency project management.
- Experience coordinating production work with multiple handoffs and multiple stakeholders, at real volume.
- Familiarity with a work-management tool such as Wrike, Asana, or Monday.com.
- Able to schedule and deploy a send in Salesforce Marketing Cloud or a similar ESP. You can independently confirm a job is staged, scheduled, and correct, not just watch someone else do it.
- Comfortable owning a queue of concurrent jobs at different stages without losing track of any of them.
- Sharp attention to detail. Broken links, wrong subject lines, and stale segment logic get caught before send, not after.
- Strong written communication. You document decisions clearly and deliver difficult updates (a delay, a scope boundary, a fee) in a way that keeps the client relationship intact.
- Comfort holding a line on process and scope, even when a client pushes back.
- Remote discipline. You manage your own time and deadlines without close supervision.
- Attention to detail in everything. For example, if you have read this far, we would love for you to tell us in your video answer what 32,311 x 5,672 is. (This is a bit quirky but it's a requirement? It's more of a fun test; but it's still part of must-have? It says "Attention to detail in everything. For example, if you have read this far, we would love for you to tell us in your video answer what 32,311 x 5,672 is." That's a specific request; we can include as a bullet maybe.)
We'll include that as a bullet.
Qualifications: Nice-to-have list:
- Comfortable making small edits directly in the platform (fixing a broken link, a minor copy tweak) to keep a job moving without waiting on a builder.
- Hands-on experience with Salesforce Marketing Cloud or iPost specifically.
- Basic comfort with AI tools (ChatGPT, Claude, Copilot, or similar), or genuine enjoyment of using them to work faster and catch errors. You do not need to be a power user, just curious and willing.
- Background in B2B associations, membership organizations, or trade publishers.
Skills: Could combine some overlapping but we can maybe list skills like: Project management, Client communication, ESP operation (Salesforce Marketing Cloud), QA, Scope management, Documentation, Remote work discipline, Attention to detail, Written communication, AI tool familiarity.
But we must not create thin sections; we need substantive content. We could put skills as a list derived from both must-have and nice-to-have. That's okay.
Benefits: from "WHAT WE OFFER". Let's extract:
- Compensation: $80,000 – $105,000 base (full-time equivalent), commensurate with experience, plus full benefits.
- Annual bonus eligibility starts in year two alongside the rest of the senior team.
- Type of Contract: W-2 employment, 100% remote. Full-time with full benefits from day one.
- Health, Dental & Vision: Full employee health coverage paid by the company
- Home office setup: Laptop, mouse, keyboard, monitor.
- 401(k) with Company Contribution: Safe harbor plan with company contributions whether you contribute or not
- Unlimited PTO: Take the time you need, when you need it
- Fully Remote: Work from anywhere in the US, no return-to-office hidden agenda
- Team Meet-Ups: Periodic in-person gatherings throughout the year to connect, plan, and have fun
- Real Impact, Small Team: Your work is visible from day one and shapes how we operate
We should not include "commensurate with experience" as filler? It's okay.
Pay: we could just put the compensation range. But we already have compensation in Benefits. However the instruction says include Pay section only if posting actually states them. It does state compensation range. So we can have Pay section with the range.
Schedule: from "WHAT YOU’LL NEED": Availability: Full-time dedication from 9:00 AM to 5:00 PM Central (EST), Monday through Friday. Work Setup: Access to reliable high-speed internet, and a dedicated quiet workspace suitable for focused work and client video calls.
We can include schedule as the hours.
Now we need to output HTML with headings and - for lists,
for prose.
We must not include any extra text outside HTML.
Let's craft.
Structure:
About the role
Vertex Communication Group ...
You will be the point person ...
Responsibilities
- Own intake and production: Monitor incoming requests, confirm completeness (content, audience, send date, approval chain) before work begins, and route each job to the right builder. Log and maintain every job in the project tracker so status is never a guessing game.
...
Requirements
- 3 to 5 years of client-facing project management, ideally in email production, marketing operations, or agency project management.
...
Qualifications
- Comfortable making small edits directly in the platform (fixing a broken link, a minor copy tweak) to keep a job moving without waiting on a builder.
...
Skills
- Project management (client-facing, email production/marketing operations)
- Client communication and stakeholder coordination
- ESP operation – Salesforce Marketing Cloud (or similar)
- Quality assurance and proofing
- Scope and timeline management
- Documentation and knowledge sharing
- Remote work discipline and self‑management
- Attention to detail
- Strong written communication
- Basic familiarity with AI tools (ChatGPT, Claude, Copilot, etc.)
Benef
- for lists,
for prose. We must not include any extra text outside HTML. Let's craft. Structure:
About the role
Vertex Communication Group ...
You will be the point person ...
Responsibilities
- Own intake and production: Monitor incoming requests, confirm completeness (content, audience, send date, approval chain) before work begins, and route each job to the right builder. Log and maintain every job in the project tracker so status is never a guessing game. ...
Requirements
- 3 to 5 years of client-facing project management, ideally in email production, marketing operations, or agency project management. ...
Qualifications
- Comfortable making small edits directly in the platform (fixing a broken link, a minor copy tweak) to keep a job moving without waiting on a builder. ...
Skills
- Project management (client-facing, email production/marketing operations)
- Client communication and stakeholder coordination
- ESP operation – Salesforce Marketing Cloud (or similar)
- Quality assurance and proofing
- Scope and timeline management
- Documentation and knowledge sharing
- Remote work discipline and self‑management
- Attention to detail
- Strong written communication
- Basic familiarity with AI tools (ChatGPT, Claude, Copilot, etc.)
Benef