Very self-satisfied, and deservedly so. Like when you use that one piece of scrap wood in the garage you've been saving for this one occasion, or something from that drawer of metric-threaded bolts that just saves the project you're working on. It was all worth it, see? This is why we do it. No different with the author's digital preservation and online tool use. Pleasant read.
Another tidbit, based upon finding out which company the phone number belonged to: you could go to the library and access business directories. Think the yellow pages, only they were geared towards businesses rather than towards consumers. Print versions were broken down by industry, but electronic ones (on CD-ROM) were searchable. It was also a tool for looking for unadvertised jobs, since those directories seemed to be geared towards making cold calls (albeit, for people doing sales).
You'd mail your resume in (it was a 'hack' back then to hand-deliver it), then get a call in a couple days or weeks. Then someone who was home during the day (if you already had a job) would answer the phone and take the message from the HR person (or they'd leave one on your answering machine), you'd then have an appointment to go in or return a call to set one up...
My first full time programmer job I got in early 2003. I had only 1 year left in University and a friend of mine was working in this "hotel reservation website" company owned by some gringos (this was in La Paz, BCS back in the day).
My friend told me he will talk with the boss there and see if they wanted to have me. They were a "Microsoft" shop, mainly doing Visual Basic. This was early .NET days. Because I was a student with all time in my hands, I taught myself C#.
Anyways, they invited me to the small office, I arrived, my friend introduced me to the "boss" (a guy who had got out of University maybe 4 years before) and he gave me a programming challenge. Basically to implement a CRUD in C# for some random domain that I have forgotten. This was in a PC that they lent me (Laptops were not common in Mexico in those days)
It took me about an hour to finish it and handle it in. They then thanked me and told me they will be in touch later.
Apparently, they had scheduled around 4 or 5 hours for the problem and I blazed through it (humble bragging I know hehe). After a couple of days, I asked my friend about the job, and he told me to call to the boss, as it will show interest. I called later that week, apparently exactly at the moment they were having a meeting about me and the position. They basically told my friend I will be his "protege", so he would be my boss.
In hindsight it was a nice place. We were like 8 people max in the team (including devs and designers, doing Flash, and the accountant lady that also sold us Burritos for breakfast). Golden years now that I think of it (the office was just by the broadwalk, so we would go out to the beach).
But yeah, the interview process was completely personal and down to earth. Not the crazy stuff that you see nowadays. It marked me, as every time I have to hire people I try to replicate the feeling I had at that time. I was hell nervous, but excited to show what I knew.
Sorry for the long Abe Simpson story-rant, it's cool to remember.
We were told the quality of paper mattered and that the envelope should have the same high-end watermark that the resume sheet had. Inkjet printed resumes were discouraged because the quality back then was low and the resolution made anti-aliasing on the type come out weird. Laser printed only, please.
imo the job process is totally broken its an AI arms race. You have people doing mass ai apply with slop CVs and then recruitment just doing the inverse with AI ATS. Working on something I think could help solve the issue just need to find recruiters to talk to see if it's any good.
Mine is from Poland, early 90s, and even more analog. I worked at a Polish-Italian company. Our accountant used an ERP program, DOS, written in Clipper. There was no internet, so the vendor's consultant had to come to the office in person. The consultant was a young woman. She became my girlfriend and she pulled me into ERP.
The girlfriend left. The ERP stayed for over 30 years ;)
Unpopular take: This was significantly better for employers and employees.
It worked as both an effort and presentation filter which both reduced the overload of candidates, allowing for more attention, higher variation of skills that didnt often show like traditional resume bonafides and mad companies more likely to invest more in employees as it was a pain to go do again.
For employees it was great too. Much like the world pre-dating apps the business world wasnt all looking for the equivalent of trust fund, 6'5", blue eyes. As well as the points mentioned above.
Classified ads for jobs were still a thing up until around Y2K. MonsterBoard (what it used to be called) was one of the first online job platforms and then Dice came along. I used to have good luck finding contract gigs through dice.
I responded to an ad in the newspaper for a C programming job way back in mid-1980s. The team that posted the ad was not impressed with my resume, but they sent it on to a different team within the same company. That team hired me and I stayed at that company for 14 years.
Unlike the author, I kept the ad in a box for 35 years, at which point I scanned it and threw out the hard copy.
Edit: Also, the resume I mailed to them was printed by a print shop.
I had an old coworker who told me he got into software development in the sixties by walking into an IBM office and asking for a job. He had no education beyond high school and no experience with computers. They just had him take an aptitude test and then he worked on mainframes for decades.
Working on mainframes and with computers was considered secretarial work by almost everyone around that time. The role of computers in work, and the status of working with computers, has changed in incredible ways.
In 1981, my first job in Silicon Valley was obtained by answering a blind (no company name) ad in the Mercury News. It was a kooky company that built burn-in ovens for semiconductors (mostly 2164 memory chips back then).
I had a lot of fun there. The purchasing manager was a Scottish guy and he had an after hours drinking club in a small conference room with a wet bar. I was only 24 years old and working crazy hours. I'd get a few beers around 7 pm and then go back to work writing 8080 assembly language code for a few more hours.
I also ended up smoking weed with the CEO and CFO a couple of times. The CFO was not a young guy. I'm not sure how old he was, but he had all white hair. The CEO gave me a mason jar full of his homegrown weed as a gift when I finished the project.
That company and even the building is long gone. It's now a Google parking garage.
The IBM anecdote in the comments captures something important. The old system had a lot of problems, but it did one thing well: it forced a much faster path from "can this person do the work" to actually finding out. You walked in, they gave you an aptitude test, and the test result was the decision.
We've somehow ended up with a hiring process that's simultaneously more information-rich and worse at answering the basic question. You can see someone's entire LinkedIn history, their GitHub, their blog posts, their conference talks, and still have no idea whether they'll be effective in the role. The signal-to-noise ratio went the wrong direction.
35 comments
[ 2.0 ms ] story [ 19.3 ms ] thread"How We Used to Get Jobs".
Now that guy is probably competing with tons of people more talented willing to work for less
Perhaps she said "bulk load of resumes" and you misheard it as the funnier version?
https://en.wiktionary.org/wiki/buttload
Because nobody was going to carry a Sun workstation down to the meeting room just for your interview.
My friend told me he will talk with the boss there and see if they wanted to have me. They were a "Microsoft" shop, mainly doing Visual Basic. This was early .NET days. Because I was a student with all time in my hands, I taught myself C#.
Anyways, they invited me to the small office, I arrived, my friend introduced me to the "boss" (a guy who had got out of University maybe 4 years before) and he gave me a programming challenge. Basically to implement a CRUD in C# for some random domain that I have forgotten. This was in a PC that they lent me (Laptops were not common in Mexico in those days)
It took me about an hour to finish it and handle it in. They then thanked me and told me they will be in touch later.
Apparently, they had scheduled around 4 or 5 hours for the problem and I blazed through it (humble bragging I know hehe). After a couple of days, I asked my friend about the job, and he told me to call to the boss, as it will show interest. I called later that week, apparently exactly at the moment they were having a meeting about me and the position. They basically told my friend I will be his "protege", so he would be my boss.
In hindsight it was a nice place. We were like 8 people max in the team (including devs and designers, doing Flash, and the accountant lady that also sold us Burritos for breakfast). Golden years now that I think of it (the office was just by the broadwalk, so we would go out to the beach).
But yeah, the interview process was completely personal and down to earth. Not the crazy stuff that you see nowadays. It marked me, as every time I have to hire people I try to replicate the feeling I had at that time. I was hell nervous, but excited to show what I knew.
Sorry for the long Abe Simpson story-rant, it's cool to remember.
It worked as both an effort and presentation filter which both reduced the overload of candidates, allowing for more attention, higher variation of skills that didnt often show like traditional resume bonafides and mad companies more likely to invest more in employees as it was a pain to go do again.
For employees it was great too. Much like the world pre-dating apps the business world wasnt all looking for the equivalent of trust fund, 6'5", blue eyes. As well as the points mentioned above.
Unlike the author, I kept the ad in a box for 35 years, at which point I scanned it and threw out the hard copy.
Edit: Also, the resume I mailed to them was printed by a print shop.
I had a lot of fun there. The purchasing manager was a Scottish guy and he had an after hours drinking club in a small conference room with a wet bar. I was only 24 years old and working crazy hours. I'd get a few beers around 7 pm and then go back to work writing 8080 assembly language code for a few more hours.
I also ended up smoking weed with the CEO and CFO a couple of times. The CFO was not a young guy. I'm not sure how old he was, but he had all white hair. The CEO gave me a mason jar full of his homegrown weed as a gift when I finished the project.
That company and even the building is long gone. It's now a Google parking garage.
We've somehow ended up with a hiring process that's simultaneously more information-rich and worse at answering the basic question. You can see someone's entire LinkedIn history, their GitHub, their blog posts, their conference talks, and still have no idea whether they'll be effective in the role. The signal-to-noise ratio went the wrong direction.