Account Manager, Mid-Market
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into 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.
We need to parse the posting.
The posting includes:
- About Aurora Solar (company description)
- About The Team
- About The Role (description)
- Your Impact (list of bullet-like sentences)
- What You Bring (requirements/qualifications)
- Nice to Haves (additional qualifications)
- What We Offer (benefits list with emojis)
- Where Aurorans are (locations)
- Compensation Philosophy (pay philosophy)
- Diversity statement (EEO) - we should remove EEO boilerplate.
- Accommodation statement (maybe also boilerplate) - remove.
We need to decide which sections to include: About the role (we have About The Role). Responsibilities (Your Impact). Requirements/Qualifications (What You Bring). Skills (maybe we can combine with Requirements? But we need separate sections only if content exists). Benefits (What We Offer). Pay (Compensation Philosophy). Schedule (maybe not present; there is no explicit schedule info). So we should not include Schedule unless present.
We must not repeat job title as heading. The job title is not given explicitly in the snippet; maybe it's "Scaled Account Manager" or similar but not present. So we ignore.
We need to preserve all substantive information. So we need to include company description? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It does not mention About the company or About the team. Should we include them? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive list. It says "include a section ONLY when the posting has real, specific content for it". It does not forbid other headings, but the examples are those. Probably we should stick to those headings. However, we need to preserve all substantive information; if we omit About the company and About the team, we lose info. But maybe we can incorporate that info under About the role? Not ideal. The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings like About the company. But the examples list typical sections. Might be okay to include About the company as a as well, but they didn't list it. However, they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we can add other headings like About the company, About the team if needed.
But we need to avoid boilerplate like EEO etc. So we will keep About Aurora Solar, About The Team, About The Role, Your Impact (Responsibilities), What You Bring (Requirements/Qualifications), Nice to Haves (maybe Skills?), What We Offer (Benefits), Compensation Philosophy (Pay). Where Aurorans are (maybe location info) could be included under About the company or a separate section like Locations. Not required but we can include as a short paragraph.
We must not include duplicated lines. Ensure we preserve all substantive info.
We need to format lists with - . For prose, use
.
We need to decide which content goes under which heading.
Let's extract:
About Aurora Solar paragraph: "Aurora is on a mission to create a future of solar for all. Our award-winning software puts the power of data and technology into the hands of every solar professional to make solar adoption simple and predictable. Our software has designed millions of solar projects so far, empowering solar companies to sell, design, and install residential and commercial solar arrays accurately, seamlessly, and at scale. We’ve been named one of "The Best Remote Companies" by BuiltIn.com and have been recognized for the second time as a Certified Green Business (CGB) with the city of San Francisco. We’re in this together to support the world’s transition to solar."
About The Team: "The Scaled AM team is built on a simple belief: when our customers win, we win. We obsess over customer outcomes, not activity metrics or internal optics, and we hold ourselves accountable to the impact we actually deliver. We move fast, share what's working, and push each other to build smarter, not just work harder."
About The Role: "In this role, you'll own a high-volume portfolio of solar professionals in Aurora's Scaled Account Management segment where you will execute the account management playbooks, systems and processes that let you serve them well at scale. You'll drive retention, early renewals, and expansion across a large book of business by pairing sharp account management instincts with a real appetite for leveraging AI agents, automated workflows, and operational design. You won't just use the tools, you'll help shape them. This is a role where your account management skills and your systems thinking sharpen each other. The customers are real, the relationships matter, and the workflows you execute directly determine how well you can serve them."
Your Impact (list of bullet-like sentences):
- Own and grow a high-volume portfolio of accounts in the Scaled AM segment, driving retention, early renewal upsells, and expansion through a combination of proactive outreach and AI-assisted workflows.
- Serve as the primary relationship owner for customers under approximately $25K to $50K ARR, ensuring every account receives timely, relevant engagement, even at scale.
- Operationalize and continuously improve AI-assisted workflows that support customer onboarding, ramp acceleration, health monitoring, and upsell identification.
- Identify and act on ramping risk signals early, ensuring new logos reach their utilization thresholds within the ramp window.
- Surface and qualify early upsell opportunities by detecting usage-based signals and coordinating with Account Executives and Enterprise Account Managers on expansion motions.
- Maintain clean, structured Salesforce data across the Scaled AM segment, including contact/account hygiene, renewal timelines, so that AI-driven workflows operate on reliable inputs.
- Partner with GTM Ops to scope, test, and refine the tooling and field structures that power scaled customer intelligence.
- Document workflows, playbooks, and operational processes for repeatable, low-maintenance assets the team can build on.
- Identify recurring customer questions, content gaps, and failed resolution patterns, and route them to the right internal owner (Support, Product, Sales) through a structured process.
- Advocate for customers internally while contributing to Aurora's broader go-to-market strategy and product feedback loops.
What You Bring (requirements):
- 2+ years of experience in Account Management, Customer Success, or Sales, preferably in a SaaS or clean tech environment.
- Proven ability to manage a high-volume book of business with strong retention and upsell results, even with limited one-on-one customer time.
- Comfort building and executing structured workflows — you don't just manage accounts, you build systems to manage them better.
- Experience with Salesforce or similar CRM tools; you understand why data hygiene matters and you maintain it as a daily habit, not a quarterly cleanup.
- Ability to identify account health signals — usage data, engagement trends, renewal timelines — and act on them before risk becomes obvious.
- Strong written communication skills; you can craft outreach that feels personal at scale and represent Aurora's voice clearly across a large customer base.
- Collaborative instincts — you're comfortable working cross-functionally with Sales, RevOps, Support, Product, and GTM Ops to get things done for your customers.
- Organized, self-directed, and able to manage competing priorities across a complex portfolio without letting things fall through the cracks.
Nice to Haves:
- Experience working with AI tools in a professional workflow context — drafting, summarizing, routing, or automating repeatable tasks.
- Familiarity with AI agent platforms or automation tools and an interest in building workflows, not just using them.
- Background in solar, clean energy, or construction tech — understanding of the contractor and installer market is a real advantage.
- Prior experience in a high-growth SaaS environment where you had to build processes, not just follow them.
- Ability to scope operational needs clearly and partner with technical or ops stakeholders to implement them.
- Familiarity with credit-based, usage-based, or tiered SaaS pricing models.
- Experience contributing to internal documentation, playbooks, or knowledge bases — you know how to write something once so the team benefits from it repeatedly.
What We Offer (benefits):
- 🏖️Flexible PTO
- 🍼Parental Leave
- 💰WFH Stipend
- 🏢 Coworking Stipend
- ☀️Energize Fridays
- 📶Connectivity Stipend
- Learning & Development
- 🩺Medical, Dental, and Vision
- Please take a look at our U.S. Benefits Booklet for a deeper dive into our offerings
Where Aurorans are: "Aurora currently has teams within the US, Canada, Poland, and Germany with additional locations on the horizon. We’re united in our work to support the world’s transition to solar!"
Compensation Philosophy: paragraph about pay ranges anchored to median, new hires at start of range, etc.
EEO statement: remove.
Accommodation statement: remove.
Now we need to map to headings.
Possible sections:
- About the company (maybe
About Aurora Solar
)
- About the team (About the Team
)
- About the role (About the Role
)
- Responsibilities (Responsibilities
) using Your Impact bullets.
- Requirements (Requirements
) using What You Bring.
- Skills (Skills
) maybe we can put Nice to Haves under Skills? Or we could have Qualifications and Skills separate. The instruction mentions Qualifications and Skills as possible headings. We have Requirements (which could be Qualifications) and Nice to Haves (which could be Skills). Let's decide: Use Qualifications
for What You Bring (requirements). Use Skills
for Nice to Haves (nice-to-have skills). Or we could combine Requirements and Skills into one section but better to follow instruction: they listed Requirements, Qualifications, Skills as separate. We have content for Requirements (maybe Qualifications) and Skills (nice-to-haves). We'll make Qualifications for What You Bring, Skills for Nice to Haves.
- Benefits (Benefits
) using What We Offer.
- Pay (Pay
) using Compensation Philosophy.
- Location (Locations
) maybe not in list but we can include as Locations
or incorporate under About the company. Since not in examples but we can add.
- Schedule: not present, so omit.
We must not include filler like "commensurate with experience". Not present.
We need to ensure we don't include boilerplate like EEO etc.
Now produce HTML fragment.
We'll wrap each section in
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into 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. We need to parse the posting. The posting includes: - About Aurora Solar (company description) - About The Team - About The Role (description) - Your Impact (list of bullet-like sentences) - What You Bring (requirements/qualifications) - Nice to Haves (additional qualifications) - What We Offer (benefits list with emojis) - Where Aurorans are (locations) - Compensation Philosophy (pay philosophy) - Diversity statement (EEO) - we should remove EEO boilerplate. - Accommodation statement (maybe also boilerplate) - remove. We need to decide which sections to include: About the role (we have About The Role). Responsibilities (Your Impact). Requirements/Qualifications (What You Bring). Skills (maybe we can combine with Requirements? But we need separate sections only if content exists). Benefits (What We Offer). Pay (Compensation Philosophy). Schedule (maybe not present; there is no explicit schedule info). So we should not include Schedule unless present. We must not repeat job title as heading. The job title is not given explicitly in the snippet; maybe it's "Scaled Account Manager" or similar but not present. So we ignore. We need to preserve all substantive information. So we need to include company description? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It does not mention About the company or About the team. Should we include them? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive list. It says "include a section ONLY when the posting has real, specific content for it". It does not forbid other headings, but the examples are those. Probably we should stick to those headings. However, we need to preserve all substantive information; if we omit About the company and About the team, we lose info. But maybe we can incorporate that info under About the role? Not ideal. The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings like About the company. But the examples list typical sections. Might be okay to include About the company as a as well, but they didn't list it. However, they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we can add other headings like About the company, About the team if needed.
But we need to avoid boilerplate like EEO etc. So we will keep About Aurora Solar, About The Team, About The Role, Your Impact (Responsibilities), What You Bring (Requirements/Qualifications), Nice to Haves (maybe Skills?), What We Offer (Benefits), Compensation Philosophy (Pay). Where Aurorans are (maybe location info) could be included under About the company or a separate section like Locations. Not required but we can include as a short paragraph.
We must not include duplicated lines. Ensure we preserve all substantive info.
We need to format lists with - . For prose, use
.
We need to decide which content goes under which heading.
Let's extract:
About Aurora Solar paragraph: "Aurora is on a mission to create a future of solar for all. Our award-winning software puts the power of data and technology into the hands of every solar professional to make solar adoption simple and predictable. Our software has designed millions of solar projects so far, empowering solar companies to sell, design, and install residential and commercial solar arrays accurately, seamlessly, and at scale. We’ve been named one of "The Best Remote Companies" by BuiltIn.com and have been recognized for the second time as a Certified Green Business (CGB) with the city of San Francisco. We’re in this together to support the world’s transition to solar."
About The Team: "The Scaled AM team is built on a simple belief: when our customers win, we win. We obsess over customer outcomes, not activity metrics or internal optics, and we hold ourselves accountable to the impact we actually deliver. We move fast, share what's working, and push each other to build smarter, not just work harder."
About The Role: "In this role, you'll own a high-volume portfolio of solar professionals in Aurora's Scaled Account Management segment where you will execute the account management playbooks, systems and processes that let you serve them well at scale. You'll drive retention, early renewals, and expansion across a large book of business by pairing sharp account management instincts with a real appetite for leveraging AI agents, automated workflows, and operational design. You won't just use the tools, you'll help shape them. This is a role where your account management skills and your systems thinking sharpen each other. The customers are real, the relationships matter, and the workflows you execute directly determine how well you can serve them."
Your Impact (list of bullet-like sentences):
- Own and grow a high-volume portfolio of accounts in the Scaled AM segment, driving retention, early renewal upsells, and expansion through a combination of proactive outreach and AI-assisted workflows.
- Serve as the primary relationship owner for customers under approximately $25K to $50K ARR, ensuring every account receives timely, relevant engagement, even at scale.
- Operationalize and continuously improve AI-assisted workflows that support customer onboarding, ramp acceleration, health monitoring, and upsell identification.
- Identify and act on ramping risk signals early, ensuring new logos reach their utilization thresholds within the ramp window.
- Surface and qualify early upsell opportunities by detecting usage-based signals and coordinating with Account Executives and Enterprise Account Managers on expansion motions.
- Maintain clean, structured Salesforce data across the Scaled AM segment, including contact/account hygiene, renewal timelines, so that AI-driven workflows operate on reliable inputs.
- Partner with GTM Ops to scope, test, and refine the tooling and field structures that power scaled customer intelligence.
- Document workflows, playbooks, and operational processes for repeatable, low-maintenance assets the team can build on.
- Identify recurring customer questions, content gaps, and failed resolution patterns, and route them to the right internal owner (Support, Product, Sales) through a structured process.
- Advocate for customers internally while contributing to Aurora's broader go-to-market strategy and product feedback loops.
What You Bring (requirements):
- 2+ years of experience in Account Management, Customer Success, or Sales, preferably in a SaaS or clean tech environment.
- Proven ability to manage a high-volume book of business with strong retention and upsell results, even with limited one-on-one customer time.
- Comfort building and executing structured workflows — you don't just manage accounts, you build systems to manage them better.
- Experience with Salesforce or similar CRM tools; you understand why data hygiene matters and you maintain it as a daily habit, not a quarterly cleanup.
- Ability to identify account health signals — usage data, engagement trends, renewal timelines — and act on them before risk becomes obvious.
- Strong written communication skills; you can craft outreach that feels personal at scale and represent Aurora's voice clearly across a large customer base.
- Collaborative instincts — you're comfortable working cross-functionally with Sales, RevOps, Support, Product, and GTM Ops to get things done for your customers.
- Organized, self-directed, and able to manage competing priorities across a complex portfolio without letting things fall through the cracks.
Nice to Haves:
- Experience working with AI tools in a professional workflow context — drafting, summarizing, routing, or automating repeatable tasks.
- Familiarity with AI agent platforms or automation tools and an interest in building workflows, not just using them.
- Background in solar, clean energy, or construction tech — understanding of the contractor and installer market is a real advantage.
- Prior experience in a high-growth SaaS environment where you had to build processes, not just follow them.
- Ability to scope operational needs clearly and partner with technical or ops stakeholders to implement them.
- Familiarity with credit-based, usage-based, or tiered SaaS pricing models.
- Experience contributing to internal documentation, playbooks, or knowledge bases — you know how to write something once so the team benefits from it repeatedly.
What We Offer (benefits):
- 🏖️Flexible PTO
- 🍼Parental Leave
- 💰WFH Stipend
- 🏢 Coworking Stipend
- ☀️Energize Fridays
- 📶Connectivity Stipend
- Learning & Development
- 🩺Medical, Dental, and Vision
- Please take a look at our U.S. Benefits Booklet for a deeper dive into our offerings
Where Aurorans are: "Aurora currently has teams within the US, Canada, Poland, and Germany with additional locations on the horizon. We’re united in our work to support the world’s transition to solar!"
Compensation Philosophy: paragraph about pay ranges anchored to median, new hires at start of range, etc.
EEO statement: remove.
Accommodation statement: remove.
Now we need to map to headings.
Possible sections:
- About the company (maybe
About Aurora Solar
)
- About the team (About the Team
)
- About the role (About the Role
)
- Responsibilities (Responsibilities
) using Your Impact bullets.
- Requirements (Requirements
) using What You Bring.
- Skills (Skills
) maybe we can put Nice to Haves under Skills? Or we could have Qualifications and Skills separate. The instruction mentions Qualifications and Skills as possible headings. We have Requirements (which could be Qualifications) and Nice to Haves (which could be Skills). Let's decide: Use Qualifications
for What You Bring (requirements). Use Skills
for Nice to Haves (nice-to-have skills). Or we could combine Requirements and Skills into one section but better to follow instruction: they listed Requirements, Qualifications, Skills as separate. We have content for Requirements (maybe Qualifications) and Skills (nice-to-haves). We'll make Qualifications for What You Bring, Skills for Nice to Haves.
- Benefits (Benefits
) using What We Offer.
- Pay (Pay
) using Compensation Philosophy.
- Location (Locations
) maybe not in list but we can include as Locations
or incorporate under About the company. Since not in examples but we can add.
- Schedule: not present, so omit.
We must not include filler like "commensurate with experience". Not present.
We need to ensure we don't include boilerplate like EEO etc.
Now produce HTML fragment.
We'll wrap each section in
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we can add other headings like About the company, About the team if needed.
But we need to avoid boilerplate like EEO etc. So we will keep About Aurora Solar, About The Team, About The Role, Your Impact (Responsibilities), What You Bring (Requirements/Qualifications), Nice to Haves (maybe Skills?), What We Offer (Benefits), Compensation Philosophy (Pay). Where Aurorans are (maybe location info) could be included under About the company or a separate section like Locations. Not required but we can include as a short paragraph.
We must not include duplicated lines. Ensure we preserve all substantive info.
We need to format lists with - . For prose, use
.
We need to decide which content goes under which heading.
Let's extract:
About Aurora Solar paragraph: "Aurora is on a mission to create a future of solar for all. Our award-winning software puts the power of data and technology into the hands of every solar professional to make solar adoption simple and predictable. Our software has designed millions of solar projects so far, empowering solar companies to sell, design, and install residential and commercial solar arrays accurately, seamlessly, and at scale. We’ve been named one of "The Best Remote Companies" by BuiltIn.com and have been recognized for the second time as a Certified Green Business (CGB) with the city of San Francisco. We’re in this together to support the world’s transition to solar."
About The Team: "The Scaled AM team is built on a simple belief: when our customers win, we win. We obsess over customer outcomes, not activity metrics or internal optics, and we hold ourselves accountable to the impact we actually deliver. We move fast, share what's working, and push each other to build smarter, not just work harder."
About The Role: "In this role, you'll own a high-volume portfolio of solar professionals in Aurora's Scaled Account Management segment where you will execute the account management playbooks, systems and processes that let you serve them well at scale. You'll drive retention, early renewals, and expansion across a large book of business by pairing sharp account management instincts with a real appetite for leveraging AI agents, automated workflows, and operational design. You won't just use the tools, you'll help shape them. This is a role where your account management skills and your systems thinking sharpen each other. The customers are real, the relationships matter, and the workflows you execute directly determine how well you can serve them."
Your Impact (list of bullet-like sentences):
- Own and grow a high-volume portfolio of accounts in the Scaled AM segment, driving retention, early renewal upsells, and expansion through a combination of proactive outreach and AI-assisted workflows.
- Serve as the primary relationship owner for customers under approximately $25K to $50K ARR, ensuring every account receives timely, relevant engagement, even at scale.
- Operationalize and continuously improve AI-assisted workflows that support customer onboarding, ramp acceleration, health monitoring, and upsell identification.
- Identify and act on ramping risk signals early, ensuring new logos reach their utilization thresholds within the ramp window.
- Surface and qualify early upsell opportunities by detecting usage-based signals and coordinating with Account Executives and Enterprise Account Managers on expansion motions.
- Maintain clean, structured Salesforce data across the Scaled AM segment, including contact/account hygiene, renewal timelines, so that AI-driven workflows operate on reliable inputs.
- Partner with GTM Ops to scope, test, and refine the tooling and field structures that power scaled customer intelligence.
- Document workflows, playbooks, and operational processes for repeatable, low-maintenance assets the team can build on.
- Identify recurring customer questions, content gaps, and failed resolution patterns, and route them to the right internal owner (Support, Product, Sales) through a structured process.
- Advocate for customers internally while contributing to Aurora's broader go-to-market strategy and product feedback loops.
What You Bring (requirements):
- 2+ years of experience in Account Management, Customer Success, or Sales, preferably in a SaaS or clean tech environment.
- Proven ability to manage a high-volume book of business with strong retention and upsell results, even with limited one-on-one customer time.
- Comfort building and executing structured workflows — you don't just manage accounts, you build systems to manage them better.
- Experience with Salesforce or similar CRM tools; you understand why data hygiene matters and you maintain it as a daily habit, not a quarterly cleanup.
- Ability to identify account health signals — usage data, engagement trends, renewal timelines — and act on them before risk becomes obvious.
- Strong written communication skills; you can craft outreach that feels personal at scale and represent Aurora's voice clearly across a large customer base.
- Collaborative instincts — you're comfortable working cross-functionally with Sales, RevOps, Support, Product, and GTM Ops to get things done for your customers.
- Organized, self-directed, and able to manage competing priorities across a complex portfolio without letting things fall through the cracks.
Nice to Haves:
- Experience working with AI tools in a professional workflow context — drafting, summarizing, routing, or automating repeatable tasks.
- Familiarity with AI agent platforms or automation tools and an interest in building workflows, not just using them.
- Background in solar, clean energy, or construction tech — understanding of the contractor and installer market is a real advantage.
- Prior experience in a high-growth SaaS environment where you had to build processes, not just follow them.
- Ability to scope operational needs clearly and partner with technical or ops stakeholders to implement them.
- Familiarity with credit-based, usage-based, or tiered SaaS pricing models.
- Experience contributing to internal documentation, playbooks, or knowledge bases — you know how to write something once so the team benefits from it repeatedly.
What We Offer (benefits):
- 🏖️Flexible PTO
- 🍼Parental Leave
- 💰WFH Stipend
- 🏢 Coworking Stipend
- ☀️Energize Fridays
- 📶Connectivity Stipend
- Learning & Development
- 🩺Medical, Dental, and Vision
- Please take a look at our U.S. Benefits Booklet for a deeper dive into our offerings
Where Aurorans are: "Aurora currently has teams within the US, Canada, Poland, and Germany with additional locations on the horizon. We’re united in our work to support the world’s transition to solar!"
Compensation Philosophy: paragraph about pay ranges anchored to median, new hires at start of range, etc.
EEO statement: remove.
Accommodation statement: remove.
Now we need to map to headings.
Possible sections:
- About the company (maybe
About Aurora Solar
)
- About the team (About the Team
)
- About the role (About the Role
)
- Responsibilities (Responsibilities
) using Your Impact bullets.
- Requirements (Requirements
) using What You Bring.
- Skills (Skills
) maybe we can put Nice to Haves under Skills? Or we could have Qualifications and Skills separate. The instruction mentions Qualifications and Skills as possible headings. We have Requirements (which could be Qualifications) and Nice to Haves (which could be Skills). Let's decide: Use Qualifications
for What You Bring (requirements). Use Skills
for Nice to Haves (nice-to-have skills). Or we could combine Requirements and Skills into one section but better to follow instruction: they listed Requirements, Qualifications, Skills as separate. We have content for Requirements (maybe Qualifications) and Skills (nice-to-haves). We'll make Qualifications for What You Bring, Skills for Nice to Haves.
- Benefits (Benefits
) using What We Offer.
- Pay (Pay
) using Compensation Philosophy.
- Location (Locations
) maybe not in list but we can include as Locations
or incorporate under About the company. Since not in examples but we can add.
- Schedule: not present, so omit.
We must not include filler like "commensurate with experience". Not present.
We need to ensure we don't include boilerplate like EEO etc.
Now produce HTML fragment.
We'll wrap each section in
. We need to decide which content goes under which heading. Let's extract: About Aurora Solar paragraph: "Aurora is on a mission to create a future of solar for all. Our award-winning software puts the power of data and technology into the hands of every solar professional to make solar adoption simple and predictable. Our software has designed millions of solar projects so far, empowering solar companies to sell, design, and install residential and commercial solar arrays accurately, seamlessly, and at scale. We’ve been named one of "The Best Remote Companies" by BuiltIn.com and have been recognized for the second time as a Certified Green Business (CGB) with the city of San Francisco. We’re in this together to support the world’s transition to solar." About The Team: "The Scaled AM team is built on a simple belief: when our customers win, we win. We obsess over customer outcomes, not activity metrics or internal optics, and we hold ourselves accountable to the impact we actually deliver. We move fast, share what's working, and push each other to build smarter, not just work harder." About The Role: "In this role, you'll own a high-volume portfolio of solar professionals in Aurora's Scaled Account Management segment where you will execute the account management playbooks, systems and processes that let you serve them well at scale. You'll drive retention, early renewals, and expansion across a large book of business by pairing sharp account management instincts with a real appetite for leveraging AI agents, automated workflows, and operational design. You won't just use the tools, you'll help shape them. This is a role where your account management skills and your systems thinking sharpen each other. The customers are real, the relationships matter, and the workflows you execute directly determine how well you can serve them." Your Impact (list of bullet-like sentences): - Own and grow a high-volume portfolio of accounts in the Scaled AM segment, driving retention, early renewal upsells, and expansion through a combination of proactive outreach and AI-assisted workflows. - Serve as the primary relationship owner for customers under approximately $25K to $50K ARR, ensuring every account receives timely, relevant engagement, even at scale. - Operationalize and continuously improve AI-assisted workflows that support customer onboarding, ramp acceleration, health monitoring, and upsell identification. - Identify and act on ramping risk signals early, ensuring new logos reach their utilization thresholds within the ramp window. - Surface and qualify early upsell opportunities by detecting usage-based signals and coordinating with Account Executives and Enterprise Account Managers on expansion motions. - Maintain clean, structured Salesforce data across the Scaled AM segment, including contact/account hygiene, renewal timelines, so that AI-driven workflows operate on reliable inputs. - Partner with GTM Ops to scope, test, and refine the tooling and field structures that power scaled customer intelligence. - Document workflows, playbooks, and operational processes for repeatable, low-maintenance assets the team can build on. - Identify recurring customer questions, content gaps, and failed resolution patterns, and route them to the right internal owner (Support, Product, Sales) through a structured process. - Advocate for customers internally while contributing to Aurora's broader go-to-market strategy and product feedback loops. What You Bring (requirements): - 2+ years of experience in Account Management, Customer Success, or Sales, preferably in a SaaS or clean tech environment. - Proven ability to manage a high-volume book of business with strong retention and upsell results, even with limited one-on-one customer time. - Comfort building and executing structured workflows — you don't just manage accounts, you build systems to manage them better. - Experience with Salesforce or similar CRM tools; you understand why data hygiene matters and you maintain it as a daily habit, not a quarterly cleanup. - Ability to identify account health signals — usage data, engagement trends, renewal timelines — and act on them before risk becomes obvious. - Strong written communication skills; you can craft outreach that feels personal at scale and represent Aurora's voice clearly across a large customer base. - Collaborative instincts — you're comfortable working cross-functionally with Sales, RevOps, Support, Product, and GTM Ops to get things done for your customers. - Organized, self-directed, and able to manage competing priorities across a complex portfolio without letting things fall through the cracks. Nice to Haves: - Experience working with AI tools in a professional workflow context — drafting, summarizing, routing, or automating repeatable tasks. - Familiarity with AI agent platforms or automation tools and an interest in building workflows, not just using them. - Background in solar, clean energy, or construction tech — understanding of the contractor and installer market is a real advantage. - Prior experience in a high-growth SaaS environment where you had to build processes, not just follow them. - Ability to scope operational needs clearly and partner with technical or ops stakeholders to implement them. - Familiarity with credit-based, usage-based, or tiered SaaS pricing models. - Experience contributing to internal documentation, playbooks, or knowledge bases — you know how to write something once so the team benefits from it repeatedly. What We Offer (benefits): - 🏖️Flexible PTO - 🍼Parental Leave - 💰WFH Stipend - 🏢 Coworking Stipend - ☀️Energize Fridays - 📶Connectivity Stipend - Learning & Development - 🩺Medical, Dental, and Vision - Please take a look at our U.S. Benefits Booklet for a deeper dive into our offerings Where Aurorans are: "Aurora currently has teams within the US, Canada, Poland, and Germany with additional locations on the horizon. We’re united in our work to support the world’s transition to solar!" Compensation Philosophy: paragraph about pay ranges anchored to median, new hires at start of range, etc. EEO statement: remove. Accommodation statement: remove. Now we need to map to headings. Possible sections: - About the company (maybe