Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:00,260 --> 00:00:03,105
When you're interviewing
for a technical position,
2
00:00:03,105 --> 00:00:05,130
you'll likely have one or
more interviews where you'll
3
00:00:05,130 --> 00:00:06,660
specifically need to demonstrate
4
00:00:06,660 --> 00:00:08,265
your technical skills
and knowledge.
5
00:00:08,265 --> 00:00:09,630
These interviews may
take the form of
6
00:00:09,630 --> 00:00:11,610
technical troubleshooting
scenarios or
7
00:00:11,610 --> 00:00:14,070
explanations of technical
concepts and subjects.
8
00:00:14,070 --> 00:00:15,810
As we've said, you want to have
9
00:00:15,810 --> 00:00:18,450
a solid foundation for all
the fundamental concepts.
10
00:00:18,450 --> 00:00:19,830
A good interviewer will push
11
00:00:19,830 --> 00:00:21,275
you to the limits
of your knowledge.
12
00:00:21,275 --> 00:00:22,590
This means it's very likely
13
00:00:22,590 --> 00:00:23,850
that during an
interview you'll reach
14
00:00:23,850 --> 00:00:25,440
a point where you're
not sure you know
15
00:00:25,440 --> 00:00:27,720
the right answer,
this is expected.
16
00:00:27,720 --> 00:00:29,970
But you shouldn't just
say, "I don't know."
17
00:00:29,970 --> 00:00:31,500
If you were supporting a user,
18
00:00:31,500 --> 00:00:33,060
you wouldn't say it then either.
19
00:00:33,060 --> 00:00:34,540
It's okay to admit
you're not sure,
20
00:00:34,540 --> 00:00:35,780
but you should then explain
21
00:00:35,780 --> 00:00:37,675
what you would do
to find the answer.
22
00:00:37,675 --> 00:00:39,665
As an IT support specialist,
23
00:00:39,665 --> 00:00:41,060
you should expect to often face
24
00:00:41,060 --> 00:00:42,530
new and unfamiliar problems.
25
00:00:42,530 --> 00:00:44,420
Having a good problem
solving strategy is
26
00:00:44,420 --> 00:00:46,655
more important than
knowing all the answers.
27
00:00:46,655 --> 00:00:49,339
If the question you're
answering is big and complex,
28
00:00:49,339 --> 00:00:50,630
outline how you'd break down
29
00:00:50,630 --> 00:00:51,950
the work needed to
solve the problem
30
00:00:51,950 --> 00:00:53,795
before going into
the exact details
31
00:00:53,795 --> 00:00:54,950
of what needs to be done.
32
00:00:54,950 --> 00:00:56,120
If you're thinking about what
33
00:00:56,120 --> 00:00:57,450
the best solution could be,
34
00:00:57,450 --> 00:00:58,670
share your train of thought with
35
00:00:58,670 --> 00:01:00,895
your interviewer so
they can follow along.
36
00:01:00,895 --> 00:01:02,600
Thinking aloud not only helps
37
00:01:02,600 --> 00:01:04,240
the interviewer see
your thought process,
38
00:01:04,240 --> 00:01:06,350
but it also helps you
work through the problem.
39
00:01:06,350 --> 00:01:07,970
For example, if you get stuck
40
00:01:07,970 --> 00:01:09,755
with a technical
troubleshooting scenario,
41
00:01:09,755 --> 00:01:11,780
you can try and recap
what information you've
42
00:01:11,780 --> 00:01:13,820
gathered and state potential
causes that can be
43
00:01:13,820 --> 00:01:16,100
ruled out with certainty
and then try to figure out
44
00:01:16,100 --> 00:01:18,480
what info is still missing
to rule out other causes.
45
00:01:18,480 --> 00:01:20,675
When you mention concepts
or technologies,
46
00:01:20,675 --> 00:01:22,280
you should be ready
to explain them and
47
00:01:22,280 --> 00:01:25,105
articulate why you might
choose one thing over another.
48
00:01:25,105 --> 00:01:27,080
For instance, if
you're working through
49
00:01:27,080 --> 00:01:29,210
a networking problem
and say something like,
50
00:01:29,210 --> 00:01:31,460
the problem might be related
to the DNS settings.
51
00:01:31,460 --> 00:01:33,515
Be ready to explain what DNS is,
52
00:01:33,515 --> 00:01:34,985
and why it relates to the issue.
53
00:01:34,985 --> 00:01:37,445
You should also clarify
the questions constraints.
54
00:01:37,445 --> 00:01:40,670
Don't assume anything, it's
okay and even expected to ask
55
00:01:40,670 --> 00:01:42,140
the interviewer follow
up questions to
56
00:01:42,140 --> 00:01:44,345
ensure that the problem
is correctly framed.
57
00:01:44,345 --> 00:01:46,640
Always use the data
and evidence you have
58
00:01:46,640 --> 00:01:48,820
from the interviewer to
inform your next steps.
59
00:01:48,820 --> 00:01:51,110
For example, if you need
to solve a problem about
60
00:01:51,110 --> 00:01:53,675
a user being unable to connect
to an internal system,
61
00:01:53,675 --> 00:01:55,430
you should ask follow
up questions like,
62
00:01:55,430 --> 00:01:57,425
what operating system
the user is using,
63
00:01:57,425 --> 00:01:58,310
how their computer is
64
00:01:58,310 --> 00:01:59,690
supposed to connect
to the network,
65
00:01:59,690 --> 00:02:01,595
what error messages
they are getting,
66
00:02:01,595 --> 00:02:03,565
whether other users
are affected?
67
00:02:03,565 --> 00:02:06,545
Your goal is to narrow the
scope to find the root cause.
68
00:02:06,545 --> 00:02:08,420
If the question is very complex,
69
00:02:08,420 --> 00:02:09,590
it might become difficult to
70
00:02:09,590 --> 00:02:10,970
follow or explain the solution.
71
00:02:10,970 --> 00:02:12,860
In this case, it's
useful to take
72
00:02:12,860 --> 00:02:15,280
notes and use diagrams to
illustrate the problem.
73
00:02:15,280 --> 00:02:17,330
You can use this process
when it makes sense.
74
00:02:17,330 --> 00:02:18,500
It doesn't mean you need to
75
00:02:18,500 --> 00:02:20,285
write everything down
during an interview.
76
00:02:20,285 --> 00:02:22,730
Sometimes the answer is straight
forward and you can just
77
00:02:22,730 --> 00:02:25,860
go ahead and explain it
without writing anything down.
6060
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.