Daniel Verastiqui

Howdy, I'm Daniel Verastiqui.

I'm a seasoned Technical Services Leader, Full-Stack Developer, and Technical Writer with over two decades of experience in the tech industry. Since 2000, I've been developing innovative processes and philosophies for delivering best-in-class technical support. My expertise spans managing teams, crafting scalable support frameworks, and leveraging technology to improve user experiences. Whether it's building custom tools, streamlining workflows, or driving customer success, I thrive on finding creative solutions to complex challenges.

Let's connect and explore how I can bring value to your organization.

I've Worn Many Hats

Proven Technical Leader 🫡

From assisting CCIE candidates with hands-on lab work to managing a global team, I've held almost every role related to technical services. When I joined Uplogix in 2006, I became the first member of their 24/7/365 paid technical support team. Over the years, as we grew, I trained new employees and established a preferred way of helping our customers. As a Lead, Manager, and eventually, Director, I was responsible for setting the tone of Uplogix Support.

My approach involves creating efficient processes, fostering excellent written communication skills, and prioritizing customer satisfaction. To support the team, I built custom web applications and integrated tools like Zendesk, Jira Service Desk, and HelpScout to keep our customer satisfaction rate above 95% during my tenure. This led to a 90%+ renewal rate for paid support, providing almost $5m in ARR.

Disciplined Technical Writer đź“ť

My experience as a technical writer began out of necessity when Uplogix lost its dedicated technical writer, and I stepped in to fill the gap. Since then, I have written and maintained a wide range of documentation, including User Guides, Setup Guides, Command References, and Knowledge Base articles. My BA in English has been invaluable in this role, enabling me to communicate complex technical information in a way that is both understandable and accessible.

My goal was not only to write great documentation but also to provide the technical services team with easily referenced articles that they could share with customers, which reduced the amount they had to write in ticket response and allowed them to respond faster.

đź”— Writing Samples

Senior Systems Administrator đź’»

I have extensive experience in systems administration, particularly in deploying and maintaining LAMP stacks for web applications. I can quickly set up and configure a Linux, Apache, MySQL, and PHP environment. Ubuntu is my preferred Linux distribution due to its ease of use, stability, and large community support. I also have experience with RedHat, CentOS, and Debian. Whether working on the command line or clicking around in Windows, I’m equally comfortable managing system configurations, troubleshooting issues, and optimizing server performance.

Expert Technical Instructor 👨‍🏫

One of the things we liked to say at Uplogix was we don't sell tools; we sell toolboxes. While our products could do a million amazing things, customers sometimes felt overwhelmed by trying to figure out how our appliances worked rather than focusing on what problems they were trying to solve. That's where customer training came into play. Training not only empowers users to fully leverage the products and services they've purchased, but it also establishes us as subject matter experts in various technologies.

Throughout my career, I've developed comprehensive training programs for groups large and small in both online and in-person settings. The goals of these programs were to educate the user, demonstrate our consultative worth, and ensure our products become the standard in their networks.

I particularly enjoyed face-to-face training with customers, which allowed me to build lasting, personal relationships. Good training is just the beginning of a long period of cooperative work with the customer.

Self-Taught Full-Stack Developer ⚙️

Let me be clear: I am not a software developer. I am, however, fond of automating complex tasks. When I joined UT System as a college student, I was part of a 10-person team responsible for looking at a calendar and routing video streams for long-distance learning classes. Over time, I realized that I could write some code that would pull the class schedule from an Oracle database, figure out the best route for the video, and then log into various DACS (Digital Access Cross-Connect System) servers via Telnet to make the appropriate connections. My program worked flawlessly, saving UT System over $25,000 in proprietary software and eliminating all student positions.

That program, lovingly called DAXinator, was written in Java, which I found overpowered for my later needs. Eventually, I discovered the LAMP stack (Linux, Apache, MySQL, PHP) and learned to build dynamic web applications quickly. Over the years, I've refined my skills in all aspects of the LAMP stack and added other technologies like APIs, JSON, cURL, jQuery, and Bootstrap. Today, I can rapidly and efficiently create robust, user-friendly web applications that are fast, process-focused, and scalable.

I've Worked a Few Places

Lantronix, Inc.

Senior Manager, Client Services

2022 — 2024

Uplogix, Inc.

Director of Client Services

Technical Services Director

Technical Support Manager

Technical Support Specialist

2006 — 2022

The University of Texas System

Network Analyst

2000 — 2006

I've Built Some Cool Stuff

Central CRM

Central is a custom CRM I developed to track all technical information for our customers. It became an invaluable tool for sharing real-time status updates, sales notes, and configuration details across departments. By providing a centralized location to access a customer's entire technical journey, Central ensured that everyone—from support to sales—was on the same page. This enhanced level of information sharing was critical in fostering customer intimacy. The more we knew about our customers, the better we could anticipate their needs and provide exceptional support.

I originally conceived Central as a "Facebook for Customers" and gave it a similar design to the Facebook homepage. From this page, you can add updates, see recent updates from colleagues, find commonly accessed customers, and keep track of maintenance renewals. Other departments used this page to get a sense of who we (support) are currently interacting with and who needs attention.

Customer Records

  • Company Name
  • Headline (One of our biggest customers! $3m run rate.)
  • Team: Account Executive, Sales Engineer, Inside Sales Rep
  • Configuration: Domain, Stage, Software Version, Maintenance End Date, Zendesk ID, Salesforce ID, Status
  • Customer-specific task management
  • Changelog for auditing
  • Updates detailing interactions with Support, Sales Engineering, Sales, or other department
  • Comprehensive Proof of Concept Checklist with Status
  • Comprehensive Deployment Checklist with Status
  • Contact Management for managing access to Support Site, Ticketing System, and Software Downloads
  • Dossier for collecting environmental data: Out-of-band strategy, AAA environment, IP addressing for management platforms, etc.

Other features

  • Zendesk integration via API ensured priority ticket routing for paying customers
  • Slack integration via Webhooks (via cURL) sends important alerts and events to the appropriate team channel
  • Automated sending of welcome emails to new customer contacts
  • Automated sending of status and request emails to all departments involved with RMAs
  • Automated update of Zendesk tickets via API as RMAs are processed, including shipping notifications and return reminders
  • Aggregation and generation of software licenses based on customer purchases
  • Metrics for support tickets and RMAs

Technical Info

  • Runs in VMware on the latest Ubuntu
  • Uses MySQL and filesystem for storage
  • Integrates with Active Directory and WordPress (via OAuth) for AAA
  • 1,300+ PHP files
  • 140,000+ lines of code

Screenshots

Online Documentation Library

Back in 2006, online documentation was hard to come by, but it was clear very early that our customers didn't like poring over PDFs to find answers. After trying various solutions that weren't quite what we needed, I built an app to display our documentation the way we wanted it to be displayed.

Technical Info

  • Articles are stored in a MySQL database in Markdown format
  • When an article is requested, it is automatically parsed into HTML and styled with CSS and Bootstrap
  • The entire site is run out of one PHP file; permalinks are parsed and the appropriate database call is performed
  • Version history is maintained for every article article
  • Entire library can be exported, styled, and converted in PDF using pandoc
  • Includes a back-end management web application to update articles, with granular authorization for editors

Screenshots

Secure Firmware Downloads

At Uplogix, software updates required an active maintenance subscription, so we couldn't just make those files available on our corporate website. To solve this problem, I built a software delivery app that used AAA, which was defined by Central, to allow specific customers to download software only when their maintenance contract was active. This process included gating software behind a EULA, creating and destroying temporary download links, and styling raw directory listings via .htaccess.

Zendesk Administration & Customization

Since we had our own documentation library and knowledge base, I didn't need to customize Zendesk until very recently. Luckily, they allow you to edit your template and add any needed features. I updated our theme to more closely match the Lantronix website and give customers an easy-on-the-eyes, minimal website through which to access tickets and read knowledge base articles.

Support Site & SSO

Zendesk offers the option of offloading AAA to another server via SSO. At Uplogix, I wrote a simple shim that would perform a lookup whenever someone tried to log into the ticketing system. Access was defined in Central and securely synchronized to our website. Later, we replaced my shim with an OAuth plugin in WordPress.

In both cases, we were able to define who could open tickets in our Zendesk instance and (based on free vs paid) route tickets to the correct team. This ability is invaluable if you're already running AAA and want to integrate Zendesk without importing or recreating your entire user base.

Further, a Slack integration let us know when users were logging in, downloading software, and opening new tickets. This visibility allowed us to anticipate contact from a customer and thus be ready to support them.

Photos

Personal Projects

Published Science Fiction Novelist

➡️ danielverastiqui.com

2004 — 2024

© 2024 Daniel Verastiqui

This website was created using HTML, PHP, CSS, and Bootstrap. It runs on a LAMP stack on Ubuntu.