????優(yōu)秀的軟件工程師很難找,，更不要說聘用和留住他們了。

????難怪越來越多的人拼了命想成為軟件工程師,。招聘網(wǎng)站Glassdoor的數(shù)據(jù)顯示,，谷歌（Google）軟件工程師的平均年薪保持在145,000美元上下，但也有550,000美元的天價(jià),。

????但經(jīng)過培訓(xùn)成為軟件工程師,、拿下知名高薪職位，就算對一些名校計(jì)算機(jī)科學(xué)專業(yè)的畢業(yè)生來說也絕對不是一件容易的事,。教育初創(chuàng)公司Codeacademy的聯(lián)合創(chuàng)始人扎克?西姆斯和科技業(yè)招聘網(wǎng)站Hired.com的聯(lián)合創(chuàng)始人馬特?密茨凱維奇就如何在硅谷獲得高薪工作提出了幾點(diǎn)建議,。

????不要只學(xué)習(xí)課程。

????動手做點(diǎn)什么,，比方說一個(gè)網(wǎng)站或iPhone應(yīng)用程序,。西姆斯說：“如果只上課，更多地是滿足課程要求,。但如果是你想做點(diǎn)什么,，你就會不斷地應(yīng)用學(xué)到的東西，得到成長,?！倍遥芏酀撛诠椭饕蚕Ｍ芸吹揭恍┈F(xiàn)實(shí)的作品,，了解你真正能做些什么,。

????要學(xué)習(xí)數(shù)據(jù)結(jié)構(gòu)和算法。

????密茨凱維奇解釋說,，兩者都是計(jì)算機(jī)科學(xué)的基礎(chǔ),，在公司面試中占比很大。有些人可能會編應(yīng)用程序,，寫很多代碼,，但對數(shù)據(jù)結(jié)構(gòu)和算法沒有深入的理解。潛在雇主很快就會發(fā)現(xiàn)基礎(chǔ)理解的缺失,。

????不要為了軟件工程師而當(dāng)軟件工程師,。

????搞清楚你要做的是什么，確保有合理的原因,?！翱梢試L試一下，搞明白這些是不是你真正感興趣的,，之后再全身心投入,，”西姆斯說。他還指出,，想當(dāng)然地以為未來能夠獲得一線公司年薪120,000美元的工作機(jī)會也是不現(xiàn)實(shí)的,。“不是每個(gè)人都在谷歌工作,。也不是每個(gè)人都在初創(chuàng)公司工作,。”

????不要以為自己可以唱獨(dú)角戲,。

????與普遍觀點(diǎn)相反,，編寫代碼不總是大學(xué)宿舍里的單打獨(dú)斗。（當(dāng)然,，可以是這樣,。）更為常見的情況是，這是一項(xiàng)與其他人協(xié)作的過程,。別人可以幫助你指出該學(xué)什么,，找出你代碼中的錯(cuò)誤，還可以根據(jù)你的代碼繼續(xù)推進(jìn),。

????要養(yǎng)成習(xí)慣,。

????“我看到很多學(xué)員說，我會每天學(xué)15分鐘,，”堅(jiān)持做下去,，”西姆斯解釋說,。實(shí)際上，這種看似零散的方式比發(fā)誓你將在兩周內(nèi)學(xué)習(xí)如何建一個(gè)網(wǎng)站更加現(xiàn)實(shí),。借用一句古諺：這是一場馬拉松,，不是百米沖刺。（財(cái)富中文網(wǎng)）???

????Great software engineers are hard to find, let alone hire and keep.

????Which is why more people than ever are trying to become one. The average annual salary for Google (GOOG) software engineers, for instance, now hovers around $145,000 and skyrockets to as much as $550,000, according to job site Glassdoor.

????But training to be a software engineer and snagging a high-profile, high-paying position afterwards isn't simple or easy, even for some computer science grads from top-tier schools. Zach Sims, co-founder of the education startup Codeacademy, and Matt Mickiewicz, co-founder of tech job recruiting site Hired.com, offer several do's and don'ts for landing a plum role in Silicon Valley.

????Don't: Just take courses.

????Build something, like a website or an iPhone app. "If you're just taking a class, it becomes much more about fulfilling the requirements for a class, but if it's about what you want to build, you're constantly being reinforced by seeing the actual manifestations of what you're learning," says Sims. Plus, many potential employers will want to see a portfolio of real-world work demonstrating what you can really do.

????Do: Study data structures and algorithms.

????Both are computer science fundamentals, and both make up a large part of the interview process with companies, explains Mickiewicz. It's possible for people to build some applications and write a lot of code without having a deep understanding of data structures and algorithms -- and some do -- but that lack of basic understanding is something potential employers will suss out quickly.

????Don't: Do it just because.

????Understand what you're getting yourself into, and make sure it's for the right reasons. "You can kind of dip your toes in and figure out whether this is something you're really interested in before committing whole-hog," says Sims. He also points out that it's unrealistic to assume you'll get a job at a top company that pays $120,000 a year. "Not everyone works at Google. Not everyone works at a startup."

????Also, don't: Think you can fly solo.

????Contrary to popular belief, coding isn't always a solo activity conducted from one's college dorm room. (Though of course, it can be.) More often, it's a collaborative process with others, who may for instance, help you figure out what to learn, troubleshoot your code or build on top of it.

????But do: Form habits.

????"We see a lot of learners say, 'I'll do 15 minutes a day,' sticking to that and actually doing it," explains Sims. Indeed, this piecemeal approach is more realistic than swearing you'll learn how to build a website in two weeks. To borrow the old adage: It's a marathon, folks, not a sprint.