Back to list
Views:   15.5K
Replies:  3

Career Advancement: moving from Mid Level to Senior Level

Several years ago I was diagnosed with cancer and taught my self C# to keep my mind off of the chemo and radiation. I have come a long way however, I feel that I am kinda stuck in the Mid Level area in the dot net arena. I have been developing for several years in both C# and, however when I apply for a senior level job and they test me and I get to a second interview and then have a difficult question or two then loose the job.

I am getting jobs that are letting me do some great programming but nothing that is like doing Design Patterns. I am now developing a new application for my brother for free to learn how to develop a 3 tier application like the Patterns in Action reference application in the Design Pattern Framework. Does any one have any other suggestions to me moving to the Senior Level or is it just time and effort?

Thanks & Regards
Allan F. Gagnon
Allan Gagnon, Jun 04, 2010
Reply 1
Here is an interesting post on the subject of what the difference between junior, mid-level, and senior developer:
Robert Blixt, Jul 13, 2010
Thanks for the link. A good overview.
May 09, 2010
Reply 2

The main questions that tend to come up in C# Architect interviews relate to:
1) Event Life Cycles
2) Basic Design Patterns, usually with a focus on data management.
3) Inheritance, polymorphism and encapsulation
4) Interfaces, virtual methods and overrides.
5) Delegates and threads. If its they usually don't ask many questions about threading.
6) Data access and storage.
7) Code Management and Build Processes.
8) Methodologies.  Try to stay neutral on these as they are like religion.
9) OR/Ms. Again, try to stay neutral on these.

There are other areas depending on the type of project they are working on as well, e.g. WPF, Silverlight, MVC.

Aaron Burton, Jul 01, 2010
Reply 3
By your post, it looks like your issue might be answering interview questions, not really technology itself. Scott Hanselman has a really good blog post of stuff that you should be able to answer.

What Great .NET Developers Ought To Know (More .NET Interview Questions)

There are several blog posts across the web that try to answer these questions. I believe that your journey in seeking the answers to this questions will help you learn about these topics, and keep what interviewers want in mind.

The second half of this questions, is that you need to practice answering these questions. I bought myself an inexpensive whiteboard, that I use to practice some of the questions. This has helped in getting me to calm down, and sound more confident.

There is no substitute for knowing your stuff, but I think you are close to getting your first senior position.

You might also try your hand at helping with .NET open source projects. I have created several on CodePlex, and those are a good source of evidence to future employers. I just got a job (about a month ago), exactly because the interviewer and his team were able to download and examine code from the largest of my projects.

- Hector
Hector Sosa, Jun 05, 2010
Stay Inspired!
Join other developers and designers who have already signed up for our mailing list.
Terms     Privacy     Cookies       Do Not Sell       Licensing      
Made with    in Austin, Texas.  - vsn 44.0.0
© Data & Object Factory, LLC.