Business Development Representative
maybe under no heading? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Thus we need to produce sections only if there is content. We have content for: - About the role: there is a paragraph "About The Role" describing the role, teams, etc. So we can create
About the role
with paragraphs. - Responsibilities: there is "Core Responsibilities (All Teams)" list and then team-specific responsibilities. So we can createResponsibilities
with- items.
- Requirements/Qualifications/Skills: The posting has "What We’re Looking For" list of qualifications, plus "Join a team built on these core values" (values). Also "No experience necessary, however recent sales (or sales adjacent) experience is a plus..." etc. So we can treat these as Requirements or Qualifications or Skills. We need to decide which sections to include. We have content for Requirements (maybe "What We’re Looking For") and Skills (maybe "Experience with sales & marketing technology stack"). Also "Qualifications" maybe similar. We can combine but better to separate if distinct.
We have Benefits: "Our Commitment To Your Total Well-being" lists benefits: medical, dental, vision, life and AD&D insurance, short- and long-term disability, infertility support, WPATH-aligned transgender health benefits, EAP, transit benefits, FSA and HSA options, Ownership: Equity for all employees, Time: Flexible paid time off, paid parental leave, fully paid four-week sabbatical in sixth year, Growth: Company-paid professional coaching, Wealth: Day-one 401(k) match plus matching on qualified student loan payments. So we have Benefits content.
Pay: There's salary range: New York City: $60,000-$65,000, plus variable compensation commission. So we have Pay content.
Schedule: There's mention: "We’re headquartered in NYC and offer hybrid NY-based positions (four days/ week in-office, with no required office days during the summer and winter holidays)." Also "This role is based out of our NYC office." So schedule: hybrid, four days/week in-office, no required office days during summer/winter holidays. So we have schedule content.
Thus we can include sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule.
We need to avoid filler like "commensurate with experience". Not present.
We must preserve all substantive information, not invent or summarize away detail. So we need to include details from each section.
We need to use
- for any list of duties/requirements/benefits. For prose, use
. We need to remove boilerplate: EEO, equal-opportunity, scam-warning, navigation, cookie, legal, application instructions. At end there is EEO statement and accommodations etc. We should drop that. Also drop "What Happens Next" etc (application instructions). Also drop "Come join us!" etc. We need to keep all substantive info: company description, role description, responsibilities (core and team-specific), what we're looking for (qualifications), core values maybe could be part of Requirements or separate? The core values are not exactly requirements but could be part of "Qualifications"? Might be better to put under a separate section like "Culture" but not allowed headings. We could incorporate into Requirements or Qualifications as prose. Since we have limited headings, we could put core values under Requirements as a
. Or we could create a section "Qualifications" for the list of what we're looking for, and "Skills" for experience with sales & marketing tech stack, and maybe "Requirements" for the core values? Hmm. Better: Use sections as per typical job posting: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content: - About the role: description of role, teams, location, hybrid. - Responsibilities: core responsibilities list + team-specific responsibilities. - Requirements: maybe "No experience necessary, however recent sales (or sales adjacent) experience is a plus (i.e. recruiting, real estate, or non-profit experience). B2B tech/SaaS sales experience as an SDR/BDR is a plus. Curiosity and interest for financial products and retirement planning. Demonstrated track record of high performance. High energy and willingness to learn. Strong oral and written communication skills with even stronger listening skills. Relentless in your pursuit of success and are willing to put in the extra effort to achieve your goals." That's a list of requirements/qualifications. - Qualifications: maybe "Experience with sales & marketing technology stack." Could be considered a skill. But we can also treat that as Skills. - Skills: maybe "Experience with sales & marketing technology stack." Also maybe "Strong oral and written communication skills" etc but those are already in Requirements. We could combine Requirements and Qualifications into one section, but we need to follow instruction to use headings only when there is real specific content. We could have both Requirements and Qualifications if we can split content meaningfully. Let's split: Requirements: the list of personal attributes, experience plus etc. Qualifications: maybe "No experience necessary, however recent sales (or sales adjacent) experience is a plus" is more like qualification. Hmm. Alternatively, we could treat "What We’re Looking For" as Requirements, and "Join a team built on these core values" as Qualifications (cultural fit). And "Experience with sales & marketing technology stack" as Skills. Thus: - Requirements: the bullet list under "What We’re Looking For" (excluding the tech stack line). Actually the list includes: No experience necessary, however recent sales (or sales adjacent) experience is a plus (i.e. recruiting, real estate, or non-profit experience). B2B tech/SaaS sales experience as an SDR/BDR is a plus. Curiosity and interest for financial products and retirement planning. Demonstrated track record of high performance. High energy and willingness to learn. Strong oral and written communication skills with even stronger listening skills. Relentless in your pursuit of success and are willing to put in the extra effort to achieve your goals. Experience with sales & marketing technology stack. We could split: Requirements: personal attributes (high performance, high energy, communication skills, relentless, etc). Qualifications: experience-related (sales adjacent, B2B tech/SaaS, curiosity for financial products). Skills: Experience with sales & marketing technology stack. But the instruction says prefer a few substantive sections over many thin ones. So maybe better to combine Requirements and Qualifications into one section, and Skills separate. But we have headings list includes both Requirements and Qualifications and Skills. We could include all three if we have content. Let's see if we can allocate distinct content: Requirements: "Demonstrated track record of high performance. High energy and willingness to learn. Strong oral and written communication skills with even stronger listening skills. Relentless in your pursuit of success and are willing to put in the extra effort to achieve your goals." Qualifications: "No experience necessary, however recent sales (or sales adjacent) experience is a plus (i.e. recruiting, real estate, or non-profit experience). B2B tech/SaaS sales experience as an SDR/BDR is a plus. Curiosity and interest for financial products and retirement planning." Skills: "Experience with sales & marketing technology stack." That seems reasonable. Now Benefits: we have list. Pay: salary range and variable compensation. Schedule: hybrid, four days/week in-office, no required office days during summer/winter holidays. Now we need to output HTML fragment only, no /, no markdown. We'll produce:
About the role
...
ThenResponsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
...
ThenSchedule
...
We need to ensure we preserve all substantive information. Let's extract exact phrasing. About Betterment paragraph: "Betterment is a leading, technology-driven financial services company that offers investing, savings and retirement solutions for retail investors and investment advisors as well as financial wellness solutions, including a 401(k) for small and medium-sized businesses. Our team is passionate about our mission, to empower people to build wealth with confidence and ease. We’re headquartered in NYC and offer hybrid NY-based positions (four days/ week in-office, with no required office days during the summer and winter holidays)." We could include that as part of About the role? Actually About the role section should focus on role description. The company description could be separate but we don't have a heading for About the company. Could include as abefore any heading? The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid having a
without heading at start. So we could lead with a
containing the company description. That seems okay. Then About the role: we have paragraph under "About The Role": "We're hiring ambitious, tech-savvy Business Development Representatives to join one of three teams driving top-of-funnel growth across Betterment's retirement and advisor solutions businesses: Direct 401(k) BDR — builds pipeline with small and mid-sized businesses looking to launch or switch their 401(k) plan.Advised 401(k) BDR — builds pipeline with financial advisors and RIAs looking to offer or improve 401(k) plans for their business-owner clients.Custody BDR — builds pipeline with independent RIAs evaluating or switching custodians for Betterment Advisor Solutions (BAS). In each of these roles, you'll own outbound prospecting at the top of the sales funnel — an activity-heavy role where you'll identify, engage, and qualify prospects before handing off warm opportunities to Account Executives. You're a self-starter who's comfortable with high call/email volume, quick to learn a technical product, and motivated by hitting (and beating) targets. Candidates will be considered for the team(s) whose current hiring needs best match their background and interests; the specific team will be confirmed during the interview process. This role is based out of our NYC office." We need to preserve that. Now Responsibilities: "Core Responsibilities (All Teams)" list: - Generate new opportunities using outbound tactics (email sequences, cold calling, LinkedIn, etc) to assist the sales process at the top of the funnel. - Identifying, targeting and nurturing potential outbound opportunities by creating new target lists and always being one step ahead of trends. - Understanding the need of prospects and communicating them clearly to Account Executives. - Clearly articulating Betterment’s Advised value proposition and products to prospects in specific verticals. - Meet and exceed meeting set and pipeline goals. - Ensure effective and consistent use of Salesforce & other prospecting tools. - Provide “voice of the prospect and industry” to marketing and product management to drive roadmaps. - We are
- for any list of duties/requirements/benefits. For prose, use