Senior Field Applications Engineer
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. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to decide which sections to include based on content.
We have:
- About Us: description of company. Could be "About the role"? Actually "About Us" is about company, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those headings.
We have "Summary" which describes role: "The Senior Applications Engineer at Amphenol CDI serves as a technical authority..." This could be "About the role". So we can put
About the role
and then a with the summary.
We have "Essential Job Functions" which is a list of duties. Could be "Responsibilities". So
Responsibilities
with - each bullet.
We have "Qualifications" which includes education and experience, language requirements. That's "Qualifications". So
Qualifications
with maybe for bullet points? The qualifications are paragraphs; we can put for each paragraph or
for list items. The instruction: Use - for any list of duties/requirements/benefits. So for qualifications we can treat as list.
We have "Job Skills" which is skills: Advanced/Proficient in MS Office Suite and SharePoint, Knowledge of ERP systems, SAP preferred, 3D CAD SolidWorks experience. That's "Skills". So
Skills
with .
We have "Physical Demands" maybe not a standard heading; but we could include as a section? The allowed headings list includes only those; but we could still include if content is substantive? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but not exclusive? It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but likely they expect to use those headings. However "Physical Demands" is not in the list; but we could incorporate into "Requirements"? Not exactly. Could be part of "Qualifications"? Might be better to omit if not matching allowed headings? The instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those headings where appropriate; other headings may be omitted or we could still use them but they'd be non-standard. Safer to stick to those headings.
We have "Environmental Policy", "Personal Protective Equipment Requirements", "Export Compliance Disclaimer", "Travel", "Salary Information". Some of these could map to "Benefits", "Pay", "Schedule". Travel could be part of "Schedule"? Not exactly. Salary Information maps to "Pay". Benefits: none given. So we can include Pay section for salary info. Travel maybe could be part of "Schedule"? Not really; schedule is about work hours/shift. Travel is not schedule. Could omit travel if not matching allowed headings. But we could include a section "Travel" if we think it's substantive; but instruction says prefer a few substantive sections over many thin ones. Might be okay to include Travel as its own heading? Not in examples but maybe allowed. However they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." indicates those are examples, not an exhaustive list. So we can use other headings if needed. But to be safe, we could include Travel as its own heading Travel
. Similarly Environmental Policy maybe not needed. Personal Protective Equipment Requirements maybe not needed. Export Compliance Disclaimer maybe needed as it's a requirement (must be US Person). Could be part of Qualifications? Actually it's a disclaimer about ITAR/EAR access; that is a requirement for the role (must be US Person). Could be included under Qualifications as a bullet. But we already have Qualifications; we could add a bullet there.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we must include all important info: About Us, Summary, Essential Job Functions, Qualifications (education/experience, language), Job Skills, Physical Demands, Environmental Policy, Personal Protective Equipment Requirements, Export Compliance Disclaimer, Travel, Salary Information. Also maybe the "BUSINESS IMPACT & PERFORMANCE EXPECTATIONS" part under Essential Job Functions? Actually that appears after Essential Job Functions? In the text: after Essential Job Functions bullet list, there is "BUSINESS IMPACT & PERFORMANCE EXPECTATIONS Influence ≥7% of total company bookings through direct technical leadership and customer engagement Deliver ≥12 design wins annually across the CDI product portfolio, establishing a pipeline of future production revenue". This is also part of essential job functions? It's separate but still substantive. Should be included.
We need to remove boilerplate: EEO, equal-opportunity, scam-warning, navigation, cookie, legal, application instructions, etc. Also remove duplicated lines.
We need to output only HTML fragment.
Let's extract substantive content:
About Us:
"Amphenol CDI is a global leader in high-performance interconnect solutions. From enabling mission-critical communications for military and aerospace customers to driving innovation in commercial and test & measurement markets, we engineer the connections that power tomorrow’s technology. With our principal manufacturing site located in Cerritos, California, and global engineering resources across Amphenol, we serve a wide range of customers in Military & Defense, Aerospace, Commercial, Space, Industrial, and Test & Measurement sectors."
Summary:
"The Senior Applications Engineer at Amphenol CDI serves as a technical authority and primary resource for RF and interconnect solutions, supporting customer design-in, adoption, and long-term success. This role partners closely with Sales, Engineering, Product Development, and Marketing to ensure customer technical requirements are clearly understood, translated into viable product solutions, and leveraged to influence product and market strategy. The Senior Applications Engineer will act as a go-to expert for the broader team, providing guidance and mentorship as needed, while also directly engaging with customers and strategic accounts to drive technical wins and shape future product direction."
Essential Job Functions (list):
- Act as the technical authority and primary customer interface across the CDI product portfolio, with deep expertise in RF/microwave solutions
- Own and lead customer engagement from concept through production, independently driving design-in, technical alignment, and program closure
- Provide system-level guidance and architectural support, enabling customers to optimize performance, integration, and overall solution design
- Lead resolution of complex technical and commercial challenges, delivering clear, timely, and business-aligned solutions with minimal oversight
- Partner closely with sales to convert opportunities into design wins, directly influencing bookings, margin, and market share
- Evaluate and validate custom design opportunities, including feasibility, costing, and margin alignment to ensure commercially viable solutions
- Support customer qualification and compliance requirements across key markets, including aerospace, defense, and communications
- Deliver pre- and post-sale technical support, maintaining ownership of customer success and ongoing product adoption
- Provide market, application, and competitive insights to guide product development, positioning, and long-term strategy
- Develop and maintain high-quality technical collateral, including application notes, reference designs, and customer-facing documentation
- Serve as a mentor and technical leader, elevating team capability and setting the standard for customer engagement and execution
- Other duties as required in support of the department and the company*
BUSINESS IMPACT & PERFORMANCE EXPECTATIONS:
- Influence ≥7% of total company bookings through direct technical leadership and customer engagement
- Deliver ≥12 design wins annually across the CDI product portfolio, establishing a pipeline of future production revenue
Qualifications:
"To succeed in this job, an individual must satisfactorily perform each essential job function. The requirements below represent the required knowledge, skill, and ability. Reasonable accommodations may be made to enable individuals with disabilities to perform essential functions."
EDUCATION And EXPERIENCE:
- Bachelor’s degree in Electrical Engineering, Mechanical Engineering, Physics, or related technical discipline required.
- 7–10 years of experience in Applications Engineering, Field Engineering, or Product Development within interconnects, RF/microwave, aerospace, defense, or related high-reliability markets.
- Demonstrated track record of translating customer requirements into product solutions and securing design wins.
- Strong background in customer-facing roles, including design-in support, technical presentations, and solution selling.
- Experience collaborating cross-functionally with Sales, Marketing, Engineering, and Operations to drive business outcomes.
- Proven ability to conduct competitive analysis, assess market trends, and provide input to product roadmaps.
- Hands-on familiarity with CAD tools, signal integrity analysis, or test equipment (network analyzers, oscilloscopes, etc.) desirable.
Language Requirements:
- Excellent verbal and written communication skills in English.
- Conversational in any other language is a plus.
Job Skills:
- Advanced/Proficient in MS Office Suite and SharePoint.
- Knowledge of ERP systems, SAP preferred.
- 3D CAD SolidWorks experience
Physical Demands:
"As part of their job duties, the employee must sit for lengthy periods while operating a computer. They frequently use their hands to type, handle objects, and communicate verbally. Additionally, they may need to stand, walk, reach, and occasionally lift objects weighing up to twenty (20) pounds. This role requires lifting, carrying, pushing, pulling, reaching overhead, reaching at or below shoulder level, and keyboarding. According to ADA regulations, reasonable accommodation will be provided to ensure that individuals with disabilities can perform the job's essential functions."
Environmental Policy:
"Amphenol CDI is fully committed to minimizing the environmental impact of its operations, activities, and products. To achieve this, we adhere to all applicable environmental regulations and laws, prevent pollution, and continuously improve our environmental performance in all our global operations. This is possible through an Environmental Management System that provides a framework for setting and reviewing our environmental objectives and targets. We aim to identify and reduce any negative environmental impact our business activities may have."
Personal Protective Equipment Requirements:
"ASTM F–2412–2005, ANSI Z41–1999, or ANSI Z41–1991 rated safety toe shoes in specific areas.Clear ANSI Z87.1 safety-rated glasses in specific areas.Hearing protection in specific locations.
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. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - About Us: description of company. Could be "About the role"? Actually "About Us" is about company, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those headings. We have "Summary" which describes role: "The Senior Applications Engineer at Amphenol CDI serves as a technical authority..." This could be "About the role". So we can put
About the role
and then awith the summary. We have "Essential Job Functions" which is a list of duties. Could be "Responsibilities". So
Responsibilities
with- each bullet.
We have "Qualifications" which includes education and experience, language requirements. That's "Qualifications". So
Qualifications
with maybe- for bullet points? The qualifications are paragraphs; we can put
- for any list of duties/requirements/benefits. So for qualifications we can treat as list.
We have "Job Skills" which is skills: Advanced/Proficient in MS Office Suite and SharePoint, Knowledge of ERP systems, SAP preferred, 3D CAD SolidWorks experience. That's "Skills". So
Skills
with- .
We have "Physical Demands" maybe not a standard heading; but we could include as a section? The allowed headings list includes only those; but we could still include if content is substantive? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but not exclusive? It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but likely they expect to use those headings. However "Physical Demands" is not in the list; but we could incorporate into "Requirements"? Not exactly. Could be part of "Qualifications"? Might be better to omit if not matching allowed headings? The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those headings where appropriate; other headings may be omitted or we could still use them but they'd be non-standard. Safer to stick to those headings. We have "Environmental Policy", "Personal Protective Equipment Requirements", "Export Compliance Disclaimer", "Travel", "Salary Information". Some of these could map to "Benefits", "Pay", "Schedule". Travel could be part of "Schedule"? Not exactly. Salary Information maps to "Pay". Benefits: none given. So we can include Pay section for salary info. Travel maybe could be part of "Schedule"? Not really; schedule is about work hours/shift. Travel is not schedule. Could omit travel if not matching allowed headings. But we could include a section "Travel" if we think it's substantive; but instruction says prefer a few substantive sections over many thin ones. Might be okay to include Travel as its own heading? Not in examples but maybe allowed. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." indicates those are examples, not an exhaustive list. So we can use other headings if needed. But to be safe, we could include Travel as its own heading
Travel
. Similarly Environmental Policy maybe not needed. Personal Protective Equipment Requirements maybe not needed. Export Compliance Disclaimer maybe needed as it's a requirement (must be US Person). Could be part of Qualifications? Actually it's a disclaimer about ITAR/EAR access; that is a requirement for the role (must be US Person). Could be included under Qualifications as a bullet. But we already have Qualifications; we could add a bullet there. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must include all important info: About Us, Summary, Essential Job Functions, Qualifications (education/experience, language), Job Skills, Physical Demands, Environmental Policy, Personal Protective Equipment Requirements, Export Compliance Disclaimer, Travel, Salary Information. Also maybe the "BUSINESS IMPACT & PERFORMANCE EXPECTATIONS" part under Essential Job Functions? Actually that appears after Essential Job Functions? In the text: after Essential Job Functions bullet list, there is "BUSINESS IMPACT & PERFORMANCE EXPECTATIONS Influence ≥7% of total company bookings through direct technical leadership and customer engagement Deliver ≥12 design wins annually across the CDI product portfolio, establishing a pipeline of future production revenue". This is also part of essential job functions? It's separate but still substantive. Should be included. We need to remove boilerplate: EEO, equal-opportunity, scam-warning, navigation, cookie, legal, application instructions, etc. Also remove duplicated lines. We need to output only HTML fragment. Let's extract substantive content: About Us: "Amphenol CDI is a global leader in high-performance interconnect solutions. From enabling mission-critical communications for military and aerospace customers to driving innovation in commercial and test & measurement markets, we engineer the connections that power tomorrow’s technology. With our principal manufacturing site located in Cerritos, California, and global engineering resources across Amphenol, we serve a wide range of customers in Military & Defense, Aerospace, Commercial, Space, Industrial, and Test & Measurement sectors." Summary: "The Senior Applications Engineer at Amphenol CDI serves as a technical authority and primary resource for RF and interconnect solutions, supporting customer design-in, adoption, and long-term success. This role partners closely with Sales, Engineering, Product Development, and Marketing to ensure customer technical requirements are clearly understood, translated into viable product solutions, and leveraged to influence product and market strategy. The Senior Applications Engineer will act as a go-to expert for the broader team, providing guidance and mentorship as needed, while also directly engaging with customers and strategic accounts to drive technical wins and shape future product direction." Essential Job Functions (list): - Act as the technical authority and primary customer interface across the CDI product portfolio, with deep expertise in RF/microwave solutions - Own and lead customer engagement from concept through production, independently driving design-in, technical alignment, and program closure - Provide system-level guidance and architectural support, enabling customers to optimize performance, integration, and overall solution design - Lead resolution of complex technical and commercial challenges, delivering clear, timely, and business-aligned solutions with minimal oversight - Partner closely with sales to convert opportunities into design wins, directly influencing bookings, margin, and market share - Evaluate and validate custom design opportunities, including feasibility, costing, and margin alignment to ensure commercially viable solutions - Support customer qualification and compliance requirements across key markets, including aerospace, defense, and communications - Deliver pre- and post-sale technical support, maintaining ownership of customer success and ongoing product adoption - Provide market, application, and competitive insights to guide product development, positioning, and long-term strategy - Develop and maintain high-quality technical collateral, including application notes, reference designs, and customer-facing documentation - Serve as a mentor and technical leader, elevating team capability and setting the standard for customer engagement and execution - Other duties as required in support of the department and the company* BUSINESS IMPACT & PERFORMANCE EXPECTATIONS: - Influence ≥7% of total company bookings through direct technical leadership and customer engagement - Deliver ≥12 design wins annually across the CDI product portfolio, establishing a pipeline of future production revenue Qualifications: "To succeed in this job, an individual must satisfactorily perform each essential job function. The requirements below represent the required knowledge, skill, and ability. Reasonable accommodations may be made to enable individuals with disabilities to perform essential functions." EDUCATION And EXPERIENCE: - Bachelor’s degree in Electrical Engineering, Mechanical Engineering, Physics, or related technical discipline required. - 7–10 years of experience in Applications Engineering, Field Engineering, or Product Development within interconnects, RF/microwave, aerospace, defense, or related high-reliability markets. - Demonstrated track record of translating customer requirements into product solutions and securing design wins. - Strong background in customer-facing roles, including design-in support, technical presentations, and solution selling. - Experience collaborating cross-functionally with Sales, Marketing, Engineering, and Operations to drive business outcomes. - Proven ability to conduct competitive analysis, assess market trends, and provide input to product roadmaps. - Hands-on familiarity with CAD tools, signal integrity analysis, or test equipment (network analyzers, oscilloscopes, etc.) desirable. Language Requirements: - Excellent verbal and written communication skills in English. - Conversational in any other language is a plus. Job Skills: - Advanced/Proficient in MS Office Suite and SharePoint. - Knowledge of ERP systems, SAP preferred. - 3D CAD SolidWorks experience Physical Demands: "As part of their job duties, the employee must sit for lengthy periods while operating a computer. They frequently use their hands to type, handle objects, and communicate verbally. Additionally, they may need to stand, walk, reach, and occasionally lift objects weighing up to twenty (20) pounds. This role requires lifting, carrying, pushing, pulling, reaching overhead, reaching at or below shoulder level, and keyboarding. According to ADA regulations, reasonable accommodation will be provided to ensure that individuals with disabilities can perform the job's essential functions." Environmental Policy: "Amphenol CDI is fully committed to minimizing the environmental impact of its operations, activities, and products. To achieve this, we adhere to all applicable environmental regulations and laws, prevent pollution, and continuously improve our environmental performance in all our global operations. This is possible through an Environmental Management System that provides a framework for setting and reviewing our environmental objectives and targets. We aim to identify and reduce any negative environmental impact our business activities may have." Personal Protective Equipment Requirements: "ASTM F–2412–2005, ANSI Z41–1999, or ANSI Z41–1991 rated safety toe shoes in specific areas.Clear ANSI Z87.1 safety-rated glasses in specific areas.Hearing protection in specific locations.
for each paragraph or
- for list items. The instruction: Use
- for any list of duties/requirements/benefits. So for qualifications we can treat as list.
We have "Job Skills" which is skills: Advanced/Proficient in MS Office Suite and SharePoint, Knowledge of ERP systems, SAP preferred, 3D CAD SolidWorks experience. That's "Skills". So