Ready for a junior support role

Junior Desktop Support Specialist

Technical support with a human signal.

I turn “it stopped working” into calm, clear next steps. I’m building a career around patient troubleshooting, dependable follow-through, and making technology feel less intimidating.

01User-first mindset
02Hands-on home lab
03Always documenting
support_session.log LIVE
INC-0027NORMAL

user@desk:~$ My laptop can’t connect to Wi-Fi.

  1. Listen firstConfirm impact and recent changes
  2. Isolate the causeAdapter, network, credentials, or DNS
  3. Apply & verifyRestore service and test with the user
  4. 4Document clearlyLeave the next technician a useful trail
Resolution confidence92%
Windows 10/11Microsoft 365Hardware SupportActive Directory FundamentalsNetworking BasicsRemote Support

My growing toolkit

Strong foundations.
Curious by default.

I’m early in my IT career and serious about the fundamentals—the everyday skills that keep people productive and earn their trust.

BUILDING

Identity & access

Practicing the account lifecycle basics that help users get secure access without unnecessary friction.

  • Active Directory basics
  • Password resets
  • Groups & permissions
PRACTICED

Hardware support

Comfortable identifying components, checking connections, replacing common parts, and narrowing down hardware faults.

  • PC components
  • Workstation setup
  • Preventive care
FOUNDATIONAL

Networking

Working knowledge of the path between a device and its destination—and the tools to find where that path breaks.

  • TCP/IP & DNS
  • Wi-Fi troubleshooting
  • ipconfig, ping & tracert
LEARNING

Microsoft 365

Supporting the productivity tools people rely on, from sign-in and Outlook basics to Teams and OneDrive sync issues.

  • Outlook & Teams
  • OneDrive basics
  • Account support

How I work the problem

No mystery fixes.
Just a clear process.

Great junior support isn’t about knowing every answer. It’s about asking useful questions, testing carefully, communicating honestly, and learning from every ticket.

Patient with peopleCareful with systemsHungry to learn
01

Understand

Listen without assumptions. Translate symptoms into a clear, shared problem statement.

02

Investigate

Start simple, gather evidence, and change one thing at a time so the result means something.

03

Resolve

Fix the root cause when possible, test the outcome, and confirm the user is truly back to work.

04

Improve

Document the path, share what worked, and add the lesson to my growing support playbook.

Currently in the lab

I learn by building the thing.

This portfolio runs on infrastructure I configured myself: Debian 13, Apache, MariaDB, PHP, Git-based deployments, webhooks, and automated TLS.

Debian 13 onlineApache servingMariaDB connectedGit + Gogs deployedLet's Encrypt securePHP 8.4 running

Start a conversation

Got an opportunity?
Open a ticket.

Hiring for a junior support role, building an IT team, or just want to compare troubleshooting notes? Send a message—no hold music required.

NEW SUPPORT REQUEST
TKT-0000