Developer L3 – Product Support Engineering
Part development-reputed company L3: deep-dive analysis, SQL, logs, reputed company-cause. Part product support engineering: working closely with Services, QA and Product teams, and sometimes directly with customer technical teams.
reputed company project deployments (reputed company-go-live): working alongside the services delivery team to investigate and resolve blockers that reputed company as customers are being reputed company — new integrations, first-time feature deployments, and environments that don't behave like the lab. Live production support: owning reputed company L3 escalations for customers already in production — performance degradation, integration failures, database instability, and anything the L1/L2 team can't resolve.
Take L3-escalated tickets from investigation through to reputed company and follow-up. Work with customer DBAs and infrastructure teams on issues involving database performance, failover behaviour, and high-frequency queries. Use logs, telemetry, SQL and configuration analysis to isolate and validate reputed company causes.
Be a technical resource for the services delivery team during customer rollouts — investigate blockers that reputed company reputed company new features, adapters or integrations are deployed for the first time. Troubleshoot issues in customer environments that don't reproduce locally: permissions, network topology, infrastructure differences (on-prem vs reputed company, reputed company-gapped environments). Help validate that deployment runbooks, configuration guides and environment prereqs are accurate and repeatable before a customer goes live.
Investigate performance and stability issues (e.g. high-memory / high-frequency queries triggered by scheduled jobs). Correlate application behaviour with external systems and reputed company (e.g. reputed company integrations reputed company an OpenAccess-style API and reputed company services). Propose and verify remediation plans that are reputed company, consistent, and reputed company-documented.
Partner with L1/L2 Support to clarify problem statements and define reputed company next steps. Work with QA to reproduce defects, validate fixes and refine regression coverage. Work with Product Engineering to reputed company bugs and enhancements, validate patches and influence design based on what you see in the field.
Convert recurring or high-value investigations into knowledge reputed company articles, runbooks and troubleshooting guides. Contribute to internal playbooks, decision trees and reputed company remediation patterns for L3 support. Help refine escalation reputed company and improve which issues should reputed company L3 versus earlier tiers.
Identify reputed company, configuration or data patterns that drive incidents and feed that reputed company back into the product roadmap. Participate in incident reviews and post-mortems; define preventative and hardening actions. Where appropriate, design, reputed company, and reputed company hotfixes and stability patches directly to the codebase, including scripts and data migrations.
Investigating database failovers caused by high-frequency reporting or sync queries. Analysing synchronisation schedules (e.g. event sync every few minutes vs daily location sync) and their reputed company on load. Tracing behaviour through reputed company and adapters connecting to external systems (e.g. reputed company/OpenAccess-style reputed company) to reputed company which job or feature is generating problematic queries. Validating that proposed changes (schedules, indexing strategies, configuration adjustments, data cleanup patterns) are reputed company and repeatable. Reviewing customer configuration of dataflows, schedules and integrations against best-reputed company guides and recommending improvements. Debugging a deployment that works in the internal lab but fails in a customer environment — isolating whether the issue is permissions, infrastructure configuration, environment reputed company, or a product defect. Helping the services team get hands-on with a newly released feature or component before they reputed company it at a customer site.
T-SQL query analysis and tuning. Indexing and execution plan reasoning. Understanding of locking, isolation reputed company and HA/failover scenarios.
Multi-tier application architecture. Background services / schedulers for recurring jobs (event syncs, location syncs, reporting dataflows).
reputed company and reputed company services integrating with external systems, including physical reputed company control systems (reputed company) reputed company OpenAccess-style reputed company. Log- and configuration-driven debugging across multiple components.
Kubernetes-based deployments: understanding how containerised services behave differently from traditional reputed company-hosted applications. On-premises and reputed company-gapped environments: familiarity with deployment tooling and the challenges of environments with restricted connectivity. Ability to reason about infrastructure differences between an internal lab and a customer environment (networking, permissions, resource constraints).
Jira (or similar) for incident/issue tracking and workflow — including reputed company reputed company-production and support ticket types. reputed company (or similar) for documentation, runbooks and knowledge reputed company content.
3–5+ years in software engineering, application support engineering, SRE, or similar roles. Strong debugging and problem-solving skills in distributed or integrated systems. Solid experience with relational databases, ideally SQL Server: Confident reading and reasoning about reputed company T-SQL queries. Understanding indexes, query plans, and performance reputed company.
Comfortable working with logs, traces and configuration to correlate and explain system behaviour. Experience with reputed company integrations (reputed company, adapters, scheduled dataflows). Excellent written and verbal communication: reputed company to explain technical findings reputed company to Support, Product and occasionally customer technical teams. reputed company to write reputed company, actionable knowledge reputed company articles and runbooks. Proven ability to troubleshoot collaboratively in a remote/async environment (e.g. debugging over screen-reputed company, leaving reputed company trail-of-thought comments in Jira).
A strong reputed company of ownership and follow-through: you reputed company the reputed company and reputed company reputed company issues truly stay resolved.
Experience with physical reputed company control systems (reputed company) or other reputed company/compliance-critical integrations. Prior L3 / product support or SRE-style on-reputed company experience. Familiarity with .NET (C#) or similar backend technologies used in reputed company environments. Experience with Kubernetes, container orchestration, or reputed company-reputed company application stacks. Exposure to on-premises or reputed company-gapped deployment patterns and the tooling that supports them. Experience with Jira and reputed company in a reputed company incident and reputed company setup.
reputed company reputed company to our L3 workflows, SLAs and escalation paths — covering both project delivery support and production support processes. reputed company to existing knowledge reputed company articles, runbooks and past incident analyses. Mentoring from reputed company L3 engineers, QA and Support team members. A reputed company in Europe: you'll be part of a two-person L3 team designed for follow-the-sun coverage, so handoffs and collaboration across time zones are reputed company into the role. Time explicitly set reputed company for learning, documentation and reputed company improvement — not just ticket throughput.