What carries over
| What you did as a technical support engineer | Where it shows up now |
|---|---|
| Read logs during escalations | Find root causes |
| Followed runbooks | Write and improve runbooks |
| Worked night shifts on incidents | Share an on-call rota |
| Updated customers during outages | Write clear incident updates |
What is new
- Writing simple scripts to automate repeat fixes.
- Setting service goals and alerts that matter.
- Writing blameless incident reviews.
Try it: Root Cause or Restart
Four incidents: decide which need a root-cause fix and which a restart is enough for.
Root Cause or Restart
Your first proof in 30 days
Monitor one small app with alerts, automate one repeat fix and write an incident review of a test outage. Share them as a public repo with screenshots.
Your 30/60/90 quests
XP: learning 20 · proof 60 · outreach 40. Ranks: Wayfinder → Builder → Pathmaker. Progress stays in your browser only.
Worries, answered
I was never a developer. Support work already covers logs, runbooks and incidents; scripting can be learned in steps.
Is this just more night shifts? Ask how on-call is shared and how often people are paged.
Pay, honestly
We haven't verified pay data for this move. Some SRE roles pay an on-call allowance on top of salary, so ask how on-call is paid.
Your realistic 90 days
You worked as a technical support engineer. This plan moves you toward SRE work in 90 days, using what you already do.
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.
Your first 7 days
| Day | Task | Done when |
|---|---|---|
| 1 | Pick one small app you can run on a free tier | App picked |
| 2 | Set up a free uptime monitor | Monitor live |
| 3 | Read the Google SRE book chapter on monitoring | 3 notes |
| 4 | Write a script that automates one fix | Script |
| 5 | Run a test outage | Test done |
| 6 | Write an incident review | Review |
| 7 | Save 10 postings | 10 links |
Days 1–30: Monitored app and review
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Publish a monitored app, one automated fix and an incident review | about 8 hours over 3 weeks | repo + review | Runbook 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. |
| Show your proof to 5 people who hire for this role | about 1 hour | 5 messages | Show it to 2 people who hire for this role. | Optional. If reaching out feels like too much this week, skip it and put the time into your proof. |
Signal by day 30: Your automated fix brings the app back after your test outage, and one of the 5 people you showed it to replies.
Days 31–60: Applications
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Turn your proof into a one-page case and CV line | about 8 hours | case + CV | CV line only. | Put it on hold while interviews take up your time, then come back to it. |
| Apply to 10 SRE roles | 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 for SRE roles
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Practise a 2-minute story of why you are moving | about 2 hours | 2 practice 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 technical interview.
Other worries
Age, a career gap, no degree, English, family pressure and savings are covered on the route page and the role page.
One search that fits your background
The full set of search strings for this move is on the route page. These strings work on LinkedIn, Naukri and foundit; Instahyre and Cutshort are worth a weekly look too. Add your old job title to any of them with AND, so your searches surface roles that want both skills.
Job-hunt moves that matter for this route
- Show your monitored app, script and incident review.
- Tell one story of a repeat incident you helped stop.
- Look at SaaS firms, banks and IT services teams with SRE or production support groups.
Fake-job traps
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.
Back to Support Engineer · About the SRE / Production Support route · Development hub
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 checked | Where |
|---|---|
| Google SRE book (free online) | sre.google |
| PagerDuty Incident Response guide | response.pagerduty.com |