Am I moving too fast by being the only IT person this early?

November 18, 2026 5 answers
Asked by 7w~mosaicfunnel_318

I have about a year and eight months of IT experience and now handle infrastructure, networking, security, cloud, applications, and support on my own. I have a lot of freedom, but no senior IT person to learn from or check my decisions.

I want to move toward cloud architecture. Is this a good opportunity to grow, or should I look for a larger team with more guidance?

Answers

_d92!plaxeno.7

It's a great learning opportunity, but your learning opportunity and the company's risk are two different things. Being trusted with everything does not mean one person can safely cover every specialty.

Ask for a budget for a part-time consultant or experienced contractor to review bigger decisions. You can still own the work, but you'll have someone to spot assumptions and gaps before a change affects the whole business. Document the environment and make sure management understands where you need outside help.

_c94~ferricrane.8:

A review before a major infrastructure or security change could also help you understand the reasoning behind alternatives, not just whether your plan works.

Reply to this answer
q.673~copperladle

Don't assume a bigger department automatically means mentoring. You might get excellent guidance, or you might find that senior people are too busy to teach and your access is more limited.

If you interview elsewhere, ask how technical reviews work, who would help you develop, and what you'd actually get to own. Compare the learning opportunities, not just the size of the team. Self-learning will still be part of the job either way.

Reply to this answer
8p+grommetlark_627

The part I'd pay attention to is how management handles mistakes. There's a big difference between giving you room to learn and expecting one relatively new person to know everything.

Have a frank conversation about priorities, staffing and what happens when something goes wrong. If the responsibility has grown a lot, it's also fair to ask whether your title and pay should reflect it. A supportive answer is a good sign. Blaming you for every gap in a one-person operation is not.

Reply to this answer
9f+canvasgrommet_721

Use the freedom while you've got it. Working across support, networks, cloud and applications can give you a useful view of how systems fit together, which is relevant to architecture.

Keep notes on the problems you solve, the choices you make and why. For cloud specifically, make time to study the underlying networking, security and infrastructure concepts rather than only fixing whatever breaks next. That gives you both a stronger foundation and concrete work to discuss when you look for your next role.

_e46~brindlelever.2:

That record can also expose quick fixes that need a more durable solution later.

Reply to this answer
_p48+fablewicket.6

Self-learning can get you far, but the blind spots are tricky. Documentation and AI tools can suggest an answer without knowing all the dependencies or risks in your environment.

Look for experienced people outside your company who can talk through your reasoning. You don't need to leave immediately to get another perspective, though a future role with strong technical review could fill a gap that solo work doesn't.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions