Indigo .NET UI Development

Well this was the week to find out where I’d be working and come September, I’ll be taking my web development and design hobby to the next level at Indigo, Canada’s largest books retailer. That’s right, you’re looking at (err, reading) a soon-to-be professional web developer.

Of course, I had my sights set on the Product Planning position at Microsoft, so I was decidedly disappointed when I didn’t get an offer from them. For days while I awaited word, I went over the two interviews I had for the position again and again in my mind. There were so many things I wanted to say, to show what I could bring to the table, but it seemed like the topics just never came up. I attribute it partly to the short length of the interviews, but also in large part to faults of my own. I need to work on my interview skills; I feel that regardless of what the interviewer asks, I should be able to portray myself the way I want to and to guide the direction of the interview, even if those questions don’t come up.

Another time, perhaps. I do have one more work term left and I’ll be taking these lessons learned to heart.

Enough moping. Back to Indigo. I’m very excited about the position as I’ll have the opportunity to work on both the UI/design aspect of the project as well as back-end development. In the web market, too often you only have the chance to do one or the other. Speaking of the project, it’s a new web application just in the design phase now, so by the time I get there in September, I should be entering it at the ground floor. Hopefully that means I’ll have some control over how it’s implemented.

The Indigo interview was a different animal from the Microsoft one. I was in complete control, and I let my passion for the web industry ooze. In fact, this blog played a large part in getting the job. After speaking about my design experience, I decided my point would be stronger with a tangible example, and pointed the interviewer to randomprocess.ca. It didn’t take long for him to be impressed by the design as well as clean XHTML and CSS. Combined with my ASP.NET and PHP development experience at Sybase, I painted myself as a well-rounded web developer and designer.

The office is in downtown Toronto, which, in my mind, is one of the detractors. I’m just a small-town kid, having grown up in Charlottetown. My experiences with the big city consist of being a tourist, seeing how things are so different. I’ll be giving the city a chance; then no one will be able to say I don’t like the hustle and bustle just because I haven’t experienced it.

5 thoughts on “Indigo .NET UI Development”

  1. Hehe, if I were interviewing you, I would’ve followed up the XHTML comment with asking you why you chose to write in XHTML when most browsers don’t support it, and aren’t looking to support XHTML 2.0 vs. HTML 5. 😛 Just saying.

  2. While many of the features of XHTML haven’t been supported by Internet Explorer, I’ve always found it (the code) to be a bit more structured (and adheres to a more strict form) compared to HTML4. I’d rather not get into the debate between XHTML2 and HTML5 at this point, mostly because I don’t think I have enough knowledge of the two draft standards to debate it intelligently ( 😉 ), but based on backwards compatibility alone, HTML5 seems to be a better bet at this point.

    And thanks, Tim. I hope it’s what I’m imagining it to be.

  3. I agree, XHTML is much nicer on the eyes and more consistent when comparing it to HTML 4.01. I really wish they would come out with HTML 5 a bit faster so that we can all be on our merry ways and write nice code that’ll be interpreted properly by all the browsers. I asked this question because I wrote my workterm report on HTML 5 vs XHTML 2 and I was surprised by the lack of real support for XHTML 1.0 / 1.1. Up until then I was coding in XHTML 1.1 Strict and it was just making my life difficult.

Leave a Reply

Your email address will not be published. Required fields are marked *