Jobs · Utah

Business Development Representative

Pattern · Lehi, UT · 1 mo ago
HybridFull-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. Remove boilerplate, navigation, EEO, etc. Use

for headings,
  • for lists,

    for prose. We need to parse the posting. Key info: - Company: Pattern. - Role: Business Development Representative. - Focus: identifying and engaging potential clients to drive business growth. Collaborate with sales and marketing, trade shows, marketing events. - Full-time, hybrid schedule based in Lehi, Utah. - Day in the life: list of duties: - Lead generation through research and contact sourcing, conducting cold calls, sending emails, utilizing LinkedIn to connect with prospects and schedule meetings. - Work closely with sales team to understand their needs, share insights from prospect interactions, coordinate efforts for lead conversion. - Assist in organizing and attending marketing events, trade shows, webinars to generate leads and network. - Engage in ongoing training sessions to improve sales techniques, product knowledge, industry insights. - Monitor personal performance metrics (calls made, meetings scheduled, leads converted) and adjusting strategies as needed to meet/exceed targets. - Research relevant stakeholders usually in marketing, sales or ecommerce roles and identify value propositions. - Craft and test value-driven messages specific to current pain points and needs. - Work closely with enterprise sales reps on sales funnels, plans, pipeline and targets tracking everything you do in Salesforce. - Outbound outreach with compelling messages through phone & email. - Work closely with marketing team to penetrate and set appointments with enterprise accounts. - Requirements/Qualifications: - Bachelor's degree in business or related field. - Track record of hitting quota. - Experience in phone sales and qualifying leads. - Excellent written and communication skills - on par with enterprise executives. - Creative thinker and problem solver. - Highly organized and disciplined. - Proficiency with GoogleSuite. - Experience with Salesforce CRM. - Experience with LinkedIn Sales Navigator and Outreach. - Strong communication and organizational skills, a proactive attitude, and resilience in the face of challenges. - "What does high performance look like?" maybe part of expectations but not a separate section; could be under Responsibilities or Qualifications? Might be considered "Expectations". But we only have set sections; we could put under Responsibilities or maybe a separate "Expectations" not allowed. Probably incorporate into Responsibilities. - Potential career growth: move into Inside Sales Representative. - First 30,60,90 days: structured onboarding program with three-month ramp-up period, gradually take on more responsibilities and work towards meeting monthly sales quotas. - Team: work alongside Pattern US sales team, mentored by Director of Business Development and Enterprise Account Reps. Collaborate regularly with team, work tightly with fast paced SaaS department. - Company culture: list of values (Game Changers, Data Fanatics, Partner Obsessed, Team of Doers). Could be under "About the role" or separate "Culture". Not in allowed sections; maybe include under "About the role" as prose. - Hiring process: steps. Could be under "About the role" or maybe separate but not allowed. Probably include under "About the role" as prose. - How to stand out: bullet points. - Why should I work at Pattern? Benefits: list includes Unlimited PTO, Paid Holidays, Onsite Fitness Center, Company Paid Life Insurance, Casual Dress Code, Competitive Pay, Health, Vision, and Dental Insurance, 401(k) match (Pattern matches 100% of first 3% in eligible compensation deferred and 50% of next 2%). Also mention "Competitive Pay" but no specific number. Since we cannot create Pay section unless posting actually states them. It says "Competitive Pay" but not a specific figure. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits list, so we can include Benefits section. It also mentions hybrid schedule based in Lehi, Utah. That's schedule info: "This is a full-time role and will work a hybrid schedule based in Lehi, Utah." So we can include Schedule section with that statement. Pay: only "Competitive Pay" which is vague but still states Pay exists. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive Pay". That's a statement about pay, albeit not specific. Should we include Pay section? It says "Competitive Pay". That's a statement about pay. I'd include Pay section with that statement. However, the rule also says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") . "Competitive Pay" is not exactly filler but could be considered vague. It's not a specific number, but it's still a statement. I'd include it. - Benefits: we have list. - Schedule: hybrid schedule based in Lehi, Utah, full-time. Now we need to decide sections. Potential sections: - About the role: could include overview of role, mission, company description, maybe culture, hiring process, how to stand out, why work at Pattern? But we have separate Benefits, Pay, Schedule sections. About the role could contain description of role, responsibilities? But we also have Responsibilities section. Usually About the role is a brief summary. We'll put a concise paragraph summarizing the role: Business Development Representative focusing on lead generation, collaborating with sales/marketing, etc. - Responsibilities: list of duties (the day in the life bullet points). Use

    • . - Requirements: maybe education and experience? Could combine with Qualifications? The spec includes both Requirements and Qualifications sections. We need to decide what goes where. Typically Requirements: hard requirements like degree, experience, skills. Qualifications: maybe preferred? But we have both. We'll split: Requirements: Bachelor's degree, track record of hitting quota, experience in phone sales and qualifying leads, proficiency with GoogleSuite, Experience with Salesforce CRM, Experience with LinkedIn Sales Navigator and Outreach. Qualifications: Excellent written and communication skills, creative thinker and problem solver, highly organized and disciplined, strong communication and organizational skills, proactive attitude, resilience. However there is overlap. Could also put "Excellent written and communication skills - on par with enterprise executives" under Qualifications. We'll try to avoid duplication. - Skills: maybe list of specific tools/skills: GoogleSuite, Salesforce CRM, LinkedIn Sales Navigator, Outreach, phone sales, lead qualification, etc. But we already have those in Requirements. Could move tools to Skills. Let's think: The posting includes "Proficiency with GoogleSuite", "Experience with Salesforce CRM", "Experience with LinkedIn Sales Navigator and Outreach". Those are skills. Also "Excellent written and communication skills". "Creative thinker and problem solver". "Highly organized and disciplined". "Strong communication and organizational skills". "Proactive attitude", "resilience". Those are more like competencies. We could put them under Skills. But we also have Requirements for degree, experience, track record. Let's allocate: - Requirements: Bachelor's degree in business or related field; Track record of hitting quota; Experience in phone sales and qualifying leads. - Qualifications: Excellent written and communication skills (on par with enterprise executives); Creative thinker and problem solver; Highly organized and disciplined; Strong communication and organizational skills; Proactive attitude; Resilience. - Skills: Proficiency with GoogleSuite; Experience with Salesforce CRM; Experience with LinkedIn Sales Navigator and Outreach. But there is also "Excellent written and communication skills - on par with enterprise executives" which is a skill. Could be under Skills. However we already have similar under Qualifications. Might be okay. We need to avoid duplication. Let's decide: - Requirements: Bachelor's degree in business or related field; Track record of hitting quota; Experience in phone sales and qualifying leads. - Qualifications: Excellent written and communication skills (on par with enterprise executives); Creative thinker and problem solver; Highly organized and disciplined; Strong communication and organizational skills; Proactive attitude; Resilience. - Skills: Proficiency with GoogleSuite; Experience with Salesforce CRM; Experience with LinkedIn Sales Navigator and Outreach. Now Responsibilities: list of duties as above. About the role: short paragraph summarizing role and company. Benefits: list as
      • . Pay: statement "Competitive Pay". Schedule: "Full-time role with hybrid schedule based in Lehi, Utah." We should also include maybe "Location: Lehi, Utah (hybrid)". That's schedule. Now ensure we don't include boilerplate: remove EEO, AI hiring process note, reference to pattern.com email, etc. Also remove "To learn more, visit pattern.com or email [email protected]." Remove "Pattern has been named one of the fastest growing tech companies..." maybe that's about company but could be part of About the role? It's not boilerplate; it's company accolades. Could include in About the role. However the instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The accolades are not boilerplate; they are substantive. Could keep. But we need to preserve ALL substantive information; do not invent or summarize away detail. So we should include accolades if they are substantive. However we must avoid duplication. The posting includes: "Pattern has been named one of the fastest growing tech companies headquartered in North America by Deloitte and one of best-led companies by Inc. We place employee experience at the center of our business model and have been recognized as one of Newsweek’s Global Most Loved Workplaces®." That's substantive about company culture. Could include in About the role. Also "We need a Business Development Representative at Pattern to focus on identifying and engaging potential clients to drive business growth." That's role description. Also "This role will collaborate closely with sales and marketing teams to align strategies and share insights on lead quality and market trends, while also participating in trade shows and marketing events." That's responsibility. Also "This is a full-time role and will work a hybrid schedule based in Lehi, Utah." schedule. Also "What is a day in the life of a Business Development Representative?" then list. Also "What will I need to thrive in this role?" list. Also "What does high performance look like?" list. Also "What is my potential for career growth?" statement. Also "What does success look like in the first 30, 60, 90 days?" statement. Also "What is the team like?" statement. Also "What’s the company culture?" list of values. Also "What is the hiring process?" list. Also "How can I stand out as an applicant?" list. Also "Why should I work at Pattern? Benefits ..." list. We need to include all substantive info, but we must not create sections with filler. We can include multiple sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Also maybe we could add a section for "Career Growth" or "Onboarding" but not in allowed list. So we must fit those details into allowed sections or omit? The instruction: "Prefer a few substantive sections over many thin ones." It doesn't forbid adding other sections not in list? It says: "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, but likely they expect only those headings. It says "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should limit to those headings. So we need to fit all substantive info into those sections. Thus we need to distribute: -

Similar jobs