Showing posts with label interview. Show all posts
Showing posts with label interview. Show all posts

Tuesday, May 24, 2011

EXCLUSIVE: Interview With Apple's First CEO Michael Scott (AAPL)


Michael ScottWhen Steve Jobs and Steve Wozniak founded Apple in 1976, they couldn't be trusted to run the company.

So, Mike Markkula, Apple's first backer, and the man that guided the company early on, brought in a CEO to do the droll, adult things needed to keep a company running.

His choice for CEO was Michael Scott, who had previously worked with him at Fairchild.

In the course of our reporting about the first ten Apple employees, we managed to get Scott on the phone. Below is a transcript of our conversation.

Business Insider: You were employee number seven when you came into Apple, right?

Michael Scott: No, because I assigned the employee numbers. I was employee number seven, because I wanted number seven. I was actually employee number five at that time. So I was 007, of course, as a joke.

BI: What was it like when you came into the company? You were recruited by Mike Markkula, Apple's first investor, right?

MS: Markkula and I go way back. We both started in 1967-68, I think. We started the same day at Fairchild. He wanted the nickname "Mike," so I got the nickname "Scotty." Coincidentally, we also have the same birthday, except he's a year and a day older. We worked together at Fairchild for five years, he went on to Intel and I went on to National Semiconductor. We always stayed in touch because we had lunch on our birthday. So he called me, I guess in 1976, and said that he'd met these two guys that wanted to do a home computer. He could handle the marketing, but he wanted me to handle the details. So I met with him and the two Steves and read the business plan, which was quite wrong because it said TI was going to be our major competitor. And for some reason, they never got into the PC business.

BI: What were your impressions on meeting the two Steves?

MS: I never got to see the garage, I just saw it at Markkula's place up on a hill. Jobs did the talking, and Woz was the quiet one, although more lately Woz has found his voice more. In the early days, we were all so busy, that it was well partitioned over who did what. Woz was doing circuit board itself, Jobs was handling rest of Apple II, Markkula was working on marketing, and I was working on getting us into the manufacturing and all the rest of the business parts.

The story that's untold is that Rod Holt was brought in as product engineer and there were several flaws in Apple II that were never publicized. One thing Holt has to his credit is that he created the switching power supply that allowed us to do a very lightweight computer compared to everybody else's that used transformers. We used high-speed switching vs. the classical transformer, so we were able to get the weight down. But within their first Apple II, when we tried running it warm like you would in Florida or someplace like that, it stopped working. So that was a secret at the time. How do you get it to work all the time? We kept that a trade secret. That was Holt that found that out. If you stuck in a scope probe to try and figure out what was wrong, it started working again, which was very frustrating, and we were against a time schedule to get into production and we had to freeze the circuit board.

So the other problem we had was where the case itself, which used structural foam, because we couldn't afford the lead time to do hard tooling. We had a lot of trouble with the case when we molded it, it would warp and wouldn't hold its shape.

That's one of the things I still remember. In the spring of 1977, Jobs had this Falcon pickup truck, which I don't think is made anymore. So we'd run off to the molding shop to see what was needed in order to get us cases fast enough.

You're only taking the first ten employees, so by June of 1977, we were at 10. In May, at the first computer fair, we were at 7. So by August of that year we had positive cash flow and were on our way.

Michael ScottBI: From May to August you went to positive cash flow?

MS: Yeah, we paid of all our loans and at that time, made the decision to… that was the time to choose when to end our first physical year. We made our first $50,000 in profit and paid taxes on that, so you're able to go forward estimating the amount of taxes you are willing to pay is equal to your previous year, so we were able to save a year in taxes forward as we continued to grow. That year ending was for tax planning, and not for anything else.

BI: When you were running around with everyone in those early days, was Steve Jobs then as assertive as he is today? It's funny hearing about you guys doing these manufacturing things and now there are these legends of him tearing down an iPod the night before it releases because it doesn't make the proper clicking sound. Was he as particular then as he is said to be now, or in the early days was he learning and acting differently?

MS: No, he was maybe more particular. The Apple II case came, it had a beige and a green, so for all the standard colors of beige available in the world, of which there are thousands, none was exactly proper for him. So we actually had to create "Apple beige" and get that registered.

I stayed out of it but for weeks, maybe almost six weeks, the original Apple II case, Jobs wanted a rounded edge on it so it didn't have a hard feel. They spent weeks and weeks arguing exactly how rounded it would be. So that attention to detail is what Steve is known for, but it also is his weakness because he pays attention to the detail of the product, but not to the people.

To me, the biggest thing in growing a company is you need to grow the people, so it's like being a farmer, you need to grow your staff and everybody else too as much as you can to enable the company to grow, just as much as you need to sell the product.

