Junior Account Executive

We need to output only 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. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove lines like "To learn more, visit pattern.com or email [email protected]." That's contact info maybe considered boilerplate? It's contact info but not required? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Contact info maybe not required but could be considered not essential? It's not part of job description; we could drop it. Also "Pattern has been named one of the fastest growing tech companies..." that's about company; could be part of About the role? Might be considered company overview; we could include in About the role. Also "We place employee experience at the center..." that's benefits/culture; could go under Benefits or About the role. We need to decide sections. We have content: description of role, day in the life, required qualifications, preferred qualifications, team description, high performance, hiring process, how to stand out, why work at Pattern (benefits list). Also mention full-time based in Lehi, Utah. Pay not specified; schedule not specified. So we should not create Pay or Schedule sections because no specific content. Benefits we have list: Unlimited PTO, Paid Holidays, Onsite Fitness Center, Company Paid Life Insurance, Casual Dress Code, Competitive Pay, Health, Vision, and Dental Insurance, 401(k) match (details). Also mention "Pattern matches 100% of the first 3%..." etc. So we can include Benefits section. We need sections: About the role (maybe overview), Responsibilities (day in the life tasks), Requirements (required qualifications), Qualifications (maybe preferred qualifications?), Skills (maybe combine required/preferred?), Benefits. The instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can include those that have content. We must not invent or summarize away detail. Must preserve all substantive information. So we need to include all details from posting, but we can format them into appropriate sections. We must not repeat job title. Must not include Job ID/requisition numbers. We must remove duplicated lines. There's some duplication maybe like "Pattern accelerates brands..." appears once. We need to keep all substantive info: company description, role description, day in the life, required qualifications, preferred qualifications, team description, high performance, hiring process, how to stand out, why work at Pattern (benefits). Also mention full-time based in Lehi, Utah. Also mention using Claude daily. Also mention travel to industry events. Also mention hitting quarterly and annual bookings targets. Also mention using Salesforce. Also mention building relationships. Also mention using Claude for research, demo prep, proposal drafting, self-checking CRM hygiene. Also mention partnering with Solutions Engineering team and Senior AEs on technical demos, POCs, RFP responses. Also mention negotiating pricing, scope, contract terms within guidelines, manage deal through legal and procurement. Also mention keep Salesforce current. Also mention building relationships with brand marketing, ecommerce ops, IT stakeholders. Also mention travel to industry events and trade shows to find qualified leads and new business. Also mention consistently hit quarterly and annual bookings targets. Also mention "This is a data-driven, AI-forward role: you'll use Claude daily to research accounts, prep for demos, and keep your pipeline audit-ready." Already covered. Also mention "This is a full-time role based in Lehi, Utah, with room to grow into a full-cycle or enterprise AE seat." Also mention "What is a day in the life of a Junior AE?" then bullet list. Also mention "Required Qualifications" list. Also mention "Preferred Qualifications" list. Also mention "What does the team look like?" description. Also mention "What does high performance look like?" description. Also mention "What is the hiring process?" list steps. Also mention "How can I stand out as an applicant?" list. Also mention "Why should I work at Pattern?" benefits list. Also mention EEO statement etc - we must remove that boilerplate. Also mention "We may use artificial intelligence (AI) tools to support parts of the hiring process..." that's maybe not boilerplate but could be considered part of hiring process; we could keep it under hiring process? It's about AI tools used in hiring. Might be considered part of hiring process. We'll keep it under hiring process. Also mention "If you would like more information about how your data is processed, please contact us." That's maybe boilerplate; we can drop. Now we need to decide sections. Potential sections: - About the role: could include company overview, role summary, full-time location, growth opportunity. - Responsibilities: day in the life tasks. - Requirements: required qualifications. - Qualifications: preferred qualifications (or we could call it Preferred Qualifications). The instruction says use headings like Qualifications. We'll have Qualifications for preferred. - Skills: maybe combine required/preferred skills? But we already have Requirements and Qualifications; maybe Skills for specific skills like Claude, Salesforce, etc. However we might not need Skills if we already covered. But we need to include only sections with real content. We could omit Skills if we feel it's redundant. But we need to preserve all substantive info; we can put skill details under Requirements or Qualifications. So we can skip Skills. - Benefits: list. - Pay: not specified -> omit. - Schedule: not specified -> omit. Thus output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. We must ensure we include all substantive info. Let's extract and rephrase but preserve details (no summarizing away). We must not invent or summarize away detail; we can keep same sentences. We'll produce HTML with

