Live data from Hacker News

My salary as a full-stack developer

remotehunt.com

91–100 of 126 posts

Re: My salary as a full-stack developer

#91
post #68

Earlier quoted context omitted.

> I would imagine if someone could get a job at a FAANG they'd have a job at a FAANG. Why would you imagine that? Plenty of highly skilled people do not hold a FAANG job up as some kind of holy grail of jobs.

The context is that the OP is saying they make $72K, and someone is responding "just work at Google", which is disturbingly out of touch.

I didn't say "just work at google" like anyone can - I'm saying based on what I've read of OPs bio, they can get a job there. How do I know? Because I've conducted thousands of interviews and sat on hiring committees at multiple of the FAANG companies.

Re: My salary as a full-stack developer

#92

Earlier quoted context omitted.

At 72k it would be ~13% fed (and also much lower in any state I can think of).

Says 22% here: https://www.nerdwallet.com/article/taxes/federal-income-tax-... Certainly with the way brackets work they're only paying 22% on anything between ~40K and 72K.

13% is the "marginal" rate (i.e. the percentage that you would actually pay on 72k, after applying the various brackets)

Re: My salary as a full-stack developer

#93
post #86

Earlier quoted context omitted.

In my experience, points are more accurate than hours, since most people work with high variability in productivity over time that can't be captured by a mechanism as crude as a stopwatch, so a corollary metric creates a more accurate number than an absolute metric.

https://www.joelonsoftware.com/2007/10/26/evidence-based-sch... Time based software development estimates before the magical "story points" system was in vogue.

It’s also more useful when looking back IMO. Points are more meant to be a soft guess for going forward.

Re: My salary as a full-stack developer

#94
post #88

Earlier quoted context omitted.

You can do that with story points rather than hours

Story points are not a tool for duration, they are a tool for relative estimation and should never be converted to time in any capacity. _Especially_ not inter-team. This is the current biggest mistake in the industry, imo.

I agree, but I'd say story points are themselves a mistake. In the end, what matters is time. Story points don't matter if the schedule slips. So you either get story points and no way to keep a schedule, or story points + time estimates (with useless story points), or just go with time estimates.

The schedule may still slip, since estimating time is very difficult, but at least some of the time it will be correct (or estimates will get padded until things happen on time). Either way, it's more useful than giving up on the problem.

Re: My salary as a full-stack developer

#95
post #67

Earlier quoted context omitted.

Toptal gets away with massively underpaying Sr Devs by hiring them from relatively cheap countries where that money goes a long way. A US-based Sr Dev contractor working remotely, making 75/hr, is being massively ripped off if they're capable of working with any even remotely commercially viable technology.

I think the numbers on Glassdoor are representing actual Toptal employees, not their contractors.

Could be, but if so their employees are insanely underpaid

Re: My salary as a full-stack developer

#96

Earlier quoted context omitted.

At 72k it would be ~13% fed (and also much lower in any state I can think of).

Says 22% here: https://www.nerdwallet.com/article/taxes/federal-income-tax-... Certainly with the way brackets work they're only paying 22% on anything between ~40K and 72K.

You don't seem to understand how the progressive taxation works. In U.S. you pay 0 tax on first ~20k income, 15% on the next 35k, 22% on next 40k and so on (random numbers). The 22% is what you pay on anything above 55k in this example. But for the first 55k you pay only 20k * 0% + 35k * 15%=5250, e.g. 9.5%

Re: My salary as a full-stack developer

#97
I'll share mine.

2011 - Graduated with double degree B.S. in Electrical Engineering & Computer Science from Texas Tech University

Software Engineer @ Raytheon II&S in Garland, TX

2011 $61k/year (all # values are in $k)

2012 $63

Software Development Engineer I (SDE1) @ Amazon in Seattle

2013 $90 salary + $20 signing bonus + $53 stock bonus (vested over the next 4 years)

2014 $117 Total Compensation (TC) = $92 base salary + $13 2nd year bonus + $11 stocks value

Promoted to SDE2

2015 $138 TC = $105 + $33 stocks

2016 $171 TC = $108 + $63 stocks

2017 $195 TC = $110 + $84 stocks

19% bump after switching teams within Amazon and getting a new manager

2018 $251 TC = $131 + $119 stocks

2019 $245 TC = $150 + $96

2020 $255 TC = $157 + $97

Promoted to SDE3 (Senior Software Engineer)

2021 $309 TC = $160 + 149

I'm currently a full-stack engineer, as in I've worked with or currently work with:

- Backend service development: Java, Scala, & C++

- Front-end development: CSS, JavaScript & Typescript

- Server-side rendering: Perl & Java

- App Development in Android (Java & Kotlin) & iOS (Objective-C & Swift)

- Script development in Java, Ruby, Python, & SQL

- System design, design reviews, AWS, etc.

- DevOps (Oncall, CD/CI, Integration testing, Chaos testing, Agile process improvements etc.)

- Interview candidates, mentor new hires & teammates, promotion recommendations & reviews

Re: My salary as a full-stack developer

#98
post #96

Earlier quoted context omitted.

Says 22% here: https://www.nerdwallet.com/article/taxes/federal-income-tax-... Certainly with the way brackets work they're only paying 22% on anything between ~40K and 72K.

You don't seem to understand how the progressive taxation works. In U.S. you pay 0 tax on first ~20k income, 15% on the next 35k, 22% on next 40k and so on (random numbers). The 22% is what you pay on anything above 55k in this example. But for the first 55k you pay only 20k * 0% + 35k * 15%=5250, e.g. 9.5%

[deleted]

Re: My salary as a full-stack developer

#99
post #88

Earlier quoted context omitted.

Story points are not a tool for duration, they are a tool for relative estimation and should never be converted to time in any capacity. _Especially_ not inter-team. This is the current biggest mistake in the industry, imo.

I agree, but I'd say story points are themselves a mistake. In the end, what matters is time. Story points don't matter if the schedule slips. So you either get story points and no way to keep a schedule, or story points + time estimates (with useless story points), or just go with time estimates. The schedule may still slip, since estimating time is very difficult, but at least some of the time it will be correct (o…

The entire purpose of introducing story points is to move away from time estimating. Time estimating is broken and inaccurate. Complexity estimating is marginally more accurate but still with a wide range of inaccuracy.

Instead teams should focus on delivering value incrementally, then using metrics over those increments as a measure for future increments.

Re: My salary as a full-stack developer

#100
post #96

Earlier quoted context omitted.

Says 22% here: https://www.nerdwallet.com/article/taxes/federal-income-tax-... Certainly with the way brackets work they're only paying 22% on anything between ~40K and 72K.

You don't seem to understand how the progressive taxation works. In U.S. you pay 0 tax on first ~20k income, 15% on the next 35k, 22% on next 40k and so on (random numbers). The 22% is what you pay on anything above 55k in this example. But for the first 55k you pay only 20k * 0% + 35k * 15%=5250, e.g. 9.5%

[deleted]
Post reply on HN