Quote:
Originally Posted by Nickco43
Yesterday I was denied by J&J and two other companies I applied to on one of my application frenzies. Today I got two personal emails from Cisco and Ferguson saying they want to interview me.
The Cisco job is to be a FT project manager. It pretty much everything I wanted in a post college job so I really hope it pans out. The location is good, the company culture is good and I feel like the job description matches my skill set.
I never thought of this before but I think I know exactly what to say during the interview to show Cisco that I know how to analyze and problem solve. I want to explain how I figured out how to get cheap car parts on eBay. Only 1/2 the battle of starting up my CIC kits was figuring out how to technically do it. The other 1/2 was figuring out how to source parts for cheap. If you go on eBay and search "CIC" or E90 CIC" you will get a bunch of listings for about $200 for the screen and $200 for the head unit.
Most modern cars have over 20 modules, do you think someone knows what each of these 20 modules are for all of the make and models of cars? Absolutely not, junkyards can barely manage to separate bad used parts from good or remove parts without breaking them. I asked myself how would a junkyard list a CIC? I searched and found out that most junkyards in the US use the "hollander" list to find compatibility and to list their parts. What does hollander parts call a CIC? They call it "Audio Equipment Radio Am-fm-cd Receiver With Satellite Fits 10-16 BMW Z4". I searched that term on eBay and there are a load of CICs ranging from $50-$150. With that price range I am able to make some good money. The funny thing is that this version of the CIC does not even fit the Z4 so even the hollander list is wrong.
Any thoughts? Would that be too technical?
|
1. Project manager on what? Ferguson job is for....what? Project manager also?
2. Analyzing and problem solving is all well and good but as a project manager your job will be centered more around tracking, coordinating, and communicating. Familiarize yourself with Excel, Jira, etc.
3. Don't go into an interview with a plan for a specific question - you never know who you'll get and what they'll ask. If you spend all your time prepping for a question that never comes, you may struggle to answer whatever they DO ask you. Have a general idea of some of the generic questions, but don't get too hung up on a specific one - be ready to think on your feet.
4. By generic typical questions (and not just talking about Cisco here) I mean the usual "what would you say are your strengths / weakness" "where do you see yourself in 5 years" etc. But at the same time I've also had random questions about other companies before - "how does google maps know traffic?" or random things like "why do you think manhole covers are round?"