Technical Manager, Fiber Lasers

We need to output 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. Must not include Job ID etc. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. We need to parse the posting. Content: - Intro about company (maybe not needed? It's part of description but not a section heading. Could be part of About the role? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we need to create sections accordingly. The "About the role" likely corresponds to the description of the role (the paragraph after "We currently seek a Technical Manager..."). - Responsibilities: The "Essential duties and responsibilities include, but are not limited to:" and subpoints. - Requirements: maybe "Key Qualifications" includes Education, Experience, Technical Expertise, Leadership Competencies, General Expectations. Could be split into Requirements and Qualifications? The instruction lists both Requirements and Qualifications as possible headings. We need to decide what goes where. Usually Requirements are mandatory (education, experience). Qualifications could be preferred? But we have both. We'll put Education, Experience under Requirements. Qualifications could be Technical Expertise, Leadership Competencies, General Expectations? Or maybe Skills. The instruction includes Skills as a possible heading. We could put Technical Expertise under Skills. Leadership Competencies maybe under Qualifications? Let's think. Better: Use sections that match content: About the role (overview), Responsibilities (duties), Requirements (education + experience), Qualifications (technical expertise + leadership competencies), Skills (maybe not needed if covered), Benefits (benefits described), Pay (not specified -> we must NOT include Pay section unless posting actually states them). The posting says "competitive salaries" but no specific numbers. That's not specific; we should not include Pay because it's not specific (just "competitive salaries"). The rule: 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. Benefits: they mention "competitive salaries and generous benefits programs, including medical, dental, tuition reimbursement and a matching 401(k) plan." That's specific enough for Benefits section. So include Benefits. Schedule: not mentioned, so omit. Pay: not specific numbers, so omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits. We need to decide if we need Skills separate. Could combine technical expertise into Skills. But we also have Leadership Competencies maybe under Qualifications. Let's map: - About the role: paragraph describing role purpose and location. - Responsibilities: list of duties (Technical Leadership, Team & Program Management, Cross-Functional Collaboration, Innovation & External Engagement). Use

• . - Requirements: Education (M.S. or Ph.D. in Optical Engineering, Physics, Electrical Engineering, or related discipline.) Experience (8–15 years of experience in high power fiber lasers). Also maybe "Demonstrated excellence in experimental optical physics..." etc. That seems more like qualifications. But we can put experience and education under Requirements. The rest under Qualifications. - Qualifications: Could include "Strong track record in establishing and executing R&D projects", "Demonstrated experience delivering fiber laser products from concept through commercialization.", "Drive to work both independently and as a critical member of interdisciplinary teams", "Prior technical leadership or people management experience required." plus maybe "Technical Expertise" list? But we might put Technical Expertise under Skills. - Skills: list of technical expertise: Yb, Er, Tm fiber laser architectures, physics modelling, optical fibers, nonlinear effects, fiber devices, thermal management, laser safety, etc. Also leadership competencies: proven ability to lead teams, decision-making, cross-functional communicator, balance innovation, documentation, presentation skills. Also general expectations: effective communications, MS Office, discretion, safety policies, Standards of Conduct. We could combine leadership and general expectations under Skills or Qualifications. Let's decide: Qualifications: education + experience? Actually typical job posting: Requirements = education + experience; Qualifications = skills, competencies. But we have both headings available. Let's assign: - Requirements: Education and Experience (8-15 years). Possibly also "Prior technical leadership or people management experience required." but that's more qualification. - Qualifications: Technical Expertise, Leadership Competencies, General Expectations. - Skills: maybe not needed if we put technical expertise under Qualifications. But we have a Skills heading available; we could put the technical expertise list there, and leadership under Qualifications. However we need to avoid thin sections. Let's think: we could have About the role, Responsibilities, Requirements, Qualifications, Benefits. That's five sections. That seems fine. Skills could be merged into Qualifications. Thus:

  About the role

  ... (description)

  Responsibilities

  • ... each bullet

  Requirements

  • Education: M.S. or Ph.D. in Optical Engineering, Physics, Electrical Engineering, or related discipline.
  • Experience: 8–15 years of experience in high power fiber lasers.

  Qualifications

  • Technical Expertise: Strong knowledge of Yb, Er, Tm and other single/double-clad fiber laser architectures; physics, modelling and simulation of active fibers; optical fibers, modes and waveguide design; nonlinear effects (SBS, SRS, mode instability); fiber devices such as fiber combiners, gratings, and mode-field adapters; thermal management and packaging; laser safety and reliability standards.
  • Leadership Competencies: Proven ability to lead and develop technical teams; strong decision-making and problem-solving skills; effective cross-functional communicator; balance innovation with schedule, cost, and manufacturability constraints; drive to work both independently and as a critical member of interdisciplinary teams; exceptional documentation and presentation skills to all levels of the organization.
  • General Expectations: Demonstrate effective communications (verbal, written) skills; proficient with MS Office Word and Excel; maintain discretion when working with confidential and proprietary information; strict adherence to Company safety policies and procedures; conform to all aspects of Lightera’s “Standards of Conduct” document.

  Benefits

  • Competitive salaries
  • Generous benefits programs including medical, dental, tuition reimbursement, and a matching 401(k) plan.
  We need to ensure we preserve all substantive information. Did we miss anything? Let's review original text. Intro about company lineage etc. Not needed for role? Might be considered part of About the role? But we could include a brief paragraph about company under About the role? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So About the role likely should contain description of the role and maybe company context. The initial paragraph about LIGHTERA's lineage and mission could be considered part of About the role (company background). However the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid including company description. So we can include that in About the role. Thus About the role paragraph: combine the introductory sentences about LIGHTERA's lineage, mission, and the specific role description. Let's craft: "LIGHTERA has one of the longest and most respectable corporate lineages in American business, tracing back to Alexander Graham Bell and the invention of the telephone over a century ago. The company has a proven track record of being first in the industry with application-specific fibers, optical connectors, ribbon cables, erbium-doped fibers, Raman fiber lasers, fiber gratings, and more. Its mission is to provide leading optical innovations and solutions by designing, manufacturing, and supplying the best optical fibers, fiber cable, components, and devices for customers, with exceptional service that creates value for shareholders, customers, and employees. To achieve this, LIGHTERA continues shaping the future of communications by applying the best minds to the challenges customers will continually face. The company currently seeks a Technical Manager to support its Fiber Lasers Department in Somerset, NJ. The Technical Manager, Fiber Lasers leads the development and execution of fiber laser technologies, overseeing technical teams responsible for laser architecture, optical design, and system integration. This role combines hands-on technical leadership with people management and program ownership to deliver high-performance, reliable, and manufacturable fiber laser products." That covers the substantive info. Now Responsibilities: we need to list each bullet from "Essential duties and responsibilities include, but are not limited to:" and subpoints. We have sections: Technical Leadership - Lead design and development of fiber laser systems (CW and pulsed), including seed sources, amplifiers, pump coupling, and beam delivery. - Oversee optical, thermal, and mechanical design trade-offs to meet power, beam quality, and reliability targets. - Drive performance optimization, stability improvements, and nonlinear effect mitigation. - Identify and explore new areas of high-potential, fiber laser research to seed the long-term product funnel. - Support fiber laser product development by guiding root-cause analysis of field and production issues. Team & Program Management - Manage and mentor a multidisciplinary team of engineers and scientists. - Define project scope, milestones, budgets, and resource allocation. - Conduct technical reviews and ensure adherence to development processes. - Align technology roadmap with business and product strategy. Cross-Functional Collaboration - Partner with manufacturing to ensure scalable fiber assembly and packaging processes. - Collaborate with other technical leads to develop programs spanning fiber lasers, sensing, telecommunications, and medical applications. - Work with quality and reliability teams on qualification and lifetime testing. - Support Marketing and Sales Teams in customer-facing technical discussions and advanced applications. Innovation & External Engagement - Contribute to IP strategy, invention disclosures, and patent reviews. - Guide team in authoring high-profile journal and conference proceeding publications. - Monitor industry advancements through engagement with organizations such as SPIE, Optica, and IEEE. - Perform other related duties as required. We need to put each as

  . Could group under subheadings? But we only allowed

  for section headings, not subheadings. Could we include inside

  ? Probably okay. But we should keep simple: each duty as

  . Could we preserve the grouping by using

  Technical Leadership: ...? That might be okay. But we need to preserve all info; grouping is not required but could help readability. However the instruction says use

  • for any list of duties/requirements/benefits. It doesn't forbid adding extra markup inside
  • . So we can include headings inside
  • using . That's fine. Thus each
  • can contain the bolded heading and then the details. Similarly for Requirements: we have Education and Experience. Could also include "Prior technical leadership or people management experience required." but we placed that under Qualifications. Let's verify if we missed any requirement: The posting also says "Demonstrated excellence in experimental optical physics, including assembly, test, measurement, and analysis of fiber lasers". That seems like a qualification, not a requirement. We'll put under Qualifications maybe under Technical Expertise? Actually that is more like a skill/experience. We'll incorporate into Technical Expertise maybe as a bullet. Let's list all qualification-like statements: From "Key Qualifications": Education M.S. or Ph.D. in Optical Engineering, Physics, Electrical Engineering, or related discipline. Experience 8–15 years of experience in high power fiber lasers Demonstrated excellence in experimental optical physics, including assembly, test, measurement, and analysis of fiber lasers Strong track record in establishing and executing R