Technical Support Engineer at Pear Tree. in Gauteng, South Africa

Position : Technical Support Engineer

Salary : £1,200 – £1,600 per month

Working Hours: : UK business hours

Holidays : UK public holidays

About the Role

Our UK client isn't just scaling; they're redefining human risk and secure behaviour management in cybersecurity. Trusted by global enterprises—including Vodafone, Merck, Arriva, and Hershey—they reduce human cyber risk through AI-driven automation, with Agentic AI extending this capability even further.

Support is where the product meets reality. Every ticket represents a customer telling us something true about the platform, and every ticket is either a question we keep answering or a problem we solve once and eliminate at the source.

We are engaging a dedicated Technical Support Engineer based remotely in South Africa to take full end-to-end ownership of customer issues: investigating logs, reproducing defects in test tenants, handing fully documented cases to our Product Lead for engineering fixes, keeping customers proactively updated, and eliminating root causes from the platform, documentation, or onboarding flows.

This is a technical B2B SaaS engagement, not a script-reading helpdesk. You are inheriting a disciplined, high-standard operation where support functions directly as a strategic product feedback loop rather than a cost centre.

Key Responsibilities

Case Investigation & Troubleshooting

• Inbound Queue Management: Triage, investigate, and resolve inbound customer tickets inside Intercom within agreed SLAs, setting clear expectation windows for every update.
• Evidence-First Diagnostics: Check platform and audit logs, Sentry error events, browser developer consoles, network traces, API request/response payloads, and tenant configurations before asking the customer for additional details.
• Defect Reproduction: Replicate issues inside sandbox environments and test tenants. When issues do not immediately reproduce, isolate anomalies across user logs, timestamps, and tenant settings rather than sending generic checklists to customers.
• Proactive Monitoring: Review daily system error records and Sentry events to identify tenant-level failures before customers notice them, initiating proactive outreach with the issue and resolution already in place.
• Release Verification: Review bi-weekly release notes on ship day, validate new and changed functionality in sandbox tenants, verify hotfixes against original reproduction steps, and close out waiting customer tickets.

Escalations & Root Cause Elimination

• Actionable Engineering Escalations: Provide our Product Lead with complete, zero-rework handovers—including reproduction steps, tenant/user IDs, UTC timestamps, relevant log excerpts, and eliminated variables—ready for engineering action.
• Customer Ownership: Maintain single-point-of-contact ownership with the customer while the engineering fix is being developed, providing dependable, scheduled progress updates.
• Systematic Ticket Categorisation: Tag every closed ticket with a defined root cause (product bug, UX friction, documentation gap, environment issue, or missing feature).
• Documentation & Product Feedback: Update help centre documentation, setup guides, and troubleshooting workflows to enable customer self-service, while presenting evidenced UX friction reports directly to the Product Lead.

Required Skills & Experience

• 3+ Years in B2B SaaS Support: Proven background in multi-tenant, cloud-based platform troubleshooting within technical support, application support, or customer-facing engineering roles.
• Technical Troubleshooting Toolkit: Hands-on competence analyzing logs, inspecting network requests and responses (REST/JSON), checking HTTP status codes, and using browser developer tools.
• Enterprise Customer Communication: Demonstrated experience liaising professionally with B2B technical buyers (CISOs, IT Directors, SOC teams, platform administrators) with flawless written and spoken English.
• Root Cause Track Record: Concrete examples of identifying recurring platform issues, creating documentation that deflected tickets, or proposing shipped UX/product fixes.
• Support Platform Proficiency: Practical experience with Intercom (or comparable tools such as Zendesk, Freshdesk, HubSpot Service Hub) and ticket workflow management.
• Independent Contractor Discipline: Self-motivated remote work ethic from a dedicated South African home-office setup aligned with UK business hours.

Nice to Have:

• Prior exposure to the cybersecurity domain or human risk platforms (e.g., KnowBe4, Proofpoint, Mimecast, Hoxhunt).
• Practical administration of Microsoft 365 or Google Workspace mail flow (SPF, DKIM, DMARC).
• Basic read-only SQL querying skills.
• SSO and identity provisioning knowledge (SAML, OIDC, SCIM, Microsoft Entra ID / Active Directory).
• Familiarity with cloud and web frameworks (Cloudflare, Vue, Nuxt, PostgreSQL) or compliance standards (ISO 27001, SOC 2, UK GDPR).

Engagement Terms & Operating Principles

• Workspace & Contingency Setup: Dedicated workspace equipped with a high-performance laptop, high-speed fibre internet, secondary connectivity, a verified load-shedding power contingency (inverter/UPS), and a professional headset and webcam.
• Certification Requirement: Attainment of Intercom certification within the first 90 days of engagement.
• Core Working Philosophy:
  1. Check first, then speak: Every statement must be backed by data and system records; never guess or send unverified assumptions.
  2. The diagnostic burden is ours: Do not send troubleshooting task lists back to the customer when the data exists in our logs.
  3. Zero uncommunicated delays: Provide explicit next-update times and meet them consistently.

What Success Looks Like

By day 90, you are managing the Intercom queue autonomously within SLA, maintaining a 100% root-cause classification rate on closed tickets, and delivering complete, verified escalations that require zero rework from the Product Lead.

You have established a daily routine of proactive outreach from system error logs, verified bi-weekly release hotfixes independently, and proposed at least three shipped improvements across documentation, UX, or product features that tangibly reduce recurring ticket volume.