Résumé and cover letter built just for you!

• Started as an initiative inside a larger organization; now an independent public benefit corporation. Why this matters: not a typical marketing agency, so expect the conversation to touch genuine interest in the mission, not just marketing mechanics.
• Works on behalf of hundreds of member stations nationwide. Why this matters: multi-client, multi-stakeholder coordination, a close cousin of the ~20-account shared Marketo instance you ran.
• Headquartered in the Northeast. The role is remote, so location shouldn't be a live issue. It's still worth knowing where the core team sits.
• Core services span donor CRM and donor-acquisition programs. Why this matters: fundraising operations at scale for member stations, and this role produces the donor communications that machine runs on.
• Stated core values: excellence, innovation, trust, and community. Why this matters: expect a values-forward, mission-first tone from the interviewer.
• Publishes its results in dollars raised for member stations. Why this matters: they measure their impact in hard numbers, so answer in your own measurable terms: campaign volume, program counts, list sizes, compliance outcomes.
• Publishes a public diversity statement. Be ready to speak to inclusive collaboration across a large, varied partner network if it comes up.
• What the posting itself asks for: end-to-end email production (scheduling, asset coordination, campaign setup, HTML production, QA and deployment) at high volume, 75 million or more emails a year across 50 or more client organizations, inside Iterable, working with a separate strategy team that owns testing priorities. The role also carries two direct reports.

These are practice material to help you walk in warmed up, not a script anyone will actually read from. Behavioral questions below use the STAR format: Situation, Task, Action, Result. Interviewers lean on it because past behavior is the best predictor of future performance, and it keeps your answer concrete. The Technical, Role Specific and Culture Fit questions are more conversational, so answer those naturally.

Q: Tell me about a time you managed high-volume email production across multiple accounts or clients at once.

A: At my last company I managed two enterprise Marketo instances supporting the company, its foundation and roughly 20 B2B agency client accounts at the same time: about 240 email campaigns a year across newsletters, nurture streams and targeted programs, plus around 75 landing pages and forms. I kept it running cleanly with shared workspaces, naming conventions and QA checklists so nothing crossed between clients by mistake.

Q: Tell me about a time you had to work closely with a team that owned strategy while you owned execution.

A: That's the shape of my two enterprise client engagements. Those teams set the messaging and testing priorities, and I owned building and checking the actual programs: four-version variant-subject emails with branching logic for openers versus non-openers, landing pages, forms, and the reporting that fed their next round of decisions.

Q: Tell me about a time you built a process or documentation system that had to scale.

A: Two examples: the naming conventions, QA checklists and runbooks I used to keep about 20 concurrent client accounts consistent on a shared instance, and the Subject Access Request process I built for our GDPR, CASL and CCPA consent program: a landing page and form to take in privacy requests, logged in a tracker and resolved on a compliance timeline every time, as the underlying laws kept changing.

Q: Tell me about a time you managed a high volume of time-sensitive communications under a deadline.

A: A client's webinar program is the clearest example. I owned the full lifecycle end to end: invitations, confirmations, reminders and follow-ups, plus the registration pages and forms, all on fixed event dates that couldn't slip.

Q: This role runs on Iterable. What's your experience with it?

A: I haven't worked in Iterable directly. My hands-on platform depth is Marketo (currently certified) and Oracle Eloqua, plus Salesforce integration work. What I'd point to instead is how fast I've picked up new stacks before: every new agency client engagement meant learning that account's own configuration and quirks quickly while still hitting production deadlines. The production discipline transfers directly. The platform-specific screens are what I'd be ramping on.

Q: Walk me through your hands-on HTML and email production skills.

A: I build and troubleshoot HTML and CSS directly for email templates and landing pages rather than relying only on a visual editor. That has been part of my day-to-day for years.

Q: How do you approach QA before a send goes out at scale?

A: I run everything through a checklist before deployment: links, tokens and personalization, rendering across email clients, segmentation logic and suppression lists. That discipline is what let me run about 240 campaigns a year across about 20 accounts without cross-client errors.

Q: This role has two direct reports. What does that side of the job look like day to day, and how do you see yourself stepping into it?

A: This would be new for me. Every role in my background has been individual-contributor level, not people management, and I named that directly in my cover letter. What I bring instead is the process and documentation discipline that makes a team's work consistent and easy to review, which is a natural foundation for supporting two production specialists, and I'm looking to grow into the management side.

Q: How does the team handle production during your highest-volume windows? I'd imagine Giving Days are one of those.

A: I'd want to understand your specific cadence, and my instinct from running about 240 campaigns a year is that the answer is usually pre-built templates, a clear QA checklist and tight sequencing so volume doesn't force shortcuts on deployment quality.

Q: What's the biggest production pain point you're hoping this hire solves?

A: Ask this one live. It's a useful question for you, not one to answer yourself. See Questions to Ask below.

Q: Why public media, and why this company specifically?

A: Public media runs on donor trust and operational discipline in equal measure. That combination is the kind of work I've done for more than 11 years: building the systems that let an organization keep its promises to the people supporting it at scale. Doing that collaboratively for hundreds of stations, rather than one company at a time, is an interesting version of the multi-client work I already know how to do.

Q: How do you approach ramping onto a new platform quickly while still owning live production?

A: I lean on documentation from day one. I write down what I'm learning as I learn it, which becomes my own reference and, later, something a teammate can use too. I'd also want early access to a sandbox or a low-risk send to build confidence before touching anything client-facing.

• What does a typical production week look like for the email operations team, and how does that change during a Giving Day or a major fundraising push?
• What's the current split of responsibilities between this role and the two production specialists who'd report to me?
• What support or ramp-up plan is typical for someone coming in without direct Iterable experience?
• How does this team work day to day with the strategy team that owns testing priorities? What does the handoff look like?
• What would success look like in this role at the 90-day mark?
• What's the biggest production bottleneck the team is hoping this hire helps solve?
• What does growth typically look like from this role?

• This is very likely a People-Operations screen, not a technical deep dive. The interviewer's title (Senior Manager, People Operations) is the tell. Lead with a clear, confident background and motivation. Save deep platform detail for a later round if one comes.
• Be upfront about the two open gaps, Iterable and people management, rather than downplaying them. Both are named honestly in your cover letter already. "New, and I'm ready to grow into it" lands much better than pretending they're not gaps.
• Confirm the call format (phone or video) from the calendar invite before Tuesday so you're not caught off guard.
• Keep the job posting open during the call so you can reference specifics naturally.
• Have two or three of the Behavioral answers above ready to go conversationally. You don't need to recite them, just know the shape of each story cold.

Spend 15 to 20 minutes here before Tuesday. Start with the company's Mission and What We Do pages to get its own framing of its work, skim Our Partners to see the range of stations it serves, then look up your interviewer on LinkedIn once you're ready, and search for anyone whose title suggests they run email production or marketing operations, since that's likely your next-round interviewer.

• The company's mission and values page
• What We Do: services overview, from CRM to donor acquisition
• Our Partners: the member-station network it serves
• The company's careers page, for context on how it presents open roles
• The company on LinkedIn: updates and recent posts
• The job posting: re-read the full posting once more the night before