- get the job done
- willing to adapt to your development style
- basically understand the concept of development
Now, most of the tech jobs are actually filling a space in a cubicle, cranking away at malformed, ugly code that's not even in the language you know because it's in a framework that uses a non-intuitive syntax, and it's cleaned up by testing apps and pre-processor apps so the coder wouldn't know if it worked or not, the way they wrote it.
Ironically though, when they interview you, they ask a slew of irrelevant questions, most of which actually don't have an answer, or perhaps have answers they don't even know.
Q: List all the ways to restart SAMBA from the command line
A: Depends on the distribution, probably at least 20 different, negating the "all the ways"
Q: A server has a CPU at 98% with only two running apps. What do you do?
A: Check the logs and turn off the apps.
And the worst setup is having you do a test exercise. There is almost no way to get this one right. Watch the video below to see what I mean...
