I turned them down after an interview in around 2000/2001 (they started out in London). The reason was that the idea seemed completely useless to me and I thought they'd never make a business out of it :-)
That's interesting - I had a vague recollection of having heard of them before launch - I guess they were hiring from the pool of developers being laid off from the dotcom bust?
I have an image in my mind of my boss at the time going around the office asking if anyone was interested in talking to this thing called Shazam. I've long wondered if I imagined it. I certainly didn't act on it.
I remember (not much later than this) interviewing at a place where the product was intended to be "an automated assistant that listens to your phone call and pipes supporting information to your computer as you speak". Obviously I gave them a wide berth. It's funny to think about the "gap" in magic - Shazam seems magical but totally worked, this other idea seemed magical and, at the time, totally was.
I checked my email and the interview was actually in mid March 2002, not 2000/2001. I think still just before they did the initial launch of the premium phone service. Here's the job spec:
> Role: Senior software engineer - Low Level Device , Distributed
Communications Role mission: To ensure that Shazam's subsystems are integrated and interface effectively and efficiently with external partners' systems/hosting environments, yielding available, robust and scalable full offerings. Key Performance Areas: 1. Design real time software using standard techniques and protocols, to be scalable, maintainable and robust 2. Manage & collaborate within and between team(s) 3. Implement quality
software solutions within budget 4. Ensures that design and implementation of software is of high quality 5. Ensures that all deliverables are documented Required Skills/Capabilities <B7> Knowledge of interfacing peripheral and devices to Linux <B7> Knowledge of Linux device drivers a plus. <B7> Distributed messaging techniques and protocols, eg: PVM, MPI <B7> Ability to
grasp and work with abstract concepts <B7> Familiar with current software engineering methodologies e.g. RUP, XP <B7> Understands and is able to manage quality assurance e.g., module tests, code review Required Knowledge/Previous Key Experience <B7> At least 4 years of full-time software engineering within a team of at least 3 sofware engineers. <B7> Must have been
involved in all phases of the software cycle from requirements engineering
to launch. <B7> Must have developed low level device or communications software
<B7> Experience with Computer telephony a big plus <B7> Experience with a
high-growth startup environment a plus Ideal Qualifications Ideally
University degree in Computer Science (alternatively at least 4 years of
proven software engineering experience). Please forward your CV/resume',
with cover e-mail, including full details of your earnings expectations, to recruit <at> shazamteam.com
Just read this paper, it is brilliant. And TIL about Shazam and the idea still sounds useless to me. Seems like I have never had this problem in my life.
I use it several times a week. Driving with classical station on. Is this Mozart? That cadence sounded like Mozart, but I'm not sure. <Shazam and wait 10 seconds> Oh, it's Brahms! And now I have it auto-saved to listen to when I get home.
