My understanding of the US is that typically "contractor" over there implies "consultancy worker" which is the staffing equivalent of shovelware.
Please correct me if wrong!
My understanding of the US is that typically "contractor" over there implies "consultancy worker" which is the staffing equivalent of shovelware.
Please correct me if wrong!
Many of the higher-end software engineers negotiate their own contracts, and in doing so act as "Consultants", because corporate standard contracts don't work for them. It's not usually about pay - FAANG has pay ranges that go up - But in the before times, it included things like WFH and additional allowances for time off.
For example recently I got an offer for a 4 months contract role at Microsoft, hybrid (so partly on site), as a Machine Learning Engineer for $65 an hour. I would consider that rate insulting even for low CoL EU countries.
I simply find the economics of freelance/contract work in the US baffling. The contract isn't even fully remote, so you can't take advantage of geo arbitrage and live in a cheaper place. I'd be surprise if they hire anyone more than an intern-level developer for that rate. FFS, I paid more for some dude to come and tidy my lawn.
I wonder if these two phenomenon are related?
Indeed, that's what I thought the article was about, reading the title.
Most of the UK population, if asked "what's a contractor" would assume construction.
At least in American English vernacular, saying "he's a contractor" either means he builds houses, or he's an independent contractor (doing some "consulting-ish" work). The lack of context for that phrase is indeed confusing!
Although, there's no shame in asking one of the walking, talking neural nets that have traditionally been willing to supply clarification, especially when they created the bit of context that is the source of confusion.