← Back to the notebook

My work as a Support Engineer at Acquia moves between people and systems. A customer needs to know what happens next. An application needs investigation. A teammate may need help deciding where to start.

The work spans Drupal, cloud hosting, GitLab-powered CI/CD, and deployment environments. The objective is to help customers stay productive while making technical progress on the underlying issue.

Prioritize the impact

I start by considering the impact and urgency of the cases and escalations in front of me. A production outage needs a different response from a development question. P0/P1 incident work can change the shape of the day, so priorities need to reflect what customers are experiencing.

That prioritization includes communication. A customer should understand who is investigating, what is known, and what the next step will be—even when a complete resolution is not yet available.

Build an explanation from evidence

Much of my day involves reviewing logs, checking system behavior, and investigating application or infrastructure issues. My toolkit includes Linux, SQL/MySQL, APIs, observability tools, and scripting, alongside my experience with cloud and deployment environments.

I try to keep observations separate from assumptions. An error message is a starting point, not always the root cause. Recent changes are relevant context, but they still need to be tested against the evidence.

When an issue needs deeper product expertise, I collaborate with Product and Engineering. A useful escalation carries a clear problem statement, customer impact, relevant evidence, and the investigation already completed. That gives the next engineer a meaningful starting point.

Turn the investigation into shared knowledge

My responsibilities also include root-cause analysis, release validation, runbooks, and knowledge-base content. These are opportunities to make the next investigation easier.

A useful runbook explains what to check and why. A useful knowledge article helps someone recognize a problem and choose a sensible next step. Product feedback should connect technical behavior with the customer’s experience of it.

The objective is not only to close the current case. It is also to reduce repeated confusion and help the team respond more consistently.

Make time for the next engineer

I mentor Tier-1 engineers and help Associate Support Specialists build confidence with Drupal, Acquia’s products, and customer communication. I am a point of contact when a case escalates or a colleague needs technical guidance.

I want colleagues to understand the reasoning behind an answer. Walking through an investigation together can help someone recognize the same pattern later—and ask better questions when the pattern is different.

What transfers to a new product

A new platform brings its own architecture, vocabulary, and failure modes. I would not assume that supporting one product automatically makes me an expert in another.

What does transfer is the process: establish impact, investigate methodically, communicate clearly, collaborate with engineering, and document what helps the next person. My growing knowledge of AWS, Docker, Kubernetes, and automation gives me more ways to ask useful technical questions as I learn a new environment.

That is the balance I enjoy in support: helping a customer move forward today while building the knowledge that makes tomorrow’s work better.