BI: Can you explain that? So was that your job to make sure you brought in all the right people and he wasn't very attuned to that?

MS: I don't know how much he's changed being a manager, but he would not, for instance… he was never allowed to have much of a staff while he was there because he would not supervise them. He wouldn't make sure they got their reviews on time or that they got their raises, or that they got the health they need.

You have to take care of the people as well as the product. As they say he yells at people, at times you have to yell, but at times you have to be supportive too, and I would say that that's still what makes Steve, Steve. The thing that everyone still misses is that there always was and still is a lot more to Apple than just two Steves. But thank God I think our early decision to let the two Steve's do the publicity, I'm happy for that.

BI: When you came in, you were the CEO, correct? Were you immediately appointed CEO?

MS: Yes, so I got to do the part numbering system. I got to do all the stuff nobody else wanted to do. I opened the bank account, and did the employee numbers.

BI: What is the significance of the employee numbers, since you were saying that you took seven because you wanted it.

MS: We had to have a payroll, and in order to minimize how much work we had to do, I had to sign up with Bank of America's payroll system, and those days you didn't have a choice. You had to assign employee numbers.

That was a dispute you get into -- who gets number 1? One of the first things was that of course, each Steve wanted number 1. I know I didn't give it to Jobs because I thought that would be too much. I don't remember if it was Woz or Marrkula that got number 1, but it didn't go to Jobs because I had enough problems anyway.

This is literally almost 20 hours per day for everybody. We couldn't add people fast enough to match the growth of the business. It was always a struggle to run from one fire to the next, no matter who you were there.

BI: In terms of these other people that have gone unsung, is Sherry Livingston -- did you hire her from National? Was she the first secretary?

She was our right hand. When she started there were only five or six of us. She was receptionist, phone operator, secretary to everybody. She was our right hand to fill in for everything. When I hired Gary Martin for accounting, he came in and I had a cardboard box under my desk. I said "here are all the receipts and checks we've been writing. Get them organized." There just wasn't time to get that done.

BI: Was it hard to recruit people in those days when you were first starting out? Because I would imagine that startup culture then was not what it is today.

MS: There wasn't enough time to really pay attention to getting people in and getting them indoctrinated into the culture, because we had no culture to begin with. The Apple culture came later. We'd already stopped Apple I production so there was no cash coming in. We had to get the Apple II out and get the cash coming in or we wouldn't have been in business. So Markkula put up a quarter million dollars and that's the cash we used to get started.

BI: What was the culture that developed at the company in the early days?

MS: Well, I guess the biggest part of the culture was that Holt made our coffee in the morning. He made the coffee to suit him, and it was so strong that it would keep us all up forever. That was subsequently a big fight that we had.

Ann Bowers…. who was…. I forgot the guys name, but she was the wife of one of the founders of Intel, she was our first VP of Personnel. This was a couple of years later. She was on this kick saying that we should not supply caffeine to the employees because it was unhealthy. And I just said, "No," because we weren't a committee and we didn't need a vote on it.

I would say that the challenge was, who was more stubborn, Steve or me, and I think I won.

The other argument at the meetings was would Steve take his dirty feet and sandals off the table, because he sat at one end of the conference table, and Markkula sat at the other end chain smoking. So we had to have special filters in the attic in the ceiling to keep the room filter. I had the smokers on one side and the people with dirty feet on the other.

[Laughter from us.]

It was not funny then. Everybody has their pet peeves.

BI: Were you hesitant to go, and it seems like you came into a big role, were you prepared to be doing what you'd be doing, or were you overwhelmed?

MS: I looked at it as an opportunity. I'd been a product line manager at National Semiconductor so I had a profit line group and had under me a marketing and finance guy, and a manufacturing area there. And I had turned down Charlie Sporck who had turned down the president of National at the time. He offered me the job of Plant Manager in Hong Kong. But I thought that would get me too far away from technology and I didn't want to move, so when Markkula asked if I wanted to start a new company, I looked at it as a chance to say everything I learned at National and Fairchild and didn't like, could I now put together a way to manage a company and learn from that.

The biggest thing I applied at Apple was in the manufacturing and in most of the way we organized stuff was that we never let anything be bolted down. The way semiconductor plants worked you had to plan way ahead.

At Apple, we designed everything to roll around on carts so we could change it as we needed to. And the other thing was that there were all kinds of accounting rules that I didn't allow at Apple. I still remember at National they had allocation for variation in the price of gold, and I was still having to pay for that when the gold price varied. And to me, that didn't make any sense. That's the way the bureaucracies get set up.

BI: When you left, was it just too much dealing with Jobs and getting into confrontations with him that drove you away ultimately?

