Agree entirely. The law hasn't caught up requiring compensation for on call/off hours work at the existing salary level (at least in the US).
Moving from devops/infrastructure to security I doubled my total comp (salary + 401k + vacation + health insurance) while reducing the hours per week I work down to ~37 hours (I also get to work remote and never work nights or weekends). If you're in ops/devops/infrastructure, I highly recommend the transition to others, the current demand for competent security professionals is quite literally bananas.
TL;DR If you're in ops, get out of ops (easy) or work someplace that will compensate you appropriately for on call/nights/weekends work (hard).
If you know how to securely design and build AWS environments, you qualify for “cloud security architect” positions based on my interviewing experience. Beyond that, interview for security positions and take note of your gaps to improve on.
Agree entirely. The law hasn't caught up requiring compensation for on call/off hours work at the existing salary level (at least in the US).
Moving from devops/infrastructure to security I doubled my total comp (salary + 401k + vacation + health insurance) while reducing the hours per week I work down to ~37 hours (I also get to work remote and never work nights or weekends). If you're in ops/devops/infrastructure, I highly recommend the transition to others, the current demand for competent security professionals is quite literally bananas.
TL;DR If you're in ops, get out of ops (easy) or work someplace that will compensate you appropriately for on call/nights/weekends work (hard).