
Originally Posted by
Hel OWeen
Had the second part of a job interview on Tuesday, which was a couple of hours trial work. They gave me a coding exercise and watched me (video conference) solve it. Though they're seeking a C# developer, they would have let me done it in VB.NET, which I'm very familiar with. I declined that, stating that taught myself C# when being unemployed, therefore I'm still quite new to it and would like to practice it whenever I can.
This is the 1st time I've ever done some kind of test in a job interview, so I have no comparison. Dunno how it went. I'm not good at pointing out what I'm good at/have done well. I'm better at spotting the bad stuff. The exercises wasn't hard and straight forward (read certain nodes from a XML file, write them back to a MarkDown file in a certain way/order). Half way through I recognized I messed up the supposed order, but that was easy to fix. Later on I blacked out on a good way to parse a string (parts of it were needed for the MD file). I knew I've done that before and while I typically also remember in which project*) I've done it, that escaped me this time around. I'm old enough to not be afraid of telling "I don't know (it/that)", so I pointed out where I'm stuck at and with a hint from them, I came up with the solution.
Let's wait and see what they think of it.
*) Google, SO, looking in your own code etc. were allowed
Bookmarks