A job description written for offshore technical support hiring must specify support tier, required tooling, escalation ownership, time zone requirement, and whether the role is voice, ticket-only, or hybrid. Generic JD templates written for US in-office hiring miss these specifics and produce the wrong candidates for offshore placements.
A job description that says “Technical Support Specialist, 3+ years experience, Tier 1-2 support, fast-paced environment” is essentially a placeholder. It describes a category, not a job. Offshore staffing firms use the JD as a primary screening instrument. When the JD is vague, the applicant pool is wide and noisy. When the JD is precise, the pool is narrow and qualified. The templates below are built for offshore hiring and include the specifics that matter: support tier, tooling, escalation scope, shift requirements, and communication expectations.
These templates can be used directly or adapted for your specific environment. Customization guidance follows each template. For the full screening methodology, see the technical support staffing overview and the step-by-step hiring guide.
Why Standard JD Templates Fail for Offshore Hiring
Standard US-market JD templates are written assuming the hiring manager can clarify vague requirements in a local interview. Offshore hiring does not have that flexibility. The offshore staffing firm sources against the written brief. Candidates self-select based on the written JD. Screening happens against the written criteria. Every important requirement needs to be in writing before the search starts.
The most common gaps in standard JD templates for technical support roles:
- No tier specification. “Technical support” can mean Tier 1 IT helpdesk, Tier 2 SaaS escalation engineer, or Tier 3 infrastructure specialist. All three require different candidates.
- No tool specificity. “Experience with ITSM platforms” is not the same as “ServiceNow ITSM experience with incident management module.” The former invites padding. The latter tests real knowledge.
- No escalation ownership defined. What does the role own vs. escalate? Candidates need this to know if they are qualified and to prepare for the role appropriately.
- No time zone requirement stated. This is legally and operationally critical for offshore placements. It must be explicit.
- No channel mix specified. Voice, chat, email, or ticket queue only? Each requires a different candidate profile.
The templates below address all five gaps.
Tier 1 Technical Support Specialist JD Template
Use this template for first-contact IT helpdesk roles handling documented, repeatable issues from a runbook or knowledge base. Adapt the tooling section to match your specific platform stack.
Role Overview
We are hiring a remote Tier 1 Technical Support Specialist based in [India / Philippines] to handle first-contact IT support for our US-based customers and internal users. This role operates [US Eastern / US Pacific / other] hours on a [day shift / evening shift] schedule. You will work from a structured knowledge base, resolve 70-80% of tickets to first-contact closure, and escalate unresolved issues with thorough documentation to the Tier 2 team.
Responsibilities
- Handle incoming support tickets via [Zendesk / ServiceNow / Jira Service Management / ConnectWise] for software, hardware, and connectivity issues
- Diagnose and resolve Tier 1 issues following documented runbooks: password resets, VPN access, software installation, printer configuration, and account provisioning
- Document all interactions, resolutions, and escalation steps clearly and accurately in the ticketing system
- Escalate unresolved or out-of-scope tickets to Tier 2 with complete issue history and attempted resolution steps
- Maintain first-contact resolution rate of 70%+ and meet SLA response targets of [X minutes] for P1 and [X hours] for P2/P3
- Participate in knowledge base updates by flagging missing resolution paths and documenting new solutions
Requirements
- 2+ years in an IT helpdesk or technical support role with documented ticket volume experience
- Hands-on experience with [Zendesk / ServiceNow / Jira SM / ConnectWise] (specify your platform)
- Strong written English communication; ability to write clear, professional customer responses under volume
- Working knowledge of Windows 10/11 environments and common business applications (Microsoft 365, Google Workspace)
- Familiarity with VPN troubleshooting, remote desktop tools (TeamViewer, AnyDesk, or similar), and basic network connectivity diagnostics
- Availability to work [specific hours in US time zone] on a fixed schedule
Nice to Have
- CompTIA A+ or ITIL Foundation certification
- Experience with active directory administration for user account provisioning
- Scripting knowledge (PowerShell, Python basics) for automated resolution tasks
Tier 2 Technical Support Engineer JD Template
Use this template for escalation-handling roles requiring structured diagnostic investigation, integration troubleshooting, and engineering-quality bug reports. The screening requirements are meaningfully higher than Tier 1.
Role Overview
We are hiring a remote Tier 2 Technical Support Engineer based in [India] to handle escalated support cases from our Tier 1 team, investigate software and integration failures, and manage multi-contact escalation tickets through to resolution. This role works [US Eastern / US Pacific] hours and requires structured diagnostic reasoning, clean engineering escalation documentation, and strong ownership of complex ticket queues.
Responsibilities
- Receive and own escalated tickets from Tier 1 involving application configuration errors, integration failures, system performance issues, and non-standard bug behavior
- Reproduce reported issues reliably, document reproduction steps, and write structured bug reports suitable for engineering review
- Communicate complex technical findings clearly to non-technical customers while managing multi-contact ticket threads professionally
- Identify patterns across escalated tickets and flag systematic product or documentation issues to the product team
- Maintain personal ticket resolution times within SLA targets and flag any tickets at risk of breach before deadline
- Build and maintain knowledge base articles for newly resolved Tier 2 issue categories
Requirements
- 3+ years in a technical support or IT support role with Tier 2 escalation ownership experience
- Demonstrated ability to reproduce and document software bugs or integration issues for engineering review
- Experience with [ServiceNow / Jira Service Management / Freshdesk] for escalation management and documentation
- Strong written English: able to write clear bug reports and professional customer communications under pressure
- Working knowledge of REST APIs, web application architecture, and common integration failure patterns (helpful for SaaS support roles)
- Availability to work [specific US time zone hours] on a fixed schedule
Nice to Have
- ITIL Intermediate or Practitioner certification
- Experience with log analysis tools (Splunk, Datadog, Graylog) or basic SQL for data investigation
- Python or JavaScript scripting for automation of repetitive Tier 2 tasks
- Previous experience at a SaaS company in a technical support engineer role
Customizing for Your Tech Stack
Both templates have placeholder fields for your specific tooling. Customizing the tool stack section meaningfully improves candidate quality because offshore hiring pipelines use keyword matching heavily in early screening. Platforms that should appear explicitly in your JD:
ITSM ticketing platforms: ServiceNow, Jira Service Management, Zendesk, Freshdesk, ConnectWise Manage, HappyFox, Kayako. Name the exact platform your team uses. Do not write “experience with major ITSM platforms” if you run ServiceNow specifically.
Remote access tools: TeamViewer, AnyDesk, Bomgar (BeyondTrust), LogMeIn, Splashtop. For roles involving remote hardware or desktop troubleshooting, the specific tool matters for screening.
Monitoring tools: For Tier 2 and infrastructure roles, list the tools your team uses: Datadog, PagerDuty, Splunk, New Relic, Grafana. Candidates with matching tool experience require less platform onboarding time.
Environment: Windows Server, Azure Active Directory, AWS environments, Google Workspace. Specify what the role will actually touch. Candidates who have worked only in Mac-and-Google environments are a different profile from Windows Server and Active Directory specialists.
Certifications to Include vs. Skip
Including certification requirements in a JD changes your applicant pool. The decision on whether to require vs. prefer any certification depends on your actual workflow needs. Guidance by tier:
Tier 1: CompTIA A+ is a legitimate baseline filter for hardware and software knowledge in Tier 1 helpdesk roles. ITIL Foundation signals awareness of service management methodology. Neither should be required unless your internal team holds them, which creates expectation parity. Set as preferred, not required, unless the role has a specific compliance or client requirement.
Tier 2: ITIL Foundation or Intermediate is meaningful for roles with formal escalation management responsibilities. It reduces onboarding time on SLA management, escalation protocol, and knowledge base standards. Microsoft or Cisco certifications are relevant if your environment requires them. AWS Cloud Practitioner or Azure Fundamentals are relevant for cloud-adjacent support roles. Set specific certs as preferred unless your client contract mandates them.
For both tiers: Never make a certification list so long that it excludes the best candidates. Certifications are signals, not proof of capability. The diagnostic reasoning exercise matters more than any certification held. The JD should reflect that by making most certs “nice to have” and keeping required certs to a minimum.
Adding Screening Criteria
Effective offshore JDs include an application screening question that filters for quality before a human reviews the resume. Add a single, required application question that surfaces diagnostic reasoning or platform experience immediately. The question should not have a single right answer but should reveal how the candidate thinks.
Example screening question for Tier 1: “A user submits a ticket saying their VPN connects but they cannot reach internal resources. They are on a company laptop running Windows 11. What are the first three things you check, and in what order? Explain your reasoning briefly.”
Example screening question for Tier 2: “A customer reports that their API integration stopped pulling data 48 hours ago. No code changes were made on their end. What steps do you take to investigate this? What information do you collect before engaging the engineering team?”
Candidates who can write a clear, structured response to these questions before a first call are far more likely to perform well in live diagnostic exercises. Candidates who write vague or generic responses (“I would check the connection settings and call them back”) reveal the gap immediately.
Compensation Guidance
Including a compensation range in the JD is recommended for offshore technical support roles. Offshore candidates research US company salary standards and benchmark against them. Hiding the range delays the process and creates surprise at offer stage. Ranges to use for JD disclosure in 2026:
- Tier 1 (India, entry-level): $9,000-$14,000 USD per year
- Tier 1 (Philippines, entry-level): $11,000-$16,000 USD per year
- Tier 2 (India, mid-level): $16,000-$28,000 USD per year
- Tier 2 (India, senior): $24,000-$40,000 USD per year
For full country and experience-level breakdowns, see the 2026 offshore technical support salary guide. If working through Kore BPO, salary guidance is provided as part of the search briefing so you do not need to publish a range in the JD if you prefer not to.
Common Questions About This Template
Should the JD specify India or Philippines as the candidate location?
Yes, if you have a preference. Being specific about target country in the JD improves screening efficiency because talent pools in India and the Philippines differ significantly at Tier 2 and above. India has deeper Tier 2 and infrastructure support pipelines. Philippines has stronger voice channel and consumer-facing Tier 1 pipelines. If you are open to both countries, specify “India or Philippines” so candidates in both markets can self-identify as eligible. If working with an offshore staffing firm, they will typically advise on the better country match for your specific role before the JD is finalized.
How long should the JD be?
400-700 words for the publicly posted version. The templates above are longer because they include customization fields and guidance notes. Strip those before posting. The final JD should have: a clear role overview paragraph (2-3 sentences), a responsibilities list (6-8 bullets), a requirements list (5-6 bullets), a nice-to-have list (2-3 bullets), and the time zone and shift requirement. Longer JDs tend to reduce qualified applicants by over-specifying nice-to-have requirements as required.
Can I use the same JD for both Tier 1 and Tier 2 hiring?
No. The candidate profiles are different enough that a combined JD produces an applicant pool that satisfies neither role well. Tier 1 candidates who see “3+ years experience with bug reproduction and integration troubleshooting” will self-disqualify even if their Tier 1 skills are strong. Tier 2 candidates who see a JD focused on password resets and knowledge base workflows will assume the role is below their level and not apply. Write a separate JD for each tier even if you are hiring for both simultaneously.
Do I need to include shift hours specifically in the JD?
Yes, as specifically as possible. “US hours” is not specific enough for a candidate planning their schedule around a night shift. Write the actual hours in their local timezone equivalent, or write both: “9am-6pm US Eastern (9:30pm-6:30am IST)” so candidates in India understand the shift clearly. Candidates who learn about the shift schedule late in the process and decline creates wasted screening cycles for both sides. Put it in the JD, not in the first interview.
How often should this JD template be updated?
Review and update the JD when you are actively hiring and any time your tooling stack changes significantly. If your team moves from Zendesk to ServiceNow, update the JD before the next hire. Outdated platform requirements in the JD produce candidates who trained on the old system without knowing the new one. Annual reviews are sufficient if you are not actively hiring. The compensation ranges in particular should be refreshed annually as offshore salary markets in India and the Philippines have been moving 8-12% per year at experienced Tier 2 levels since 2023.
Related Articles
Need a Screened Shortlist Instead?
Brief us on your support tier, tooling, and time zone. We send pre-screened candidates in 5-10 business days.
Start the Search