MS: No. I always had a deal that it was two Steves and Mike, if I didn't have all of their support, I wasn't going to stay. We grow to 1500 people and laid off 50 to clean out the dead wood. That caused a lot of hassle, and to me, I didn't need that anymore. I took us public and then got out.

ssBI: Did you ever have regrets from leaving?

MS: Well, I had another life. I went and built rockets after that. We got a rocket launched out of the water, and since then, I've done other stuff. I can say I've traveled everywhere I want to go. There are a few places in the world. I almost went to the north pole on a Russian nuclear icebreaker, but I've learned to ask questions and decided not to go on that. I found somebody that had been, and they described it as being on the inside of a 55 gallon drum with somebody beating on it with a sledgehammer 24 hours a day as you're breaking ice to go to the north pole for a nature trip. So I've done a lot of things and still am, and I'm working on stuff that's probably before your time right now.

I'm working on a tri-coder. It's from the first Star Trek. It's a handheld gadget where you hold it out and it tells you what something was. So I'm working on the libraries that would let you take something the size of a cell phone and if you're walking out the trail, aim it at a rock, and it'll tell you whether it's a sapphire, and emerald, etc. So the technology is there now. What's not there is the library routine that tells you what things are.

BI: How are you working on that? Is it a company? Do you have a team?

MS: Research at the University of Arizona, and theoretical research going on at the University in Leon, France. I've also sponsored stuff at Cal Tech, so some of it is done remote. Also I have my own laboratory at home with some fairly fancy equipment because I can. I broke down and I now have some PCs around, unfortunately, but mostly I still use Apples.

BI: What have you thought of watching the company go through the various stages of its life to where it is today? What's your take on when it became, by market cap, more valuable than Microsoft?

MS: I met Gates back in 1977. In one way we can say he screwed up way back then by making Apple very successful. We were able to buy Microsoft Basic from him for a fixed price, $25,000, convert it to run on the Apple, then give it away.

That's one of the ways Apple was really successful up front, because we had the operating system, but no application package ran on the Apple up front that would make it useful. So essentially having a spreadsheet and having Microsoft Basic on the Apple was a couple of the hooks that made us able to grow.

That's what Wigginton's main job was, rewriting Basic to get it to run on the first Apple II. The first Apple II typical configuration had 16K of memory. We had a 4K version and the biggest it went was only 48K, and I'm sitting here with terabytes about me in my own little office.

elephant Michael ScottBI: In 1997, when Jobs returned, could you have pictured it being where it is today?

MS: As long as you're learning something new and taking chances until you're old and foggy and retired. I think the Apple success still is in the role we chose in that we'd build a tool, not a toy, and that we would control both the hardware and the software aspects of it. That's still why, on all the different products, you see the success.

They've delivered the combined, well-integrated package of the hardware and the software. Fortunately, when IBM decided to get into the PC market they chop-shopped out the hardware to several different groups so you had a mess of hardware, and they've been trying to cobble the software on it ever since.

And you still see that in the phones and the iPad or the computers. You have to control both, or you end up with a mess. Android is a good example now, as Google's learning, if you don't have a level of discipline, you end up ruining the product.

That's still the way it works, it's still in the culture, you want to do things right, not just "good enough." The alternative business model is like Microsoft, where something's "good enough" to ship, instead of wanting it "just right." It's always been Apple's goal to ship something we were proud of and something people would be proud to own, and I think that's still true from thirty years ago.

BI: Are you still in touch with a lot of the early employees?

MS: Well, I'm having lunch with Sherry next week, and we're both feeling old now, because she just became a grandmother, and I talk to Dan Kottke via email every now and then Wigginton and I have planned to get together, but haven't for a while. So, some of us are still in touch, and some of us are so busy you can't get through to them anymore.

BI: When you were first starting out, did you guys quickly realize that you were on to something special?

MS: We thought we had a good product, and the idea was that you could do something different. They were selling bricks back then. I started back on IBM computers. Stuff has changed a lot. Even back then, what was a PC or computers back at that time were still big clunky things. I guess the best example was that we had a contest very early on at Apple where we awarded an extra Apple for the unusual use of the machine. The winner, and what we never realized then, and what we don't think is still true now, is you don't realize how many different ways it can impact you.

The first use was the person that swore by it, a new father who had a new son that the colic, and took the original Apple II, did his own software, hooked up a washing machine motor, the tilt mechanism from a pinball machine, a microphone to the crib. So when the kid was getting restless, the machine would come on and rock the bed. He actually had statistics to show how much more sleep he and his wife were getting because the kid would partly wake up, then go back to sleep. And that won first prize for a different use of the Apple, and I think that's still true today. People are still finding uses. You put it out in one area, and then it gets out into a lot of others.

BI: What did Jim Martindale do? What was his role?

