I'm a fresh BSCS graduate and recently started my first job as a Computer Technician. I expected the work to focus mainly on PC troubleshooting, hardware and software support, and basic networking, but the role is much broader and mostly field-based. I work with CCTV and NVR systems, UTP cabling and crimping, biometrics, alarms, metal detectors, solar-related equipment, PC assembly, and site installations.
I don't mind learning these areas, and I can see how cabling, physical infrastructure, and troubleshooting could be useful. However, my long-term plan is to move from IT support into networking and eventually network or infrastructure engineering. Outside work, I'm studying for the CCNA and practicing with Packet Tracer and Windows Server labs.
Should I stay for several months or a year to build experience, or start applying now for IT support, NOC, network technician, or junior sysadmin positions? The pay is currently around ₱455 per day, and I'm concerned that the job may remain mostly installation-focused rather than giving me enough networking or configuration experience.
My contract also requires 30 days' written notice. If I find a better role that wants someone within one or two weeks, how is that usually handled? I'd appreciate advice from anyone who started in an all-around field technician role and later moved into IT or networking.
3 Answers
You can apply immediately while continuing in your current role. A few months of experience is useful, but it isn’t worth rejecting a good NOC or junior network position just to reach an arbitrary one-year mark. Compare the actual responsibilities, learning opportunities, pay, and career path of each offer.
Be honest about your notice period during interviews. A 30-day notice is common enough that many employers will plan around it. If a company truly needs someone sooner, ask whether they can wait, negotiate a shorter release with your employer, or use accrued leave if that is allowed. Don’t simply disappear or violate the agreement without understanding the consequences.
The job is more relevant than it may seem. Structured cabling teaches you about the physical layer, while CCTV, NVRs, access control, and site installations expose you to real network-performance and infrastructure problems. You’ll also build troubleshooting, customer-facing, and project skills that are useful in infrastructure work.
I’d stay long enough to learn as much as possible, but there’s no reason you have to stop looking. Keep studying, document the systems you work on, and try to get involved with configuration and network-related tasks rather than only installation.
There’s value in staying for a while because real-world experience takes time, especially when you’re learning how users, facilities, vendors, and business requirements affect technical decisions. However, staying for three or four years is not mandatory if the role has no path toward the work you want.
Give yourself a clear review point, such as six to twelve months. By then, assess whether you’ve gained meaningful troubleshooting and networking experience, whether the company can involve you in network upgrades or maintenance, and whether the compensation is reasonable. If not, move toward a role that better matches your IT and networking goals.
A six-to-twelve-month review point sounds practical. I’ll keep building my CCNA and lab experience while seeing whether my current employer can give me more networking-related responsibilities.
That makes sense. I’m grateful for the practical experience, but I’ll try to get more exposure to configuration and networking. My main concern is staying too long if the role remains almost entirely installation work.