You were the person who answered when things broke

Ticket queues, SLAs, night shifts, cPanel and DNS issues, slow databases, angry escalations and the bug that only happened for one client. You learned how systems fail and how to calm people while you fix them.

FromSupport EngineerToSRE / Production Support

Now AI agents answer many first-line tickets, and large firms have cut support teams. Simple L1 answers are the part being automated first. What stays scarce is someone who finds the real cause, handles escalations, writes the fix down and keeps customers. Small hosts and large IT services firms both need this.

Salesforce's chief executive said in September 2025 that the company cut about 4,000 support roles as AI agents took on more support work (CNBC, Sep 2025). the Times of India reported that the five largest Indian IT firms together shed 6,981 employees in FY26, led by TCS (Times of India), and BusinessLine found three of five large Indian IT firms with smaller sales and support teams, with one analyst saying AI can handle most level-one support tasks (BusinessLine, Nov 2025). These describe companies and categories, not your city or your skills. The rest of this page is our reading of the work itself.

Try it: Bot, L2 or L3

Four tickets arrive at once. Decide which the bot can answer, which go to L2 and which need L3.

Bot, L2 or L3

Three routes that reuse what you did

Did you enjoy finding the real cause, not just closing the ticket? SRE and production support engineers keep systems running, tune alerts and write runbooks so incidents happen less. Route: SRE / Production Support.

Were your best days the ones where a customer stayed because you helped? Customer success managers keep customers using a product and renewing, with the trust support built. Route: Customer Success Manager.

Did you fix more WordPress sites on hosting tickets than anything else? A WordPress care business sells monthly updates, backups, uptime checks and small fixes to a handful of clients. Route: WordPress Care Business.

Free tools to practise on (checked 27 Oct 2026)

  • Google SRE book (free online). Read how large teams run on-call, alerts and incident reviews (sre.google).
  • WordPress Hosting Team handbook. See how hosts are advised to run WordPress well (make.wordpress.org).
  • WP-CLI commands. Fix common WordPress issues from the command line (developer.wordpress.org).
  • HubSpot Academy. Take free lessons on customer success and service (academy.hubspot.com).

Pay, honestly

We haven't verified pay data for these routes. SRE and customer success roles are often salaried, while a care business is often paid monthly by clients; ask about shifts and on-call before you compare.

Your realistic 90 days

You worked in hosting or application support. AI agents now take many first-line tickets, so your value moves to root causes, reliability, customers and owning sites.

Assumes 2–3 hours a day alongside job applications, a laptop and a phone, and free plans only. Every step has a smaller version and a way to pause. Use them. It runs in three blocks of 30 days, each ending with a signal that you're on track. A signal is not a promise of a job or income.

What AI changed in your old tasks

You used to… Now you…
Answered the same L1 questions daily Review what the bot answered and fix its gaps
Escalated anything unusual Own the unusual cases end to end
Followed someone else's runbook Write and improve the runbook

Your first 7 days

Day Task Done when
1 List the 10 ticket types you handled most 10 types
2 Mark which a bot could answer safely Marked
3 Read one chapter of the SRE book 3 notes
4 Write fix steps for your most common ticket 1 runbook page
5 Pick a route (SRE, customer success or care business) Route chosen
6 Make one sample for that route 1 sample
7 Save 10 postings or 10 possible clients 10 links

Days 1–30: Runbook for top tickets

Step Time Done when Smaller version If you need to pause
Write a runbook for the five tickets you solved most often and test it on a practice setup about 6 hours over 3 weeks runbook + test log Two tickets only. Stop at the end of the step you're on and write two lines about where you stopped. Pick it up from those notes later.
Message 5 people who hire for your chosen route about 1 hour 5 messages Message 2 people who hire for your chosen route. Optional. If reaching out feels like too much this week, skip it and put the time into your proof.

Signal by day 30: Your runbook fixes all five tickets on your practice setup, and one of the 5 people you messaged replies.

Days 31–60: Your chosen route

Step Time Done when Smaller version If you need to pause
Build the first proof for your chosen route about 8 hours proof link A one-page plan. Put it on hold while interviews take up your time, then come back to it.
Apply to 10 roles where your technical support years count about 5 hours 10 logged Apply to 5 roles. Stop sending for now. Keep a list of who you've contacted so you can follow up later without doubling up.

