Office 2010 Home And Business Product Key blog doe

This write-up was originally posted in August 2008 and continues to be each a popular publish and a poignant query. Does a failed startup on your resume count towards you?,Window 7
This is often a superb query. In traditional recruiter style, I’m going to get very definitive and say: I think that it depends. :-) Startups are fantastic because they force people to wear multiple hats,Office 2007 Key, work in a resource-constrained environment, and think about how what they work on interacts with other pieces of the puzzle rather than of owning a very narrow project or piece of code. While that entrepreneurial flexibility is highly desirable in any size org,Microsoft Office 2007 Standard Key, a pattern of several in a row might unfairly brand someone as a serial startup person, likely to bolt every year or so.Speaking of patterns, how many failed startups are we talking here? I love people who take risks and follow their passions, but if your resume lists a series of short stints at failed startups,Office 2010 Home And Business Product Key, I think it’s natural to query a person’s career management skills. I’m always curious to get my candidate’s take on why the company failed. Were there adverse market conditions at play? Was the product ahead of the need? Was it unforeseen technology gaps,Office 2010 Serial Number, poor product or shady business dealings? I think it’s fair game to find out what role the candidate played in contributing to the success or failure of any venture. Another thing to keep in mind is that building and scaling provide different challenges and not everyone is good at (or wants to do) each. During the interview cycle, you might be asked about whether you are solely a "V.1 person" or if growing a product/service is something you’d find as intriguing as building from scratch. Lastly, it’s worth mentioning that failure is not an absolute. Microsoft LOVES to ask questions around what one has learned while failing. We’d be foolish to discount valuable lessons learned in defeat. I think it’s funny that I’m answering this query because my whole "pre-Microsoft" career had been finding candidates for small startups in the Bay Area and Puget Sound. During that time I learned a lot of lessons that have helped pave the way for future successes. Anyone have a decent "lesson learned at Startup X" story they’d like to share? - Matt