From the course: Tech Career Skills: Interviewing Developers
Unlock the full course today
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
Team work and individual work
From the course: Tech Career Skills: Interviewing Developers
Team work and individual work
- When you ask about their previous work, candidates want to impress you with their work and experience. Regrettably, sometimes they shade their answers to make their work look better than it really is. A typical answer in that vein would be... - We designed and wrote a completely new microservices architecture for our data layer. - Notice the emphasis on we. Now that answer might be okay. Perhaps the candidate worked on that data layer with one or two other people. But they might be trying to exaggerate their own expertise by taking credit for work they were not involved in very closely. I begin to suspect that if they are vague about exactly what they did in that area, or the vocal tone doesn't have much confidence in it. If I sense that potential problem, I'll ask, "Did you do that or did the team to that?" If they become defensive or even more vague in answer to that question, then it's a red flag for me. I feel…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Contents
-
-
-
-
-
(Locked)
Deeper questions2m 21s
-
(Locked)
What's your philosophy of user interface design?2m 32s
-
(Locked)
Comparing platforms2m 17s
-
(Locked)
Pros and cons of agile methodologies2m 2s
-
(Locked)
How do you become familiar with new technologies?1m 36s
-
(Locked)
Questions about n-tier architectures2m 5s
-
(Locked)
No-win situations2m 59s
-
(Locked)
Team work and individual work1m 14s
-
(Locked)
User experience1m 2s
-
(Locked)
-
-
-