I may've gotten him mixed up with somebody else, but I'm pretty sure he was our first foreman/production guy. The production room, which was originally only 700 square feet, and mostly was just doing final tests and debugs, and I think Kottke worked for him for a while, and if I remember right that was the beginning of our production operation. They've always been kind of funny at Apple, because we've always tried to chop shop out a lot of it. On the Apple II, 95% of the cost was just materials, not the labor, so that was quite a bit different than the historical way of doing things.

BI: That's because you guys were customizing?

MS: No, the cost of the microprocessor and the cost of the memory was such a high percentage of the value of the product. The other thing we ended up doing was, historically, when we went into the business for retail. The retailers at the time all wanted a 50% markup and we couldn't afford that much margin and meet the price points we wanted. So the original Apple II price point was $1195, and it still is.

Over thirty years, but you're getting a lot more for your money. One of the big original arguments on the Apple was that we really wanted it to be under a thousand dollars. We wanted it to be $995, but we just could not do it cheap enough to get to that price point, so that was one of the other big internal arguments at the time, was how to price the machine.

BI: t's funny to think about because Apple is known for being profitable and going after margins, it's funny to think that even back then, the company still wanted to try and protect that good margin.

MS: The catch is that it's not only for Apple. The whole rest of the chain has to make money too. So you have to have distributors and retail stores and everybody has to make a markup. You have to ask if they're truly adding value for what the markup is. Then there's the tradeoff there too. You could say Apple could've grown faster at some point in time if it didn't keep the price up as high. But if you set the prices too high, you establish a price umbrella that lets competition get into the business. I noticed that with the iPad, Apple is no longer making that mistake.

wozniak jobsBI: Anything else you want to share?

MS: Just the legacy. You can't fight the mythology. Once it takes off on the internet, there's no changing it.

BI: What kind of mythology?

MS: It doesn't matter. The story itself becomes more exciting than what the truth was, so you have to just stay with what sounds good.

BI: You mean about Apple being built, or it in truth being a lot of work?

MS: A lot of Apple is still somewhat mythology, and somewhat history, and you can't go back and change what it's perceived to be. What it's perceived to be is what the reality is now. What the daily grind was.

BI: You're saying that it's perceived as a bunch of guys…

MS: There's a lot more hard work and sweat involved in getting stuff done than anyone could imagine.

BI: I think that's true probably in any startup where you only have ten people, you have to grind out 20-hour days once you get it going.

MS: For four or five years, Apple doubled in size every three months. It's hard for it to double that fast now, but it's still doing pretty good.

BI: Doubled in size every three months, do you mean in headcount?

MS: And in square footage. My last year there, we were adding a quarter million square feet every three months to our total facilities. And even on headcount, yes you start. Between our fourth and fifth year, you go from 500 to 1500 employees. Most of the time when we were growing, we had to bring in temp workers because we couldn't hire them fast enough, so we'd bring in temporary workers, then we'd pay the headhunter fees to convert them over to Apple employees. You do what you have to do. That's to me, for a small business growing now, they succeed because they have no choice. You need to stay in business. Once you get big enough, there's a cushion and a lot more room for inefficiency. Just look at the government.

BI: What was it like early on with Steve Jobs. Was he just overlooking product and seeing details? What was his role in that first year or two?

MS: A little side story that he and I would fight over. If we were negotiating price for parts, we could negotiate a price with a vendor and at the last minute, Steve would come in and bang on the table and demand to get one more penny off. And of course they would give him one more penny off. Then he'd crow "well I see you didn't do as good a job as you could've getting the price down."

And I'm saying, "Yeah but that one more penny might've cost us a bit more ill will for times when parts are in short supply."

BI: Did those things ever come back to hurt you guys?

MS: While I was there, it never did come back to hurt us, but there's always a judgment call, and it's always because nothing's ever as black and white as you would like to think it is.

BI: Was there tension with you being brought in as, what we call now, "adult supervision." Did you get the sense that he wanted to be in charge of the company and resented you or anything?

MS: Steve just wants to be Steve. Steve's never shy about telling you what he wants and where he stands. He's very straightforward to deal with. Unlike other people that don't tell you what they mean. If you're a politician versus a businessman, that attitude can have its ups and downs.

Related: The First 10 Apple Employees: Where Are They Now?

For the latest tech news, visit SAI: Silicon Alley Insider. Follow us on Twitter and Facebook.

Join the conversation about this story »

See Also:







EXCLUSIVE: Interview With Apple's First CEO Michael Scott (AAPL)


Backlink: http://feedproxy.google.com/~r/typepad/alleyinsider/silicon_alley_insider/~3/YsYZ8c_8yE4/apples-first-ceo-michael-scott-2011-5

Saturday, February 19, 2011

(Founder Stories) Fred Wilson, The Full Interview

