Account Executive, Renewals
Harper · New York, NY · 3 wk ago
On-siteBusiness Development$150k–$200k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate.
We need to parse the posting.
Let's extract content.
The posting starts: "Harper is an AI-native commercial insurance company in San Francisco. We're not bolting AI onto insurance — we're rebuilding the entire business as software, on a simple bet: turning expert human judgment into compute is one of the largest transitions left to make, and a trillion-dollar industry still run 90% by hand is the place to prove it. We've grown ~100x in the last year and we move at that speed — on-site, in person, long days, very high standards. Almost no one joins Harper for insurance; they join to build the company that replaces how it works."
That's about the company, could be "About the role"? Actually "About the role" is typical heading for description of role. The first paragraph is about company, but we could treat as "About the role" maybe. However we need to preserve substantive info. Could put under "About the role". Or we could have a section "About Harper" but not in allowed headings. Allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must map content to those.
We have sections: "The role" description: "Keep good Harper customers by starting early, explaining the renewal clearly, and carrying each policy to a confident decision. A renewal is not a reminder email. ...". That's responsibilities.
Then "Why now" description: about recurring sales responsibility separate from new business and service. Could be part of responsibilities.
"What You Own": bullet list of duties. That's responsibilities.
"The renewal outcomes you own": also responsibilities.
"Who Thrives Here": qualifications/requirements.
"Who Should Not Apply": maybe requirements or disqualifiers.
"Compensation & Logistics": includes Salary, Equity, Location, Schedule, Licensing. So Pay, Schedule, Benefits? Benefits separate.
"Benefits": health, dental, vision insurance. Office-specific benefits set by location.
"To apply": instructions - we must remove application instructions.
"Compensation Range: $130K - $200K" duplicates salary.
We need to avoid duplication.
We need to produce sections with content.
Let's decide:
- About the role: maybe combine company mission and role purpose. Could be: "Harper is an AI-native commercial insurance company ... The role: Keep good Harper customers by starting early, explaining the renewal clearly, and carrying each policy to a confident decision." But we must not repeat job title. Could just give overview.
Better: Use "About the role" to describe the purpose of the role: "Own the commercial conversation for policy renewals, ensuring each policy is reviewed, re‑understood, and either renewed, remarketed, or adjusted before expiration."
But we must preserve ALL substantive information; we cannot invent or summarize away detail. However we can paraphrase but must keep meaning. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can rephrase? It says do NOT invent or summarize away detail. Summarizing away detail would be removing details. So we need to keep details. So we need to include all details from posting, but we can format them.
Thus we need to include all bullet points etc.
Thus we need to create sections with lists.
Let's extract details:
Company description: Harper is an AI-native commercial insurance company in San Francisco. We're not bolting AI onto insurance — we're rebuilding the entire business as software, on a simple bet: turning expert human judgment into compute is one of the largest transitions left to make, and a trillion-dollar industry still run 90% by hand is the place to prove it. We've grown ~100x in the last year and we move at that speed — on-site, in person, long days, very high standards. Almost no one joins Harper for insurance; they join to build the company that replaces how it works.
That's substantive.
Now role description: "The role Keep good Harper customers by starting early, explaining the renewal clearly, and carrying each policy to a confident decision. A renewal is not a reminder email. The customer's business may have changed, the market may have moved, and a successor policy must be earned before the current term expires. You own that commercial conversation. Harper's systems surface expiring policies, prior terms, changed exposures, and the next action. You verify the account, lead the customer conversation, and earn the next term."
That's responsibilities.
"Why now": "Harper's growing policy book creates a recurring sales responsibility separate from new business and service. Service handles post-bind requests. You own the commercial decision for the next term, including updated needs, remarketing when required, and the final renewal close."
That's also responsibilities.
"What You Own": bullet list:
- Start early. Work the renewal book from a clear expiration-based clock rather than waiting for a carrier reminder or customer escalation.
- Re-understand the business. Confirm material changes in operations, payroll, revenue, locations, vehicles, contracts, and coverage needs.
- Build the renewal plan. Decide with placement and insurance experts whether to renew in place, remarket, change structure, or add coverage.
- Lead the customer conversation. Explain the options, changes, price, conditions, and deadline in plain language.
- Close the next term. Ask for the business, collect the required decision and completion items, and keep ownership through bind.
- Protect the account. Catch service issues, poor prior experience, or unresolved obligations that could undermine the renewal.
- Record the outcome. Capture why the customer renewed, changed, waited, or left. Identify expansion. Surface genuine new coverage needs without turning routine service changes into sales.
"The renewal outcomes you own": bullet list:
- Assigned policies have a verified expiration date, renewal plan, and next customer action early enough to act.
- Recommendations make the current term, successor option, material changes, unresolved conditions, and deadline clear.
- Bound renewals move forward with the accepted option and completion steps recorded.
- Lost renewals preserve the customer's stated reason, or an honest unknown when the reason is not available.
- Renewal conversion, retention, total booked revenue, and time to decision improve without hiding lapsed or replaced terms.
"Who Thrives Here": bullet list:
- You have closed renewals, account expansions, or recurring commercial relationships.
- You can manage a large book with different clocks and levels of complexity.
- You build trust quickly and can deliver a difficult price or coverage conversation directly.
- You know when an account needs re-marketing rather than another follow-up.
- You use account history and source documents instead of relying on one status.
- You can earn and maintain the required commercial insurance licenses.
- You are based in Atlanta or San Francisco, or ready to relocate.
"Who Should Not Apply": bullet list:
- You treat renewals as customer service reminders.
- You wait for the customer or carrier to create urgency.
- You avoid direct closing conversations.
- You infer renewal success from a cancellation or stage field.
- You need a remote or hybrid default.
"Compensation & Logistics": includes:
- Salary: $150,000–$200,000 OTE. Top performers earn more.
- Equity: Yes.
- Location: On-site, San Francisco, New York, or Atlanta. Based here or willing to relocate.
- Schedule: Monday–Friday, very early morning start, in-office 5 days a week.
- Licensing: Commercial insurance producer license required within ~30 days of start; Harper pays for training and licensing.
"Benefits": Harper offers health, dental, and vision insurance. Office-specific benefits are set by working location.
"To apply": instructions - remove.
"Compensation Range: $130K - $200K" duplicate; we can ignore duplicate or note but we should not duplicate. Probably we should keep only one mention; we can keep the $150k-200k OTE and note top performers earn more. The $130k-200k range maybe alternative; but we should not invent or summarize away detail. The posting includes both ranges; we need to preserve ALL substantive information. So we need to include both? The $130K - $200K appears at end after "To apply". It's likely a repetition but still substantive. We could include both but maybe combine? The instruction: do NOT summarize away detail. If we combine into a single range we might lose detail (the two ranges differ). Safer to include both statements, maybe as separate sentences.
Thus Pay section: include Salary: $150,000–$200,000 OTE. Top performers earn more. Also Compensation Range: $130K - $200K.
Equity: Yes.
Location: On-site, San Francisco, New York, or Atlanta. Based here or willing to relocate.
Schedule: Monday–Friday, very early morning start, in-office 5 days a week.
Licensing: Commercial insurance producer license required within ~30 days of start; Harper pays for training and licensing.
Benefits: Harper offers health, dental, and vision insurance. Office-specific benefits are set by working location.
Now we need to map to allowed headings.
We have About the role: could include company description and role purpose? But we have many responsibilities sections. Perhaps we put company description under About the role. Then Responsibilities: combine "The role", "Why now", "What You Own", "The renewal outcomes you own". That's a lot but okay.
Requirements: maybe "Who Thrives Here" and "Who Should Not Apply" combined? But Requirements vs Qualifications vs Skills: we need to decide.
Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide where each piece fits.
Typically:
- About the role: overview of role and company.
- Responsibilities: duties.
- Requirements: mandatory qualifications (e.g., license, location, experience).
- Qualifications: preferred qualifications.
- Skills: specific skills.
- Benefits: benefits.
- Pay: compensation.
- Schedule: work schedule.
We have info:
- Experience: closed renewals, account expansions, recurring commercial relationships. Manage large book, etc. That's experience/requirements.
- Ability to build trust, deliver difficult conversations, know when to re-market, use account history, earn/maintain license. Those could be skills/qualifications.
- Location based in Atlanta or SF or ready to relocate: requirement.
- License required: requirement.
- Not wanting remote/hybrid: maybe requirement.
Thus we can put Requirements: license, location, experience (closed renewals etc). Qualifications: maybe ability to manage large book, build trust, etc. Skills: maybe communication, negotiation, analytical.
But we must not invent detail; we need to map existing statements.
Let's list statements from "Who Thrives Here":
- You have closed renewals, account expansions, or recurring commercial relationships. (experience)
- You can manage a large book with different clocks and levels of complexity. (skill/experience)
- You build trust quickly and can deliver a difficult price or coverage conversation directly. (skill)
- You know when an account needs re-marketing rather than another follow-up. (skill)
- You use account history and source documents instead of relying on one status. (skill)
- You can earn and maintain the required commercial insurance licenses. (requirement)
- You are based in Atlanta or San Francisco, or ready to relocate. (requirement)
"Who Should Not Apply": negative traits, could be requirements (i.e., you must not have these). Could be included in Requirements as "Must not treat renewals as customer service reminders, must not wait for customer or carrier to create urgency, must not avoid direct closing conversations, must not infer renewal success from a cancellation or stage field, must not need a remote or hybrid default."
Thus Requirements can include both positive and negative.
Qualifications maybe none left; but we