Product Data Engineer Technician III

We need to produce 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 as heading. Must not include Job ID etc. Must preserve all substantive info, no invented details. Remove boilerplate like EEO, accommodation, ITAR, etc. Also remove duplicated lines. We need to parse the job description. Let's extract sections: The posting includes: - JOB DESCRIPTION ACCOUNTABILITIES & ESSENTIAL FUNCTIONS (list of duties) - Skills & Certifications (list of skill evaluation) - Product Data Engineer Technician I (education/experience) - Product Data Engineer Technician II (list) - Product Data Engineer Technician III (list) - Requirements (list) - ABOUT US (company description) - Then EEO etc. We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: Could be the "JOB DESCRIPTION ACCOUNTABILITIES & ESSENTIAL FUNCTIONS" maybe also "ABOUT US"? Actually About the role likely describes the role itself. The job description includes responsibilities. So we can put responsibilities under Responsibilities heading. About the role could be a brief summary: maybe from the first paragraph? The posting starts with "Performs technical data research, assessment and acquisition..." That's responsibilities. So we could treat that as Responsibilities. About the role could be a short description: maybe from "Product Data Engineer Technician I/II/III"? But those are levels. Could treat them as Qualifications? Actually they are levels with education/experience. We need to include sections only if there is real specific content. Let's gather: Responsibilities: bullet list of duties from "Performs technical data research..." through "Represents the company in a professional manner with internal and external customers". That's a list. Skills: from "Skills & Certifications" list. Qualifications: maybe education/experience requirements from the levels and the "Requirements" section. Requirements: maybe the "Requirements" bullet list (Bachelor’s Degree etc). Actually there is a "Requirements" heading later. But we have overlapping. Let's extract each distinct piece: 1. Responsibilities (Accountabilities & Essential Functions): - Performs technical data research, assessment and acquisition using the Internet, Supplier websites, search engines, spreadsheets, and internal databases - Normalizes all collected data into a consistent format that is governed by Tech Data established procedures - Collaborates, coordinates, and manages the classification, collection, implementation, and maintenance of the product technical data using Product Information Management (PIM) system and Data Quality Analyst tools - Plans, develops, and manages the hierarchies for assigned product categories based on product type and/or technology through technical processes - Ensures that collected data is relevant for uses that are sourcing products, in all regions worldwide - Develop a basic Mouser Product Data acumen and use it with each classification and attribution task assigned - Develops an understanding of the classification Hierarchy to the extent that misclassified products can be readily identified and reclassified into the correct template - Evaluate template attributes for relevance with the template Taxonomy and make recommendations for changes that would benefit customers - Evaluate the data as presented on Mouser.com and make recommendations regarding normalization, sorting, and order of parametric attributes to enhance the overall product sourcing for customers - Establish open and timely communications with interested parties, stakeholders, and teams - Expected to utilize organizational skills to document, categorize, prioritize, provide easy access to information, ask questions, follow up and maintain communications - Represents the company in a professional manner with internal and external customers 2. Skills & Certifications (list): - Skill evaluation: Behavioral (80%) - Ability to manage multiple projects and priorities - Familiarity in working in and with cross-functional teams - Strong organizational skills - Strong ability to work independently or in teams with a collaborative interpersonal style - Demonstrates a positive attitude toward self and others - Ability to set and track goals - Uses sound judgement to identify issues and escalates when appropriate - Able to research data for long periods of time - Able to quickly learn new software applications and adapt to project related process changes - Detailed and thorough in work habits with multi-tasking ability - Demonstrated ability in reading, analyzing, and interpreting Technical Data Sheets, Product Guides, Scientific and Technical Journals and other related engineering documents - Professional with the ability to interface directly with internal business contacts and represent the business unit - PC experience in Microsoft Windows environment, proficient with internet email, Microsoft Word, Excel, Power Point, Outlook, and related platforms - Electronic Design, Systems Design, Test Engineering or Electronic Component experience required - Exhibits strong analytical, technical, problem solving and organizational skills - Able to work with minimum supervision and independent judgements 3. Product Data Engineer Technician I: - Bachelor’s Degree in Electrical Engineering or relevant discipline. In lieu of a degree 4 years of relevant work experience is desired; or equivalent combination of education and/or experience 4. Product Data Engineer Technician II: - Maintain and continuously build on an established strong Mouser Product Data classification and attribution assignments - Contribute to functional design of process solutions - Proficient to quickly learn and adapt to project related process changes - Proficient in work habits with multi-tasking ability - Proficient in classifying and attributing products using the Product Information Management (PIM) system and related tools - Proficient in in using Excel - Knowledge and understanding of Mouser Taxonomy and hierarchies - Proficient in reading and using Technical Data Sheets and related scientific document 5. Product Data Engineer Technician III: - The passion to improve processes, initiate change and embrace new technologies - Serve as a subject matter expert (SME) within established product areas - Strong functional design contributor of process solutions - Proficient to quickly learn new software applications and adapt to project related process changes, communicating the benefits and results to others - Professional with the ability to interface directly with business contact and represent Mouser - Aware and interested in emerging technologies in the Electronic Component field - Proficient in identifying Business Terms and Parametric definitions, values for a wide range of Electronic Components - Solid knowledge and understanding of the PCN and Life Cycle of components 6. Requirements (separate section): - Bachelor’s Degree in Electrical Engineering or relevant discipline. In lieu of a degree 5+ years of relevant work experience in Electrical Engineering or technical field is acceptable - 2+ years Electronic Component experience required. For internal candidates, experience can be a combination of internal and external experience. But note that there is also a Requirements for Technician III: Bachelor’s Degree ... 6 years ... 4+ years Electronic Component experience required. We need to preserve all substantive info. So we need to include all these details. We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have no explicit Benefits, Pay, Schedule info in the posting (except maybe "competitive pay and benefits" in About US). That's a generic statement: "Mouser employees enjoy competitive pay and benefits, a business casual dress environment, a state-of-the-art facility in which to work, and an experienced management team with vision and a passion for growth." That is about benefits and pay but vague. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "competitive pay and benefits" but not specific details. Is that enough? It says "competitive pay and benefits" - that is a statement about pay and benefits existing, but not specific. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that they enjoy competitive pay and benefits. That is a statement about benefits and pay. However, we must avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "competitive pay and benefits" is not filler; it's a statement that they offer competitive pay and benefits. So we could include a Benefits section with that sentence, and a Pay section maybe also from that sentence? But we need to avoid duplication. The sentence mentions both pay and benefits. Could we put that under Benefits? Or we could split? The instruction: "include a section ONLY when the posting has real, specific content for it". The phrase "competitive pay and benefits" is somewhat generic but still content. I'd include a Benefits section with that sentence, and maybe a Pay section with same? Might be redundant. Better to combine into one Benefits section that mentions pay and benefits. But we have separate headings for Pay and Benefits. We could put the sentence under Benefits and not create Pay section because no specific pay details. However the sentence includes pay. But we could still include Benefits only. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (and pay) but not specifics. I'd include Benefits section with that sentence, and omit Pay and Schedule because no schedule info. Now About the role: Could be a brief summary from the "ABOUT US" maybe? Actually About the role could be a description of the role: maybe the first sentence "Performs technical data research..." but that's more responsibilities. However we already have Responsibilities. About the role could be a higher-level description: maybe from "Product Data Engineer Technician I/II/III" describing the role levels. But we could treat About the role as a short paragraph summarizing the position: maybe from the job title? Not given. Could we leave About the role empty? We must not create a heading with filler. So we should only include About the role if there is real specific content. Is there? The posting does not have a separate "About the role" paragraph. The closest is the "JOB DESCRIPTION ACCOUNTABILITIES & ESSENTIAL FUNCTIONS" which is responsibilities. So we could skip About the role. Thus sections: Responsibilities, Skills, Qualifications (maybe combine education/experience from levels and Requirements), Requirements (maybe separate?), Benefits. But we need to avoid duplication. Let's think: Qualifications vs Requirements. Usually Qualifications are education, experience, skills. Requirements could be specific mandatory items. The posting has multiple lists: Skills & Certifications (skills), Product Data Engineer Technician I/II/III (maybe qualifications/experience), Requirements (education/experience). We could combine all into Qualifications section, and maybe Requirements as a separate if distinct. But to avoid thin sections, we could merge. Better: Use Qualifications for education/experience requirements (including the Technician levels and Requirements). Use Skills for the skill list. Use Responsibilities for duties. Use Benefits for the competitive pay and benefits statement. Thus we will have:

Responsibilities

...

Skills

...

Qualifications

...

(include all education/experience statements and level-specific expectations)

Benefits

Mouser employees enjoy competitive pay and benefits, a business casual dress environment, a state-of-the-art facility in which to work, and an experienced management team with vision and a passion for growth.

We must not include boilerplate like EEO etc. Remove that. Now we need to ensure we preserve all substantive info from the lists. Let's extract each item precisely. Responsibilities list items (as above). We'll copy them exactly as in posting, preserving punctuation. Skills list items: we need to copy each bullet. Qualifications: combine: - Product Data Engineer Technician I: Bachelor’s Degree in Electrical Engineering or relevant discipline. In lieu of a degree 4 years of relevant work experience is desired; or equivalent combination of education and/or experience - Product Data Engineer Technician II: Maintain and continuously build on an established strong Mouser Product Data classification and attribution assignments; Contribute to functional design of process solutions; Proficient to quickly learn and adapt to project related process changes; Proficient in work