I was offered $30 an hour, compared with the $22 I currently make, to be the only in-house IT person supporting six car dealerships. During the interview, the GM and maintenance director only identified three immediate responsibilities: replacing outdated cameras and fixing their software issues, setting up a phone call tree, and upgrading alarm panels. They said I would be my own boss and could ask the maintenance director for help when needed.
The dealerships already use an outside provider for help-desk tickets and field issues, which makes me wonder what my ongoing responsibilities would actually be. The camera and phone work could turn into maintenance, but the alarm work is currently handled by the maintenance team. I am concerned that, once these projects are finished, management may wonder why they still need the position.
The pay increase would make a big difference for my family, but I also want a role that builds my IT career and offers some long-term stability. Does this sound like a worthwhile opportunity, or more like a temporary project and low-voltage maintenance position? What questions should I ask before accepting?
4 Answers
If you enjoy your current job and do not urgently need the extra money, be cautious. A higher hourly rate is not enough if the new position has no defined scope, no growth path, and unclear expectations across six sites. On the other hand, if the schedule is light and the company supports you, it could give you time to learn the dealership's software and business processes while earning more.
Ask whether they expect this to become an IT manager or internal technology role. If they are interested in gradually reducing dependence on the outside provider, get that expectation documented rather than relying on vague promises.
This may be an opportunity created because the company is tired of paying the outside provider for every project. Take a close look at what the provider currently handles and identify work you could bring in-house. Improving phone availability, reducing downtime, documenting systems, and supporting dealership software could give you plenty of value beyond the initial assignments.
Before accepting, make sure management is willing to discuss a longer-term plan. You do not want to discover that this is simply a cheaper way to complete a few installations. If you take it, keep records of improvements, savings, response times, and completed projects so you can demonstrate your value or use the experience to move into a better role later.
I would ask them directly what the job becomes after those three projects are complete. Find out whether you will be expected to manage workstations, networks, users, cybersecurity, business applications, vendors, and day-to-day technology problems, or whether you are simply being hired to coordinate installations.
Also clarify whether you are doing the physical work yourself or managing contractors, what the project budgets are, whether travel between all six locations is required, and whether mileage, fuel, or a company vehicle is provided. If the position is mostly project work, negotiate a title that reflects project or technology management rather than taking a vague technician role.
The raise is significant, but the role sounds closer to an onsite technology and facilities technician than a conventional systems administrator. That is not automatically bad, especially if the workload is manageable, but it may not provide the career growth you want.
I would only accept after getting clear answers about reporting structure, travel, on-call expectations, benefits, job security, performance reviews, and what happens when the listed projects are finished. If they cannot explain your ongoing responsibilities, assume the position may last only as long as the projects do. You can still take it for the money if the risk is acceptable, but keep looking for other opportunities and do not stop building your broader IT skills.
It is also possible they want someone physically present while the outside provider continues handling help desk work. That can still be useful, but the responsibilities and boundaries need to be written down so you are not treated as the person responsible for every technical problem in six locations.