LVT
Technical Support Engineer II
About this role
LVT seeks a Technical Support Engineer II to troubleshoot and resolve technical issues on deployed AI-driven site intelligence units. You'll independently diagnose and fix problems across cellular, network, and Linux systems while collaborating with internal teams and customers to maintain system uptime.
What you'll do
- Independently troubleshoot and resolve routine to moderately complex incidents on deployed units
- Diagnose connectivity and performance issues using log analysis and diagnostic tools
- Make configuration changes to optimize system and network performance
- Document troubleshooting steps and resolutions in detail within ServiceNow
- Communicate with internal teams and external customers via tickets, chat, or phone
- Contribute to continuous improvement by providing input on procedures and documentation
What they're looking for
- Network systems administration
- Linux systems administration
- Cellular network troubleshooting
- LAN configuration and diagnostics
- Log analysis and system diagnostics
- Technical documentation and writing
- Incident management and prioritization
- ServiceNow ticket management
Benefits
- Comprehensive health, dental, and vision coverage
- 401(k) retirement plan with up to 4% company match
- Flexible paid time off
- Support for health, family, and financial wellness
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
LVT
LVT builds an AI-driven IoT platform that connects physical and digital worlds through intelligent site technology. The company is hiring Fullstack Software Engineers to develop responsive frontend and scalable backend features using TypeScript, as well as Application Security Engineers to strengthen security practices across their platform.
View all jobs at LVTLikely interview questions
- Describe your experience troubleshooting Linux-based systems and the tools you typically use for diagnostics.
- Tell us about a time you resolved a complex network connectivity issue; how did you approach the problem?