Account Executive

We need to extract substantive content: About Assembly Software (company description), Vision Statement, Mission Statement, Core Values, Selling is in your DNA! (maybe responsibilities/qualifications?), When You’re Considering a New Job... includes location, benefits, compensation, etc. Need to format with headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. The posting is more about company description and benefits, not specific role responsibilities. There's no explicit responsibilities list. There's "Selling is in your DNA!" which seems like qualifications/skills for a sales role (Account Executive). There's mention of competitive compensation package with uncapped commissions, built-in accelerators. Benefits described. Location: remote with occasional visits to Miami office. So we can create sections: About the role? Not exactly; maybe "About the role" could be derived from description of role? The posting doesn't have a separate "About the role" heading but we can infer from content: It's describing an Account Executive role. We could put that under "About the role". However we must not invent content; we can paraphrase but must preserve all substantive info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot create a heading and then put content that wasn't explicitly under that heading? It says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can create sections based on headings present in the posting? The posting does not have those headings; they are instructions for us to use those headings for reformatting. So we need to map the content to those headings. If there is no specific content for a heading, we should omit it. So we need to see what content maps to each heading. Headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content: Company description (About Assembly Software) - could go under About the role? Not exactly; but maybe we treat that as "About the role" describing the role at Assembly Software. However the instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings. It doesn't forbid using About the role for company description. Usually "About the role" would describe the role, not the company. But we have no explicit role description besides the "Selling is in your DNA!" bullet list which describes qualifications/skills/responsibilities. So we could put that under Responsibilities or Qualifications/Skills. Let's parse the "Selling is in your DNA!" paragraph: - You have a competitive nature and love to win. - You are a master at building relationships and closing deals. - Colleagues often come to you for advice because you are an expert when it comes to the products and services you sell. - You are well organized and leverage Salesforce (or other CRM software) to increase your efficiency and effectiveness. - You are a client whisperer! You have a unique and professional way of communicating and understanding your clients’ needs. - Clients can’t say no to your web demos and co-workers come to you so they can learn from the best. - Your positive attitude and drive are contagious and makes you an invaluable part of the team. - You are known for bringing teams together cross-functionally and have a knack for building high trust relationships. - Your natural communication approach is one that effectively, respectfully, and inclusively builds a sense of belonging among employees who differ from one another. - You are a strategic thinker and are proactive problem solver and you are able to find ways to cohesively support employees and business drivers. That seems like a mix of responsibilities, qualifications, skills. Could be considered "Qualifications" or "Skills". We could split: Responsibilities: building relationships, closing deals, leveraging Salesforce, delivering web demos, being a client whisperer, bringing teams cross-functionally, building high trust relationships, strategic thinking, proactive problem solving, supporting employees and business drivers. Qualifications: competitive nature, love to win, expert in products/services, well organized, positive attitude, drive, communication approach inclusive, etc. Skills: relationship building, closing deals, Salesforce, communication, strategic thinking, problem solving. But we must not invent or summarize away detail; we can keep the sentences as is, maybe as list items. Benefits: described: competitive health, dental, vision benefits; short and long term disability; other supplemental insurance; 401k; flexible time off; paid parental leave; employee assistance program. Also mention of competitive compensation package with uncapped commissions and built-in accelerators (Pay). Location: remote with occasional visits to Miami office (Schedule? maybe location not schedule). Schedule not mentioned. So we may omit Schedule. Pay: we have "competitive compensation package with uncapped commissions for our Account Executives, and built-in accelerators." That's specific enough for Pay section. Benefits: we have details. About the role: maybe we can include a brief description: "Assembly Software is a SaaS organization and leading provider of case management solutions..." etc. That's from the FAQ section. Could be considered About the role (the role at Assembly Software). We'll include that. Responsibilities: maybe we can extract from the "Selling is in your DNA!" the action-oriented statements: building relationships, closing deals, leveraging Salesforce, delivering web demos, being a client whisperer, bringing teams cross-functionally, building high trust relationships, strategic thinking, proactive problem solving, supporting employees and business drivers. We'll list those. Requirements: maybe none explicit besides being an Account Executive? Not given. Could omit Requirements. Qualifications: maybe the traits: competitive nature, love to win, expert in products/services, well organized, positive attitude, drive, communication approach inclusive, etc. We'll list. Skills: maybe specific skills: relationship building, closing deals, Salesforce, communication, strategic thinking, problem solving. We'll list. But we must avoid duplication; we can decide to combine Qualifications and Skills into one section if content thin. However instruction: "Prefer a few substantive sections over many thin ones." So we could combine Qualifications and Skills into one "Qualifications" section, or have separate if substantive. Let's see if we have enough for each. Qualifications: competitive nature, love to win, expert in products/services, well organized, positive attitude, drive, communication approach inclusive, ability to build trust, strategic thinker, proactive problem solver. Skills: relationship building, closing deals, Salesforce, communication, strategic thinking, problem solving. There's overlap. Might be better to have a single "Qualifications and Skills" but headings are fixed. We could put under Qualifications the trait-based items, and under Skills the specific abilities. That seems okay. Now Benefits: list items. Pay: one sentence. Schedule: none -> omit. Now About the role: we need to include company description and maybe role context. Let's extract from the "About Assembly Software" paragraph and the FAQ about location and specialness. About Assembly Software paragraph: "When you join Assembly Software, you’re joining a team that genuinely cares about you, your career, and your excitement about your job. When you work for a tech company in the legal field, there are endless opportunities ripe for disruption, and you’ll be on the forefront of that innovation. We want you to pursue what drives you and push your boundaries! Assembly Software is where people come to shake up a historically buttoned-up industry." Vision Statement, Mission Statement, Core Values: those are also substantive. Should we include them? They are not under any of the headings but could be part of About the role? Possibly we could include them under About the role as they describe the company. The instruction: "Preserve ALL substantive information". So we need to include Vision, Mission, Core Values somewhere. Since we don't have a heading for those, we could put them under About the role as a paragraph list. But we must not create a heading with filler. So we can include them as part of About the role content. Thus About the role will contain: the introductory paragraph, Vision Statement, Mission Statement, Core Values, plus maybe the FAQ about location and what makes Assembly special, plus the info about SaaS, leading provider, user base, acquisition, etc. We need to ensure we don't repeat the job title as a heading (we aren't). We must not include Job ID/requisition numbers (none). Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is an EEO statement: "Assembly Software provides equal employment opportunities..." That's boilerplate; we should remove it. Also maybe the "When You’re Considering a New Job..." section includes FAQs that are not boilerplate; we keep location, benefits, etc. We must also remove duplicated lines. There's no obvious duplication. Now produce HTML fragment with headings

and appropriate

• or

  . We'll structure:

  About the role

  ... (company description, vision, mission, core values, location, special aspects)

  Responsibilities

  • ...
  ...

  Qualifications

  • ...
  ...

  Skills

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  ...

  We must ensure we don't create empty sections. Now let's extract content precisely. From the text: About Assembly Software paragraph: "When you join Assembly Software, you’re joining a team that genuinely cares about you, your career, and your excitement about your job. When you work for a tech company in the legal field, there are endless opportunities ripe for disruption, and you’ll be on the forefront of that innovation. We want you to pursue what drives you and push your boundaries! Assembly Software is where people come to shake up a historically buttoned-up industry." Vision Statement: "Assembly's vision is to provide the legal community the best practice management software that enables client advocacy from anywhere at anytime." Mission Statement: "Our mission is to provide intuitive and comprehensive legal practice management solutions enhancing efficiency and profitability for our customers." Core Values list: "We are Accountable: We accept responsibility for our choices and actions. We value transparency + feedback. We Never Stop Learning: We pursue growth + learning. We Thrive as a Team: We value others' opinions + work respectfully with one another. We are Collaborative Innovators: We are adventurous, creative + open-minded. We are Here to Be of Service to our Customer + our Colleagues: No matter our role, we are all here to be of service + add value. We have Unyielding Integrity: We do the right thin, even when no one is watching. We Embrace Diversity + Inclusion: We are passionate about creating and cultivating an inclusive culture that promotes and values diversity." Note there's a typo "thin" but we keep as is. FAQ section: "I am tired of the daily grind of a commute, where are you located? With the exception of scheduled visits to our Miami, FL office and scheduled video meetings, you get to work in the comfort of your own home in your PJs if you’d like!" "What makes Assembly Software so special? The people are the heart of our organization! Our passion for our products and our entrepreneurial spirit creates an energetic and fun work culture. Assembly Software is a SaaS organization and the leading provider of case management solutions and through our three brands, Needles, Needles Neos and TrialWorks, we have a rich multi-decade history. Today we have assembled the largest user base in the industry, with over 2,500 law firm customers and more than 40,000 users. In 2017, the business was acquired by Ridge Road Partners – a group of long-term focused, business builders – who are transforming the business into a dynamic, fast-growth enterprise. Additionally,