Jobs · Information Technology · Utah

Technical Trainer

Motorola Solutions · Salt Lake City, UT · 3 wk ago
On-siteInformation Technology$80k–$85k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we have company overview and department overview. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
  • for any list of duties/requirements/benefits, and

    for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. We have: - Company Overview (descriptive paragraph) - Department Overview (descriptive paragraph) - Job Description (intro paragraph) - THE OPPORTUNITY (some description) - Role And Responsibilities (list of duties) - Required Qualifications (list) - Preferred Knowledge, Skills, And Abilities (list) - Working Conditions And Physical Requirements (list) - COMPENSATION: $80,000 - $85,000 / annually (Pay) - Benefits: "Our U.S. Benefits Include ..." list - Travel Requirements: None - Relocation Provided: None - Position Type Experienced - Referral Payment Plan No - EEO Statement (remove) - etc. We need to remove boilerplate: EEO statement, accommodation request, etc. We need to keep substantive info: company overview, department overview, job description, opportunity, responsibilities, required qualifications, preferred qualifications, working conditions, compensation, benefits. We need to use headings: maybe "About the role" could combine company overview and department overview? But we have separate sections: maybe "About the role" could be the job description/intro. However we can also have "Department Overview" as a heading? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings, but suggests using those. Probably we should map content to those headings. We can have: -

    About the role

    : combine company overview, department overview, job description/intro, THE OPPORTUNITY paragraph. -

    Responsibilities

    : list of duties from Role And Responsibilities. -

    Requirements

    : maybe combine Required Qualifications and Preferred Knowledge, Skills, And Abilities? But they differentiate Requirements vs Qualifications vs Skills. Could do: -

    Qualifications

    : Required Qualifications. -

    Skills

    : Preferred Knowledge, Skills, And Abilities. -

    Requirements

    : maybe Working Conditions? Not exactly. Could treat Working Conditions as part of Requirements? Or we could have a separate section for Working Conditions but not in list; maybe we can omit if not needed? But we need to preserve all substantive info. So we need to include Working Conditions somewhere. Could put under

    Working Conditions

    but not in allowed list; but instruction says use those headings as examples, not exclusive. It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use other headings if needed, but better to stick to those. Working Conditions could be part of Requirements or Qualifications? Might be better to have a separate "Working Conditions" heading, but it's not in the list; but it's not prohibited. The instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we can add other headings if needed. But they also say "Prefer a few substantive sections over many thin ones." So we might combine Working Conditions into Requirements or Qualifications. We could have: - About the role (company overview, department overview, job description, opportunity) - Responsibilities (list) - Qualifications (required) - Skills (preferred) - Working Conditions (list) - Pay (compensation) - Benefits (list) Schedule: not provided (only Monday-Friday onsite). Actually schedule is mentioned: "This position is fully onsite, Monday through Friday, at Silvus Technologies ‘Salt Lake City manufacturing site." That's schedule info. So we can include Schedule section. Thus we have sections: About the role, Responsibilities, Qualifications, Skills, Working Conditions, Pay, Benefits, Schedule. We need to ensure we don't create sections with filler like "not specified". All have content. Now we need to format lists: Use
    • for any list of duties/requirements/benefits. For prose, use

      . We need to preserve all substantive info: need to include details like "Deliver hands-on training for new Operations staff, including assembly, inspection, soldering, and equipment use." etc. We need to include the compensation range: $80,000 - $85,000 / annually. Benefits list: Incentive Bonus Plans, Medical, Dental, Vision benefits, 401K with Company Match, 10 Paid Holidays, Generous Paid Time Off Packages, Employee Stock Purchase Plan, Paid Parental & Family Leave, and more! We need to include schedule: fully onsite, Monday through Friday. We need to include working conditions: Office environment; occasional exposure to heat, cold, allergens while performing tests or demonstrations in the field; Lift equipment up to 25 lbs.; Perform bending and reaching movements; Kneeling or squatting to access lower shelves; Walking/Moving in the labs. We need to include required qualifications list: - High School Diploma or GED. - 3–5 years of hands-on experience in Electronics Manufacturing or Technical Training; OR completion of a 2-year college or technical program with at least 1 year of relevant training or operations experience. - Experience delivering hands-on training or technical instruction in a Production or Manufacturing environment. - Experience with soldering, PCB assembly, or inspection processes. - Experience with maintaining training records or documentation. - Ability to read and interpret schematics, drawings, work instructions, and inspection requirements. - Proficient with PC and familiar with MS Office. - Must have excellent organizational skills, be highly attentive to detail, and have the capacity to handle numerous tasks simultaneously. - Excellent and effective oral and written communication. - Must be a U.S. Person (U.S. Citizen, or U.S. Permanent Resident) due to clients under U.S. federal contracts. - All employment is contingent upon the successful clearance of a background check and drug test. Preferred Knowledge, Skills, And Abilities list: - Prior experience in a fast-paced production/manufacturing environment. - Experience writing technical procedures or training materials. - Familiarity with ISO 9001 training and competency requirements. - IPC Certified Trainer (CIT) for J-STD-001 and/or IPC-A-610. We need to ensure we don't repeat duplicated lines. There's a "Basic Requirements" section that repeats Required Qualifications; we should not duplicate. We need to remove boilerplate: EEO statement, accommodation request, etc. We also need to remove "Travel Requirements None", "Relocation Provided None", "Position Type Experienced", "Referral Payment Plan No". Those are minor metadata; we can fold into a short

      or drop. Probably drop them as they are not substantive? But they are info; but we can include them in a short paragraph under About the role maybe. However instruction says fold minor metadata into a short

      or drop it. So we could include a short paragraph like "Travel: None. Relocation: None. Position Type: Experienced." But maybe better to drop as not essential. However we need to preserve ALL substantive information; is travel requirement substantive? It says None, which is not substantive? It's a statement that there is no travel. Could be considered substantive but minor. We could include in a short paragraph. Similarly, schedule we already have. We need to avoid repeating the job title as heading. Now produce HTML fragment. Structure:

      About the role

      Company overview paragraph + department overview + job description + opportunity.

      We need to combine multiple paragraphs into one

      ? Could be multiple

      inside the section. That's fine. We'll output:

      About the role

      At Motorola Solutions, we believe that everything starts with our people. We’re a global close-knit community, united by the relentless pursuit to help keep people safer everywhere. We build and connect technologies to help protect people, property and places. Our solutions foster the collaboration that’s critical for safer communities, safer schools, safer hospitals, safer businesses, and ultimately, safer nations. Connect with a career that matters, and help us build a safer future.

      Silvus Technologies, a leading provider of advanced MANET and MIMO communications systems, is reshaping mesh network technology for mission-critical applications – on the ground, in the air and at sea. Its battle-proven StreamCaster family of MANET radios and proprietary MN-MIMO waveform provides the vital communications link for defense, law enforcement and public safety agencies around the world, and in the toughest operational environments. Silvus Technologies is a wholly owned subsidiary of Motorola Solutions, Inc.

      Would you like to join an incredibly talented group of people, doing very challenging work, with the prime directive of “Keeping Our Heroes Connected”? THE OPPORTUNITY Silvus is seeking a full-time Technical Trainer who will report to the Quality Manager at our Salt Lake City facility. This role is responsible for delivering, developing, and maintaining technical training programs for new and existing Operations team personnel, including assemblers, technicians, and inspectors. The technical trainer maintains proper training documentation, ensures ISO 9001 compliance for training records, proctors IPC certification courses, and collaborates closely with Engineering, Production, and Quality teams to ensure personnel are properly trained according to Silvus standards, industry requirements, and customer expectations. This position is fully onsite, Monday through Friday, at Silvus Technologies ‘Salt Lake City manufacturing site.

      Then Responsibilities:

      Responsibilities

      • Deliver hands-on training for new Operations staff, including assembly, inspection, soldering, and equipment use.
      • Maintain and update training curricula, training materials, skill assessments, and qualification documentation.
      • Ensure training records, matrices, and competency logs are complete, accurate, and maintained in accordance with ISO 9001 requirements.
      • Proctor and administer IPC-J-STD-001 and IPC-A-610 training and evaluations.
      • Maintain a clean, organized, and fully equipped training area, including soldering stations, microscopes, tools, and training boards.
      • Update training materials and curricula based on ECO changes, engineering updates, or process improvements.
      • Conduct refresher training and re-certification for Operations employees as needed.
      • Track new hire progress and training completion in collaboration with Production team leadership.
      • Support the Quality Engineering team by identifying skill gaps contributing to defects or rework and developing targeted training plans.
      • Assist in generating or updating work instructions, visual aids, and operator guidance

Similar jobs

Technical Trainer

Kirby-Smith Machinery, Inc.Tulsa, OK· 1 mo ago
Information Technologyapply on careers.hireology.com

Technical Trainer

Clarke Power Services, Inc.Cincinnati, OH· 1 mo ago
Information Technologyapply on recruiting.paylocity.com

Technical Trainer

Kirby-Smith Machinery, Inc.Fort Worth, TX· 1 mo ago
Information Technologyapply on careers.hireology.com

Technical Trainer

Horizontal TalentSan Francisco, CA· 2 mo ago
Information Technology$126–$185/hrapply on horizontaltalent.com

Technical Trainer

Lockheed MartinOwego, NY· 3 mo ago
Information Technologyapply on sjobs.brassring.com

Technical Trainer

BSH Home Appliances Corporation - North AmericaIrvine, CA· 3 mo ago
Information Technology$72k–$96k/yrapply on phh.tbe.taleo.net