If you're already in QE, you likely write some code, understand systems from the outside, and know where things break. This track assumes that baseline and focuses specifically on the gaps between "QE who scripts" and "Developer" — DSA fluency, system design literacy, and developer-standard workflows.
Arrays, strings, linked lists, trees, graphs, and the problem-solving patterns (two pointers, sliding window, BFS/DFS, dynamic programming basics) that interviews actually test — practiced until they're reflexive, not memorized.
Scalability basics, database design trade-offs, API design, caching, and load balancing concepts — enough to hold your own in a system design interview round, and to understand the systems you've been testing at a deeper level.
Git branching strategies (not just basic commits), meaningful code reviews, clean code principles, and the habits that separate "writes scripts" from "ships production code."
Technical mock rounds specific to dev roles, resume repositioning that reframes your QE experience as a strength (not something to hide), and portfolio projects that demonstrate development — not testing — skill.