I'm a Level 1 technician with about a year of experience, and I joined a national managed service provider only three weeks ago. Until recently, another technician with Level 2/3 experience and I handled the clients in our area. After that coworker was let go, I suddenly became the primary technician and de facto systems administrator for all of those clients.
The company has very little documentation, no useful knowledge base or standard procedures, and no obvious escalation path. I'm not aware of any plan to hire another senior technician locally. My experience with backend infrastructure is limited, and I had expected to learn under the person who was dismissed.
Last week, I attempted to update a client's production Windows Server. The next morning, the server was offline and the client's entire business was unable to operate. I asked other technicians for help and tried troubleshooting remotely, but ultimately had to go onsite and physically reboot the Hyper-V host. Fortunately, the production server came back and no data was lost, although the client was understandably upset. The client also had no backup system in place.
I know this experience could help me build valuable infrastructure skills, and I was considering staying for roughly a year. However, I'm worried that I'm not qualified for the responsibilities I've been given, and I'm now anxious about making another serious mistake. How can I protect my mental health, learn as much as possible, and decide whether staying is worth it?
4 Answers
Start looking for another job now rather than waiting until you’ve completed a year. You can still use this role as valuable experience, but there’s a real difference between being given opportunities to grow and being left alone with critical infrastructure and no escalation path. Don’t stay in a situation that is seriously damaging your mental health just to reach an arbitrary time milestone.
Treat the next several months as structured professional development, not as proof that you’re supposed to know everything already. Build your own documentation, study the technologies you encounter, and avoid making risky production changes without a tested backup, a rollback plan, and explicit approval. This may eventually make you capable of the job, but it may also reveal that the employer is simply understaffed and exposing junior employees to unreasonable risk.
Don’t beat yourself up over one incident. Experienced administrators make mistakes too. The important lesson is to identify which changes could interrupt production, schedule them appropriately, confirm that backups and rollback plans exist, and communicate the maintenance window clearly. If the company expects you to manage critical systems without documentation, senior support, or proper safeguards, that is a management failure—not something you can solve through confidence alone.
Document everything you do, including system details, changes, approvals, maintenance windows, incidents, and the lack of backups or procedures. Ask management in writing what your authority and escalation process are, and request compensation that reflects the responsibilities you’re actually carrying. Set boundaries around hours and on-call work so the company doesn’t quietly turn this into constant nights and weekends. At the same time, learn as much as you can about the environments and use that experience to strengthen your resume.
That’s fair. I’ll keep learning here while quietly applying elsewhere instead of assuming I have to endure it for a full year.