|
|
|
|
|
by rhubarbcustard
3957 days ago
|
|
I have interviewed a fair number of people for different positions over the years, here's my 2p: 1. I would look at your CV and see your narrow focus but I would still be wondering based on your experiences whether you could move to the technology we use. 2. Good/great developers seem to be in short supply, if you can prove your ability to understand code, build robust things and ship you would be just fine in my interview. 3. I think you would find a lot of very similar technology in the Java field and it wouldn't be a huge hurdle for you to pick that up if you have a good and deep understanding of how you currently deliver apps using ASP. If you could show on your portfolio how you have picked up Java/Ruby/Python/whatever based on your 20 years of experience and show you understand "how things work" rather than the nitty gritty of a the language then you would beat a lot of the people we interview. In short, if you came to an interview for a Java job I would be more interested in how easy you would be able to learn what we do with Spring etc and how much and how deeply you understood the stack you were working with rather than worrying too much about you not have "5 years of Spring MVC" or whatever other blurbs HR stuck on the job description. I've interviewed a lot of people who have no clue whatsoever how MVC works and have no notion about how things fit together to make a system, they just fill in the gaps in the Spring/Hibernate/library config and write a few lines of code and "it just works". If you have the deep knowledge I think you can easily take a senior/architect role in Java-land. |
|