71–80 of 104 posts
Since when is working two jobs a bad thing? Plenty of people work two or three jobs to make ends meet. If you can make both work, and you aren't violating any contracts or NDAs, I don't see why you should feel bad about that.
Earlier quoted context omitted.
If it's more than just a cost-of-living bonus for high-rent areas, then yes it is. You're saying "Hey engineer A, you're just as good as B, but we're going to pay you less because people that live near you aren't getting paid as much. If you'd like a raise, move somewhere where engineers get more money." Again, if it's just the cost-of-living bonus (like, all our engineers get $80K, plus $X/month where X is average r…
While I can't comment on Travis CI, Gitlab from what I understand, used to hire a 3rd party company that would perform research (based on cost of living, taxes etc.) to gauge your salary (across different regions). That said, what's stopping remote engineers starting to work in expensive regions (say Vancover/Toronto) and then moving to cheaper regions (Saskatchewan/Manitoba/Alberta) for example - would salaries be a…
Gitlab people on here have previously said yes: pay gets adjusted when you move.
I'd like to land one (1) FT remote job, and here we've got folks talking about working two at the same time :)
What problems have you had in trying to land a full time remote job?
1 - You'd be bored (so?)
2 - We only allow remote work for people who've worked remotely full-time before (always enjoy a good Catch-22).
3 - You haven't actually worked with language X (Clojure in the most recent case) professionally (only on personal projects), so we'd want you in the office (on the other side of the country) so you're closer to help as you learn to code in a new language (a particularly insulting thing to say to a senior software engineer).
4 - Oh, why did you turn down our offer for 40% less than your current pay?
and my personal favorite:
5 - :static: the interviewer just goes dark after I spend an entire Saturday afternoon completing a homework assignment and then go through a 2 hour live coding interview.
Eventually one stops trying. My experience interviewing leads me to believe there is a gross oversupply of good software engineers looking for remote work (If I may be so bold as to call myself a 'good' software engineer).
I wonder if there is anyone who is working remote has outsourced themselves? Get a remote job that pays quite a bit more than you need to live comfortably in your area, then hire a remote worker from India to do the work for you.
I've seen it done onsite. There was a guy who worked an 8-5 job in my building and the building next door simultaneously. He would show up, look busy, then run next door and do the same thing. He did this for about 8 months before one of his managers caught on and told his other manager. He ended up losing both jobs at the same time.
There was an engineering director at one of my previous workplaces that was a little hard to reach. People though he was attending high level meetings including his reports. One of them called him once during work and he answered by the name of another company unintentionally. They spoke with HR and through some investigations found out the guy was coming to work and during the middle of the day going to his other jo…
My greeting is usually short: "Hi, this is Mike."
I've seen it done onsite. There was a guy who worked an 8-5 job in my building and the building next door simultaneously. He would show up, look busy, then run next door and do the same thing. He did this for about 8 months before one of his managers caught on and told his other manager. He ended up losing both jobs at the same time.
so he lost both jobs. but oddly, the on-site manager felt guilty mentioning it during reference checks, and he went on to be a fairly well paid manager.
Double dipping is the wrong phrase here. Having two jobs or two gigs is not double dipping. Double dipping is typically a form of cheating by getting paid 2x for 1x amount of work. Say I was being paid to create a website for two clients and it took me 100 hours to finish it. Then I used the same codebase for another client, spent 5 hours modifying it, and then delivered it to them billing another 100 hours. That wou…
Even that's not double dipping. Depending on how your contract is structured, it might be the smart thing to do. If I tell you that I'll produce a certain product for $15,000 and you're OK with that, does it really matter in the end if it took me 5 hours or 150? Either way, you pay the same amount. Now, if you have a contract that specified time & materials and I pad the hours, then I can agree we could have a proble…
Earlier quoted context omitted.
What problems have you had in trying to land a full time remote job?
Things I've heard: 1 - You'd be bored (so?) 2 - We only allow remote work for people who've worked remotely full-time before (always enjoy a good Catch-22). 3 - You haven't actually worked with language X (Clojure in the most recent case) professionally (only on personal projects), so we'd want you in the office (on the other side of the country) so you're closer to help as you learn to code in a new language (a part…
2) start and learn everything needed in about a week and work fast after that
3) be open to become full time - and you'll likely get an offer 1 to 3 months in, or more like they'll switch you fte.
Does it matter? In software engineering you should be judged by the quantity and quality of the code, nothing in those metrics disqualifies double-dipping. If anything contracting on the side gives employees exposure to tech stacks and processes outside their normal day to day.