I believe the main reason employers have an issue with moonlighters is that they view it as lack of loyalty. There may be other reasons, such as concerns regarding whether the employee can perform at 100% at two or more jobs, but I really do think that loyalty is the primary concern by a large margin.
Is there much else to learn? This is simply not as interesting a story as it's being made out to be.
"Really smart and likable; enjoyed working with him"
People generally don't enjoy working with people who suck at their job.
That's news to me. Fabulous news even. Not sure when this change took place but it's for the better.
But this is the archetype of engineer that companies really want: Exceptional at passing technical interviews, willing to work 24/7 to make it happen, but as cheap as possible but all made up for promising 'equity'.
This is an actual "10x engineer" that exists, but somehow it has upset some VCs because he was moonlighting at multiple companies as a hack.
The best part is, remote YC startups were targeted and they are all talking about banning Soham secretly on bookface.
It is now clear that some are "allowed" to hack the system of others to their advantage but you are "not allowed" to do it against YC.
> For instance, Rohan Pandey, a founding research engineer of the YC-backed startup Reworkd, told TechCrunch that he interviewed Parekh for a role and he was a strong candidate. Pandey, who is no longer with the startup, says Parekh was one of the top three performers on an algorithms-focused interview they gave candidates.
That party will last until the regulators notice...
By all accounts Parekh did not fulfill his obligation, apparently he is a very good engineer, but he did not give his time to the companies he was hired by. He was constantly calling sick, fail to finish his tasks up until got fired. Since he was a salaried employee, he still received the paycheck despite his abysmal performance.
That said, he definitely became a folk hero :) He is a charming person who pulled a fascinating stunt.
I wish it was just doing the job, it should be that way unless you are on commission or one of the owners
*edit: assuming he did the job that is..
It's very hard on other people, who, in some cases, are making tremendous efforts, such as running marathons again, due to these types of people...
https://www.joelonsoftware.com/2016/12/09/developers-side-pr...
>>Your game designer works for a year and invents 7 games. At the end of the year, she sues you, claiming that she owns 4 of them, because those particular games were invented between 5pm and 9am, when she wasn’t on duty. >>Ooops. That’s not what you meant. You wanted to pay her for all the games that she invents, and you recognize that the actual process of invention for which you are paying her may happen at any time… on weekdays, weekends, in the office, in the cubicle, at home, in the shower, climbing a mountain on vacation.
Also
>>Being an employee of a high tech company whose product is intellectual means that you have decided that you want to sell your intellectual output.
So the case of an Overemployed engineer who signs an exclusivity deal and works 8 hours at one job and then 8 hours at another job, is still breach of contract, the employee is not well rested, the focus is literally split in half, and there's also concerns of mixing and polluting IP claims.
What's more, the Soham Parekh case is an even clearer case of breach and even fraud, it's not like the dude was fulfilling or apparently fulfilling his obligations, he never worked, first week he took the week off and lied about why, just 0 output but still trying to get that first paycheck.
There is a subtler discussion on OverEmployment, but this is not it, we should all agree that this is fraud.
Most tech-jobs are boring-as-hell bullshit jobs that are required to deal with stupidly designed systems whose phil. is stuck in the dark-ages of PDP-10 (which is why a lot of it gets shipped off to India, or not to 'AI').
You need to treat the performance of your programmers as opaque, you shouldn't trust your ability to gauge their performance.
Suppose you buy a novel, and you buy it thinking that it was written by an 80year old Author that traveled the world and learned a lot of experiences and was actually a genius and a seductor of women and was a philantropist that rubbed shoulders with politicians.
If you then learn that the novel was actually written by a ghostwriter in china, or by ChatGPT, then would the value of the Novel be the same? No, it would be almost worthless, the content of the novel is the same, if you inspect the product you would not be able to tell the difference. Sometimes the value, or indicators of the value, are in the process.
Stepping back out of the metaphor, the product will show its true value 2, 5 10 years down the line, will it crash when the marketing team figures it out, or you have a viral moment and 100K concurrent users?
You cannot rely solely on the inspection of the deliverables, you must assume that there are invisible or hard to inspect properties that are almost impossible to divine from inspecting the deliverable, but easier to understand by inspecting the talent and process that builds it.
>how could this have happened
Not everybody has interviewed a North Korean hacker with a real-time deepfake avatar either...
“Don’t hire people like this guy” is circular. It’s not meaningful information. There’s nothing to learn!
Background checks would not and did not detect him.
I can't tell you what to do differently because I don't know what you are doing. But I can say you can catch him, and others have caught him, so why can't you?
But typical background checks would not catch someone doing this, and in fact did not catch him several times, clearly.
Background checks do not alert you to other business who claim to have recently hired someone, so it's not clear how this helps whatsoever. He had references, he had a LinkedIn, etc. etc. Your solution is made up.
If you believe background checks would help, then answer my prior question: which type of background check? The standard ones would not detect this!
At least in Europe. I guess in US it's all different.
Generally speaking, no. Full time jobs are supposed to be full time, and the expectation, and explicit agreement the employee signed up for, is that employees will apply their skills for 40h/week regardless of level, vision, or skills.
Have you read your employment contract and/or employee handbook? You probably have one or both of those even if you don’t know it, but if you don’t have one of those, have you asked your employer what they think about this, whether they agree to let you work 10h/week and keep your full salary if you can “complete” your work? It sounds funny to me to even say it that way. At no time in my life has there been a specific set of tasks and work per week after which I could say my work was complete, software engineering doesn’t work like that.
Again, the right the company has to demand your full time attention is that was the agreement you signed up for: salary in return for 40h/week of your best effort.
Microsoft, Apple, Google, and a bunch of others famously got busted colluding to avoid hiring from each other, and the employment contracts at the time also had exclusivity clauses. I know because mine did, and I received a payout from the settlement of that lawsuit.