Our client is looking for a quality Systems Engineer to join their team! 

JOB RESPONSIBILITIES

• responsible for the overall architecture of the products our client designs.
•  essential in designing, implementing and maintaining information pertaining to product development including: evaluation, selection and adaptation of company procedures as well as translation of technical guidance. 
• Customer Interface (CI) Role: Represents the point of view of the customer, and sees that it respected throughout the program. Serves as the interface to customer technical personnel in this role, striving to build the “right” system, and that the details are as customer-friendly as possible. Keeps customer technical personnel up to date on design decisions, rationales, issues, and concerns. Works the technical side of change requests, finding out what the customer intends and why, and communicating the impacts that are discovered.
• Requirements Owner (RO) Role: Assists Requirements Engineering team in translating customer needs into specific, well-written (traceable, allocated) system requirements to architect and design systems and subsystems (sub-elements, pieces, software and hardware, control items, etc.). Requirements duties include understanding all external interfaces and ensuring the functional architecture correctly captures the need.
• Advanced Development (AD) Role: Unique to our client, Systems Engineers, in concurrence with their work in the product launch space, also have the opportunity to work on advanced development projects. This work pertains to current projects in process, or can be exploratory in nature, based on current market trends and societal innovations. It’s an opportunity to stretch our minds creatively, learn and apply new techniques and explore different ways to meet our internal and external customer needs.
• System Designer (SD) Role: Creates the high-level system architecture and design and selects major components. Because of the complexity of projects employing systems engineers, the emphasis tends to be on architecture, high-level design, integration, and verification, rather than on low-level development.
• System Analyst (SA) Role: Confirms that the designed system will meet requirements. Typical analyses include system weight, power, throughput, and output predictions for hardware systems, memory usage, interface traffic, response times, fault setting, and diagnostics for software systems. Usually the more complex parts of the system need models in order to demonstrate that they will work properly and interface properly with the external world
• .System Integrator (SI) Role: Serves as a proactive troubleshooter, looking for problems and arranging to prevent them. Since many problems happen at interfaces, this role involves a very, close scrutiny of interfaces, particularly internal, subsystem-to-subsystem interfaces, to ensure that each subsystem is not going to interfere with the others
• .Logistics and Operations (LO) Role: Captures the back end of the “cradle-to-grave” system life cycle. During the operational phase, systems engineers sometimes operate the system for the customer; more often, they serve “on call” to answer questions and resolve anomalies. Bring maintenance, operation, logistics, and disposal concerns to the requirements, design, and development phases.
• Coordinator (CO) Role: Coordinates groups and resolve system issues, seeking consensus, or making recommendations, when consensus among the participants becomes difficult to achieve. Team leadership and the ability to facilitate groups in developing their own leadership skills and working norms are skills that are more necessary for this role than for others.
• Validation and Verification (VV) Role: Plan and implement the system verification program to ensure the system, as designed and built, will meet the specified requirements. Write the detailed system test plans and test procedures. Answer questions surrounding system behavior during system verification. Respond to anomalies with the best possible understanding of the system design.
   

•  A Bachelor's degree in Mechanical, Electrical, or Computer Science Engineering or demonstrated equivalent work experience may be considered.
• A Master's degree in Systems, Mechanical, Electrical, or Computer Science Engineering preferred.
• Minimum of 2 years of work experience in product development required.
• Experience in development of mechatronic components and/or systems preferred.
• Experience and or interest in the automotive industry

Comp: 86-120K Base (bonus is company discretionary)