Did you ever get that feeling that you probably should have looked over a few old notes or books before you walked in? Yeah, I had that feeling. The problem is that the feeling came after the interview. Overall, I would say that I forgot two key things, don’t ask me why it was these two things. This was the first time I was interviewed by a team of people, about six. I wasn’t expecting some of the questions they asked me, but with my background I should have.
In this blog I will go over the two biggest things that I couldn’t remember. By the way, this interview was for a web editor position. Most of the questions felt like they came out of my Senior Software Engineering course, sort of like a final exam.
* Lifecycles. Software engineers use them to efficiently develop applications, sort of like a step by step process. My problem was that I couldn’t remember some of the phases in between, the meat of a particular lifecycle. I decided to talk about the lifecycle known as the waterfall model.
Basically it goes like this:
Interpret Software Requirements - document clients expectations of a product formally after an official meeting/s
Design - determine which type of solution is best for the problem at hand, there are some great design patterns out there which are great, see GoF
Impelmentation - the actual coding
Verification - includes testing individual modules of the product; then all as a whole
Maintenance - includes updating software, adding enhancements, basically you’re keeping things running and if a problem comes up you fix it to get it working up to clients needs
There’s more to this particular lifecycle model, but those are the basics. I completely forgot the design and verification phases, don’t know why. Maybe I was nervous.
* Joins in SQL (Structured Query Language). There are different types of joins, and they’re all used for different things. What you are left with after a join is basically another table that can further be queried. I think I couldn’t get it totally across that I had this comprehension. Joins are used to query against more than one table in a database. You can do this by making a SQL statement with sub statements within it to extract the information you need.
In the end, just remembering things is not always the best way of evaluating ones know how and experience. Now that I remember (get it?), I wasn’t wearing my lucky underwear. Have a good week.
~edit
I just received an ‘anonymous’ comment to this blog, hmm, and the IP is logged. So how anonymous is that? :-) If I am humbling myself, please have the common decency to not believe you are as ‘anonymous’ as you think you are. Thank you.