>Medina said he experienced the high-pay, no-work situation early in his career when he was a software engineer in grad school. He finished his project months early, and warned his company he would be leaving after graduation.
>They kept him on for the remaining months to train others on his software but didn't want him to start a new coding project. His job during those months involved hanging out at the office writing a little documentation and being available to answer questions, he recalls.
This isn't a good example. The company budgeted X dollars over Y months for a total comp package of Z for an engineer they knew had a discrete timeline, and the engineer finished in Y-3 months. What should the company do, fire the engineer and save delta-Z? The company got what it wanted and more by having him stick around and answer questions and do documentation work for 8-10 hours a week of "free" labor.
>They kept him on for the remaining months to train others on his software but didn't want him to start a new coding project. His job during those months involved hanging out at the office writing a little documentation and being available to answer questions, he recalls.
This isn't a good example. The company budgeted X dollars over Y months for a total comp package of Z for an engineer they knew had a discrete timeline, and the engineer finished in Y-3 months. What should the company do, fire the engineer and save delta-Z? The company got what it wanted and more by having him stick around and answer questions and do documentation work for 8-10 hours a week of "free" labor.