Bilingual (Spanish) Technical Support Specialist | Networking Solutions
- .
- Requirements: maybe combine qualifications and expectations? The spec says separate sections: Requirements, Qualifications, Skills. We need to decide what goes where.
We have qualifications: CCNA, experience with equipment, understanding of networking fundamentals, VPN, cellular, troubleshooting tools, OSI model.
We have expectations: language fluency, communication, customer-focused, general understanding, willingness to learn, problem solving, computer skills, interest, experience preferred.
We could treat "Requirements" as mandatory items (Fluent English and Spanish required, ability to communicate, etc.) and "Qualifications" as preferred (CCNA, experience). "Skills" could be technical skills (networking fundamentals, tools, etc.). But we need to avoid duplication.
Better: Use sections as they appear: "What We Expect Of You" could be Skills. "Good understanding ..." could be Requirements or Qualifications. Let's map:
- About the role: intro.
- Responsibilities: duties list.
- Requirements: mandatory expectations (Fluent English and Spanish required, ability to communicate, customer-focused, willingness to learn, problem solving, computer skills, interest, experience preferred? Actually experience preferred is not mandatory). Might be better to put mandatory items: Fluent English and Spanish required; Ability to communicate clearly; Customer-focused mindset; Willingness to quickly learn technical concepts; Strong problem-solving skills; Good computer skills; Interest in technology; Experience in customer service... preferred (maybe not required). We'll keep as required.
- Qualifications: CCNA or equivalent, experience with network equipment (advantage). Also maybe "General understanding of computer networks, internet connectivity, routers, switches, gateways, modems, or similar technology." That's more like a requirement but could be qualification.
- Skills: technical networking fundamentals, VPN, cellular, troubleshooting tools, OSI model.
- Benefits: list benefits.
- Pay: not mentioned; we should not create Pay section.
- Schedule: we have Working hours: Standard Working hours; Summer hours (short days on Fridays) for June and July months. Also shift-based role; exact hours to be confirmed. That's schedule info. So we can include Schedule section.
We must not include placeholder text like "not specified". We have actual schedule info.
Now produce HTML.
We need
for each section heading. Use
- for lists. Use
for prose. We must not repeat job title as heading. No markdown. Let's craft. Section About the role: combine intro paragraphs. Paragraph: "We are looking for a Technical Support Specialist to join our technical support team in Irving, Texas. In this role, you will support business customers using Teltonika Networks products, provide first-line technical assistance, and help resolve product-related questions through clear and professional communication. Teltonika Networks develops and manufactures industrial and enterprise connectivity equipment, including routers, switches, gateways, and modems. Our networking devices are used by business customers in complex areas such as Industry 4.0, Smart City, IoT, and Green Energy solutions." That's one
. Responsibilities: list items. We need to split the responsibilities sentences into bullet points. Responsibilities list: - Provide technical support to business customers through multiple channels, including phone, helpdesk, email, and other communication platforms, depending on customer demand and support volume. - Handle both real-time phone interactions and written support requests, responding to helpdesk tickets within the required response time and providing timely assistance with straightforward technical issues. - Assist customers with product-related questions, troubleshooting, configuration, integration, and basic network-related issues. - Advise customers and sales representatives on the use and integration of Teltonika Networks products, helping them find practical solutions to their technical needs. - Support international customers across different regions and time zones as part of a shift-based support model, adapting between communication channels according to the current support workload. - Escalate complex or unresolved technical cases to Networking and IoT Engineers, providing clear technical context, troubleshooting steps, and all relevant information required for further investigation. - Maintain clear and professional communication with customers and internal technical teams throughout the support and escalation process. Make
- for each. Requirements: mandatory expectations. List: - Fluent English and Spanish are required. - Ability to communicate clearly with business customers through phone, email, ticketing systems, online meetings, forums, and other support channels. - Customer-focused mindset with patience, active listening, and the ability to explain technical information in a clear and practical way. - Willingness to quickly learn technical concepts related to industrial networking equipment. - Strong problem-solving skills and the ability to analyze issues step by step. - Good computer skills and experience using common office tools such as Excel, Word, and web-based systems. - Interest in technology, networking, IoT, and innovation. - Experience in customer service, technical support, IT support, B2B support, or a similar customer-facing role is preferred. Note: "preferred" maybe not required but still expectation. We'll include. Qualifications: maybe CCNA or equivalent, experience with network equipment. List: - CCNA certification or equivalent networking knowledge would be considered an advantage. - Experience with network equipment, routers, switches, gateways, modems, or similar networking products would be considered an advantage. Also maybe "General understanding of computer networks, internet connectivity, routers, switches, gateways, modems, or similar technology." Could be qualification but we already have similar in requirements. Might duplicate. We'll keep as qualification. Skills: technical networking fundamentals etc. List: - Good understanding of computer networking fundamentals, including TCP/IP, IPv4/IPv6, subnetting, routing, NAT, DHCP, DNS, VLANs, and LAN/WAN concepts. - Basic understanding of VPN technologies, such as IPsec, OpenVPN, and WireGuard, as well as firewall and network security concepts. - Basic understanding of cellular networking technologies, including 4G/LTE, 5G, APN configuration, SIM connectivity, and mobile network troubleshooting. - Ability to troubleshoot network connectivity issues using common tools and methods, such as ping, traceroute, DNS troubleshooting, and packet analysis. - Understanding of the OSI model and basic network troubleshooting methodologies. Benefits: list. - Company funded health insurance - 401k - 3 weeks of Paid Vacation - 6 Sick days + day off on your Birthday Also maybe "Training: onboarding on Teltonika‘s internal systems, Sales process, product related topics" could be part of benefits or separate? Could be under Benefits? It's training. Not a benefit per se but could be included. However spec only includes Benefits section; we can include training as part of Benefits? Might be okay to include as bullet under Benefits. But spec says only include sections when posting has real content. Training is mentioned; we could add a separate section? Not in allowed headings. Could fold into Benefits or maybe under About the role? Probably better to add as a bullet under Benefits: "Training: onboarding on Teltonika’s internal systems, Sales process, product related topics". We'll include. Also "Work Environment: Multicultural and diverse environment which highly values knowledge and exchange of ideas, supportive and positive attitude in the team" could be part of Benefits or maybe a separate section but not allowed. Could add to Benefits as bullet
- for lists. Use