Use interviews to find your weak points and get practice. You don't want to come across your perfect job and have that be your first interview.
For my part, when I look at low-level programmers, I really just want to make sure they have a handle on pointers and the allocator, stack vs. heap, strategies for making that understandable (RAII in C++ or reference counting for example), how to debug access violation (and what it really means). Most everything else can be taught.
Also, for crypto, there are lots of entry-points for web developers -- web penetration is a big part of it.
Good tips, thanks. I haven't really interviewed in a while.
I am looking at pentesting as a potential next step. Based on my initial research it seems doable and might lead to good opportunities down the road...
I'm in a vaguely similar boat. Electronic Engineer, doing low-level software for the last decade, and now having to pivot to more web stuff, because there's little other work where I am. And yes, also in mid-thirties.
For my part, when I look at low-level programmers, I really just want to make sure they have a handle on pointers and the allocator, stack vs. heap, strategies for making that understandable (RAII in C++ or reference counting for example), how to debug access violation (and what it really means). Most everything else can be taught.
Also, for crypto, there are lots of entry-points for web developers -- web penetration is a big part of it.