1.5 YoE in Wi-Fi / Embedded Systems, am I risking getting pigeonholed?
retained text
Hey everyone, I currently have 1 YoE working in the Wi-Fi/embedded space at a Tier-1 networking firm. My day-to-day stack revolves around C, Go, and Bash. My current TC sits around 32–34 LPA (subject to stock performance). The work environment is comfortable and the compensation is solid, but I'm concerned about domain lock-in. Long-term (5+ years down the line), I don't see myself staying in core networking or firmware. My goal is to pivot toward distributed systems and backend engineering. I'm torn between two paths right now: Switching now (\~1.5 YoE): Capitalize on generalist hiring loops (SDE-1/early career) where interviewers test core CS fundamentals, DSA, and basic concurrency rather than deep backend architecture. Staying until 2 YoE: Complete a full 2-year tenure, see initial end-to-end features through, and let RSUs vest. A few specific questions for folks who have made a similar transition: Does hitting the 2-year mark in embedded make it significantly harder to transition without being down-leveled or rejected for lacking production backend/cloud experience? Given my current TC , how realistic are lateral/upward compensation hikes for an early-career SDE transitioning domains into product/backend firms? Since I already use Go alongside C, what specific gaps should I prioritize closing to make my resume stand out for distributed systems roles? Would appreciate honest perspectives from anyone who has successfully navigated a firmware/networking-to-backend pivot.
document fetched 2026-09-24 00:26 · canonical https://reddit.com/r/developersIndia/comments/1wo8y0b/15_yoe_in_wifi_embedded_systems_am_i_risking