3 ms·

I would really, really love to hear some details of how you ended up in the very high paying jobs, and any advise you might have for how to manage one's career

I would really, really love to hear some details of how you ended up in the very high paying jobs, and any advise you might have for how to manage one's career to maximise earning potential, assuming one starts off with a quant / ML / software eng background. Also, if you have any observations or advise for developers who are NOT based in the US, i'd love to hear that.

siberianbear 10y ago
I went to a “second-tier” school in the University of California. Having worked with engineers from better schools (e.g., Stanford), I would say I was as talented on average as they were, but I had terrible study habits in high school and so my grades weren’t that good. At the university I did a lot of stuff that wasn’t required for my degree, like doing a senior design project and leading the local chapter of IEEE. I hustled to get internships. I took an internship doing IT support at a civil engineering firm my first year, but later I got better internships at Apple and Intel. By the time I graduated, I was a far stronger candidate than my peers at my school. I had six job offers when I graduated. I job hopped a couple of times early in my career for better positions, but I eventually ended up at a company I really liked and stayed there for twelve years. You don’t say much about your background or where you are, so it’s hard to answer your question. I think there’s really two parts to your question: “1. How do I become a great software engineer?” and “2. How do I emigrate to a country with higher salaries for engineers?” To me, these are pretty basic questions. To be a great software engineer, teach yourself to solve difficult problems and then go do it. Always push the limit of your ability. Learn multiple languages. If you’re a system software person, go tinker with databases. If you’re a compiler guy, go tinker with neural networks. If you’re a C programmer, go learn Scheme or Haskell. Read books on lots of topics: microprocessor design, good software engineering practices, design patterns, etc. In your job, be indispensable. Be the guy who can solve any bug or solve any problem, even if it spans multiple areas of knowledge. Be indispensable. Don’t be the guy who holes himself up as a guru in a little obscure walled-off technical area and hides his knowledge as a form of power or job security. There is no job security. Even if you’re good, your company could go through a rough spot and lay you off. The only job security is to be known in a network of other people as a great engineer, and then if you don’t have work it’s no problem to find another job. If you go interviewing for any serious jobs, you’re going to get coding questions. Whether they are a great way of assessing a candidate is a topic of debate on HN, but that doesn’t matter. You’re going to get them. People have put together anthologies of these questions: be sure you can solve them. If you practice and are good at it, you will be able to solve similar problems that you haven’t seen before. If you’re in an “emerging economy” with low salaries for engineers, then figure out how to get to a different country. The demand for software engineers worldwide is huge right now, and so if you can figure out a way to legally work in a richer country and you have any talent at all, you can find a job. Visa programs put a high value on university degrees in technical fields, so if you don’t have one it’s likely you’ll need to get one. The United States has the best paying jobs for software engineers right now, but it is very hard to emigrate to right now because the H1-B visa category is oversubscribed. The best way to get in now is to go work for a big company that has a presence in both the USA and abroad (like, say, Google) and then after a year you can transfer to the USA on an L1 if your employer allows it. I’m no expert on moving to Europe, but I know that various countries have “blue card” programs for skilled technical people to move to Europe on. Anecdotally, I believe the best-paying jobs are in northern Europe, especially in Germany. But the pay will be less than in the USA. I transferred one engineer from Silicon Valley to Germany (his request) and I had to give him a 25% salary cut and he got a lot less equity compensation going forward. The good news is that there is a huge demand for skilled programmers everywhere. I’m so glad that my childhood passion was computers and not medieval French poetry, in which case I’d be serving lattes at a coffee shop and be living in fear that a robot is going to take my minimum-wage job.
- ddorian43 10y ago
  25% cut from SF wage to DE there's still alot left.
- lgieron 10y ago
  > Anecdotally, I believe the best-paying jobs are in northern Europe, especially in Germany I think nothing in Europe beats London. Of course, the rents are insane, but if you don't have a family and are willing to live in a shitty place (maybe with flatmates) with a commute, it doesn't affect you as much.
  - gambiting 10y ago
    Nothing in London gets close to what people make in SF, and the rent is equally insane. I know senior software engineers in London with 15-20 years experience and they make ~100k pounds(~140k USD)/year,sometimes a bit more sometimes a bit less, and equity is definitely not a given thing. Obviously UK/US salaries are not directly comparable , but still, if you want to be making >$300k/year, then you need to work in finance in London, not IT.
    - lgieron 10y ago
      I'm not sure how typical it is for a grunt level developer to be making >$300k in SV. For that kind of money, you typically need to be a manager (team lead at least). I think you can expect yearly earnings of around 150k pounds when you're contracting in London as a (obviously top-notch) technical team lead, which is about $220k. It's less than $300k, but contracting taxes in UK are about 20%, compared to the 33+% figure siberianbear gave. Plus, you don't need to wait years for the stocks to vest. The biggest problem with that is that a lot of companies don't like to contract out management, so you're options may be somewhat limited (and if you choose full-time employment instead, you go straight into the maw of 40% taxation).
      - d4rkph1b3r 10y ago
        >For that kind of money, you typically need to be a manager (team lead at least). False. You have to be very senior, but you do not need to 'typically' be a manager. There was a spreadsheet a few months ago on HN showing that with RSUs, most of the top tech companies pay above this for their higher level (non manager) engineers. >It's less than $300k, but contracting taxes in UK are about 20% Wow, contracting taxes are higher in the US, maybe it is a comparable if you can make 150k+ doing consulting work in the UK!