headings and

• for lists,

  for prose. We need to avoid repeating job title. The title is "Junior Account Executive". We'll not repeat. Now craft content. About the role: include company description, role summary, location, growth. Pattern accelerates brands on global ecommerce marketplaces leveraging proprietary technology and AI. Utilizing more than 66 trillion data points, sophisticated machine learning and AI models, Pattern optimizes and automates all levers of ecommerce growth for global brands, including advertising, content management, logistics and fulfillment, pricing, forecasting and customer service. Hundreds of global brands depend on Pattern’s ecommerce acceleration platform every day to drive profitable revenue growth across 60+ global marketplaces—including Amazon, Walmart.com , Target.com , eBay, Tmall, TikTok Shop, JD, and Mercado Libre. 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®. As a Junior Account Executive on our PXM (Product Experience Management) team, you'll start by building and qualifying pipeline for our Senior Account Executives — then, as you grow into the role, you'll take on full-cycle opportunities of your own, from demo through negotiation and close, helping brands adopt Pattern's PXM platform to manage and optimize their product content across Amazon and multi-channel ecommerce. This is a data-driven, AI-forward role: you'll use Claude daily to research accounts, prep for demos, and keep your pipeline audit-ready. This is a full-time role based in Lehi, Utah, with room to grow into a full-cycle or enterprise AE seat. That seems good. Responsibilities: day in the life tasks. We can list bullet points: - Build sales pipeline for Senior Account Executives and learn top of the funnel process for PXM (early term). - Eventually own and progress a pipeline of qualified opportunities from first demo through close, partnering closely with BDRs/SDRs on handoff quality. - Run engaging, consultative discovery calls of PXM's content management, syndication, and workflow tools for brand and ecommerce stakeholders. - Use Claude as your daily working tool — for account research, demo prep, proposal drafting, and self-checking your own CRM hygiene before it's ever flagged in a report. - Partner with the Solutions Engineering team and Senior Account Executives on technical demos, POCs, and RFP responses for more complex accounts. - Work with Senior Account Executives to negotiate pricing, scope, and contract terms within established guidelines, and manage the deal through legal and procurement. - Keep Salesforce current and trustworthy — contacts, notes, next steps, and forecast category — since it drives your own comp and the team's reporting. - Build relationships with brand marketing, ecommerce operations, and IT stakeholders to understand their content and syndication pain points. - Travel to industry events and trade shows to find qualified leads and new business. - Consistently hit quarterly and annual bookings targets. We need to preserve all details; we can keep as bullet list. Requirements: required qualifications list. - Bachelor's degree in Business or related field, or equivalent experience. - 1–2 years of closing sales experience (SaaS preferred), or a proven track record as a BDR/SDR ready to move into a closing role. - Track record of hitting quota or activity targets. - Excellent written and verbal communication skills. - Genuine comfort using AI tools (specifically Claude) as part of your daily workflow — for research, demo prep, and pipeline hygiene. - We're looking for people who want to be on the cutting edge here, not people who tolerate AI as an add-on. - Highly organized and disciplined, with strong CRM habits. - Proficiency with Microsoft Office software including Word, Excel, and PowerPoint. We could also include "We're looking for people who want to be on the cutting edge here, not people who tolerate AI as an add-on." That's a statement; we can keep as bullet. Qualifications: preferred qualifications list. - Experience selling SaaS, PIM, DAM, DXP, or other ecommerce/martech platforms. - Familiarity with Amazon or other marketplace ecosystems. - Experience with Salesforce CRM, Outreach, and LinkedIn Sales Navigator. - Prior experience using Claude or another AI copilot inside a sales workflow. - Proficiency in additional languages is a bonus. Also maybe include "What does the team look like?" and "What does high performance look like?" and "What is the hiring process?" and "How can I stand out as an applicant?" Those are substantive but we have no specific sections for them. Could we incorporate them into existing sections? The instruction says we should prefer a few substantive sections over many thin ones. We could add sections like Team, High Performance, Hiring Process, Stand Out. But we have limited predefined headings; we can add extra headings beyond the list? 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 "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we could also add other headings if needed, but better to stick to those. However we have substantive info about team, high performance, hiring process, how to stand out. We could fold them into existing sections: e.g., About the role could include team and high performance? Or we could add sections like Team, High Performance, Hiring Process, Stand Out as separate headings; but they are not in the examples but likely allowed. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "