> Markdown version of [/jobs/ext/1323448-staff-technical-support-engineer](https://www.wearedevelopers.com/jobs/ext/1323448-staff-technical-support-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Staff Technical Support Engineer - **Company:** Proscia Inc. - **Location:** Philadelphia, PA, United States (Remote available) - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Customer Data Management, Linux, Distributed Systems, Statistical Hypothesis Testing, Network Architecture, Open Source Technology, SQL Databases, Kubernetes, Docker - **Published:** July 17, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=6028da983cd3ec51 ## About the Role * 8+ years in technical, customer-facing engineering roles, including senior or lead-level scope. * A drive to solve difficult problems for their own sake - not just because it's your job, but because you won't be satisfied until your own curiosity is sated. * A track record of getting ahead of problems and spotting systemic patterns, driving preventative fixes that measurably cut escalation volume. * Comfort in ambiguity: you analyze complex, messy data, make high-stakes calls independently, and stay effective where there's no runbook yet. * You've owned a technical escalation process end-to-end and at scale from customer request through Engineering and Product. * Deep troubleshooting across distributed systems, with a strong command of network architecture, infrastructure fundamentals and modern remote-diagnosis techniques. * Advanced knowledge or expertise in some or all of: Linux, Kubernetes, Docker Compose, and SQL. * You've made AI tools a default part of how you investigate, reason, and build, and you know how to validate and constrain what they produce rather than trust it blindly. * You raise the bar for teams, not just tickets. You've mentored, set technical standards that outlast any single problem, and advocated for customers across the entire org chart. Nice-to-Haves * Experience influencing product or engineering roadmaps from support and customer data. * Knowledge of digital pathology, or experience in healthcare, regulated, or other mission-critical environments where failure has real consequences. * Open-source work, side projects, or a portfolio that shows how you think and build. * A background that spans multiple domains - you've reinvented yourself before. ## Description * Get ahead of the fire. Hunt down systemic risks and recurring failure patterns before they surface as a wave of tickets. Read the signals across the customer base at scale, stay ahead of every new release, and drive the fixes that quietly remove whole categories of issues. * Own the hardest investigations. Take the ambiguous, business-critical, multi-system problems no one else can crack. Gather evidence, form and test hypotheses, reproduce the worst defects in lab environments, and follow the thread across application, infrastructure, and live customer environments until the true root cause is undeniable. * Shape how the platform is built and supported. Turn field patterns into influence: partner with Engineering, Product, and QA on roadmap decisions, define how issues move from customer to engineering, and carry the voice of the customer into product and infrastructure planning. * Multiply the team. Make everyone around you better. Mentor and coach engineers, lead technical training and pairing, set the standard for documentation and knowledge quality, and build the onboarding and career frameworks the team grows into. * Lead the deep deployment work. Run the complex upgrades, migrations, and provisioning efforts where both the technical depth and the stakes are highest and where divergent customer environments fly in the face of runbooks and expectations. * Be there when it counts. When a critical incident hits, you lead: steady, high-touch customer communication and live troubleshooting on major incident calls. ## Related Videos - [Docker network without Docker](https://www.wearedevelopers.com/videos/1418-docker-network-without-docker) - [Docker Compose: Rediscovered](https://www.wearedevelopers.com/videos/1978-docker-compose-rediscovered) - [Understanding Kubernetes in a visual way](https://www.wearedevelopers.com/videos/100085-understanding-kubernetes-in-a-visual-way) - [Shipping Faster with Less: Render on Cloud Hosting, AI Workloads, and the Future of DevOps](https://www.wearedevelopers.com/videos/1894-shipping-faster-with-less-render-on-cloud-hosting-ai-workloads-and-the-future-of-devops) - [Docker exec without Docker](https://www.wearedevelopers.com/videos/1094-docker-exec-without-docker) - [Docker build without Docker](https://www.wearedevelopers.com/videos/100114-docker-build-without-docker) ## Related Articles - [Coffee with Developers - Maria Apazoglou - Making AI understandable for all in production](https://www.wearedevelopers.com/magazine/475-coffee-with-developers-maria-apazoglou-making-ai-understandable-for-all-in-production) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Résumé-Driven Development: How IT trends affect the job market for software developers](https://www.wearedevelopers.com/magazine/59-resume-driven-development-how-it-trends-affect-the-job-market-for-software-developers) - [Why Upskilling And Reskilling is Important For Developers](https://www.wearedevelopers.com/magazine/428-why-upskilling-and-reskilling-is-important-for-developers) - [Highest Paying Tech Companies for Developers](https://www.wearedevelopers.com/magazine/220-highest-paying-tech-companies-for-developers) - [How to Become an AI Engineer](https://www.wearedevelopers.com/magazine/331-how-to-become-an-ai-engineer)