The same exact thing happened to the guy behind ReactOS (an Open Source Windows NT replacement). The guy became /so/ familiar with Windows that he eventually got a job on the actual Windows Kernel team.
edit (due to the downvotes): Sorry, this was an honest question. I've been working for about 15 years and have always been really put off by the institutional structure of large companies ... the constitution of them just doesn't work for the kind of green-field I'm (and I thought most hackers) are looking for.
I wasn't trying to be negative or deleterious --- I really didn't get it.
I routinely turn down offers from the big players because I imagine once I'm in, it's going to be like the movie Brazil.
I've worked for three large companies as a non-contractor - and I mean maybe I just didn't have the right title but I found the following (in all three):
* I was prohibited from working on broken things that I was capable of fixing but I wasn't assigned to - even if nobody else was addressing them ... Almost as if there's some internal taxonomy model which strictly defines my role as X and only X. Having things lay broken is so frustrating to me.
* Pointing out that projects are on a steady course for derailment and failure was discouraged. Recommending any fix whatsoever was completely a prohibitive.
* Questions like "what does the client want?" or "Can I ask the client a question" always came back with things like "That's not your job".
* Proposals to big payoffs for small LOEs that would substantially improve the project always got shot down. Probably because the "from" field of the email was wrong.
* Creativity, innovation, and working on big new problems was incredibly discouraged. The concept that I have more than just one ability appears either cognitively impossible or structurally incompatible.
I got a nice paycheck - the work was relatively stable and secure, and everything was running smoothly --- but I was completely wasting years of my life.
On the contrary, all the small companies I've worked for have been the exact opposite. It's not that I necessary want to do contract negotiations and SOW writeups, but it gives clarity and purpose that I was just unable to get from the larger firms.
I mean again, maybe it's because my resume doesn't say "PhD, Stanford" on it - I don't know.
Has your experience been dramatically different?
Coming from the other side, that's frustrating to me too. I was working with a broken tool that the vendor wanted $200,000 to fix. I hacked together a shell script over the course of a few weeks that eased my pain, but required I work in a Linux virtual machine. I would have loved to port it to something that works on Windows like Python, but it was just glue over awk and sed and trim, and I have no idea how to replace those in any other language.
But you know who did have that knowledge? Our resident programmer. But every time I brought it up to the boss that he should work on it and get it running on Windows, the answer was "he has more important things to do, and if he has time to work on your side project, he needs more work to do". Literally. And in the next breath, the boss said "we need that script to follow our programming practices" aka Windows and Java. I'm not a damn programmer! But we do have one on the team!
when i was working at startups one of my largest sources of stress was having to constantly rush shoddy products out of the door because people were obsessed with beating some real or hypothetical competitor to market, never mind that any clients we did get to install our products either gave up early or tied us up with loads of support issues that we again had to fix on a quick-release, ad-hoc basis rather than systematically and correctly.
incidentally my resume says "phd dropout", so if the lack of a big-name university on your phd makes you disinclined to apply to places like google or salesforce, you should at least reconsider. in my experience these companies care a lot less about that sort of branding than they possibly did in the past.
You certainly won't see similar challenges if you limit your scope to companies with less than 50 people and less than 10 million in funding. Unless you are a founder or maybe a first hire that would seem to preclude you from almost any interesting company coming out of SV in the last 15 or so years.
Not ever hacker is a startup entrepreneur.
Similar projects know to stay really, really far away from anyone associated with the company whose product they're duplicating. WINE wants nothing to do with you if you've ever come within 500 feet of Microsoft's source code. If the project's founder is willing to give up that easily, it's certainly an easy, cheap way to kill off such a project.
It seems highly likely that Apple has some interest in protecting their brand. Part of the whole "Most amazing phone we've ever made" is the implication that the things you can do on iPhone can't be done on commodity hardware. This would undermine that in a way.
To say there is no way they would hire instead of doing a C&D if that was the motive is really silly. We don't know why they did it, but we can basically assume they know he was doing that before the hiring process.
This is nothing but a research project that does not mean much in the real world. It got that person a job at Apple. So that's a win for that individual. I don't think one can expect more out of the project really.
I have started a job with Apple, and will not be continuing work on this project. The team at Columbia will probably be doing some follow up work, but I won't be involved from here on out.
So basically Apple has tried to kill or at least slow down the release of this to the public (he's obviously talented, I'm just saying that killing progress on this project likely factored somewhere into the hiring decision).