Earlier quoted context omitted.
I'm guessing it might be because the years of embedded C experience (even if it's decades) don't necessarily show you're able to put aside what you learned and learn what's a wildly different language that happens to have some superficial similarities. In some respects it might be even harder to get someone with too many years in C to start writing C++-style code (or vice-versa!), given how difficult both languages a…
C'mon. In practice the differences are hugely overblown. The fundamentals are about the same. Also doing "modern" Cpp with dogmatically ugly static and reinterpret_cast and shared or unique_ptr:s everywhere is just annoying. "Best practices" in SWE are usually antipatterns since they are Cargo culted in a dogmatic way. But then again I am a embedded C programmer ...
> Also doing "modern" Cpp [...] is just annoying.
You're basically saying "I can totally do what you're asking, but I actually think it's super annoying and I'd very much rather do things my own way, so you should hire me because I'm an excellent candidate." Do you expect this to be a good sell?