Jobs · Customer Service · Minnesota

Field Service Technician - Pharma Solid Filling & Packaging Systems

Syntegon · Brooklyn Park, MN · 1 mo ago
Customer Service$40–$50/hrFull-time
We need to output HTML fragment with headings

for 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 as heading. No Job ID etc. Remove boilerplate (cookie/navigation/legal/EEO etc). Must preserve all substantive info. Let's parse the posting. First paragraph: "Together with 6,900 colleagues worldwide, we are the strategic partner for the pharmaceutical, biotech and food industries. With seamless processes, innovative technologies, and sustainable solutions, we help our customers achieve their goals. For example, we ensure that vaccines are safely filled and that tablets can fully release their active ingredients. Your favorite chocolate and snacks are also sustainably packaged with our help. Apply now and become part of our team! The Syntegon Technology Services location in Raleigh, North Carolina is the headquarters of the North American Service Hub of Syntegon, which concentrates on the customer's unique requirements." That's about the company and location. Could be "About the role"? Actually "About the role" is a heading for description of role. The first paragraph is more about company. Might be considered "About the role"? Usually "About the role" includes summary of role. The posting includes a "Summary:" line: "Responsible for installation, testing, analyzing, maintaining, repairing and training on Syntegon Pharmaceutical Solid Systems at customer sites. Provide customers with excellent technical customer service and ensure complete satisfaction. This position has a direct and significant impact on maintaining our customer base as well as growing new business for Syntegon Technology." Thus we can have a section "About the role" (or maybe "Summary") but instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. We have "What you can expect:" then "Summary:" then "Key Responsibilities:" then "What you'll bring:" then "Basic Requirements:" then "Preferred Qualifications:" then "Additional Information" includes compensation and benefits. Thus we can create sections: - About the role: maybe include the summary paragraph (the "What you can expect:" summary). Could also include the initial company description? But that's not about the role. Probably better to put the summary under About the role. - Responsibilities: list from "Key Responsibilities:" bullet points. - Requirements: could combine Basic Requirements and maybe Preferred Qualifications? But we have separate headings Requirements and Qualifications. Usually Requirements = basic requirements, Qualifications = preferred qualifications. We'll follow that. - Skills: maybe we can extract skills from preferred qualifications? But we have a separate Skills heading. Could list skills like proficiency in operating controls, etc. However we might not need a separate Skills section if content is thin. The instruction: Prefer a few substantive sections over many thin ones. So we might combine skills into Qualifications or Requirements. But we have headings for Skills; we can include if there is substantive content. The posting includes "Proficiency in operating controls, and prior work experience in repair/maintenance of control systems, such as servo drives, HMI's and programmable controllers." and "Demonstrated advanced mechanical, electrical and software skills. systems of equipment (Allen Bradley, Siemens, PLC, PMAC, etc.) Ability to support various software control platforms for complete packaging lines." That's skills. So we could have a Skills section. - Benefits: from Additional Information: health insurance, 401(k), disability, life insurance, education assistance, PTO, EAP. - Pay: compensation range $40 - $50 per hour. - Schedule: not explicitly stated; maybe travel 80% of the time domestically and internationally. That's travel requirement, not schedule. No explicit schedule like full-time, shift. So we should not create Schedule section unless posting actually states it. It does not. So omit Schedule. - Also we might include a short paragraph for location/metadata? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we could include a short paragraph at top maybe about location? But we already have About the role maybe includes location? The location is given: "The Syntegon Technology Services location in Raleigh, North Carolina is the headquarters of the North American Service Hub of Syntegon". That's location info. Could be part of About the role or a separate short p. Since it's not a heading, we can include as a

before sections. We must not include boilerplate like EEO, STEM initiatives, equal opportunity, etc. Remove those lines. Also remove "Apply now and become part of our team!" maybe considered call to action; but it's not boilerplate? It's application instruction; we should remove application instructions. The instruction says remove application instructions. So we should drop "Apply now and become part of our team!" and also the line about applying exclusively through online system etc. That's application instruction. Also remove EEO statement, STEM initiatives, etc. We must preserve all substantive information. So keep company description, location, summary, responsibilities, basic requirements, preferred qualifications, skills, benefits, pay. Now craft HTML. We'll start with a

for location/company intro? Could combine location and company description into a

before sections. Let's draft:

Together with 6,900 colleagues worldwide, we are the strategic partner for the pharmaceutical, biotech and food industries. With seamless processes, innovative technologies, and sustainable solutions, we help our customers achieve their goals. For example, we ensure that vaccines are safely filled and that tablets can fully release their active ingredients. Your favorite chocolate and snacks are also sustainably packaged with our help. The Syntegon Technology Services location in Raleigh, North Carolina is the headquarters of the North American Service Hub of Syntegon, which concentrates on the customer's unique requirements.

