Customer Engineer
About the role
Position Summary
Most of your day will be spent troubleshooting. Enterprise customers using Harness security, feature management, and code coverage products will come to you with complex, often ambiguous issues — and your job is to dig in, find the root cause, and see it through to resolution. You will own issues end-to-end, get on calls with customers, work closely with Engineering and Product to escalate and close problems quickly, and document what you learn so the whole team gets faster.
This is a deeply technical role. You will trace failures through logs and APIs, write scripts when needed, and design solutions when the problem calls for it. We are not looking for someone who routes tickets — we are looking for someone who digs in and solves problems.
This role is structured to grow with you. We invest in developing technical depth across the team, and the breadth of product areas you will work across means there is always something new to learn. If you are earlier in your career and have strong fundamentals and the right instincts, we want to hear from you.
You will develop expertise in the following Harness modules over time. Prior knowledge of any of them is an advantage — but not a requirement. What matters is the ability to pick up a new technical product quickly and work in depth.
- Qwiet (SAST + SCA) — AI-powered static analysis for detecting code vulnerabilities, exposed secrets, and risky open-source dependencies.
- Traceable API Security — API discovery, runtime protection, and security testing integrated into CI/CD pipelines.
- Feature Management & Experimentation — Feature flags, targeted rollouts, A/B testing, and experimentation frameworks for engineering and product teams.
- Codecov — Code coverage reporting and analysis integrated into CI/CD workflows.
About the role
Technical Troubleshooting & Issue Resolution
- Own customer issues end-to-end — from first contact through root cause and resolution — across the product areas above.
- Debug failures across integrations, APIs, agents, scanners, pipeline configurations, and runtime environments.
- Use observability tooling (Datadog, Splunk, Prometheus, CloudWatch, or similar) to trace failures and identify root cause.