I'm applying for a senior Site Reliability Engineer role and, while I've been working in systems, release, and DevOps roles for a fair amount of time, my coding skills aren't strong. The team seems highly skilled, and during my call with the hiring manager, I was overwhelmed by technical jargon. I've managed to secure a spot for the technical assessment, but I'm not sure if I'm the right fit for this job, and I'm considering a career change. However, I also need the money for housing. Should I go ahead with the assessment, knowing it might be a rough experience, and just take it as a learning opportunity? Or would it be better to skip it and not waste anyone's time? I guess I just want to know if it's worth the potential embarrassment. Update: I did go through with it, and it turned out to be much better than I anticipated! Thanks for all the support, everyone!
3 Answers
I think you should absolutely go for it! They must have seen something in your application to bring you this far, so don’t doubt yourself. If it feels challenging, just think of it as an opportunity to show your problem-solving approach, even if you don’t know the exact answer. Plus, every experience is a learning one!
If you're free and have the time, just do it! There's really no downside—you might even surprise yourself. Most teams have areas where they can improve, and you might find inefficiencies once you're in. Plus, experiencing the process could give you some insights for future roles.
Definitely go for the assessment! I had a similar experience where I felt out of my depth, but I saw it as a chance to learn. Even if you don't get the job, you’ll leave with a better understanding of what employers are looking for and what skills you might want to work on. It's all part of the growth process!
Exactly! I think the assessment is just as much for you to gauge fit as it is for them. Think of it as an informal way of exploring your options!