Skip to main content
Q&A

Why are you still an automation engineer?

qabash.com
qabash.comAmbassador
2d ago 126 6
AI writes 90% of your code...
Why are you still a automation engineer?

~ credits @nishantgohel

No accepted answer yet

If a comment solves your problem, the author can mark it as the accepted answer.

6 Comments

Sort:
Ishan Dev Shukl
Because writing code was never the whole job. Understanding systems, identifying risks, designing coverage, validating AI-generated tests, debugging failures, and owning quality still require engineering judgment.

AI may change who writes the automation. It doesn't eliminate the need for someone who knows what should be automated, why, and whether the results can be trusted.

The real shift is from writing scripts to engineering quality.
qabash.com

Eventually AI can all do this well atleast for small products. ~ @nishantgohel

qabash.com

That means the real test engineer will always be needed. ~ @abhay

qabash.com
Roles will blend. Same people will do more ~
@ajay184fgmail-com
qabash.com
~ @beinghumantester What we say for coding same definition goes for scripting. Scoping is something that needs human judgement and even if ai can do whole automation the problem lies in accountability that who will be accountable if something is missed.
Dharmendra Kumar
Because writing code was never the whole job.
AI can generate automation scripts. But someone still needs to decide what to test, challenge assumptions, validate results, investigate failures, and determine whether the tests provide real confidence.

The real question isn't “Who writes the code?”
It's “Who takes responsibility for the quality?”

And yes, automation engineers who only write scripts need to rethink their value. 

Join the discussion

Sign in to join the discussion

Sign in