Jobs · Engineering · Washington

Systems/AI Software Engineer

Experis · Redmond, WA · 3 wk ago
On-siteEngineeringContract
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, navigation, application instructions. Also remove duplicated lines. Must preserve all substantive info. Let's parse content: - Intro: "The ideal candidate is a strong software engineer who enjoys working across technology boundaries, learning new areas, and turning research ideas into practical engineering solutions.*** Our client, a leading technology research and development organization, is seeking a Software Design Engineer to join their team. As a Software Design Engineer, you will be part of the Applications Development & Testing department supporting innovative research projects. The ideal candidate will demonstrate strong problem-solving skills, adaptability, and a passion for turning research ideas into practical engineering solutions, which will align successfully in the organization." - Job Title line: "Job Title: Software Design Engineer" (should not be heading, we can ignore or embed in a paragraph? 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. So we can include location and pay range in a short paragraph. - Location: "Location: Redmond, WA - Onsite" - Pay Range: "Pay Range: $53 - $57.hr on Experis W2 (Benefits/PTO/401k)" - Top 3 Must-Have HARD Skills & years of experience for each: list: "2-4 years Window operating systems development Windows testing and debugging Developing software in C/C++, Python, PowerShell, and potentially Rust/C#. Computer Science Engineering degree" - "What's the Job?" paragraph: "Design, implement, test, debug, and maintain software across systems, AI, and developer platforms. Develop software in languages such as C/C++, Python, PowerShell, and potentially Rust/C#. Work with operating systems, system components, virtualization, and systems infrastructure. Build automation tools for software engineering, testing, debugging, and developer workflows. Develop and integrate AI-powered solutions for software engineering and program analysis." - "What's Needed?" paragraph: "Bachelor's degree in computer science, computer engineering, or a related technical field. 2-4 years of experience in software development and systems software design. Strong foundation in data structures, algorithms, and software design principles. Experience troubleshooting and performing in-depth testing on complex software systems. Proficiency in programming languages such as C/C++, Python, PowerShell, and familiarity with Rust/C# is a plus." - "What's in it for me?" paragraph: "Opportunity to work on cutting-edge research and next-generation systems. Engage in innovative projects that have a meaningful impact on future technology. Collaborate with a diverse and talented team of engineers and researchers. Gain experience in AI-powered engineering and scalable platform development. Work in a dynamic environment that encourages learning and professional growth." - Benefits list: "Upon Completion Of Waiting Period, Consultants Are Eligible For Medical and Prescription Drug Plans Dental Plan Vision Plan Health Savings Account Health Flexible Spending Account Dependent Care Flexible Spending Account Supplemental Life Insurance Short Term and Long Term Disability Insurance Business Travel Insurance 401(k), Plus Match Weekly Pay" - Then there is a paragraph about applying etc. That is application instructions, we should remove. - Then "About ManpowerGroup..." etc is boilerplate about company, we should remove (legal/EEO etc). So we drop that. Thus we need sections: maybe "About the role" (intro paragraph), "Responsibilities" (What's the Job?), "Requirements?), "Qualifications" (What's Needed?), "Skills" (hard skills list), "Benefits" (benefits list), "Pay" (pay range), maybe "Schedule"? Not present. So we omit Schedule. We must not create sections with filler like "commensurate with experience". We have actual content. We need to use

