StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2494936
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-03-22T18:58:34.033
FavoriteCount
0
LastActivityDate
2010-03-22T18:58:34.033
LastEditDate
LastEditorUserId
0
OwnerUserId
82592
ParentId
2489809
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
When hiring for junior positions, we generally avoid making requirements for some specific knowledge (for example, although we are working in Ruby, we weren't expecting the candidate to know it), we are relying for other qualities, such as common IT knowledge, problem solving capabilities and "nerdiness". So, the first part of interview is usually greatly improvised, talking about previous experience of the candidate: for example we talk about candidate's college projects, trying to find out how devoted he was and how deep he understands the technology beneath. We talk about the platform it was built on, with "real" questions thrown in; if he worked in Java, we talk about OOP, difference between interfaces and classes, trying to get opinions as well ("why did they added the concept of interface in Java") etc. Sole existence of an opinion on a subject is usually a good sign. Then, ask the candidate about some specific problem he had while doing the project, how did he handle it etc. You can learn a lot about the candidate by this kind of "techie smalltalk". In the second part of the interview, we expect the candidate to solve some small problem from the field we are working in. We leave up to him to choose a tool (usually any mainstream scripting language, or bash or anything he's familiar with). Any simple programming task, parsing a simple CSV file and counting distinct fields in it, for example. We watch him working from time to time, offer help etc. In other words, trying to simulate real working conditions as much as possible. So, sorry, this answer is not really a "recipe" you were asking for, but may be useful.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORuby on Rails, XML, AJAX, Perl Good Interview Questions
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMladen Jablanović
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.