What was the best business decision VC Fred Wilson ever made? What was the worst? What part of his job does he dislike the most? The answers might surprise you. In the video above, Wilson answers some rapid fire questions (delivered in a not-so-rapid fashion) from Founder Stories host Chris Dixon. The clip is an outtake from the interviews segments we ran a week ago, in which Wilson talks about frothy valuations, his investment philosophy, the relationship between VCs and startups, and the VC business in general. We cut up the interview into four separate clips, which you can find in the links above, but they were so popular I am putting the entire unedited 17-minute interview below, for those of you who missed it the first time around or want to watch it all the way through.

(Founder Stories) Fred Wilson, The Full Interview


Backlink: http://feedproxy.google.com/~r/Techcrunch/~3/kgydg_zgD6U/

Tuesday, February 15, 2011

This Is The Application That Got Me A Job Interview With Google

alysonguitar.jpg

If you read about my nightmare interviews with Google, then you know I bombed them.

But two years later I ran into one of my interviewers. He recognized my name at a conference and said, "I remember your application. I've never seen anything like it."

Even though I buckled under the pressure, I had an application that got me remembered and got my foot in the door.

Depending on where you want to work, applications don't have to be traditional and boring. They need to stand out from clutter and showcase your skills, much like business cards

If it helps, here is what worked for me.

This is the application cover I created for Google with things about myself (because Google says they really like diversity and personality):

Google application 1

And here's the cover letter I designed to match their marketing materials.

Google application 2

If you want to nail the Google inteview process, make sure you know how to answer these 15 Google Interview Questions That Will Make You Feel Stupid >>

Join the conversation about this story »




This Is The Application That Got Me A Job Interview With Google


Backlink: http://feedproxy.google.com/~r/typepad/alleyinsider/silicon_alley_insider/~3/MydsQ8_HTwo/this-is-the-application-and-cover-letter-that-got-me-an-interview-with-google-2011-2

Monday, January 3, 2011

Win $25K: Dice Best Interview Ever Contest

What if we told you that by answering an interview question from David Karp from Tumblr or Jonah Peretti from Buzzfeed or Veronica Belmont from Revision3, you could win $25,000 and a trip to NYC to interview in person? We'll, it's true.  Head over to Dice.com/contest to enter. Oh, and you'll also have a shot at 6 Xbox Kinect bundles.

Now -it's 2011. Since it's already the third of the month and your New Year's resolution went out the window two days ago, we thought we'd recap the best tech jobs of 2010 (according to Money/Payscale.com).

The Five Best Technology Jobs. Ever. Well, Okay, For 2010.Software Architect (2010 rank: 1st in IT, 1st Overall)
Background: These digital blue print makers are the true link between a company's technology and the staff. 



Why should you want to be one?  The pay is good and software architects partake in a variety of tasks from product strategy to coding.


Database Administrator (2010 rank: 2nd in IT, 7th Overall)
Background: DBAs have to be organized. Why? Because their main duty is to organize and manage the gargantuan amount of data that companies accumulate over time.  They are also responsible for updating software and troubleshooting problems.

Why should you want to be one? Companies are not accumulating data linearly, but rather exponentially. There is a demand for solving the complex problems of what to do with all these mega bytes - which is where the DBAs come in.  It's challenging work - so you better get your game face on.

Information Systems Security Engineer (2010 rank: 3rd in IT, 17th Overall)
Background: Think of them as a digital super hero. IS Security Engineers develop plans to keep your company's computer systems safe from harm (and bad guys).



Why should you want to be one? This challenging field requires acute planning and execution skills.  Please read the following to the theme of Ghostbusters: If there's somethin' strange in your security architecture - who you gonna call - IS Security Engineers. If it's somethin' weird and it don't look good - who you gonna call - IS Security Engineers.


Software Development Director (2010 rank: 4th in IT, 18th Overall)
Background: The software development director is like a conductor, but instead of the baton, they're armed with a Mountain Dew. He or she orchestrates the direction and the operation of software development organizations.



Why should you want to be one? Here's a riddle. What's a model with no insides? A mannequin. A software development director's job is to make that mannequin a model - to manage the team that builds the software that makes organizations function effectively, efficiently, and more importantly, profitably.

IT Manager (2010 rank: 5th in IT, 20th Overall)
Background: An IT manager is responsible for investigating and determining what technologies will help companies be the most productive and profitable. 



Why should you want to be one? Since technology advances faster than the national debt, IT managers have to always be on top of what technologies are emerging and determine which ones will be most impactful to their business.


Those might be the best tech jobs ever. And remember: If you need to dream a little about the best jobs out there, check this out.

-- Adam Fudala




Win $25K: Dice Best Interview Ever Contest


