It does kind of depend - I've made a career of being both: being the log designer that understands software (and makes sure the registers make sense etc) and/or the software guy that understands the c hips (and can read the verilog and find the bug) etc etc

Both require deep domain knowledge that doesn't always overlap - but being able to do both makes you more valuable