siberianbear 10y ago

I went to a “second-tier” school in the University of California. Having worked with engineers from better schools (e.g., Stanford), I would say I was as talented on average as they were, but I had terrible study habits in high school and so my grades weren’t that good. At the university I did a lot of stuff that wasn’t required for my degree, like doing a senior design project and leading the local chapter of IEEE. I hustled to get internships. I took an internship doing IT support at a civil engineering firm my first year, but later I got better internships at Apple and Intel. By the time I graduated, I was a far stronger candidate than my peers at my school. I had six job offers when I graduated. I job hopped a couple of times early in my career for better positions, but I eventually ended up at a company I really liked and stayed there for twelve years. You don’t say much about your background or where you are, so it’s hard to answer your question. I think there’s really two parts to your question: “1. How do I become a great software engineer?” and “2. How do I emigrate to a country with higher salaries for engineers?” To me, these are pretty basic questions. To be a great software engineer, teach yourself to solve difficult problems and then go do it. Always push the limit of your ability. Learn multiple languages. If you’re a system software person, go tinker with databases. If you’re a compiler guy, go tinker with neural networks. If you’re a C programmer, go learn Scheme or Haskell. Read books on lots of topics: microprocessor design, good software engineering practices, design patterns, etc. In your job, be indispensable. Be the guy who can solve any bug or solve any problem, even if it spans multiple areas of knowledge. Be indispensable. Don’t be the guy who holes himself up as a guru in a little obscure walled-off technical area and hides his knowledge as a form of power or job security. There is no job security. Even if you’re good, your company could go through a rough spot and lay you off. The only job security is to be known in a network of other people as a great engineer, and then if you don’t have work it’s no problem to find another job. If you go interviewing for any serious jobs, you’re going to get coding questions. Whether they are a great way of assessing a candidate is a topic of debate on HN, but that doesn’t matter. You’re going to get them. People have put together anthologies of these questions: be sure you can solve them. If you practice and are good at it, you will be able to solve similar problems that you haven’t seen before. If you’re in an “emerging economy” with low salaries for engineers, then figure out how to get to a different country. The demand for software engineers worldwide is huge right now, and so if you can figure out a way to legally work in a richer country and you have any talent at all, you can find a job. Visa programs put a high value on university degrees in technical fields, so if you don’t have one it’s likely you’ll need to get one. The United States has the best paying jobs for software engineers right now, but it is very hard to emigrate to right now because the H1-B visa category is oversubscribed. The best way to get in now is to go work for a big company that has a presence in both the USA and abroad (like, say, Google) and then after a year you can transfer to the USA on an L1 if your employer allows it. I’m no expert on moving to Europe, but I know that various countries have “blue card” programs for skilled technical people to move to Europe on. Anecdotally, I believe the best-paying jobs are in northern Europe, especially in Germany. But the pay will be less than in the USA. I transferred one engineer from Silicon Valley to Germany (his request) and I had to give him a 25% salary cut and he got a lot less equity compensation going forward. The good news is that there is a huge demand for skilled programmers everywhere. I’m so glad that my childhood passion was computers and not medieval French poetry, in which case I’d be serving lattes at a coffee shop and be living in fear that a robot is going to take my minimum-wage job.

ddorian43 10y ago
25% cut from SF wage to DE there's still alot left.
lgieron 10y ago
> Anecdotally, I believe the best-paying jobs are in northern Europe, especially in Germany I think nothing in Europe beats London. Of course, the rents are insane, but if you don't have a family and are willing to live in a shitty place (maybe with flatmates) with a commute, it doesn't affect you as much.
- gambiting 10y ago
  Nothing in London gets close to what people make in SF, and the rent is equally insane. I know senior software engineers in London with 15-20 years experience and they make ~100k pounds(~140k USD)/year,sometimes a bit more sometimes a bit less, and equity is definitely not a given thing. Obviously UK/US salaries are not directly comparable , but still, if you want to be making >$300k/year, then you need to work in finance in London, not IT.
  - lgieron 10y ago
    I'm not sure how typical it is for a grunt level developer to be making >$300k in SV. For that kind of money, you typically need to be a manager (team lead at least). I think you can expect yearly earnings of around 150k pounds when you're contracting in London as a (obviously top-notch) technical team lead, which is about $220k. It's less than $300k, but contracting taxes in UK are about 20%, compared to the 33+% figure siberianbear gave. Plus, you don't need to wait years for the stocks to vest. The biggest problem with that is that a lot of companies don't like to contract out management, so you're options may be somewhat limited (and if you choose full-time employment instead, you go straight into the maw of 40% taxation).
    - d4rkph1b3r 10y ago
      >For that kind of money, you typically need to be a manager (team lead at least). False. You have to be very senior, but you do not need to 'typically' be a manager. There was a spreadsheet a few months ago on HN showing that with RSUs, most of the top tech companies pay above this for their higher level (non manager) engineers. >It's less than $300k, but contracting taxes in UK are about 20% Wow, contracting taxes are higher in the US, maybe it is a comparable if you can make 150k+ doing consulting work in the UK!