Signal by day 60: A screening call.

Days 61–90: Interviews

Step Time Done when Smaller version If you need to pause
Practise a 2-minute story of an outage you helped end about 2 hours 3 runs 1 run. Optional. Skip it if the week is full; nothing later depends on it.
Ask 3 former colleagues for referrals about 2 hours 3 asks Just one instead of 3. Stop sending for now. Keep a list of who you've contacted so you can follow up later without doubling up.

Signal by day 90: A second round or a paid trial.

Worries people bring when leaving this job

  • Bots answer tickets now. They answer the easy ones. Escalations and outages still need people.
  • I was only L1 or L2. You learned how customers describe problems, which every route needs.
  • Shift work wore me out. Ask about rotas and on-call before you accept any route.
  • Gap in work. A recent runbook and practice log show your skills are current.
  • No degree in computer science. Runbooks, test logs and clear writing are proof anyone can check.
  • I need income quickly. Care clients or a support-adjacent role can bridge while you build toward SRE.

Where the openings are, and what to type

IT services firms, hosting companies, SaaS firms, banks and product companies with support or reliability teams. LinkedIn and Naukri both carry these roles.

Also worth a weekly look: Instahyre, Cutshort, Wellfound, and iimjobs or hirist for senior roles. Upwork and Contra if you want freelance work.

  • LinkedIn search string: ("application support" OR "production support" OR "L2 support" OR "L3 support" OR "site reliability" OR "customer success")
  • Naukri / foundit keywords: application support, production support, L2 support, L3 support, SRE, customer success

Job-hunt moves that matter for this route

  • Search 'production support', 'SRE' and 'customer success' on LinkedIn and Naukri, then filter to the last week.
  • Put one runbook and one incident review in a public repo.
  • Show the before-and-after time for a ticket type you wrote a fix for.

Your 30/60/90 quests

Paused. Nothing is lost — life happens. Resume whenever you're ready.

XP: learning 20 · proof 60 · outreach 40. Ranks: Wayfinder → Builder → Pathmaker. Progress stays in your browser only.

Every route starts from a station you already know.

Job scams aimed at developers

Watch for 'developer internships' or 'live project training' that charge a registration, laptop or certificate fee, 'test tasks' that ask you to build a full product for free, and anyone asking for an OTP, UPI PIN, a deposit or remote access to your bank before you start. Real employers never charge you to hire you. Use official domains only. Report in India at cybercrime.gov.in or call 1930; in the US, ReportFraud.ftc.gov.

What people in this role ask

Will AI replace support engineers? First-line answers are being automated. Escalations, outages and customer trust still need people.

Hosting or app support, which helps more? Both. Hosting gives you servers and DNS; app support gives you logs and code paths.

Do I need to code? For SRE, basic scripting helps. Customer success and care work need it less.

Development hub · Related roles: Backend developer · Java developer

Quick quiz: does this path fit?

Answer each, then press Check. Every answer explains itself.

Make your Path Card

A shareable reminder of where you're heading. The day count starts the first time you open this page; quest XP comes from your log above.

Scam check before you apply anywhere

  • Real job and gig platforms are free to join. Never pay a "joining" or "training" fee.
  • Never share an OTP or UPI PIN — no genuine employer needs them.
  • Use official domains only; type the address yourself.
  • India: report at cybercrime.gov.in or call 1930.
  • US: report at ReportFraud.ftc.gov.

Small steps, every day.

Each quest has a smaller version for hard weeks, and a pause button. Nothing is lost.

Keep exploring

Sources

Checked 27 Oct 2026. We opened every link below ourselves. Search volumes on this site come from OpenSEO keyword research (Oct 2026).

What we checkedWhere
CNBC, Sep 2025: Salesforce CEO confirms 4,000 support roles cut as AI agents take on support workcnbc.com
WP-CLI commandsdeveloper.wordpress.org
BusinessLine, Nov 2025: Indian IT majors see reduction in sales and support teamsthehindubusinessline.com
HubSpot Academyacademy.hubspot.com
WordPress Hosting Team handbookmake.wordpress.org
Times of India: top 5 Indian IT firms shed 6,981 employees in FY26, TCS down 23,460timesofindia.indiatimes.com
Google SRE book (free online)sre.google