Quote (r4f @ Jan 11 2023 07:41pm)
When I review candidates, I solely pay attention to candidates’ hands-on experience in the industry and give technical assessments accordingly. For senior level software engineers, I need to see that you’ve had at least five years as a full time SE, and in the assessment I need to see that you are productive at writing code at the level that your claimed hands-on experience should reflect. I don’t care too much about the specific programming language proficiency, and I don’t care about education. Getting to a productive SE level does require a piano-practice-like discipline. You can’t be stack-overflowing yourself to the top, although I’m sure many at other places get away with that. It’s all about mastery through repetition and getting exposed and comfortable to as many common problems and solutions. If you can’t code at that capacity, I don’t care about what theories or paradigms you have to babble about. If you’re not pushing commits to my branches actively without breaking builds, I can care less about your takeaways from reading the dragon book. Again, this is for a Senior SE. I would have completely different expectations from a Staff SE.
Before I started my own company, I worked for a handful of the popular tech companies. After you’re onboarded, it is sink or swim. If you aren’t showing your value quickly, your $500k+ pay package won’t last for very long.
If you’re expecting something more than a Junior SE without much hands-on industry experience, just know that many top tech employers share more or less the same subjective viewpoint as to what I have described above.
You have to start somewhere and you’ll get there with time.
I hope this helps.
Yes very helpful thoughts and much appreciated.
I am seeking more of a business/data analyst role though. Admittedly, as you already know, my work experience in any of these IT positions is in need of much work.
So I am not sure what the fundamental differences are between a Jr, Staff or Senior level for either the BA, DA, or as you mention SE roles.
I have a moderate knowledge and official certifications now of SQL, Python and Power BI. I know of course that work experience and hands on for 8+ hours a day is much different than studying for 3-4 hours per night for the last 5-6 months (admittedly with 1-2 days off per week). Maybe you can offer some more clarification on what the roles entail.
I had thought that my thorough understanding of all areas of the insurance business and familiarity with nearly all of the programs the company uses would help - note this is a fortune 100 company and I have worked here for years. I feel like you are suggesting this will not help me as much as I had assumed it will?