Backlink: http://career-resources.dice.com/articles/content/entry/the_5_best_technology_jobs

Friday, December 3, 2010

Here's The Awesome Interview With Nick Denton That You Missed At Ignition

Business Insider just wrapped up its IGNITION conference – a two-day discussion with some of the leading experts in journalism, social media, and advertsing about the future of media.

Above is an interview with Gawker Media founder Nick Denton from Day 1, covering topics from Gawker's redesign, the benefits and disadvanatages of sensationalism, paying for scoops, measuring writers contributions, among others.

Produced By: Kamelia Angelova, William Wei & Anika Anand

More Videos:

And Don't Miss...

Kim Kardashian: Here's Why I Am Quitting Twitter

Kim Kardashian: Twitter Deserves A Cut From Celebrities' Paid Tweets

Join the conversation about this story »




Here's The Awesome Interview With Nick Denton That You Missed At Ignition


Backlink: http://feedproxy.google.com/~r/typepad/alleyinsider/silicon_alley_insider/~3/v9EpSJlxF9U/ignition-nick-denton-2010-12

Wednesday, November 17, 2010

Interview with Richard Stiennon, Chief Research Analyst, IT-Harvest, USA

Ahead of his presentation at CeBIT Australia's IT Security Conference, we spoke with Richard Stiennon, Chief Research Analyst at IT-Harvest USA about the changing landscape of cyber threats and how organisations need to adapt and change to meet these threats head on - plus the security threats that emerge from mobile devices.

Monday, November 15, 2010

Interview Questions for Network Managers

When it comes to filling a network manager role, recruiters and interviewers want to hire someone with a balance of expert technical skills and strong communication skills. A top-notch candidate has a solid understanding of firewalls, routing protocols, SNMP, load balance and network design. 

Interview Question for Network Managers"The hardest candidates to find are those with a combination of technical, verbal and written communication skills," says Sandy Lambert, CISSP-ISSMP, managing director of recruiter Lambert and Associates. "It's easier to find somebody who is technical than it is to find somebody who understands technology and can communicate it."

Generally, interviewers want to find out how network managers "deal with people, problems and technology," adds Ilya Talman, president of Roy Talman and Associates Inc., a Chicago-based search firm specializing in IT.

The following are a list of commonly asked interview questions:

Give me an example of the most challenging project you worked on when you were the leader.

To answer this question effectively, you've got to describe a project where you used both technology and managerial skills. Hone in on the number of people managed and the complexity of the project. Interviewers are also looking to see if you have experience managing a network similar in size and complexity to theirs. Which leads to another common question: What are the sizes of the networks you've previously dealt with?

Show me how you would implement a particular network.

This question can be tailored toward a specific position or contract job, says Vasanthan Dasan, CTO and vice president of engineering for the Armada Group, a staffing firm in Silicon Valley. Candidates must articulate, and sometimes show, how they'd plan and create a network. In one instance, Dasan's question for a was, "We need to design a caching network for a client that produces mapping software for customers worldwide. How would you go about implementing this network?"

"From the way they think and understand networks, I get a sense of whether they can do the job or not," Dasan says. "I may also ask them to write that down into a statement of work that includes how long it will take, what they will deliver and how they will implement it."

Here's an example of a network. Where and how would you put security controls into it?

Network managers are increasingly being asked to handle network security issues. When Lambert worked at Citibank, she would present a diagram of its network and ask candidates to draw and explain a security strategy. Similar questions are, "What other tools have you used to increase the security of a network?" and "What were you specifically responsible for to ensure firewalls and protect the network?"

Tell me about a mission-critical, 24/7 network you worked on.

"Many Network manager positions have to deal with a 24/7 environment," observes Craig Kapper, senior regional vice president for Robert Half International. "Ultimately we want candidates who can minimize downtime in a 24/7 environment." A follow-up question could be, "What type of redundancies did you implement for failover if the network goes down?"

What are some of the duties in your current or previous job that were satisfying to you?

Some people love to be involved with all the details of a project from start to finish. Others prefer supervising workers and allocating project details. "If they liked all the details at their previous position, then they may not work as a network manager, because the network manager has to oversee everything," Lambert says. Your answer also reveals your work habits, and gives clues on whether you know know how to motivate 

Explain your hardware experience.

Interviewers are looking to understand not only your hardware experience and strengths, but how you've leveraged hardware in the past.

Explain your experience with VPN, network authenticity management, encryption and integrity issues.

With more people wanting to access company information remotely and from different devices, network managers are often asked questions regarding remote access, Kapper says.

Some other questions you may be asked:

Explain your experience implementing VoIP or wireless.

What is PKI? Describe 802.11. 

How did you map and prepare a two- to three-year strategic roadmap for a network?

How did you negotiate with vendors?

