EU remote
Technical Support II - B&T
About this role
Aspire Software is looking for an Technical Support II to join our team in Lebanon. Here is a little window into our company: Aspire Software operates and manages wholly owned software companies, providing mission-critical solutions across multiple verticals. By implementing industry best practices, Aspire delivers a time sensitive integration process, and the operation of a decentralized model has allowed it to become a hub for creating rapid growth by reinvesting in its portfolio.
About the Role The Technical Support (Tier 2) is the person who figures out what is actually happening inside our applications when standard support processes are no longer enough. You take ownership of technical issues Tier 1 cannot resolve, investigate them through logs, data, configuration, and HTTP traffic, and determine whether the cause is a software defect, configuration problem, data issue, infrastructure fault, integration failure, or end-user issue.
You sit between Tier 1 Support and our Engineering, QA, DevOps, Technical Operations, and Product teams. Tier 1 brings you the problem; you bring Engineering a diagnosis: reproducible steps, evidence, a likely root cause, and a clear statement of customer impact. You are also an early warning system, recognizing when one ticket is the first sign of an incident affecting many customers, and raising it before it spreads.
What "good" looks like in this role: issues diagnosed to a likely cause with evidence attached; escalations Engineering can act on without re-investigating; incidents spotted early and their impact stated plainly; recurring problems turned into fixes, knowledge articles, or monitoring rather than repeat tickets. Key Accountabilities & Responsibilities Technical Investigation & Diagnosis Take ownership of issues escalated from Tier 1, gathering the right information from Tier 1, internal stakeholders, and clients to investigate efficiently.
Investigate application behaviour using server and application logs, SQL queries, browser developer tools, HTTP traffic, and configuration review. Reproduce reported problems in test or staging environments, isolating the conditions (role, browser, data, configuration, timing) that trigger them. Determine the likely cause (software defect, configuration, content/data, infrastructure, integration, or end-user) and document the evidence that supports it.