for each section heading. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We need to preserve all substantive info; do not invent or summarize away detail. Let's extract details precisely. Intro paragraph: combine sentences: "The ideal candidate is a strong software engineer who enjoys working across technology boundaries, learning new areas, and turning research ideas into practical engineering solutions. Our client, a leading technology research and development organization, is seeking a Software Design Engineer to join their team. As a Software Design Engineer, you will be part of the Applications Development & Testing department supporting innovative research projects. The ideal candidate will demonstrate strong problem-solving skills, adaptability, and a passion for turning research ideas into practical engineering solutions, which will align successfully in the organization." We can put that under

    About the role

    with

    . Location and pay range: maybe combine into a short paragraph under a heading? There's no heading for location/pay but we could put under "Pay" heading for pay range, and location maybe in About the role? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So location and pay range can be a short

    maybe under a heading like "Details"? But we only have allowed headings list; we could create a

    Pay

    for pay range, and maybe include location in same paragraph? Or we could add a

    Location

    but not in allowed list. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those headings are allowed. So we should put location maybe in About the role paragraph or in a separate

    without heading? It says "fold minor metadata into a short

    or drop it." So we can create a short

    for location and pay range without a heading, or we could put pay under Pay heading and location in About the role paragraph. Thus: -

    About the role

    ... plus location? Could add location sentence: "Location: Redmond, WA - Onsite." That is minor metadata, okay. -

    Pay

    Pay Range: $53 - $57.hr on Experis W2 (Benefits/PTO/401k)

    -

    Responsibilities

    • Design, implement, test, debug, and maintain software across systems, AI, and developer platforms.
    • Develop software in languages such as C/C++, Python, PowerShell, and potentially Rust/C#.
    • Work with operating systems, system components, virtualization, and systems infrastructure.
    • Build automation tools for software engineering, testing, debugging, and developer workflows.
    • Develop and integrate AI-powered solutions for software engineering and program analysis.
    -

    Requirements

    maybe same as Qualifications? The allowed headings include Requirements and Qualifications. We need to decide which to use. The posting has "What's Needed?" which is qualifications/requirements. Could use

    Requirements

    for that content. Or we could split: Requirements for experience, Qualifications for degree. But we can just use one heading; better to use Requirements for the "What's Needed?" content. Use
    • for list. Let's extract requirements: - Bachelor's degree in computer science, computer engineering, or a related technical field. - 2-4 years of experience in software development and systems software design. - Strong foundation in data structures, algorithms, and software design principles. - Experience troubleshooting and performing in-depth testing on complex software systems. - Proficiency in programming languages such as C/C++, Python, PowerShell, and familiarity with Rust/C# is a plus. We'll put each as
    • . -

      Skills

      for hard skills list: "2-4 years Window operating systems development Windows testing and debugging Developing software in C/C++, Python, PowerShell, and potentially Rust/C#. Computer Science Engineering degree" But that list is a bit messy. Let's parse: "Top 3 Must-Have HARD Skills & years of experience for each: 2-4 years Window operating systems development Windows testing and debugging Developing software in C/C++, Python, PowerShell, and potentially Rust/C#. Computer Science Engineering degree" Interpretation: Must have 2-4 years experience in each of: Window operating systems development, Windows testing and debugging, Developing software in C/C++, Python, PowerShell, and potentially Rust/C#. Also a Computer Science Engineering degree. We can create list items: - 2-4 years of experience in Windows operating systems development - 2-4 years of experience in Windows testing and debugging - 2-4 years of experience developing software in C/C++, Python, PowerShell, and potentially Rust/C# - Computer Science Engineering degree We'll put under Skills. -

      Benefits

      • Medical and Prescription Drug Plans
      • Dental Plan
      • Vision Plan
      • Health Savings Account
      • Health Flexible Spending Account
      • Dependent Care Flexible Spending Account
      • Supplemental Life Insurance
      • Short Term and Long Term Disability Insurance
      • Business Travel Insurance
      • 401(k), Plus Match
      • Weekly Pay
      Note: "Upon Completion Of Waiting Period, Consultants Are Eligible For" prefix; we can incorporate that as a

      before list or include in first li? Better to have a short

      stating eligibility then list. Thus:

      Benefits

      Upon completion of waiting period, consultants are eligible for:

        ...
      Now ensure we didn't include any boilerplate like "EEO", "application instructions", "About ManpowerGroup". We removed. Check for duplicate lines: we have not duplicated. Now output only HTML fragment. Let's craft final HTML:

      About the role

      The ideal candidate is a strong software engineer who enjoys working across technology boundaries, learning new areas, and turning research ideas into practical engineering solutions. Our client, a leading technology research and development organization, is seeking a Software Design Engineer to join their team. As a Software Design Engineer, you will be part of the Applications Development & Testing department supporting innovative research projects. The ideal candidate will demonstrate strong problem-solving skills, adaptability, and a passion for turning research ideas into practical engineering solutions, which will align successfully in the organization. Location: Redmond, WA - Onsite.

      Pay

      Pay Range: $53 - $57.hr on Experis W2 (Benefits/PTO/401k)

      Responsibilities

      • Design, implement, test, debug, and maintain software across systems, AI, and developer platforms.
      • Develop software in languages such as C/C++, Python, PowerShell, and potentially Rust/C#.
      • Work with operating systems, system components, virtualization, and systems infrastructure.
      • Build automation tools for software engineering, testing, debugging, and developer workflows.
      • Develop and integrate AI-powered solutions for software engineering and program analysis.

      Requirements

      • Bachelor's degree in computer science, computer engineering, or a related technical field.
      • 2-4 years of experience in software development and systems software design.
      • Strong foundation in data structures, algorithms, and software design principles.
      • Experience troubles

Similar jobs

AI Systems Engineer

CodeVertex SystemUnited States· 3 mo ago
RemoteEngineeringapply on codevertexinnovations.com

AI Systems Engineer

Suffolk ConstructionBoston, MA· 3 mo ago
Information Technologyapply on careers-suffolkconstruction.icims.com