How do you control network traffic?

-- Chandler Harris

 



Post originale: http://career-resources.dice.com/articles/content/entry/interview_questions_for_network_managers

Interview Questions for Enterprise Architects

Companies interviewing enterprise architects look for a comprehensive technical skill set, along with communication skills and a passion for the job.

Interview Questions for Enterprise Architects"There are a lot of people that interview and are passionate about something else," says Craig Kapper, senior regional vice president for Robert Half International. "You can be an okay communicator, but if this is your life work and you are wildly passionate about it, you'll probably get the job."

A firm foundation in one or more current architecture is essential. These include service-oriented architecture (SOA), model-driven architecture (MDA), event-driven architecture (EDA) and object-oriented design (OOD). During an interview, you should be able to explain your experience and give concrete examples of where you implemented it. You need a solid understanding of software development processes and methodologies, and should be able to explain TCP networking, firewalls, routing and load balancing. 

Here's some key questions you can expect to be asked.

Give examples of enterprise architecture you designed and what type of protocols you used.

A successful answer includes an explanation of your experience and the methodology that was leveraged, middleware that was used to interact with complex environments, and lessons learned.

How do you see IT supporting new business initiatives?

This question attempts to reveal not only your experience and knowledge, but the vision you hold to transform and implement business strategies. 

"The enterprise architect must be able to see big picture, the forest as opposed to the trees," says Sandy Lambert, managing director of recruiter Lambert and Associates.

What advice would you give server side Web developers wanting to ensure new code was secure from external attacks?

"Enterprise level work is inevitably about security," says Kapper. With security a major priority for an organization's infrastructure, enterprise architects must have a solid understanding of current security processes, including encryption, authorization, authentication and public key infrastructure.

What problems do you expect to encounter with an organization that has a "siloed" structure? How would you deal with it?

This is an organizational question that will be specific to a company's network. Lambert asked this specific question to candidates for Citibank in order to learn how they'd connect silos of a large and diverse infrastructure and enable the enterprise vision.

What kind of cloud computing work have you done?

This is the first question Vasanthan Dasan, CTO and vice president of engineering for the Armada Group asks of enterprise architects during interviews. He's interested in hearing of how they see their role in the ongoing trend in cloud computing and migration.

"The trend I've seen over the last three years has been organizations moving applications, infrastructure and network into a hosted cloud model," he says. "I believe that trend is going to continue for the next ten years as the majority of it infrastructure is moved to a hosted model."

Even if cloud computing experience may be on a candidate's resume, Dasan asks this question to learn about a candidate's experience and knowledge about cloud computing in his or her own words.

Describe how you migrated an application in a traditional architecture to the cloud.

Dasan follows up with this to see how a candidate solves problems and approaches cloud migration with a specific architecture. At times he'll even ask the candidate to demonstrate by drawing code and designs on a board. 

"I'm looking for why they chose these methods, what features they included, what options and how they go about deciding certain components," he explains.

Prioritize the following criteria for a new code design based on importance, and explain your reasoning: performance, ease of maintenance, code accuracy, ease of use, and ease of adoption.

This one's tricky, since the right answer ultimately is what the client thinks is important. However, an honest assessment and identification that the right answer lies in an organization's needs is helpful.

Draw an example of the architecture of a high transaction website or database, and explain it.

This will test your knowledge, quick thinking ability and communication skills. The interviewer will look at load balances, Web servers, scalability, data modeling and among other things.

What enterprise resource planning (ERP) systems have you worked with?

Kapper also asks, or follows up, with related ERP questions such as: What platforms have you used for ERP implementation efforts? What ERP modules have you been specifically responsible for? What ERP tasks were you assigned to? What kind of network protocols do you use?

How did you measure success and moderate performance in one of your projects?

"I'm really looking for good communication skills," Vasan says. "The ability to articulate, model the problem, extract solutions, define interfaces between components, and have good knowledge of what's possible implementation-wise, and what's available and tested in the marketplace."

Other questions:

What is the best project you ever worked on?

What did you contribute to the project?

-- Chandler Harris



Post originale: http://career-resources.dice.com/articles/content/entry/interview_questions_for_enterprise_architects

Saturday, November 6, 2010

Interview Questions for Project Managers

Interview questions for project managers inevitably focus on past project experience. The ability to form detailed and articulate responses is one of the top factors recruiters look for, since the nature of the position entails so much communication. You should also be able to demonstrate excellent organizational skills when you describe previous projects, according to Vasanthan Dasan, CTO and VP of Engineering for the Armada Group, a cloud computing firm in Silicon Valley. Demonstrating time-management skills, and the ability to identify project roadblocks in advance, are also key.

Interview Questions Project Managers Should be Ready ForHere's a sample of the questions you'll be asked.

