>> My name is Brian Nelson, and I'm a junior network engineer.
I work for a nonprofit organization.
And my responsibilities are primarily not only to support the network engineer in any
of his current job roles or projects, but to, you know, begin to handle my own projects
and own systems that I'll maintain by myself.
It can be anything from creating user accounts to new users, creating email addresses
for the users, new mailboxes for a system, to building out servers in our virtual environment,
or even just doing basic day-to-day maintenance on any of our current systems
and platforms in our organization.
Cybersecurity, because it's such a broad field and there's so many different facets of it,
I more or less associate this -- my cybersecurity work --
with being able to secure the file systems and the servers that I work on.
Again, being a network engineer, I'm also responsible
for maintaining our network infrastructure.
So that would entail being knowledgeable --
excuse me, knowledgeable regarding our firewalls; our switches, who can access them,
how they access them; and permissions on the file shares as well.
An average project can take anywhere from one week to two weeks.
But an average day for me would pretty much entail I wake
up in the morning, I check my email.
I'm on my way to work, I'm checking email.
I get to work and it's a matter of, you know, picking up from where I left off
with a project that, you know, I didn't finish or a step that I didn't finish the day before
or maintaining emails and --
I'm sorry, responding to email from, you know, regular users.
I'm still -- that's also a part of my responsibilities.
You know, general user tickets.
You know, we have a PC configuration support specialist there.
But, you know, every once in a while a ticket or an issue will get escalated to me or, you know,
something that falls under my purview that I need to respond to.
So I'll handle that as well.