Senior Director, Pursuit Operations
Epsilon · New York, NY · 1 mo ago
HybridManagement$128k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes Overview Company Description, Responsibilities, Qualifications, Benefits, Pay (Compensation Range), maybe Schedule not present. Also maybe "Additional Information" includes company description etc. We need to include sections only when real specific content. Use for section headings. Use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Click here to view how Epsilon transforms marketing..." maybe that's extra but not boilerplate? It's a link; maybe keep? It's not essential but could be considered extra. Probably remove as it's not substantive about role. Also remove "Additional Information" maybe keep company description? The overview includes company description; we can keep that as part of About the role or Overview. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have sections: About the role (maybe from Overview Company Description), Responsibilities, Qualifications, Benefits, Pay. Possibly also "Skills" not present. We'll not create empty sections.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include details from responsibilities, qualifications, benefits, compensation range.
We must not include boilerplate like EEO, accommodations, etc. Also remove "Additional Information" maybe but we can keep company description as part of About the role.
We need to format responsibilities as list items. The responsibilities section includes many bullet-like sentences. We'll convert each sentence or clause into
- . Ensure we keep all details.
Qualifications similarly list.
Benefits: list from "Benefits As an Epsilon employee..." includes bullet points: Time to recharge: Flexible time off (FTO), 14 paid holidays, paid sick time; Family well-being: Parental/new child leave, childcare & elder care assistance, adoption assistance; Extra perks: Comprehensive health coverage, 401(k), tuition assistance, commuter benefits, professional development, employee recognition, charitable donation matching, health coaching and counseling. Also note "Epsilon benefits are subject to eligibility requirements and other terms." We'll keep that as prose maybe.
Pay: Compensation Range: USD $128,000.00 - USD $192,000.00/Annually. Also note bonus eligibility. We'll include that.
We must not include schedule.
We must not repeat job title.
We must output only HTML fragment.
Let's craft:
About the role
... overview company description ...
We need to include the overview company description text: "Overview Company Description Pursuit Operations is the engine that keeps Epsilon's pursuits moving. It exists to run a disciplined, repeatable pursuit motion so that every RFP and major pursuit is organized, on time, compliant, and client-ready. The function owns the workflow, the submission mechanics, the content library, and the process governance that turn a pipeline of opportunities into clean, high-quality client submissions. The work is measured against missed deadlines, compliance accuracy, rework, and the time it takes to move from intake to a client-ready package. Solutions at Epsilon is moving from a case-by-case, RFP-support posture to a single operating model, and Pursuit Operations is the backbone of that shift. This role builds and runs the system: clear intake paths with prioritization and SLAs, standard stages and required artifacts, a governed content library, and post-pursuit debriefs that feed improvements back into the process. The goal is a motion Sales can count on, with clear ownership and clean handoffs, that scales as the business grows. This is a hands-on operating role, not a manage-from-above seat. The Senior Director sets the standard and also runs the tracker, enforces the deadlines, and holds the quality bar on submissions. The role leads the Pursuit Operations team and develops it, while staying close enough to the work to catch the missed owner, the stale content, or the compliance gap before it reaches a client. The role reports to the leader of the Solutions organization and partners daily with Solutions Consulting, Sales Engineering, Value Consulting, and Sales. Pursuit Operations enables pursuits rather than owning them: it does not set solution strategy, scope, or feasibility, and it does not own pricing or the client narrative. Its mandate is to make the motion fast, clean, and reliable, and to be a growth enabler, never a bottleneck."
We'll put that in .
Then Responsibilities: heading
Responsibilities
then with each bullet.
We need to extract bullet points from "Responsibilities What You'll Achieve ..." and "In This Role, You Will". Let's list them:
- You will run the pursuit engine for Epsilon's Solutions organization, hands-on.
- You will build and operate the intake, workflow, submission, content, and governance systems that make every meaningful pursuit organized, on time, and client-ready, and you will lead the team that runs them.
- Orchestrate pursuit workflow end to end.
- Own the timelines, achievements, routing, reminders, and partner concerns for every active pursuit, so nothing slips.
- Run clear intake paths with prioritization, tiering, and SLAs, so each pursuit gets the right level of coverage and capacity is protected.
- Own bid mechanics and submission quality. Make sure submission requirements, compliance checks, formatting standards, portal uploads, and final packaging are buttoned up on every pursuit. The standard is zero missed deadlines and clean, compliant submissions.
- Run content assembly and version control. Maintain a single source of truth for each pursuit, with document hygiene, controlled edits, a clear final-release process, and QA, so the team never loses time to versioning chaos or sends the wrong file.
- Build and govern the reusable content system. Stand up and maintain a library of approved modules, product descriptions, proof points, case studies, language, and boilerplate, with named owners and a freshness process, so the team assembles from current, approved content rather than reinventing it each time.
- Govern the pursuit process. Define and enforce standard stages, required artifacts, intake fields, and stage gates, and run post-pursuit debriefs that capture what worked, what did not, and the top changes to process, templates, and content for next time.
- Build the operating model, not just run today's queue. Move the function from custom heroics to a repeatable system. Use standard artifacts, clear rules of engagement, and a motion that flexes from a quick advisory check to a drop-everything, must-win pursuit without changing the rules.
- Lead and develop the Pursuit Operations team. Set clear roles and ownership, coach the team, and set the standard on operational rigor, while keeping the function lean and close to the work.
- Coordinate across the pursuit. Support Solutions Consulting and Sales with packaging the client-ready story, support Sales Engineering by coordinating technical sections and accurate insertion of responses, and keep Sales on top of deadlines and collaborator coordination.
- Measure and improve the motion. Track missed deadlines, compliance accuracy, rework and version churn, and cycle time from intake to client-ready package, and use post-pursuit debriefs to drive the system forward.
We'll put each as - .
Qualifications: heading
Qualifications
then with bullet points from "What you'll bring with you:" and "Why You Might Stand Out From Other Candidates". Also include "Ten-plus years..." etc.
Let's list:
- Deep proposal and pursuit operations leadership. You have run RFP, bid, or pursuit operations for a sales or pre-sales organization, and you have owned the workflow, submission quality, and content behind it. You know what it takes to land complex submissions on time, every time.
- Operating-model and process design. You have built intake paths, SLAs, stage gates, and governance from the ground up, and turned an ad-hoc, case-by-case function into a repeatable system that people actually follow.
- Content library and knowledge management. You have established and managed a reusable content or proposal library at scale. You implemented ownership models and freshness standards. Ideally, this was on a platform like Responsive (RFPIO), Loopio, or a similar system.
- Hands-on operational rigor. You run the tracker yourself. You are the person who notices the unassigned item, the stale answer, or the compliance gap, and closes it before it becomes a problem. You hold deadlines without drama.
- People leadership. You have led and developed an operations, proposal, or pursuit team, set clear ownership, and raised the standard of work without adding bureaucracy.
- Cross-functional orchestration under deadline pressure. You coordinate across solutions, technical, commercial, and sales partners, keep everyone to the plan, and keep the motion moving when a deal gets hot.
- Measurement orientation. You manage to operational metrics: deadline compliance, cycle time, rework, and compliance accuracy, not activity for its own sake, and you can show the data.
- Ten-plus years in proposal, pursuit, bid, or sales operations, with the most recent portion leading the function for a multi-product commercial organization.
- Why You Might Stand Out From Other Candidates:
- You have taken a fragmented, every-team-has-its-own-way operation and unified it into one model, with one set of rules for intake, prioritization, artifacts, and sign-offs.
- You can impose structure in the field (SLAs, gates, version control) without becoming the bottleneck. You understand that a good process beats last-minute heroics, and that the job is to enable the win, not to gatekeep it.
- You have governed a large content library back to health (current, owned, deduplicated, and actually used) and you have the before-and-after to show for it.
- You have run high-stakes, fast-turnaround submissions (the 48-hour, must-win kind) and kept them clean and compliant under pressure.
- You are comfortable building inside a function that is still being shaped, and you deliver value without waiting for the org chart to settle.
- You have worked across a multi-product, multi-capability portfolio, and you know how to keep submissions accurate and on-message when the content spans very different products and buyers.
We'll include these as list items.
Benefits: heading Benefits
then with bullet points from benefits description.
List:
- Flexible time off (FTO)
- 14 paid holidays
- Paid sick time
- Parental/new child leave
- Childcare & elder care assistance
- Adoption assistance
- Comprehensive health coverage
- 401(k)
- Tuition assistance
- Commuter benefits
- Professional development
- Employee recognition
- Charitable donation matching
- Health coaching and counseling
Also note "Time to recharge:", "Family well-being:", "Extra perks:" but we can keep as list items maybe with subheadings? But we need to use - for any list. Could keep as list items with description. We'll include each benefit as separate
- . Also include sentence "Epsilon benefits are subject to eligibility requirements and other terms." as a
after list.
Pay: heading
Pay
then with compensation range and bonus eligibility.
Compensation Range: USD $128,000.00 - USD $192,000.00/Annually. This role may also be eligible for bonus or incentive compensation.
We'll output as:
Pay
Compensation Range: USD $128,000.00 - USD $192,000.00/Annually. This role may also be eligible for bonus or incentive compensation
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Click here to view how Epsilon transforms marketing..." maybe that's extra but not boilerplate? It's a link; maybe keep? It's not essential but could be considered extra. Probably remove as it's not substantive about role. Also remove "Additional Information" maybe keep company description? The overview includes company description; we can keep that as part of About the role or Overview. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have sections: About the role (maybe from Overview Company Description), Responsibilities, Qualifications, Benefits, Pay. Possibly also "Skills" not present. We'll not create empty sections. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include details from responsibilities, qualifications, benefits, compensation range. We must not include boilerplate like EEO, accommodations, etc. Also remove "Additional Information" maybe but we can keep company description as part of About the role. We need to format responsibilities as list items. The responsibilities section includes many bullet-like sentences. We'll convert each sentence or clause into
About the role
... overview company description ...
We need to include the overview company description text: "Overview Company Description Pursuit Operations is the engine that keeps Epsilon's pursuits moving. It exists to run a disciplined, repeatable pursuit motion so that every RFP and major pursuit is organized, on time, compliant, and client-ready. The function owns the workflow, the submission mechanics, the content library, and the process governance that turn a pipeline of opportunities into clean, high-quality client submissions. The work is measured against missed deadlines, compliance accuracy, rework, and the time it takes to move from intake to a client-ready package. Solutions at Epsilon is moving from a case-by-case, RFP-support posture to a single operating model, and Pursuit Operations is the backbone of that shift. This role builds and runs the system: clear intake paths with prioritization and SLAs, standard stages and required artifacts, a governed content library, and post-pursuit debriefs that feed improvements back into the process. The goal is a motion Sales can count on, with clear ownership and clean handoffs, that scales as the business grows. This is a hands-on operating role, not a manage-from-above seat. The Senior Director sets the standard and also runs the tracker, enforces the deadlines, and holds the quality bar on submissions. The role leads the Pursuit Operations team and develops it, while staying close enough to the work to catch the missed owner, the stale content, or the compliance gap before it reaches a client. The role reports to the leader of the Solutions organization and partners daily with Solutions Consulting, Sales Engineering, Value Consulting, and Sales. Pursuit Operations enables pursuits rather than owning them: it does not set solution strategy, scope, or feasibility, and it does not own pricing or the client narrative. Its mandate is to make the motion fast, clean, and reliable, and to be a growth enabler, never a bottleneck." We'll put that in. Then Responsibilities: heading
Responsibilities
then- with each bullet.
We need to extract bullet points from "Responsibilities What You'll Achieve ..." and "In This Role, You Will". Let's list them:
- You will run the pursuit engine for Epsilon's Solutions organization, hands-on.
- You will build and operate the intake, workflow, submission, content, and governance systems that make every meaningful pursuit organized, on time, and client-ready, and you will lead the team that runs them.
- Orchestrate pursuit workflow end to end.
- Own the timelines, achievements, routing, reminders, and partner concerns for every active pursuit, so nothing slips.
- Run clear intake paths with prioritization, tiering, and SLAs, so each pursuit gets the right level of coverage and capacity is protected.
- Own bid mechanics and submission quality. Make sure submission requirements, compliance checks, formatting standards, portal uploads, and final packaging are buttoned up on every pursuit. The standard is zero missed deadlines and clean, compliant submissions.
- Run content assembly and version control. Maintain a single source of truth for each pursuit, with document hygiene, controlled edits, a clear final-release process, and QA, so the team never loses time to versioning chaos or sends the wrong file.
- Build and govern the reusable content system. Stand up and maintain a library of approved modules, product descriptions, proof points, case studies, language, and boilerplate, with named owners and a freshness process, so the team assembles from current, approved content rather than reinventing it each time.
- Govern the pursuit process. Define and enforce standard stages, required artifacts, intake fields, and stage gates, and run post-pursuit debriefs that capture what worked, what did not, and the top changes to process, templates, and content for next time.
- Build the operating model, not just run today's queue. Move the function from custom heroics to a repeatable system. Use standard artifacts, clear rules of engagement, and a motion that flexes from a quick advisory check to a drop-everything, must-win pursuit without changing the rules.
- Lead and develop the Pursuit Operations team. Set clear roles and ownership, coach the team, and set the standard on operational rigor, while keeping the function lean and close to the work.
- Coordinate across the pursuit. Support Solutions Consulting and Sales with packaging the client-ready story, support Sales Engineering by coordinating technical sections and accurate insertion of responses, and keep Sales on top of deadlines and collaborator coordination.
- Measure and improve the motion. Track missed deadlines, compliance accuracy, rework and version churn, and cycle time from intake to client-ready package, and use post-pursuit debriefs to drive the system forward.
We'll put each as
- .
Qualifications: heading
Qualifications
then- with bullet points from "What you'll bring with you:" and "Why You Might Stand Out From Other Candidates". Also include "Ten-plus years..." etc.
Let's list:
- Deep proposal and pursuit operations leadership. You have run RFP, bid, or pursuit operations for a sales or pre-sales organization, and you have owned the workflow, submission quality, and content behind it. You know what it takes to land complex submissions on time, every time.
- Operating-model and process design. You have built intake paths, SLAs, stage gates, and governance from the ground up, and turned an ad-hoc, case-by-case function into a repeatable system that people actually follow.
- Content library and knowledge management. You have established and managed a reusable content or proposal library at scale. You implemented ownership models and freshness standards. Ideally, this was on a platform like Responsive (RFPIO), Loopio, or a similar system.
- Hands-on operational rigor. You run the tracker yourself. You are the person who notices the unassigned item, the stale answer, or the compliance gap, and closes it before it becomes a problem. You hold deadlines without drama.
- People leadership. You have led and developed an operations, proposal, or pursuit team, set clear ownership, and raised the standard of work without adding bureaucracy.
- Cross-functional orchestration under deadline pressure. You coordinate across solutions, technical, commercial, and sales partners, keep everyone to the plan, and keep the motion moving when a deal gets hot.
- Measurement orientation. You manage to operational metrics: deadline compliance, cycle time, rework, and compliance accuracy, not activity for its own sake, and you can show the data.
- Ten-plus years in proposal, pursuit, bid, or sales operations, with the most recent portion leading the function for a multi-product commercial organization.
- Why You Might Stand Out From Other Candidates:
- You have taken a fragmented, every-team-has-its-own-way operation and unified it into one model, with one set of rules for intake, prioritization, artifacts, and sign-offs.
- You can impose structure in the field (SLAs, gates, version control) without becoming the bottleneck. You understand that a good process beats last-minute heroics, and that the job is to enable the win, not to gatekeep it.
- You have governed a large content library back to health (current, owned, deduplicated, and actually used) and you have the before-and-after to show for it.
- You have run high-stakes, fast-turnaround submissions (the 48-hour, must-win kind) and kept them clean and compliant under pressure.
- You are comfortable building inside a function that is still being shaped, and you deliver value without waiting for the org chart to settle.
- You have worked across a multi-product, multi-capability portfolio, and you know how to keep submissions accurate and on-message when the content spans very different products and buyers.
We'll include these as list items.
Benefits: heading
- for any list. Could keep as list items with description. We'll include each benefit as separate
- . Also include sentence "Epsilon benefits are subject to eligibility requirements and other terms." as a
after list. Pay: heading
Pay
thenwith compensation range and bonus eligibility. Compensation Range: USD $128,000.00 - USD $192,000.00/Annually. This role may also be eligible for bonus or incentive compensation. We'll output as:
Pay
Compensation Range: USD $128,000.00 - USD $192,000.00/Annually. This role may also be eligible for bonus or incentive compensation
Benefits
then- with bullet points from benefits description.
List:
- Flexible time off (FTO)
- 14 paid holidays
- Paid sick time
- Parental/new child leave
- Childcare & elder care assistance
- Adoption assistance
- Comprehensive health coverage
- 401(k)
- Tuition assistance
- Commuter benefits
- Professional development
- Employee recognition
- Charitable donation matching
- Health coaching and counseling
Also note "Time to recharge:", "Family well-being:", "Extra perks:" but we can keep as list items maybe with subheadings? But we need to use