Electrical Design Engineer - Analog/Mixed
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Content:
- Opening tagline: "COME JOIN MID-CONTINENT! "Where your work is valued-above-market pay, real work-life balance, and a team that feels like home.""
- THE POSITION: description of role: As an Electrical Design Engineer, you will design avionics, power electronics and battery systems interfacing within high-performance and safety-critical systems. Experience entire product lifecycle... etc. This is about the role.
- THEN: THIS POSITION MAY BE FOR YOU IF: list of requirements (bulleted). This is Requirements/Qualifications/Skills.
- THEN: WE WOULD REALLY LIKE IT IF (but it's not a deal breaker): list of nice-to-have.
- THEN: WHAT YOU CAN EXPECT FROM ONE DAY TO THE NEXT: list of duties/responsibilities.
- THEN: WE ARE ONE OF THE BEST PLACES TO WORK: description of benefits, above-market pay, comprehensive benefits package, work-life balance, facility, events, etc. This includes Benefits and Pay.
- Then: Who We Are: company description (maybe not needed as section? Could be About the role? Actually "About the role" is about the position; "Who We Are" is company overview. Could be included as About the role? But we have only certain headings allowed. We could put company overview under About the role? Or maybe we can omit because not required heading. The instruction: "Prefer a few substantive sections over many thin ones." We can include About the role (role description), Responsibilities (duties), Requirements (must-haves), Qualifications (maybe same as Requirements?), Skills (maybe nice-to-have), Benefits, Pay, Schedule. But we need to avoid duplication.
We have content for:
- About the role: The position description (first paragraph after THE POSITION). Could also include company overview? But we can keep About the role as the role description.
- Responsibilities: The "WHAT YOU CAN EXPECT FROM ONE DAY TO THE NEXT" list.
- Requirements: The "THIS POSITION MAY BE FOR YOU IF" list (must-haves).
- Skills: The "WE WOULD REALLY LIKE IT IF" list (nice-to-have).
- Benefits: The "WE ARE ONE OF THE BEST PLACES TO WORK" paragraph includes benefits, work-life balance, events, etc.
- Pay: The same paragraph mentions "above-market pay". Also later: "Compensation details: 00 Yearly Salary PI6e4f8c6b267d-8697" seems garbled. There's a line: "Actual compensation offered within the targeted salary range will be determined by factors such as job-related knowledge, skills, and experience. Compensation details: 00 Yearly Salary PI6e4f8c6b267d-8697". This seems like placeholder or garbage. We should not include Pay section if content is not specific (like "00 Yearly Salary" is nonsense). The instruction: 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. The posting does state "above-market pay" and "comprehensive benefits package". So we can include Benefits section with that info. For Pay, we have "above-market pay" but no specific numbers. Is that enough? It's not a specific number but it's a statement about pay. The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "above-market pay". That is a statement about pay, albeit not specific. I think we can include Pay section with that statement. However we must avoid filler like "commensurate with experience". "above-market pay" is substantive enough? It's a qualitative statement. I'd include Pay section with that sentence.
- Schedule: No mention of schedule (e.g., full-time, hours). Not present, so omit Schedule.
Now we need to format lists with - . Use
for prose.
We must not repeat job title as heading. The job title is Electrical Design Engineer. We must not put that as heading.
We must not include Job ID/requisition numbers.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's none evident.
We must preserve all substantive information.
Let's extract prose sections.
About the role: The paragraph after THE POSITION: "As an Electrical Design Engineer , you will design avionics, power electronics and battery systems interfacing within high-performance and safety-critical systems. Experience the entire product lifecycle, from concept and requirements, through design, implementation, testing and certification, and field application. You can expect a variety of opportunities ranging from products for cockpit displays and instruments, local and remote sensing, data conversion and storage, lithium battery management, along with providing analog/digital support to the power design team for AC/DC, DC/DC, and DC/AC power conversion. At Mid-Continent Instruments and Avionics, we are committed to quality, service, integrity, and professionalism. Our employees serve the best customers from all over the world in general, business and commercial, advanced air mobility, defense and special missions markets. In this role, you'll be an important part of the reason our customers consider us a premier instrument, avionics, and aircraft power solutions provider."
We could also include the opening tagline? It's more like marketing. Could be part of About the role? Might be considered fluff but it's substantive about work valued etc. Could include as part of About the role? Might be okay. But we can keep it as part of About the role preceding the role description. However the instruction: "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." The tagline is not metadata; it's marketing. Could be included as a
before the heading? But we need to use headings for sections. We could include a
before the first
as introductory text. That's allowed? The instruction says output only HTML fragment; we can have
before headings. It didn't forbid that. We'll include the tagline as a
maybe.
Now Responsibilities: The list under "WHAT YOU CAN EXPECT FROM ONE DAY TO THE NEXT". Each sentence starts with a verb. We'll make
- for each.
List items:
- Design and implement analog front-end circuits, including amplifiers, ADC/DAC interfaces, and filtering stages to enable accurate signal processing for a range of instrumentation
- Lead mixed-signal system integration to design and verify reliable data conversion, filtering, and conditioning stages.
- Research new components, technologies, and methods to incorporate into new and existing designs
- Coordinate with other functional teams, including layout, mechanical, software, and certification engineers
- Build and troubleshoot hardware, including soldering, operation of test equipment, and daily work in both office and test lab environments
- Participate in rigorous testing and troubleshooting using tools like oscilloscopes, spectrum analyzers, and logic analyzers to validate performance against stringent requirements
- Design and integrate manufacturing tools for new products, as needed
- Create detailed documentation for design verification, testing protocols, and component selection rationales in required formats, including BOMs, ECOs, and work instructions
Now Requirements: The list under "THIS POSITION MAY BE FOR YOU IF". Each bullet is a sentence with no conjunction. We'll make
- .
List:
- You have a bachelor's degree in electrical engineering.
- You have a minimum of 5 years in analog and mixed-signal design, particularly suited to precision instrumentation, signal conditioning, and integrated circuit applications.
- You have proficiency with design and simulation tools (PADS, LTSpice, or similar schematic capture).
- You have a strong grasp of mixed-signal simulation techniques and PCB layout software.
- You have a solid understanding of signal integrity, impedance matching, and EMI/EMC design practices such as RTCA DO-160 or MIL-STD-810/461.
- You are proficient with Microsoft Office.
- You have strong attention to detail.
- You are organized, focused and results oriented.
- You are a problem-solver with critical thinking and prioritizing skills.
- You have excellent verbal, written and interpersonal communication skills.
Now Skills (nice-to-have): Under "WE WOULD REALLY LIKE IT IF (but it's not a deal breaker)". List:
- You have experience with Design for Manufacture and Design for Test (DFM & DFT)
- You have design experience in the aviation industry
Now Benefits: Under "WE ARE ONE OF THE BEST PLACES TO WORK". Paragraph: "We provide above-market pay and a comprehensive benefits package.We promote an environment where you can excel in your career while still maintaining a healthy work-life balance.Our facility is climate controlled, clean, organized, and safe. We operate in a professional, light manufacturing environment.We believe anything worth doing is worth doing right - every time.We have frequent events to keep work interesting. Our food drive is super impressive, we enjoy an annual food truck fest appreciation day, monthly fruit/donut day, employee luncheons throughout the year, wellness challenges with incentives, and frequent ticket raffles for local sporting and cultural events.We have a small company feel - even though we're doing big things!"
We need to split into maybe a
for prose. Could keep as one
but it's long. Could split into multiple
for readability but not required. We'll keep as
.
Now Pay: The posting also says "above-market pay" already captured in Benefits paragraph. But we could create a Pay section with that statement. However we already mentioned above-market pay in Benefits. To avoid duplication, maybe we just include Pay section with the statement "above-market pay". But the Benefits paragraph already includes that. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Pay and Benefits into one Benefits section? But we have headings allowed: Benefits, Pay. Could we omit Pay section because it's covered under Benefits? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "above-market pay". So we could create Pay section with that statement. However we risk thin section. But we could combine Pay and Benefits into one Benefits section and omit Pay heading. The rule says we can include a section ONLY when the posting has real, specific content for it. It does have content for pay (above-market pay). So we could include Pay section with that content. But we also have Benefits section with other benefits. That's two sections. That's okay.
But we need to avoid duplication: If we put "above-market pay" in Pay section, we should not repeat it in Benefits. We could remove that phrase from Benefits paragraph to avoid duplication. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Removing that phrase would be removing substantive information. So we need to keep it somewhere. We could keep it in Benefits paragraph and also have Pay section referencing it? That would duplicate. Better to keep it only in Benefits section and not create a separate Pay section, because the Pay section would be thin (just repeating same phrase). The rule says prefer a few substantive sections over many thin ones. So we should not create a Pay section if it would be thin. So we will omit Pay section and keep the phrase in Benefits.
Thus sections: About the role (intro paragraph + role description), Responsibilities, Requirements, Skills (nice-to-have), Benefits.
We might also include
for prose. We must not repeat job title as heading. The job title is Electrical Design Engineer. We must not put that as heading. We must not include Job ID/requisition numbers. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's none evident. We must preserve all substantive information. Let's extract prose sections. About the role: The paragraph after THE POSITION: "As an Electrical Design Engineer , you will design avionics, power electronics and battery systems interfacing within high-performance and safety-critical systems. Experience the entire product lifecycle, from concept and requirements, through design, implementation, testing and certification, and field application. You can expect a variety of opportunities ranging from products for cockpit displays and instruments, local and remote sensing, data conversion and storage, lithium battery management, along with providing analog/digital support to the power design team for AC/DC, DC/DC, and DC/AC power conversion. At Mid-Continent Instruments and Avionics, we are committed to quality, service, integrity, and professionalism. Our employees serve the best customers from all over the world in general, business and commercial, advanced air mobility, defense and special missions markets. In this role, you'll be an important part of the reason our customers consider us a premier instrument, avionics, and aircraft power solutions provider." We could also include the opening tagline? It's more like marketing. Could be part of About the role? Might be considered fluff but it's substantive about work valued etc. Could include as part of About the role? Might be okay. But we can keep it as part of About the role preceding the role description. However the instruction: "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." The tagline is not metadata; it's marketing. Could be included as a
before the heading? But we need to use headings for sections. We could include a
before the first
as introductory text. That's allowed? The instruction says output only HTML fragment; we can have
before headings. It didn't forbid that. We'll include the tagline as a
maybe. Now Responsibilities: The list under "WHAT YOU CAN EXPECT FROM ONE DAY TO THE NEXT". Each sentence starts with a verb. We'll make
- for each.
List items:
- Design and implement analog front-end circuits, including amplifiers, ADC/DAC interfaces, and filtering stages to enable accurate signal processing for a range of instrumentation
- Lead mixed-signal system integration to design and verify reliable data conversion, filtering, and conditioning stages.
- Research new components, technologies, and methods to incorporate into new and existing designs
- Coordinate with other functional teams, including layout, mechanical, software, and certification engineers
- Build and troubleshoot hardware, including soldering, operation of test equipment, and daily work in both office and test lab environments
- Participate in rigorous testing and troubleshooting using tools like oscilloscopes, spectrum analyzers, and logic analyzers to validate performance against stringent requirements
- Design and integrate manufacturing tools for new products, as needed
- Create detailed documentation for design verification, testing protocols, and component selection rationales in required formats, including BOMs, ECOs, and work instructions
Now Requirements: The list under "THIS POSITION MAY BE FOR YOU IF". Each bullet is a sentence with no conjunction. We'll make
- .
List:
- You have a bachelor's degree in electrical engineering.
- You have a minimum of 5 years in analog and mixed-signal design, particularly suited to precision instrumentation, signal conditioning, and integrated circuit applications.
- You have proficiency with design and simulation tools (PADS, LTSpice, or similar schematic capture).
- You have a strong grasp of mixed-signal simulation techniques and PCB layout software.
- You have a solid understanding of signal integrity, impedance matching, and EMI/EMC design practices such as RTCA DO-160 or MIL-STD-810/461.
- You are proficient with Microsoft Office.
- You have strong attention to detail.
- You are organized, focused and results oriented.
- You are a problem-solver with critical thinking and prioritizing skills.
- You have excellent verbal, written and interpersonal communication skills.
Now Skills (nice-to-have): Under "WE WOULD REALLY LIKE IT IF (but it's not a deal breaker)". List:
- You have experience with Design for Manufacture and Design for Test (DFM & DFT)
- You have design experience in the aviation industry
Now Benefits: Under "WE ARE ONE OF THE BEST PLACES TO WORK". Paragraph: "We provide above-market pay and a comprehensive benefits package.We promote an environment where you can excel in your career while still maintaining a healthy work-life balance.Our facility is climate controlled, clean, organized, and safe. We operate in a professional, light manufacturing environment.We believe anything worth doing is worth doing right - every time.We have frequent events to keep work interesting. Our food drive is super impressive, we enjoy an annual food truck fest appreciation day, monthly fruit/donut day, employee luncheons throughout the year, wellness challenges with incentives, and frequent ticket raffles for local sporting and cultural events.We have a small company feel - even though we're doing big things!"
We need to split into maybe a
for prose. Could keep as one
but it's long. Could split into multiple
for readability but not required. We'll keep as
. Now Pay: The posting also says "above-market pay" already captured in Benefits paragraph. But we could create a Pay section with that statement. However we already mentioned above-market pay in Benefits. To avoid duplication, maybe we just include Pay section with the statement "above-market pay". But the Benefits paragraph already includes that. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Pay and Benefits into one Benefits section? But we have headings allowed: Benefits, Pay. Could we omit Pay section because it's covered under Benefits? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "above-market pay". So we could create Pay section with that statement. However we risk thin section. But we could combine Pay and Benefits into one Benefits section and omit Pay heading. The rule says we can include a section ONLY when the posting has real, specific content for it. It does have content for pay (above-market pay). So we could include Pay section with that content. But we also have Benefits section with other benefits. That's two sections. That's okay. But we need to avoid duplication: If we put "above-market pay" in Pay section, we should not repeat it in Benefits. We could remove that phrase from Benefits paragraph to avoid duplication. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Removing that phrase would be removing substantive information. So we need to keep it somewhere. We could keep it in Benefits paragraph and also have Pay section referencing it? That would duplicate. Better to keep it only in Benefits section and not create a separate Pay section, because the Pay section would be thin (just repeating same phrase). The rule says prefer a few substantive sections over many thin ones. So we should not create a Pay section if it would be thin. So we will omit Pay section and keep the phrase in Benefits. Thus sections: About the role (intro paragraph + role description), Responsibilities, Requirements, Skills (nice-to-have), Benefits. We might also include
- .
List:
- You have a bachelor's degree in electrical engineering.
- You have a minimum of 5 years in analog and mixed-signal design, particularly suited to precision instrumentation, signal conditioning, and integrated circuit applications.
- You have proficiency with design and simulation tools (PADS, LTSpice, or similar schematic capture).
- You have a strong grasp of mixed-signal simulation techniques and PCB layout software.
- You have a solid understanding of signal integrity, impedance matching, and EMI/EMC design practices such as RTCA DO-160 or MIL-STD-810/461.
- You are proficient with Microsoft Office.
- You have strong attention to detail.
- You are organized, focused and results oriented.
- You are a problem-solver with critical thinking and prioritizing skills.
- You have excellent verbal, written and interpersonal communication skills.
Now Skills (nice-to-have): Under "WE WOULD REALLY LIKE IT IF (but it's not a deal breaker)". List:
- You have experience with Design for Manufacture and Design for Test (DFM & DFT)
- You have design experience in the aviation industry
Now Benefits: Under "WE ARE ONE OF THE BEST PLACES TO WORK". Paragraph: "We provide above-market pay and a comprehensive benefits package.We promote an environment where you can excel in your career while still maintaining a healthy work-life balance.Our facility is climate controlled, clean, organized, and safe. We operate in a professional, light manufacturing environment.We believe anything worth doing is worth doing right - every time.We have frequent events to keep work interesting. Our food drive is super impressive, we enjoy an annual food truck fest appreciation day, monthly fruit/donut day, employee luncheons throughout the year, wellness challenges with incentives, and frequent ticket raffles for local sporting and cultural events.We have a small company feel - even though we're doing big things!"
We need to split into maybe a