4 ms·
Personally, I've already spent months doing unpaid work on testing sites, and yet I'm still stuck in the same place. Have others encountered this? I have not b
by romille 6y ago
Personally, I've already spent months doing unpaid work on testing sites, and yet I'm still stuck in the same place.
Have others encountered this? I have not but I do wonder if the hiring process is becoming more demanding / time consuming.
Maybe the author needs a coach or needs to network more.
- deleted 6y ago[deleted]
- momento 6y agoYou see; I am also confused by this. The author chooses to work for free, and yet complains about his pay relative to the amount of time he must spend doing cognitively taxing work. In my 10 years as a professional software engineer I have seen this same thing happen time and time again. My colleagues devalue themselves constantly by working for free. If you earn $80k a year as an engineer, you rate is roughly $38.46 per hour if you work 2080 hours in the year. Let's say you opt to work an extra 30 minutes a day (very often the case for many devs who work into their lunch break); that equates to an extra 130 hours of work per year for free. So what you're actually doing is earning $80k a year for 2210 hours, or $36.19 per hour. That's roughly ~6% less pay for your time for working an extra 30min a day. Now imagine what happens when you work those extra 30mins + a few weekends here and there. The total percentage of your salary drops significantly as a result. Say no. Don't work for free.