Your work will be generally easier. Dealing with automated testing means your scope and depth of knowledge will be a lot smaller. While you're going to still need to know some SQL, dealing with Java or whatever language they use, the depth required is going to be much less.
Work/life balance is a gamble on either side. You could have a QA team that has huge grinds for deadlines, or it could be super laid back and casual.
I would personally say, unless you like the testing side of the world, to stay outside of a STE type role until you have your feet wet with development.
I had one round of technical interviews with the manager. He started by discussing my previous experience and some courses I am taking in my master's program. After that, he asked me about L2 switching and L3 packet flow.
This company has come on campus, so after the offline round which includes MCQ of aptitude, computer networks and operating system, nearly 10% students were shortlisted for GD round followed by interview round.
Total 4 rounds. 1st round: Online quiz (Networkathon) which had 20-25 questions. Asked switching and routing basics. 2nd round: Face-to-face interview. Started with switching and routing basics and then went in-depth for OSPF. 3rd round: Manageria
I had one round of technical interviews with the manager. He started by discussing my previous experience and some courses I am taking in my master's program. After that, he asked me about L2 switching and L3 packet flow.
This company has come on campus, so after the offline round which includes MCQ of aptitude, computer networks and operating system, nearly 10% students were shortlisted for GD round followed by interview round.
Total 4 rounds. 1st round: Online quiz (Networkathon) which had 20-25 questions. Asked switching and routing basics. 2nd round: Face-to-face interview. Started with switching and routing basics and then went in-depth for OSPF. 3rd round: Manageria