Posting record
Open 12+ days
- SES' site dates the posting
- Ghostless first sees this listing
- Last checked: still up
How we know
It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.
Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking SES, so its true age is longer.
Last checked Nov 3, 2026.
How well do you match?
See how much of this posting your resume shows, and what it's missing.
Upload your resumeWhat the posting discloses
Not stated: Pay, real vacancy, AI screening.
Why these three
Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.
Some employers add pay only on their own site. Check the original posting before you rule it out.
Skills mentioned
About the role
BMS BSW S oftware Engineer
Responsibilities
- Responsible for BMS BSW development, testing and maintenance
- Responsible for configuration and debugging of BMS AUTOSAR BSW
- Responsible for the BMS bootloader and complex drivers development
- Responsible for BMS CAN Communication, network management and UDS diagnostic development
- Responsible for BMS XCP and J1939 protocol development
Qualifications
- Bachelor’s degree or above, major in vehicle engineering, computer, electronic and electrical, automation, etc.
- Familiar with C language, with more than three years of experience in BSW development, familiar with NXP and Infineon chips.
- Familiar with AUTOSAR software architecture and related specifications, with AUTOSAR (Classic) software development experience, able to use the mainstream AUTOSAR tools for ASW, BSW, MCAL software development is preferred.
- Familiar with AUTOSAR basic software development and configuration.
- Familiar with the working mechanism of Bootloader, with relevant development experience is preferred.
- Familiar with automotive protocols (CAN/J1939/XCP) and diagnostic protocols
- Familiar with functional safety ISO26262, familiar with multi-core distribution and data protection.
Something wrong with this posting?