Chapter 1. What is Enterprise Design?
"Mr. Arking, your experience, certifications, and references are terrific, but unfortunately we can't hire you. Your resume just doesn't have enough enterprise experience... ."
That was the first time I had ever heard the word "enterprise." Wrapped subtly within a casserole of deprecating niceties and empty affirmations, assailing my staunch sense of geek-honor as I wrestled with the gravity of the moment. That was the first time I was ever turned away from a job in software development. Like most fallen nerds, I went through the normal stages of post-interview withdrawal. Similar to the departing of a close friend or relative, I felt denial, then outrage, then moved slowly into a state of grief. As the eccentric side of me skimmed through the torrent of emotions that accompany job overreaction, I began to evaluate what I did wrong. I have no enterprise experience? What does that mean? Didn't my interviewers read my resume? Weren't they impressed with my vast experience with different APIs? Didn't they appreciate my deep knowledge of different platforms and languages? I mean, look at all of the companies I worked for... all of the different applications I had built! Surely some of that demonstrated hands-on practice with enterprise!
After my failed interview I was determined to figure out what I had missed. I prided myself on being the consummate interviewee. I had all the right answers, knew all the best programming tricks. I had stacks of code ...
Get Professional Enterprise .NET now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
