Jobs · Engineering · Washington

Electronics Engineer

Kickmaker · Seattle, WA · 3 wk ago
On-siteEngineeringFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We need to parse the posting. First, identify content: - About the role: description of Kickmaker and role? The posting includes intro about Kickmaker, then "As an Electronics Engineer, you will be responsible for supporting hardware development on the projects assigned to you." That's about the role. So we can have About the role section with that paragraph. - Responsibilities: bullet list after "In this role, your responsibilities will include:" then list items. So we need a Responsibilities section with
  • each bullet. - Requirements: "Experience Required: 5 years in a relevant field". Also maybe location? But location is not a requirement. Also maybe "Your adventure at Kickmaker" is more about benefits? Actually "Your adventure at Kickmaker" describes projects, growth, etc. Could be Qualifications or Skills? Might be more about what you'll do. But we have a separate "Qualifications" maybe for education? Not present. Skills: maybe list of tools: Altium, Circuit Studio, Eagle, KiCad, etc., also testing tools, etc. Could be Skills. - Benefits: "We offer a benefits package designed to support you and your family while keeping costs low. This includes health and dental coverage, paid time off and 5 sick days for rest and renewal. You can also join our 401(k) plan to invest in your future." So Benefits section. - Pay: "Base Salary: $100 000 to $115 000/ year". So Pay section. - Schedule: Not mentioned. No schedule info. So we should not include Schedule. - Qualifications: maybe "Experience Required: 5 years in a relevant field" could go under Requirements or Qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide where to put experience. Likely Requirements. Qualifications could be education or certifications not present, so we skip Qualifications. - Skills: could list technical skills: CAD tools, prototyping, testing, supplier consultation, eco-design, etc. We'll extract from responsibilities bullet list maybe but we should not duplicate. Better to have Skills section summarizing tools and competencies: Altium, Circuit Studio, Eagle, KiCad, etc.; oscilloscope, multimeter, spectrum analyzer; supplier consultation; eco-design analysis; etc. But we must preserve all substantive information; we cannot invent or summarize away detail. However we can rephrase but must keep info. The responsibilities list already includes many of those items; we could put them under Responsibilities. Skills could be separate but might duplicate. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine responsibilities and skills into Responsibilities, and not create Skills unless distinct. However we have a list of tools that could be considered skills. But they are already in responsibilities bullet list: "Computer-Aided Design (Altium, Circuit Studio, Eagle, KiCad, etc.)" etc. So we can keep them under Responsibilities. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. Check for any other specifics: "Location: Seattle, Washington, USA" - location is not a heading; we can fold into a short

    maybe under About the role or after. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So we can include location as a short paragraph maybe after About the role. Also "Your adventure at Kickmaker" includes description of projects, growth, etc. That could be part of About the role or maybe a separate section like "What you'll do". But we already have About the role covering role description. Could add a paragraph about projects under About the role. Also "Our Culture & Spirit" etc. That's boilerplate? It's about company culture; could be considered About the role? Might be considered fluff but it's substantive about company. However instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Culture description might be okay to keep? It's not boilerplate; it's describing company spirit. Could be included in About the role. But we must not repeat job title as heading. Already not. We need to output only HTML fragment, no /, no markdown fences. Let's craft: maybe not required; just use headings and content. We'll do:

    About the role

    Kickmaker is a high-tech product design and industrialization agency supporting customers from prototype to production in markets such as medical, new mobility, electrification, agrotech, robotics, IoT and consumer devices, with cross‑disciplinary skills in embedded AI, high‑tech manufacturing automation, eco‑design, industrial design and Web 3.0. As an Electronics Engineer you will support hardware development on assigned projects, working in Seattle, Washington, USA.

    Then Responsibilities:

    Responsibilities

    • Defining project requirements based on client needs
    • Defining the product architecture according to criteria such as cost, feasibility, timeline, and components, in line with client needs
    • Computer‑Aided Design (Altium, Circuit Studio, Eagle, KiCad, etc.)
    • Prototyping (schematic, layout, wiring design)
    • Preparing manufacturing documentation (Gerber files, BOM, assembly drawings, etc.)
    • Planning, conducting, and validating tests using available tools (oscilloscope, multimeter, spectrum analyzer, etc.)
    • Supporting the project during certification phases (EMC, radio, electrical safety, etc.)
    • Consulting with suppliers (EMS): cost optimization, assembly, lead times, component sourcing, etc.
    • Providing on‑site support for projects (visits to EMS facilities, discussions on manufacturing, etc.)
    • Ensuring compliance with established process quality standards and applicable HSE regulations; participating in defining eco‑design and industrial relocation strategies
    • Participating in and implementing product life cycle analyses to improve products’ ESG impact
    • Implementing eco‑design analysis guidelines in product development
    • Ensuring the development and maintenance of the company’s brand image with clients and ensuring compliance with applicable procedures, both in the performance of their own duties and with regard to employees under their supervision
    • Remaining aware of the responsibilities associated with the performance of their duties and not claiming unawareness under any circumstances
    Requirements:

    Requirements

    Experience Required: 5 years in a relevant field.

    Benefits:

    Benefits

    We offer a benefits package designed to support you and your family while keeping costs low. This includes health and dental coverage, paid time off and 5 sick days for rest and renewal. You can also join our 401(k) plan to invest in your future.

    Pay:

    Pay

    Base Salary: $100,000 to $115,000 per year.

    We should not include Schedule. Check for any duplicated lines: we have not included navigation etc. Make sure we preserve all substantive information: we included location, description of Kickmaker, responsibilities list, experience, benefits, pay. We omitted "Your adventure at Kickmaker" description of projects and growth; also omitted "Our Culture & Spirit" and video mention. Are those substantive? They describe what you'll work on and culture. Might be considered relevant. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that info somewhere. Could add a paragraph under About the role or a separate section like "What you'll work on". Since we already have About the role, we can incorporate that description. Let's extract "Your adventure at Kickmaker": "At Kickmaker you’ll work on 5–10 projects annually, choosing from a wide range of industries : from robotics, medical devices, fitness tech, and automotive, to micro‑mobility, beauty tech, sports exoskeletons, and AI‑driven hardware. Your path evolves with your curiosity: we help you grow where your professional ambitions and personal passions meet, always connected to the latest tech breakthroughs." Also "Our Culture & Spirit": "Kickmaker is built by innovators, for innovators. Across our 7 offices we give you the tools to make your ideas happen. Our vision is simple: build a space where innovators can explore, experiment, and push boundaries together. If you’re curious about our spirit and way of working (and you’ve got a minute) check out this short video where Leonardo da Vinci “visits” Kickmaker.An image is worth a thousand words, and this one will give you the full vibe If you’ve ever looked at a product and thought, “I could build this better,” let’s talk! We may use artificial intelligence (AI) tools to support parts of the hiring process, such as reviewing applications, analyzing resumes, or assessing responses and identifying potential inconsistencies or verification signals in application materials based on available information. These tools assist our recruitment team but do not replace human judgment. Final hiring decisions are ultimately made by humans. If you would like more information about how your data is processed, please contact us." The latter part about AI tools and data processing is maybe boilerplate? It's about hiring process; could be considered application instructions? It's not exactly instructions to apply but about process. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI tools statement is about hiring process; could be considered application instructions? It's not exactly instructions to apply but about how they process data. Might be considered legal/privacy? It's about data processing. Might be considered boilerplate. Safer to drop that. The earlier culture description is substantive about company spirit; we can include in About the role. Thus About the role paragraph can be expanded. Let's craft About the role:

    About the role

    Kickmaker is a high‑tech product design and industrialization agency supporting customers from prototype to production in markets such as medical, new mobility, electrification, agrotech, robotics, IoT and consumer devices, with cross‑disciplinary skills in embedded AI, high‑tech manufacturing automation, eco‑design, industrial design and Web 3.0. As an Electronics Engineer you will support hardware development on assigned projects, working in Seattle, Washington, USA. At Kickmaker you’ll work on 5–10 projects annually, choosing from a wide range of industries — from robotics, medical devices, fitness tech, and automotive, to micro‑mobility, beauty tech, sports exoskeletons, and AI‑driven hardware. Your path evolves with your curiosity: we help you grow where your professional ambitions and personal passions meet, always connected to the latest tech breakthroughs. Kickmaker is built by innovators, for innovators; across our 7 offices we give you the tools to make your ideas happen, with a vision to build a space where innovators can explore, experiment, and push boundaries together.

    That covers culture and adventure. Now ensure we didn't miss any substantive info: "We may use artificial intelligence (AI) tools to support parts of the hiring process..." we dropped; might be considered minor metadata about hiring process; could be folded into a short p but it's about process not role. The instruction says remove application instructions. This is about hiring process, maybe considered application instructions. Safer to drop. Also "If you would like more information about how your data is processed, please contact us." That's privacy; drop. Now check for any other specifics: "Present in France, China and

Similar jobs

Electronics Engineer

EVSAllendale, NJ· 3 days ago
Information Technologyapply on evs-broadcast-equipment-n.contactrh.com

ELECTRONICS ENGINEER

Naval Air Warfare Center Training Systems Division (NAWCTSD)Patuxent River, MD· 1 mo ago
Information Technologyapply on navair.yellogov.com

Electronics Engineer

Air Force Civilian ServiceDayton, OH· 1 mo ago
Engineeringapply on afcs.experience.crmforce.mil