Senior Renewals Specialist
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). 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:
- OUR MISSION (some description)
- About Us (description)
- CORE VALUES (list of values)
- YOUR IMPACT (description of responsibilities)
- Your Experience (requirements/qualifications)
- Also maybe "If you like growth..." (some fluff)
- THE LEGAL BIT (EEO boilerplate) -> remove.
We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can choose headings that match content: "About the role" could encompass mission/about us? But we need to preserve all substantive info. Could create sections: About the role (mission + about us), Responsibilities (YOUR IMPACT), Requirements (Your Experience), Qualifications (maybe same as requirements?), Skills (maybe from experience?), Benefits (none given), Pay (none), Schedule (none). Since no explicit benefits/pay/schedule, we should not create those sections.
We need to avoid filler. So we will include sections: About the role, Responsibilities, Requirements, Qualifications, Skills maybe.
But we must not repeat headings with no content. So we need to decide which headings have substantive content.
Let's extract content:
OUR MISSION: "At Redwood, we empower our customers with lights-out automation for their mission-critical business processes."
About Us: "Redwood Software is the leading orchestration platform for the autonomous enterprise, driving business transformation at the lowest total cost of ownership. Redwood empowers organizations to intelligently automate and orchestrate mission-critical business and IT processes across complex ERP, hybrid cloud, data and emerging agentic AI systems. Through its SaaS-first automation fabric—with AI embedded across the automation lifecycle—Redwood accelerates the path to autonomous operations. Backed by 30 years of experience and trusted by more than 50% of the Fortune 50, Redwood helps organizations unlock human potential to focus on innovation, growth and what’s next."
CORE VALUES: list: "One Team. One Redwood", "Make Your Own Weather", "Obsess over Customer Success", "Work the Problem", "Be Curious", "Own the Outcome", "Respect Each Other". These are values.
YOUR IMPACT: long paragraph describing responsibilities.
Your Experience: list of requirements: "5+ years of experience in renewals, account management, or customer success within a technology company. Experience managing multiple renewal opportunities concurrently in a high-velocity environment while maintaining strong attention to detail. Familiarity with Salesforce or another CRM, with the ability to quickly learn new sales automation tools. Strong problem-solving skills and a demonstrated ability to navigate complex customer and internal challenges. Excellent organizational skills with the ability to prioritize and manage dozens of opportunities simultaneously. Excellent written and verbal communication skills, with the ability to communicate complex information clearly and effectively. Demonstrated reliability, responsibility, and exceptional attention to detail. Bachelor’s degree or equivalent experience required. Business proficiency in English required."
Also "If you like growth and working with happy, enthusiastic over-achievers, you'll enjoy your career with us!" That's fluff but could be included maybe as part of About the role? It's not essential but could be kept as prose.
We need to remove legal boilerplate.
Thus we can structure:
About the role
OUR MISSION text + About Us text combined? Could be two paragraphs.
Responsibilities
YOUR IMPACT text (maybe break into
- for each duty? The instruction: Use
- for any list of duties/requirements/benefits. The YOUR IMPACT is a paragraph with many duties separated by periods. Could we split into list items? It says "any list of duties/requirements/benefits". The text is not explicitly a list but contains many duties. We could convert each sentence into a list item for clarity. That would be a list of duties. That seems appropriate.
Similarly for Requirements: we can make a list.
Qualifications: maybe same as requirements? Could combine.
Skills: maybe list of skills from requirements.
But we need to avoid duplication. Perhaps we can have sections: About the role (mission/about us), Responsibilities (list), Requirements (list), Qualifications (list), Skills (list). However that may be many thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So we should combine where possible.
Maybe we can have: About the role (mission/about us), Responsibilities (list), Requirements & Qualifications (combined list), Skills (maybe embedded). But we need to follow heading names exactly from the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can omit those we don't have content for.
We need to decide which sections have real specific content.
- About the role: we have mission and about us => substantive.
- Responsibilities: we have YOUR IMPACT => substantive.
- Requirements: we have Your Experience => substantive.
- Qualifications: maybe we could treat Bachelor's degree etc as qualifications. Could be separate but could also be part of Requirements. Since we have both, we could split: Requirements (experience, skills) and Qualifications (education, language proficiency). That would be two sections.
- Skills: we could list specific skills like Salesforce familiarity, problem-solving, organizational, communication, reliability, attention to detail. Could be separate but could be part of Requirements.
Given we want few substantive sections, maybe we combine Requirements and Qualifications into one section called Requirements (or Qualifications). But we need to use heading exactly as given; we can choose either. Let's make one section "Requirements" that includes experience, education, language proficiency. Then we could omit Qualifications.
Skills: we could omit if covered.
Thus final sections: About the role, Responsibilities, Requirements.
Now we need to format content.
About the role: two paragraphs: mission and about us.
Responsibilities: list of duties from YOUR IMPACT. Let's split sentences:
- Own the end-to-end renewal process for high-value accounts and manage a high volume of customer renewals through the sales cycle.
- Identify upsell and cross-sell opportunities throughout the renewal process to maximize revenue.
- Proactively identify renewal risks, engage stakeholders across customer organizations, and develop creative solutions to unblock deals.
- Prepare and deliver accurate quotes and contracts, including transactions involving complex pricing structures or custom terms.
- Manage price negotiations and navigate procurement processes for larger enterprise deals.
- Act as the point of escalation when renewals encounter obstacles, including pricing exceptions, contract negotiations, and procurement delays.
- Coordinate with Sales, Finance, Legal, Customer Operations, and other cross-functional teams to resolve renewal challenges.
- Forecast renewals, analyze account health trends, and develop proactive strategies to support retention and growth across the assigned book of business.
- Track and analyze customer churn, renewal delays, and objections, providing actionable customer feedback to Product and Engineering teams.
- Collaborate closely with Finance, Order Administration, and other internal teams to align on account strategy and streamline the renewal process.
- Manage a high volume of customer communications across email and calls while maintaining accuracy, responsiveness, and attention to detail.
- Engage confidently with senior decision-makers using clear, concise, and consultative communication to build trust and accelerate decision-making.
That seems comprehensive.
Requirements: list from Your Experience:
- 5+ years of experience in renewals, account management, or customer success within a technology company.
- Experience managing multiple renewal opportunities concurrently in a high-velocity environment while maintaining strong attention to detail.
- Familiarity with Salesforce or another CRM, with the ability to quickly learn new sales automation tools.
- Strong problem-solving skills and a demonstrated ability to navigate complex customer and internal challenges.
- Excellent organizational skills with the ability to prioritize and manage dozens of opportunities simultaneously.
- Excellent written and verbal communication skills, with the ability to communicate complex information clearly and effectively.
- Demonstrated reliability, responsibility, and exceptional attention to detail.
- Bachelor’s degree or equivalent experience required.
- Business proficiency in English required.
We could also include the line "If you like growth and working with happy, enthusiastic over-achievers, you'll enjoy your career with us!" but that's fluff; maybe we can include as a paragraph under About the role or after Requirements? It's not essential but could be kept as prose. However it's not a duty/requirement; it's more cultural. Could be included in About the role as a final paragraph.
We must not include legal boilerplate.
Thus final HTML:
About the role
At Redwood, we empower our customers with lights-out automation for their mission-critical business processes.
Redwood Software is the leading orchestration platform for the autonomous enterprise, driving business transformation at the lowest total cost of ownership. Redwood empowers organizations to intelligently automate and orchestrate mission-critical business and IT processes across complex ERP, hybrid cloud, data and emerging agentic AI systems. Through its SaaS-first automation fabric—with AI embedded across the automation lifecycle—Redwood accelerates the path to autonomous operations. Backed by 30 years of experience and trusted by more than 50% of the Fortune 50, Redwood helps organizations unlock human potential to focus on innovation, growth and what’s next.
If you like growth and working with happy, enthusiastic over-achievers, you'll enjoy your career with us!
Responsibilities
- Own the end-to-end renewal process for high-value accounts and manage a high volume of customer renewals through the sales cycle.
- Identify upsell and cross-sell opportunities throughout the renewal process to maximize revenue.
- Proactively identify renewal risks, engage stakeholders across customer organizations, and develop creative solutions to unblock deals.
- Prepare and deliver accurate quotes and contracts, including transactions involving complex pricing structures or custom terms.
- Manage price negotiations and navigate procurement processes for larger enterprise deals.
- Act as the point of escalation when renewals encounter obstacles, including pricing exceptions, contract negotiations, and procurement delays.
- Coordinate with Sales, Finance, Legal, Customer Operations, and other cross-functional teams to resolve renewal challenges.
- Forecast renewals, analyze account health trends, and develop proactive strategies to support retention and growth across the assigned book of business.
- Track and analyze customer churn, renewal delays, and objections, providing actionable customer feedback to Product and Engineering teams.
- Collaborate closely with Finance, Order Administration, and other internal teams to align on account strategy and streamline the renewal process.
- Manage a high volume of customer communications across email and calls while maintaining accuracy, responsiveness, and attention to detail
for prose. Do NOT repeat the job title as a heading (the page already shows it). 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: - OUR MISSION (some description) - About Us (description) - CORE VALUES (list of values) - YOUR IMPACT (description of responsibilities) - Your Experience (requirements/qualifications) - Also maybe "If you like growth..." (some fluff) - THE LEGAL BIT (EEO boilerplate) -> remove. We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose headings that match content: "About the role" could encompass mission/about us? But we need to preserve all substantive info. Could create sections: About the role (mission + about us), Responsibilities (YOUR IMPACT), Requirements (Your Experience), Qualifications (maybe same as requirements?), Skills (maybe from experience?), Benefits (none given), Pay (none), Schedule (none). Since no explicit benefits/pay/schedule, we should not create those sections. We need to avoid filler. So we will include sections: About the role, Responsibilities, Requirements, Qualifications, Skills maybe. But we must not repeat headings with no content. So we need to decide which headings have substantive content. Let's extract content: OUR MISSION: "At Redwood, we empower our customers with lights-out automation for their mission-critical business processes." About Us: "Redwood Software is the leading orchestration platform for the autonomous enterprise, driving business transformation at the lowest total cost of ownership. Redwood empowers organizations to intelligently automate and orchestrate mission-critical business and IT processes across complex ERP, hybrid cloud, data and emerging agentic AI systems. Through its SaaS-first automation fabric—with AI embedded across the automation lifecycle—Redwood accelerates the path to autonomous operations. Backed by 30 years of experience and trusted by more than 50% of the Fortune 50, Redwood helps organizations unlock human potential to focus on innovation, growth and what’s next." CORE VALUES: list: "One Team. One Redwood", "Make Your Own Weather", "Obsess over Customer Success", "Work the Problem", "Be Curious", "Own the Outcome", "Respect Each Other". These are values. YOUR IMPACT: long paragraph describing responsibilities. Your Experience: list of requirements: "5+ years of experience in renewals, account management, or customer success within a technology company. Experience managing multiple renewal opportunities concurrently in a high-velocity environment while maintaining strong attention to detail. Familiarity with Salesforce or another CRM, with the ability to quickly learn new sales automation tools. Strong problem-solving skills and a demonstrated ability to navigate complex customer and internal challenges. Excellent organizational skills with the ability to prioritize and manage dozens of opportunities simultaneously. Excellent written and verbal communication skills, with the ability to communicate complex information clearly and effectively. Demonstrated reliability, responsibility, and exceptional attention to detail. Bachelor’s degree or equivalent experience required. Business proficiency in English required." Also "If you like growth and working with happy, enthusiastic over-achievers, you'll enjoy your career with us!" That's fluff but could be included maybe as part of About the role? It's not essential but could be kept as prose. We need to remove legal boilerplate. Thus we can structure:
About the role
OUR MISSION text + About Us text combined? Could be two paragraphs.
Responsibilities
YOUR IMPACT text (maybe break into
- for each duty? The instruction: Use
- for any list of duties/requirements/benefits. The YOUR IMPACT is a paragraph with many duties separated by periods. Could we split into list items? It says "any list of duties/requirements/benefits". The text is not explicitly a list but contains many duties. We could convert each sentence into a list item for clarity. That would be a list of duties. That seems appropriate.
Similarly for Requirements: we can make a list.
Qualifications: maybe same as requirements? Could combine.
Skills: maybe list of skills from requirements.
But we need to avoid duplication. Perhaps we can have sections: About the role (mission/about us), Responsibilities (list), Requirements (list), Qualifications (list), Skills (list). However that may be many thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So we should combine where possible.
Maybe we can have: About the role (mission/about us), Responsibilities (list), Requirements & Qualifications (combined list), Skills (maybe embedded). But we need to follow heading names exactly from the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can omit those we don't have content for.
We need to decide which sections have real specific content.
- About the role: we have mission and about us => substantive.
- Responsibilities: we have YOUR IMPACT => substantive.
- Requirements: we have Your Experience => substantive.
- Qualifications: maybe we could treat Bachelor's degree etc as qualifications. Could be separate but could also be part of Requirements. Since we have both, we could split: Requirements (experience, skills) and Qualifications (education, language proficiency). That would be two sections.
- Skills: we could list specific skills like Salesforce familiarity, problem-solving, organizational, communication, reliability, attention to detail. Could be separate but could be part of Requirements.
Given we want few substantive sections, maybe we combine Requirements and Qualifications into one section called Requirements (or Qualifications). But we need to use heading exactly as given; we can choose either. Let's make one section "Requirements" that includes experience, education, language proficiency. Then we could omit Qualifications.
Skills: we could omit if covered.
Thus final sections: About the role, Responsibilities, Requirements.
Now we need to format content.
About the role: two paragraphs: mission and about us.
Responsibilities: list of duties from YOUR IMPACT. Let's split sentences:
- Own the end-to-end renewal process for high-value accounts and manage a high volume of customer renewals through the sales cycle.
- Identify upsell and cross-sell opportunities throughout the renewal process to maximize revenue.
- Proactively identify renewal risks, engage stakeholders across customer organizations, and develop creative solutions to unblock deals.
- Prepare and deliver accurate quotes and contracts, including transactions involving complex pricing structures or custom terms.
- Manage price negotiations and navigate procurement processes for larger enterprise deals.
- Act as the point of escalation when renewals encounter obstacles, including pricing exceptions, contract negotiations, and procurement delays.
- Coordinate with Sales, Finance, Legal, Customer Operations, and other cross-functional teams to resolve renewal challenges.
- Forecast renewals, analyze account health trends, and develop proactive strategies to support retention and growth across the assigned book of business.
- Track and analyze customer churn, renewal delays, and objections, providing actionable customer feedback to Product and Engineering teams.
- Collaborate closely with Finance, Order Administration, and other internal teams to align on account strategy and streamline the renewal process.
- Manage a high volume of customer communications across email and calls while maintaining accuracy, responsiveness, and attention to detail.
- Engage confidently with senior decision-makers using clear, concise, and consultative communication to build trust and accelerate decision-making.
That seems comprehensive.
Requirements: list from Your Experience:
- 5+ years of experience in renewals, account management, or customer success within a technology company.
- Experience managing multiple renewal opportunities concurrently in a high-velocity environment while maintaining strong attention to detail.
- Familiarity with Salesforce or another CRM, with the ability to quickly learn new sales automation tools.
- Strong problem-solving skills and a demonstrated ability to navigate complex customer and internal challenges.
- Excellent organizational skills with the ability to prioritize and manage dozens of opportunities simultaneously.
- Excellent written and verbal communication skills, with the ability to communicate complex information clearly and effectively.
- Demonstrated reliability, responsibility, and exceptional attention to detail.
- Bachelor’s degree or equivalent experience required.
- Business proficiency in English required.
We could also include the line "If you like growth and working with happy, enthusiastic over-achievers, you'll enjoy your career with us!" but that's fluff; maybe we can include as a paragraph under About the role or after Requirements? It's not essential but could be kept as prose. However it's not a duty/requirement; it's more cultural. Could be included in About the role as a final paragraph.
We must not include legal boilerplate.
Thus final HTML:
About the role
At Redwood, we empower our customers with lights-out automation for their mission-critical business processes.
Redwood Software is the leading orchestration platform for the autonomous enterprise, driving business transformation at the lowest total cost of ownership. Redwood empowers organizations to intelligently automate and orchestrate mission-critical business and IT processes across complex ERP, hybrid cloud, data and emerging agentic AI systems. Through its SaaS-first automation fabric—with AI embedded across the automation lifecycle—Redwood accelerates the path to autonomous operations. Backed by 30 years of experience and trusted by more than 50% of the Fortune 50, Redwood helps organizations unlock human potential to focus on innovation, growth and what’s next.
If you like growth and working with happy, enthusiastic over-achievers, you'll enjoy your career with us!
Responsibilities
- Own the end-to-end renewal process for high-value accounts and manage a high volume of customer renewals through the sales cycle.
- Identify upsell and cross-sell opportunities throughout the renewal process to maximize revenue.
- Proactively identify renewal risks, engage stakeholders across customer organizations, and develop creative solutions to unblock deals.
- Prepare and deliver accurate quotes and contracts, including transactions involving complex pricing structures or custom terms.
- Manage price negotiations and navigate procurement processes for larger enterprise deals.
- Act as the point of escalation when renewals encounter obstacles, including pricing exceptions, contract negotiations, and procurement delays.
- Coordinate with Sales, Finance, Legal, Customer Operations, and other cross-functional teams to resolve renewal challenges.
- Forecast renewals, analyze account health trends, and develop proactive strategies to support retention and growth across the assigned book of business.
- Track and analyze customer churn, renewal delays, and objections, providing actionable customer feedback to Product and Engineering teams.
- Collaborate closely with Finance, Order Administration, and other internal teams to align on account strategy and streamline the renewal process.
- Manage a high volume of customer communications across email and calls while maintaining accuracy, responsiveness, and attention to detail
- for any list of duties/requirements/benefits. The YOUR IMPACT is a paragraph with many duties separated by periods. Could we split into list items? It says "any list of duties/requirements/benefits". The text is not explicitly a list but contains many duties. We could convert each sentence into a list item for clarity. That would be a list of duties. That seems appropriate.
Similarly for Requirements: we can make a list.
Qualifications: maybe same as requirements? Could combine.
Skills: maybe list of skills from requirements.
But we need to avoid duplication. Perhaps we can have sections: About the role (mission/about us), Responsibilities (list), Requirements (list), Qualifications (list), Skills (list). However that may be many thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So we should combine where possible.
Maybe we can have: About the role (mission/about us), Responsibilities (list), Requirements & Qualifications (combined list), Skills (maybe embedded). But we need to follow heading names exactly from the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can omit those we don't have content for.
We need to decide which sections have real specific content.
- About the role: we have mission and about us => substantive.
- Responsibilities: we have YOUR IMPACT => substantive.
- Requirements: we have Your Experience => substantive.
- Qualifications: maybe we could treat Bachelor's degree etc as qualifications. Could be separate but could also be part of Requirements. Since we have both, we could split: Requirements (experience, skills) and Qualifications (education, language proficiency). That would be two sections.
- Skills: we could list specific skills like Salesforce familiarity, problem-solving, organizational, communication, reliability, attention to detail. Could be separate but could be part of Requirements.
Given we want few substantive sections, maybe we combine Requirements and Qualifications into one section called Requirements (or Qualifications). But we need to use heading exactly as given; we can choose either. Let's make one section "Requirements" that includes experience, education, language proficiency. Then we could omit Qualifications.
Skills: we could omit if covered.
Thus final sections: About the role, Responsibilities, Requirements.
Now we need to format content.
About the role: two paragraphs: mission and about us.
Responsibilities: list of duties from YOUR IMPACT. Let's split sentences:
- Own the end-to-end renewal process for high-value accounts and manage a high volume of customer renewals through the sales cycle.
- Identify upsell and cross-sell opportunities throughout the renewal process to maximize revenue.
- Proactively identify renewal risks, engage stakeholders across customer organizations, and develop creative solutions to unblock deals.
- Prepare and deliver accurate quotes and contracts, including transactions involving complex pricing structures or custom terms.
- Manage price negotiations and navigate procurement processes for larger enterprise deals.
- Act as the point of escalation when renewals encounter obstacles, including pricing exceptions, contract negotiations, and procurement delays.
- Coordinate with Sales, Finance, Legal, Customer Operations, and other cross-functional teams to resolve renewal challenges.
- Forecast renewals, analyze account health trends, and develop proactive strategies to support retention and growth across the assigned book of business.
- Track and analyze customer churn, renewal delays, and objections, providing actionable customer feedback to Product and Engineering teams.
- Collaborate closely with Finance, Order Administration, and other internal teams to align on account strategy and streamline the renewal process.
- Manage a high volume of customer communications across email and calls while maintaining accuracy, responsiveness, and attention to detail.
- Engage confidently with senior decision-makers using clear, concise, and consultative communication to build trust and accelerate decision-making.
That seems comprehensive.
Requirements: list from Your Experience:
- 5+ years of experience in renewals, account management, or customer success within a technology company.
- Experience managing multiple renewal opportunities concurrently in a high-velocity environment while maintaining strong attention to detail.
- Familiarity with Salesforce or another CRM, with the ability to quickly learn new sales automation tools.
- Strong problem-solving skills and a demonstrated ability to navigate complex customer and internal challenges.
- Excellent organizational skills with the ability to prioritize and manage dozens of opportunities simultaneously.
- Excellent written and verbal communication skills, with the ability to communicate complex information clearly and effectively.
- Demonstrated reliability, responsibility, and exceptional attention to detail.
- Bachelor’s degree or equivalent experience required.
- Business proficiency in English required.
We could also include the line "If you like growth and working with happy, enthusiastic over-achievers, you'll enjoy your career with us!" but that's fluff; maybe we can include as a paragraph under About the role or after Requirements? It's not essential but could be kept as prose. However it's not a duty/requirement; it's more cultural. Could be included in About the role as a final paragraph.
We must not include legal boilerplate.
Thus final HTML: