Jobs · Administrative · North Carolina

Account Manager - Pittsburgh, PA/New York territory

SARSTEDT Group · Newton, NC · 1 mo ago
On-siteAdministrativeFull-time
We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. No Job ID. Remove boilerplate. We need to parse the posting: It includes "What We Do", "What You'll Be Doing", "What Your Bring", "Work environment", "How We Reward You", "About SARSTEDT", "Commitment to Quality", "To Learn More", EEO. We need to map to sections: About the role (maybe description of role), Responsibilities (list of duties), Requirements (maybe education/experience), Qualifications (maybe similar), Skills (maybe abilities), Benefits (list of benefits), Pay (compensation), Schedule (maybe travel? but schedule not given). The posting mentions "Compensation: Competitive base salary" but no specific number. That's vague; we should not include Pay section if content is just "Competitive base salary" which is vague but maybe considered real? The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "Competitive base salary" is somewhat vague but it's a statement. It's not a placeholder like "TBD". It says compensation: Competitive base salary. That's a statement, albeit not specific number. I think we can include Pay section with that sentence. Benefits: they list many benefits under "How We Reward You": Paid Time Off, Paid Holidays, Flexible Time Off, Wellness PTO, Health, Wellness, Fitness, Mental Health, Retirement, Leave Benefits, Professional Development, Employee Discounts. That's specific enough. Schedule: Not mentioned explicitly. There's travel up to 90%, overnight travel etc. That's not schedule. No mention of work hours, shift, etc. So we should not include Schedule section. Pay: include. Now sections: About the role: maybe combine "What We Do" and description of role? The "About the role" could be a brief description of the role: "As an Account Manager supporting the Pittsburgh, PA and New York territory, you’ll play a key role in building strong customer relationships and growing our business." That's from "What You'll Be Doing". We'll put that in About the role. Responsibilities: list of duties from "What You'll Be Doing": compile lists, travel, display/demonstrate product, use phone/email etc, follow-up on telesales, quote prices, prepare reports, work with inside sales, record new customer data, attend trade shows, participate in correlation studies, log interactions in CRDB, log opportunities in SAP-C4C, attend training. We need to put each as
  • under
      . Requirements: maybe education/experience: "Bachelor’s degree in Life Science, Health Science, or a related field from a four-year college or university, with 2–3 years of related experience and/or training; or an equivalent combination of education and experience. Minimum of 3 years of experience in medical or research sales required." That's requirements. Qualifications: maybe similar to requirements? Could combine but we need separate sections only if content. Could put qualifications as "Ability to stand for extended periods and frequently lift and/or move up to 25 pounds for product delivery and trade show setup. Ability to travel up to 90% throughout the assigned territory, with up to 50% overnight travel outside the territory. Valid driver’s license, ability to operate a motor vehicle, and successful completion of an MVR check required. Remote position based in the Pittsburgh, PA or New York territory." That's more qualifications/skills. Skills: maybe "Ability to stand for extended periods..." etc could be skills. But we already used that. Let's think: Requirements: education/experience. Qualifications: maybe the physical/travel/driver license. Skills: maybe communication, relationship-building, etc. But we could also put those under Skills. However we need to avoid thin sections. Let's see what content we have: - Education/experience: Bachelor's degree, 2-3 years related experience, or equivalent; Minimum 3 years medical/research sales. - Physical/Travel: Ability to stand for extended periods, lift up to 25 lbs, travel up to 90%, 50% overnight, valid driver's license, MVR check, remote position. - Skills/Abilities: Ability to compile lists, travel, demonstrate product, use phone/email, follow-up telesales, quote prices, prepare reports, work with inside sales, record data, attend trade shows, participate in correlation studies, log interactions, log opportunities, attend training. Those are more responsibilities. Thus we could have: About the role: short paragraph. Responsibilities: list of duties. Requirements: education/experience. Qualifications: physical/travel/driver license/remote. Skills: maybe not needed if we already covered abilities in qualifications. Could combine qualifications and skills but we need to avoid thin sections. Perhaps we can have Requirements (education/experience) and Qualifications (physical/travel/license) and Skills (communication, relationship-building, etc). But we need to see if there is explicit skill list: "relationship-driven role for someone who enjoys being in front of customers, developing new business, and representing the company as a trusted partner." That's a skill/attribute. Also "Compile lists of prospective customers..." etc are duties. Thus we can create Skills section with items like: Relationship-building, customer-facing, new business development, communication (phone, email, promotional material, trade shows, face-to-face), telesales follow-up, quoting, reporting, expense management (Concur), collaboration with inside sales, data recording, trade show participation, correlation studies, CRM logging (CRDB, SAP-C4C), training participation. That seems reasonable. Benefits: list as per "How We Reward You". Pay: "Compensation: Competitive base salary". We'll put that as a paragraph. Schedule: not present, omit. Now we need to output only HTML fragment, no html/body tags, no markdown. We'll use

      for each section heading. We'll need to wrap lists in
      • . We'll need to use

        for prose. We must not repeat job title. We must not include boilerplate like EEO, About SARSTEDT history, etc. Remove those. We must preserve all substantive information; we can omit boilerplate but keep the substantive content from sections we used. Let's extract substantive content: From "What We Do": description of company, but maybe not needed for role? Could be part of About the role? The instruction: About the role section likely should contain description of role, not company. But we could include a brief about the role derived from "What You'll Be Doing". The "What We Do" is about company; maybe we can omit as it's not role-specific. However the instruction says preserve ALL substantive information; but we can omit boilerplate like company history? The "What We Do" is not boilerplate; it's substantive about the company. But the sections we have are about the role, responsibilities, etc. The company overview might not fit any section; but we could include it under About the role? Might be okay to include a short paragraph about the company as part of About the role. 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 — fold minor metadata into a short

        or drop it." It doesn't forbid including company description. But we have limited sections; we could include a paragraph under About the role that includes both company description and role description. That would preserve that info. But we also have "About SARSTEDT" later with history; that's more detailed company info. That could be considered boilerplate? It's substantive but not role-specific. The instruction says preserve ALL substantive information; but we might need to include it somewhere. However we have no section for company overview; we could add a section like "About the company" but not in allowed headings list. The allowed headings are only those listed; we cannot add other headings. So we must fold minor metadata into a short

        or drop it. The company history might be considered minor metadata? It's not minor; it's substantive. But we have no place to put it; maybe we drop it as it's not required for the role? The instruction says preserve ALL substantive information; but if we cannot fit it into allowed sections, maybe we drop it? The instruction says "fold minor metadata into a short

        or drop it." So we can drop non-minor? It says "fold minor metadata into a short

        or drop it." That implies we can drop minor metadata, but we should keep substantive. However we have no section for company overview; maybe we can include it under About the role as a short paragraph (though it's not minor). That might be acceptable. Let's include a brief company overview under About the role: "SARSTEDT develops, manufactures, and distributes high-quality devices and consumables for medicine and scientific applications. With over 65 years of experience, the company offers a clean, advanced, climate-controlled manufacturing environment, competitive pay and benefits, real stability, and a focus on precision and quality." That's from the "What We Do" paragraph. We'll also include the role description. Now Responsibilities: list. Requirements: education/experience. Qualifications: physical/travel/driver license/remote. Skills: relationship-building, communication, etc. Benefits: list. Pay: paragraph. Now ensure we don't include filler like "commensurate with experience". Not present. Now produce HTML. Let's craft:

        About the role

        SARSTEDT develops, manufactures, and distributes high-quality devices and consumables for medicine and scientific applications. With over 65 years of experience, the company offers a clean, advanced, climate-controlled manufacturing environment, competitive pay and benefits, real stability, and a focus on precision and quality. As an Account Manager supporting the Pittsburgh, PA and New York territory, you’ll play a key role in building strong customer relationships and growing our business. This is a relationship‑driven role for someone who enjoys being in front of customers, developing new business, and representing the company as a trusted partner.

        Responsibilities

        • Compile lists of prospective customers for use as sales leads, based on information from business directories, industry ads, trade shows, websites, and other sources.
        • Travel throughout assigned territory to meet with regular and prospective customers on a daily basis or as directed by management.
        • Display or demonstrate product to customers using samples and/or catalog.
        • Use phone, email, promotional material, trade shows, and face‑to‑face meetings as primary sources of communication.
        • Follow‑up on telesales efforts for new business opportunities and strengthen existing customer relationships.
        • Quote prices and provide estimated dates of delivery to customers.
        • Prepare reports of business transactions and manage expenses via Concur software.
        • Work with inside sales representatives to keep account activities and literature up to date.
        • Record new customer data and other sales data for current customers.
        • Attend national and regional trade shows.
        • Participate in correlation studies, evaluations, and conversions of the company's blood collection system.
        • Log all customer interactions/activities in the CRDB such as appointments, quotes, samples, etc.
        • Log all customer business opportunities in the SAP‑C4C Sales Funnel.
        • Attend sales training, refresher courses, and new product introduction presentations as required.

        Requirements

        Bachelor’s degree in Life Science, Health Science, or a related field from a four‑year college or university, with 2–3 years of related experience and/or training; or an equivalent combination

  • Similar jobs

    Account Manager - PA

    Wise FoodsPhiladelphia, PA· 2 mo ago
    Business Developmentapply on wisesnacks.applicantpro.com