this post was submitted on 08 Jul 2026
3 points (100.0% liked)
CSCareerQuestions
2462 readers
1 users here now
A community to ask questions about the tech industry!
Rules/Guidelines
- Follow the programming.dev site rules
- Please only post questions here, not articles to avoid the discussion being about the article instead of the question
Related Communities
- !programming@programming.dev - a general programming community
- !no_stupid_questions@programming.dev - general question community
- !ask_experienced_devs@programming.dev - for questions targeted towards experienced developers
Credits
Icon base by Skoll under CC BY 3.0 with modifications to add a gradient
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Testing isn't a strictly manual process. You may be writing auto tests, you may be writing tools, you may be branching out into general uptime maintenance. You may even be programming features. All that's gonna depend on what orgs you join and what you are prepared to bring to the table.
Also worth considering the impact on AI in the field. Some orgs are gonna nix QA entirely and rely on AI to generate tests. Others are gonna move more toward TDD with AI using the manually created tests as a guide for the development of features. Still others are just gonna want some assurance that the AI puked up slop that kinda works.
I'm currently a SWE, but I know several people (many who make more than me) who've successfully pivoted into SDET roles and love what they do.