這是我自己在職涯早期也犯過的錯誤，為了讓經歷好看些，硬是去做一些與目標職位好像有些相關的side projects，但實際上這樣做通常都是反效果。原因很簡單，為了應徵而搞的side projects通常都是花兩三個月的業餘時間完成的，但是你的目標公司可都是搞相關領域搞了N年的專家，花那一丁點工夫做出來的東西有多淺根本一瞟就知道，講白了就是班門弄斧，還把自己本來更專精的領域給遮蓋掉了。
「我們的web service使用了docker container發佈」
「為什麼會有負載不均的情形？一開始切分service components的根據為何？是否有數據證明這樣的資源調整方式比一個monolithic service更精省？省多少？」
…… etc. etc.
總之對於自己的履歷上寫的經歷以及手上在做的事至少要有被挖個3 – 5層深的信心，不然最好提都不要提。
Great post, and I agree with almost everything. But I do disagree with the side-project advice for two main reasons:
First: Many side projects are small and shallow. After working 40 hours a week, few people have more than a few hours a week to put into side-projects. Even if a side project is messy, shallow, and incomplete, I think it can still be good to show off.
Second: Especially if you’re coming from an non-WP background, doing a small WordPress project (building a plugin or a site) can be extremely helpful. In the interview you’ll at least have a few words to say about what you like and don’t like about the ecosystem, and the experience will probably be extremely helpful for the trial phase of the interview.
When I applied to Automattic, I showed off an incomplete plugin that I finished more than a year later. I also talked about several projects that I started and never completed.
Of course, this is just my personal experience/opinion. Maybe I just got lucky with my interview 😀
Great points, Nabeel 🙂
I think what you said makes great sense and I should relax my opinion a bit. The case I consider problematic is that the interviewee takes the shallow side projects as the very highlight to show, instead of the professional areas that they have worked for years. So maybe the better way to put it is “You can do side projects to impress us, but please take it as the bonus, not the core." Does that make sense?
Also, from what you had done during your time with us, I can even hardly think you were just lucky, and I still think that it’s our great lost of losing you
Btw, just in case you’d be interested, WordPress.com now supports podcasting after we talked about it like two years ago https://en.support.wordpress.com/audio/podcasting/ 🙂
讚Liked by 1 person
I can definitely agree with this statement 🙂
One additional note / advice I would add to anyone applying to Automattic (and please correct me if things have changed and this is no longer true): After recommending several really strong developers who were immediately rejected, I came to realize that Automattic does not hire fresh graduate or junior developers.
Again, maybe this has changed since I left, but when I was at Automattic you really needed several (at least 5) years of solid work experience. I think this is an unfortunate side-effect of a distributed organization. The story for developing the skills of junior employees isn’t quite figured out, so they lean more towards experienced developers who are more likely to be able to work independently and self-train.
One of my big regrets is never finding time to work on that project with you! 😀
I think this assessment still holds. What changed is that we has realized that we miss a big talent pool because of this. Thus, we are actually developing and experimenting on the junior developer program. Nothing has come official yet but hopefully it will be materialized soon 🙂