Technical-support skills employers ask for and how to show them

Career sites list “communication, troubleshooting, and technical knowledge.” That is true and not useful. This page maps a small, dated sample of SaaS postings to what you can learn, practise, and show. It also links to the live Tier 1 items that exist on SupportRoadmap.

Three layers employers actually mix together

The same title can mean very different work. Separate the ads before you panic about SQL.

Entry / Tier 1 (customer + product)

EnableComp asked for product-ticket ownership and liaison with operations, product, implementation, and technology. The proof they imply is: you can own a ticket, explain the product, and hand off cleanly.

Bridge / more technical support

Reproduction, browser tools, HTTP status codes, permissions, and a written escalation. Live Tier 1 covers the start of this. It does not yet include a mock ticket or an API lab.

Support Engineer (later investigation)

FloQast’s integrations engineer posting listed SQL, API troubleshooting, OAuth/SAML/SSO, logs, and direct customer work (US base listed at $60k to $90k). PayU listed API, logs, SQL, and 3+ years of Tier 2/3 experience. That is not an entry-level synonym for technical support.

Learn → practise → demonstrate

• Ticket quality and customer writing

  Layer: Entry

  Learn: Structure: summary, steps, expected vs actual

  Practise / show: Rewrite three anonymised tickets from a product you know

  Live on this site: Ticket writing

• Product and account troubleshooting

  Layer: Entry

  Learn: Roles, seats, cache, cookies, “works for one user”

  Practise / show: Reproduce a login or permission issue in a private window

  Live on this site: Common Tier 1 issues

• Browser DevTools

  Layer: Bridge

  Learn: Network panel, status codes, console errors

  Practise / show: Save a redacted screenshot of a failed request, not a password

  Live on this site: Web browsers

• Ticketing workflow

  Layer: Entry

  Learn: How queues, macros, and internal notes work

  Practise / show: Write an internal note an engineer could act on

  Live on this site: Ticketing systems

• CV / interview proof

  Layer: Entry

  Learn: Turn investigation into bullets

  Practise / show: One story: customer blocked → what you checked → outcome

  Live on this site: Interviews and résumés

• APIs, logs, SQL, SSO

  Layer: Engineer / later

  Learn: Concepts only at first; do not skip T1

  Practise / show: Later: a redacted request/response and a written hypothesis

  Live on this site: Not a live T1 item. Foundations: browsers and networking.

For APIs and logs, the live path still helps: browsers and basic networking are how support people first see HTTP. There is no API chapter on Tier 1 today, and this page will not invent one.

How to show the skill without faking a lab

• Keep artefacts: ticket rewrite, repro notes, a redacted screenshot, a customer update.
• Name the product class (billing SaaS, collaboration app) rather than claiming confidential employer data.
• Do not paste API keys, session cookies, or personal data into a portfolio.
• Do not list CompTIA as proof of SaaS support unless the job actually asked for it.

If you want hands-on scenarios later, the waitlist is for product updates. That includes future practice if we ship it. It is not access to a simulator today.