Then sections:

About the role

Responsible for installation, testing, analyzing, maintaining, repairing and training on Syntegon Pharmaceutical Solid Systems at customer sites. Provide customers with excellent technical customer service and ensure complete satisfaction. This position has a direct and significant impact on maintaining our customer base as well as growing new business for Syntegon Technology.

Responsibilities

  • Provide turnkey support for start-up, IQ, OQ, and PQ validation testing on new machine installations.
  • Provide updates and modifications to machine control software at customer sites and training customers on use and maintenance of equipment.
  • Coordinate development activities and upgrades related to updating and improving machine functionality.
  • Provide support to Customers, Customer Service department and Sales department as required.
  • Participate in continuous training, as needed, in order to maintain technical expertise and proficiency on new equipment and existing systems applications through internal training.
  • Work in a cleanroom environment, fully gowned.
  • Work in tight quarters; on top and underneath equipment standing, stooping, kneeling and bending continuously (approx. 66% of the time).
  • Lift up to 50lbs on a regular basis.

Requirements

  • 2-year Packaging Machinery degree and 2 years of experience working on Packaging Equipment OR 5 years overall experience in repair and maintenance of capital equipment.
  • 2‑years’ experience working directly with Customers.
  • Ability to travel 80% of the time Domestically and Internationally.

Qualifications

  • BS in Electrical Engineering.
  • Experience in the packaging industry.
  • Proficiency in operating controls, and prior work experience in repair/maintenance of control systems, such as servo drives, HMI's and programmable controllers.
  • Demonstrated advanced mechanical, electrical and software skills (Allen Bradley, Siemens, PLC, PMAC, etc.).
  • Ability to support various software control platforms for complete packaging lines.
  • Experience with cGMP and GAMP requirements in the Pharmaceutical Industry.
  • Strong customer service focus with ability to assure customer confidence in the operation of equipment.
  • German‑speaking skills a plus.
We could also have Skills section but we already covered skills in Qualifications. Might be redundant. The instruction: Prefer a few substantive sections over many thin ones. So maybe we should not have both Qualifications and Skills; we could merge skills into Qualifications. But we already have Qualifications heading; we could keep it and not add Skills. However we need to decide if we want Skills separate. The posting includes many skill items; they could go under Skills. But we already have Qualifications (preferred qualifications). The distinction is fuzzy. To be safe, we could keep Qualifications as preferred qualifications and add Skills for the technical skills. But that may be thin? Let's see: Skills would include proficiency in operating controls, prior work experience in repair/maintenance of control systems, demonstrated advanced mechanical, electrical and software skills, ability to support various software control platforms, experience with cGMP and GAMP, strong customer service focus, German-speaking skills a plus. That's substantive. So we could have Skills section. But then Qualifications would be just BS in Electrical Engineering, Experience in packaging industry. That's thin. Better to combine. Thus I think we should have Requirements (basic) and Qualifications (preferred) and maybe not Skills. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't require us to use all; we can omit those lacking real content. So we can have Requirements and Qualifications (both substantive). Skills could be omitted if we feel it's covered. But we have specific skill details; they could go under Qualifications as well. However Qualifications heading is for "Preferred Qualifications". The posting has a "Preferred Qualifications:" block that includes many items, including BS in Electrical Engineering, experience in packaging industry, proficiency in operating controls, etc. So we can put all those under Qualifications. That's fine. Thus we will have: - About the role (summary) - Responsibilities - Requirements (basic) - Qualifications (preferred) - Benefits - Pay No Schedule. Now ensure we preserve all substantive info: we have location/company description in initial p. We have summary. We have responsibilities list. We have basic requirements list. We have preferred qualifications list (including BS, experience, proficiency, advanced skills, support platforms, cGMP/GAMP, customer service, German). We have benefits list. We have pay range. Check we didn't miss any: travel 80% is in Requirements (we included). Work in cleanroom, tight quarters, lift 50lbs are in Responsibilities. Good. Now ensure we removed boilerplate: removed EEO, STEM initiatives, equal opportunity, application instructions, etc. Also removed "Additional Information" heading (we incorporated its content into Benefits and Pay). Also removed "Total rewards at Syntegon include salary + bonus (if applicable) + benefits." That's somewhat generic; we could keep as part of Benefits? It's not specific benefit; it's a statement. Might be considered boilerplate? It's not a specific benefit; it's a generic statement. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. That sentence is somewhat generic but still part of the posting. However it's not a specific benefit; it's a description of total rewards. Could be considered substantive? It's not a specific benefit but it's part of the compensation description. Might be okay to keep as a

under Benefits or Pay. But we already have Benefits list; we could add a

before the list: "Total rewards at Syntegon include salary + bonus (if applicable) + benefits." That's not boilerplate; it's part of the posting. However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not those.

Similar jobs