Junior asp.NET Developer role.........

doddsy105

doddsy105

doddsy105

Associate
Joined
4 Jun 2009
Posts
353
Location
UK
I have an interview for a asp.NET junior developer role Tuesday 21st, in the email they said there will be a few basic tests on being practical and an informal chat, what kind of tests do they mean? they said the interview will take 1 - 2 hours. What kind of things should i research and practice for this sort of interview? thanks :)
 
Target practice with a Nerf gun. :)

Most likely they'll ask you to solve a problem and write your algorithm in pseudocode on a whiteboard, or possibly the same but in a language of your choice. Or if it's hands on they may sit you infront of a computer and ask you to bash out a simple ASP.NET website to do a trivial task, perhaps putting some data in a DB, or rendering some data in a table.

They won't be looking for perfection (you have a compiler and intellisense for that), they'll be looking at how you approach problems and try to figure out if you'll actually manage to get stuff done if they give you the job.

Good luck. :)
 
Last edited:
In a recent interview I had a programming test and was given a computer with an IDE and had to solve 3 programming questions. The first was to write a function to reverse the letters of each word in a sentence (not the sentence itself). The second was to write an implementation of an "overlap" function on an existing "Rectangle" class to determine if two rectangles shared at least one common point. For the third I was given a sample log file and asked to write a parser to transform it into an object graph.

Although it was timed, there was no set limit an they were looking for good programming style rather than speed, they also expected to see some unit tests for the first two problems to prove that the code worked and that you have some idea about testing.

This was for Java but it could have been any language. It's just the make sure the stuff on your CV isn't a load of rubbish and that you can actually tackle basic programming problems.
 
sloth said:
Target practice with a Nerf gun. :)

Most likely they'll ask you to solve a problem and write your algorithm in pseudocode on a whiteboard, or possibly the same but in a language of your choice. Or if it's hands on they may sit you infront of a computer and ask you to bash out a simple ASP.NET website to do a trivial task, perhaps putting some data in a DB, or rendering some data in a table.

They won't be looking for perfection (you have a compiler and intellisense for that), they'll be looking at how you approach problems and try to figure out if you'll actually manage to get stuff done if they give you the job.

Good luck. :)
Click to expand...

This pretty much, you might get a couple of questions asking you to do something like list as many error codes as you can etc. You might get some brain teasers and riddles thrown in to see if you can think outside the box.

One thing to note. If you find it hard, don't be put off or worried about it. It's probably targeted at people with more experience.

My work use the same test for industrial placements as senior developers I believe. :o
 
Last edited:
One test we do is give sample code and get them to tell us what it does and how it could be better.

I'm a senior dev now, but I totally flunked my junior test - so it's not necessarily the end of the world - I made up for it by explaining my thought process, proving although I wasn't very experienced I was smart enough to work with.
 
RobH said:
In a recent interview I had a programming test and was given a computer with an IDE and had to solve 3 programming questions. The first was to write a function to reverse the letters of each word in a sentence (not the sentence itself). The second was to write an implementation of an "overlap" function on an existing "Rectangle" class to determine if two rectangles shared at least one common point. For the third I was given a sample log file and asked to write a parser to transform it into an object graph.

Although it was timed, there was no set limit an they were looking for good programming style rather than speed, they also expected to see some unit tests for the first two problems to prove that the code worked and that you have some idea about testing.

This was for Java but it could have been any language. It's just the make sure the stuff on your CV isn't a load of rubbish and that you can actually tackle basic programming problems.
Click to expand...

That sounds horrible! Was that for a fairly junior role?
 
ringo747 said:
That sounds horrible! Was that for a fairly junior role?
Click to expand...

No, it was for a more experienced role, although I imagine they will use the same test for the junior roll but have lower expectations. If you have Java experience and know a bit about the standard libraries then it isn't that bad, there are many ways to approach each question so there is no one right answer.

For example, I just used the inbuilt java.awt.Rectangle class which has a ".contains(Rectange r)" method to check if two rectangles share at least one point. Some might class that as cheating as I didn't actually write code to check all the boundaries and such but they see it as using what you have available, don't re-invent the wheel if you don't have to.
 
I have done a few years of .NET stuff and I made a complete hash of the last interview I did. I don't write code all day every day and so I'm probably classed as a part timer. In my case anything I don't know I always just google it to find out what i need to know. I never quite understood why in some interviews you get asked really daft questions that obviously everyone would google in the real world anyway.

Unless you eat, sleep and breathe code then you won't know everything off your head.
 
You must log in or register to reply here.
Back
Top Bottom