Recent CS Grad: Pitched a dev track, but it’s 100% manual testing. People say "stay and learn," but should I run?
retained text
**TL;DR:** Recent CS grad with 1 yr dev experience joined a large, reputable company expecting a path to dev work. It turned out to be 100% manual QA with no real dev track. Senior folks outside my team advise staying to "learn the ecosystem" of a structured org. My alternative is transferring back to my previous role: a completely isolated solo dev with no tech team, no mentors, and a brutal commute, but actual coding. Should I stay for the brand name/structure or run back to coding? **Body:** Hi everyone, I graduated with a B.S. in Computer Science (high GPA) and have \~1 year of dev experience. I recently joined a well-regarded, structured company for a position pitched as leading into software development. Once I started, project leads made it clear: the role is **100% manual QA** (writing test plan documents, clicking through the app, logging bugs). Test automation was framed as a vague "nice-to-have" if I figure it out myself and architect it alone, but our tech stack is notoriously painful for automation, and the dev team already tried and abandoned it. There are no production coding tasks for me. A few experienced devs outside my immediate team told me not to throw in the towel—they argue that being inside a mature organization with Agile/Jira/sprints offers valuable lessons, that I can reframe the experience on my resume, and that patience might pay off. **My dilemma is choosing between two flawed options:** 1. **Stay in the new QA role:** 20-min commute, low stress, structured processes, and a reputable brand name on paper. But the work is completely mindless manual clicking with a massive risk of getting pigeonholed as a tester. 2. **Transfer back to my previous role:** I was essentially a solo dev acting like an in-house freelancer—**zero other software developers, no tech team, no code reviews, and no mentorship.** The daily commute is brutal. However, I was writing code and building end-to-end applications every day while applying elsewhere for proper engineering roles. **Questions:** Does staying in manual QA for the "structure and brand name" hurt my chances of getting hired as a SWE later? Is writing code as a completely isolated solo dev with no team still viewed more favorably by hiring managers than doing manual testing in a structured enterprise? For those who started in manual testing, did you successfully pivot into dev, or did hiring managers treat it as a dead end?
document fetched 2026-10-20 00:24 · canonical https://reddit.com/r/cscareerquestions/comments/1x9q14j/recent_cs_grad_pitched_a_dev_track_but_its_100