There's a pattern in software teams: the roles that work the hardest to make things invisible get the least recognition when things go right — and all the attention when things go wrong. DevOps engineers, UX Designers, and Support teams have something in common: when they're doing their job well, you barely notice them.
Learning Objectives
By the end of this lesson you will be able to:
- Describe what a DevOps engineer does and why deployment reliability matters for QA
- Explain the difference between a UI Designer and a UX Designer
- Understand the Support team's role and how their reports feed back into the development cycle
DevOps Engineer — The Keeper of the Pipeline
"It works on my machine" is a phrase that exists because of the gap between a developer's laptop and a production server. The DevOps engineer's entire job is to close that gap.
What DevOps builds and maintains:
- CI/CD pipelines — automated workflows that build, test, and deploy code every time a developer pushes a change
- Infrastructure — the cloud servers, containers (Docker), and orchestration systems (Kubernetes) where the application runs
- Monitoring — dashboards, alerts, and logging so the team knows when something breaks before users do
- Environments — Dev, Staging, and Production environments, each configured consistently
Why this matters for QA: You test on a staging environment. If that environment is misconfigured, your test results are unreliable. If the CI/CD pipeline runs automated tests incorrectly, bugs slip through. Your relationship with the DevOps engineer determines the quality of your testing infrastructure.
Pro Tip: When a bug "only happens in production" — your first call is DevOps. The environment difference is usually the culprit. Ask for environment configuration parity checks.
UX Designer — The Architect of Experience
There are two types of designers you'll encounter. It's worth knowing the distinction:
UI Designer (User Interface Designer): Focuses on the visual layer — colours, typography, spacing, icons, component styling. They produce mockups and style guides. Their output answers: "What does it look like?"
UX Designer (User Experience Designer): Focuses on the interaction layer — how users navigate, where they get confused, what steps they take to accomplish a goal. Their output answers: "How does it feel to use?"
In many teams, one person does both (a "UI/UX Designer"). In larger organisations, they're separate roles.
Why this matters for QA: UX Designers produce wireframes and prototypes — early-stage representations of how the feature should behave. Reviewing these before development starts is one of the highest-leverage activities a QA engineer can do.
If the wireframe shows a three-step checkout flow but the ticket only describes two steps, that's a bug waiting to be born — and you can catch it before anyone writes a single line of code.
Pro Tip: Ask to be included in design review sessions. Every ambiguity resolved at the design stage is five fewer bug tickets later.
Support Team — The Voice of the User
The Support team is the bridge between your users and your development team. They're the first people to hear "I can't log in," "my order disappeared," or "this feature never worked for me."
What Support does:
- Handles inbound user complaints and questions
- Triages issues (is this a bug? a user error? a known issue?)
- Creates bug reports and escalates to development
- Communicates resolutions back to users
How Support data feeds development: A single user complaint might be an isolated incident. Twenty user complaints about the same issue in one week is a P1 priority bug. Support teams aggregate this signal — and that signal should directly influence your testing priorities.
Why this matters for QA:
- Support tickets are an underused testing oracle. Real users find bugs in ways no test case anticipates.
- After a release, monitoring Support ticket volume for new issue patterns is a form of production testing.
- A QA engineer who builds a good relationship with Support has an early-warning system for production regressions.
Career insight: Volunteer to read through recent Support tickets during sprint planning. The patterns you find will make your test cases sharper than any spec document.
The Full Team Picture
PM / BA / PO → define what to build
Frontend / Backend → build it
QA → verify it works correctly
UX Designer → make sure it's usable
DevOps → make sure it reaches users reliably
Support → listen to users and feed back what breaks
No one on this list is optional. Remove any role and something suffers: quality, usability, reliability, or user trust.
Summary
| Role | Core function | QA touchpoint |
|---|---|---|
| DevOps | Pipelines, infrastructure, environments | Environment parity, CI/CD test reliability |
| UX/UI Designer | Usability, visual design, wireframes | Design review for early defect detection |
| Support | User communication, issue triage | Production bug signal, testing oracle |
You've now met the whole team. In the next module, we move into their daily working tool: the ticket tracker.