To begin the application process, please enter your email address.
Company Contact Info
- Vancouver, WA 98683
Sorry, we cannot save or unsave this job right now.
Report this Job
Saving Your Job Alert
Job Alert Saved!
Could not save Job Alert!
You have too many Job Alerts!
This email address has reached the maximum of 5 email alerts. To create a new alert, you will need to log into your email and unsubscribe from at least one.
Email Send Failed!
Kforce Technology • Vancouver, WA
Posted 23 days ago
RESPONSIBILITIES:Kforce is looking to help our client in identify two (2) C/C++ Firmware Engineers to join a team in Vancouver, Washington (WA). This is a long-term project located in Vancouver, Washington where you will be joining a team of other Firmware Engineers. Job duties:
- Port existing C/C++ modules to new interface standards
- Work with code owners to understand current interfaces
- Design new interfaces following new C++ component interface requirements
- Code & write test units for new C++ interface
- Documentation of changes
- C/C++ programing languages
- Basic Linux (Unix) utilities such as LS, RM, GREP, TAR
- Build system such as Make and Jenkins
- Understanding multithreaded and/or multi-process systems
- This team is the first line triage and local defect reproduction from internal tests such as: off-site DIST, SRVT, EDT and on-site testing DET/FW smoke testing/ME specified
- Support the Toyo emulator support that is used in engine manufacturing and HW lab
- Set up LP units
- Log and investigate issues in Jira
- Reproduce incoming CPE issues in Jira
- Experience in code debugging and usage of debuggers and tracing tools, memory corruptions and leakage detection/correction
- Python knowledge a plus (or other programming/scripting languages)
- Understanding of state machine design and implementation, event driven control, complex error detection/recovery, synchronization between multiple devices with multiple states
- Understanding of distributed control, different coupling levels between subsystems, clear break of responsibilities between subsystems, communication protocols, remote procedure calls and timing implication