>You must have experience designing and building large and complex (yet maintainable) systems, and you should be able to do so in about one-third the time that most competent people think possible. I wonder if working nights and weekends was a bonus? What's wrong with being competent and putting out a reasonable amount of work and not being overworked and under pressure?
Amazon's First Job Listing
31–40 of 60 posts
Re: Amazon's First Job Listing
#32>You must have experience designing and building large and complex (yet maintainable) systems, and you should be able to do so in about one-third the time that most competent people think possible. I wonder if working nights and weekends was a bonus? What's wrong with being competent and putting out a reasonable amount of work and not being overworked and under pressure?
The people replying to this ad are now multi-millionaires/billionaires. If you want to work a reasonable amount of work you can do it at a normal company, and get a reasonable amount of money in return.
Quite a few who answered ads just like it worked years below market rate only to see their theoretical equity dissolve, though.
Re: Amazon's First Job Listing
#33I feel like I'm missing something. Why would you ever respond to that listing? No meaningful description of the company, no outstanding benefits, just the promise of being overworked?
Re: Amazon's First Job Listing
#34Earlier quoted context omitted.
Yup you’re missing something. In addition to attracting qualified candidates, good job listings repel those who don’t agree with them. No one wants to sift through hundreds of applications. Here’s the main mission filter: “to help pioneer commerce on the Internet.” technical filter: “you should be able to do so in about one-third the time” and culture filter: “Expect talented, motivated, intense, and interesting co-w…
Now let's have look at similarly-worded ads for the 2000s dotcoms
Re: Amazon's First Job Listing
#35Fascinating that he wanted an expert C developer with a PHD who'd build stuff in one third of the time it takes others.
Hiring C developers back in the day was smart. It meant someone knew computers as much as they knew software.
Re: Amazon's First Job Listing
#36>You must have experience designing and building large and complex (yet maintainable) systems, and you should be able to do so in about one-third the time that most competent people think possible. I wonder if working nights and weekends was a bonus? What's wrong with being competent and putting out a reasonable amount of work and not being overworked and under pressure?
I don't think the ad is asking for people who are willing to work three times longer hours, it's asking for people who can produce three times the output in the same hours.
A 3x SWE can't produce 3x if they are in 6hrs of meetings a day. Likewise a 1x SWE can't produce 10x even working 12hour days.
Re: Amazon's First Job Listing
#37I feel like I'm missing something. Why would you ever respond to that listing? No meaningful description of the company, no outstanding benefits, just the promise of being overworked?
Yup you’re missing something. In addition to attracting qualified candidates, good job listings repel those who don’t agree with them. No one wants to sift through hundreds of applications. Here’s the main mission filter: “to help pioneer commerce on the Internet.” technical filter: “you should be able to do so in about one-third the time” and culture filter: “Expect talented, motivated, intense, and interesting co-w…
“you should be able to do so in about one-third the time” - No matter the era, this kind of language is a big red flag to me - More often than not people who say this have no idea what they're talking about, the kind of people who call themselves "idea men"
“Expect talented, motivated, intense, and interesting co-workers.” - meaningless phrase
I don't know how recruiting messages were in 1994, but unless this is the Velvet Underground of influential recruiting messages (not many people got this email, but those who did started startups of their own) this reads like a generic recruiting email. Given the state of things in 1994 the "pioneer commerce on the Internet" would be interesting enough to learn more though.
Re: Amazon's First Job Listing
#38Earlier quoted context omitted.
The people replying to this ad are now multi-millionaires/billionaires. If you want to work a reasonable amount of work you can do it at a normal company, and get a reasonable amount of money in return.
This is just survivor bias.
Re: Amazon's First Job Listing
#39Earlier quoted context omitted.
The people replying to this ad are now multi-millionaires/billionaires. If you want to work a reasonable amount of work you can do it at a normal company, and get a reasonable amount of money in return.
> The people replying to this ad are now multi-millionaires/billionaires. Quite a few who answered ads just like it worked years below market rate only to see their theoretical equity dissolve, though.
Re: Amazon's First Job Listing
#40I feel like I'm missing something. Why would you ever respond to that listing? No meaningful description of the company, no outstanding benefits, just the promise of being overworked?
In 1994, MS-DOS and Windows 3.1 were the most popular desktop operating systems. Most internet access was dial-up. Windows 95 was yet to be released. Steve Jobs was working on NeXT and wouldn't return to Apple for another 3 years. The GNOME project didn't even start until 1997, which is 3 years later. Python 2.0 wouldn't be released for 6 years, in 2000. Heck, Netscape Navigator's first version wasn't even out yet (not for a few months) -- there were no distinctly popular browsers other than, perhaps, Mosaic, released only a year earlier.
No one was building web apps yet; pg started Viaweb in 1995, one year later. Internet commerce was not at all an obvious idea. Very few people were working on "internet companies", and very few people yet were working primarily on UNIX (outside of open source hobbyists). This job posting was appealing to UNIX enthusiasts and academic computer scientists who were hoping to turn their hobbies into a lucrative day job, in a world where 90%+ of "computer jobs" were rudimentary IT schlep.
The entire culture you describe in your comment -- of companies needing to distinguish themselves via strong benefits and mission alignment -- wouldn't grow up for a few years. This wasn't a job posting among a sea of web startup job postings; this was, instead, one of the earliest web startup job postings in a sea of enterprise IT management and DOS/Windows desktop software development postings.
The "competition" for these developers was startup versions of companies like Redhat and Netscape (maybe), of which there were only a handful of comparables. A good documentary you can watch to put yourself more into the mindset of this period of developer history is "Revolution OS" (2001): https://watch.amazon.com/detail?gti=amzn1.dv.gti.cf101954-e0... (Amazon Prime Video) -or- https://imdb.com/title/tt0308808/ (IMDB)