Give me an example of a project you managed as it relates to this position.

Most project manager interview questions are related to previous projects. The project manager should be able to articulate project details such as planning, methodology, team management, risk management, collaboration, technical tools, obstacles, communication and results.

The best answer is to give an example of a project that is similar to your prospective employer's projects. If not, you should at least attempt to orient the answer as it relates to the position.

Here's a sample project. How would you go about planning, managing and completing it?

A variation on the first question, this one's designed to test your quick-thinking ability and depth of knowledge.

Talk about a project you worked on that had problems and what you did to fix them.

A similar question that may be asked: "Explain when an IT project wasn't in line with what the organization wanted. How did you get around that?"

"Project Managers are frequently asked about challenges and to reveal a situation where there was conflict that needed to be resolved," says Susanne Currivan, senior account manager for Project One, a New York-based IT staffing firm.

During a project, how do you inform all stakeholders of progress on a regular basis?

Effective communication is key to a successful project, so you'll need to demonstrate numerous ways and tools used to communicate with team members and stakeholders in the organization.

"Methodology and communication end up being a big part of the hiring decision," says Craig Kapper, senior regional vice president for Robert Half Technology. "Do they have the right methodology and does the project manager consistently relay progress reports to stakeholders?"

What tools do you typically use to monitor and control a project?

Obviously, there are numerous tools that can be used during a project, yet some are more robust and scalable than others. The idea here is to find out if you're using some of the more effective tools available, Kapper says.

How did you apply your training or certification to a previous position?

This question will commonly be addressed to probe your experience or certification, such as PMI. Interviewers may follow up with a request to give specific examples.

Explain how you established a relationship with your project team and how you collaborated to get things done.

This is a "culture fit" question designed to discover how you work with other people. A similar question is: "Give an example when you received coaching and how you reacted."

Others to look out for:

What project management methodologies are you most familiar with?

Give an example of a time where you had a conflict with, or disagreed with a boss or coworker.

-- Chandler Harris



Post originale: http://career-resources.dice.com/articles/content/entry/interview_questions_project_managers_should

Friday, November 5, 2010

Interview Questions Project Managers Should Be Ready For

Interview questions for project managers inevitably focus on past project experience. The ability to form detailed and articulate responses is one of the top factors recruiters look for, since the nature of the position entails so much communication. You should also be able to demonstrate excellent organizational skills when you describe previous projects, according to Vasanthan Dasan, CTO and VP of Engineering for the Armada Group, a cloud computing firm in Silicon Valley. Demonstrating time-management skills, and the ability to identify project roadblocks in advance, are also key.

Interview Questions Project Managers Should be Ready ForHere's a sample of the questions you'll be asked.

Give me an example of a project you managed as it relates to this position.

Most project manager interview questions are related to previous projects. The project manager should be able to articulate project details such as planning, methodology, team management, risk management, collaboration, technical tools, obstacles, communication and results.

The best answer is to give an example of a project that is similar to your prospective employer's projects. If not, you should at least attempt to orient the answer as it relates to the position.

Here's a sample project. How would you go about planning, managing and completing it?

A variation on the first question, this one's designed to test your quick-thinking ability and depth of knowledge.

Talk about a project you worked on that had problems and what you did to fix them.

A similar question that may be asked: "Explain when an IT project wasn't in line with what the organization wanted. How did you get around that?"

"Project Managers are frequently asked about challenges and to reveal a situation where there was conflict that needed to be resolved," says Susanne Currivan, senior account manager for Project One, a New York-based IT staffing firm.

During a project, how do you inform all stakeholders of progress on a regular basis?

Effective communication is key to a successful project, so you'll need to demonstrate numerous ways and tools used to communicate with team members and stakeholders in the organization.

"Methodology and communication end up being a big part of the hiring decision," says Craig Kapper, senior regional vice president for Robert Half Technology. "Do they have the right methodology and does the project manager consistently relay progress reports to stakeholders?"

What tools do you typically use to monitor and control a project?

Obviously, there are numerous tools that can be used during a project, yet some are more robust and scalable than others. The idea here is to find out if you're using some of the more effective tools available, Kapper says.

How did you apply your training or certification to a previous position?

This question will commonly be addressed to probe your experience or certification, such as PMI. Interviewers may follow up with a request to give specific examples.

Explain how you established a relationship with your project team and how you collaborated to get things done.

This is a "culture fit" question designed to discover how you work with other people. A similar question is: "Give an example when you received coaching and how you reacted."

Others to look out for:

What project management methodologies are you most familiar with?

Give an example of a time where you had a conflict with, or disagreed with a boss or coworker.

-- Chandler Harris



Post originale: http://career-resources.dice.com/articles/content/entry/interview_questions_project_managers_should