Should frontend engineers be required to participate in on-call rotations for backend monitoring?

My manager recently informed me that due to an imbalance between frontend and backend team sizes, I will be expected to participate in an on-call rotation primarily meant for overseeing backend issues. As a frontend engineer, I do not have the expertise to resolve backend problems directly, and my role would only involve alerting the appropriate backend personnel. Is it fair or practical to include frontend developers in monitoring tasks for backend systems, considering our different skill sets and responsibilities?

hey, i think its a bit odd that we need to watch backend alerts without proper training. has anyone here found a workaround or maybe a way to get more tailored training? curious to hear your takes on easing this imbalance.

The expectation that frontend engineers participate in on-call rotations for backend issues can pose challenges when monitoring and issue resolution require specific backend expertise. In similar situations, I found it beneficial to propose additional documentation and training to help bridge the skill gap. In my experience, clear escalation pathways and responsibilities outlined by management can mitigate potential inefficiencies. The organization should consider workload distribution and the unique skillsets of each team, ensuring that the proposed solution aligns with both practical capabilities and fairness in responsibilities.

i get the need for flexiblity but havent seen that its fair. i’m not too comfortable watchin backend issues when that’s not my strong suit; they should invest in training or rethink the rota to avoid overload.