For many SAs, they do hands-on coding and code reviews apart from their involvement on the system design/architecture side. For them, their responsibilities are similar to that of a principal/staff engineer. However, I see most new-age companies including FAANG are reluctant to even shortlist their resumes for enginnering interviews seeing their SA experience. Has anyone had similar experience? Did you consider swapping your SA "tag" with a principal/staff engineer tag in your resume? #solutionarchitect #principalengineer #staffengineer #faang
That’s simply not true. Plenty will look at SAs for Eng roles. Especially where the SA demonstrated the technical coding knowledge in past publications
Many of my friends who got recently hired at staff/senior engineering in FAANG had never published a thing in their life. So, you mean, especially for the SAs, to prove their coding capabilities for enginnering roles, they should do publications as well apart from going through regular coding rounds as part of the interviews? I understand publications are good for anyone in tech, not especially for SAs to pro e their coding skills
Yeah people have the notion that SA are sales people when we are actually very very far from that. Idk who even created that myth. I think they don’t take us seriously as engineers because we don’t push code into production. The code we write is to “demo” to customers or create workshops, it’s not directly tied to a product. So eventhough we can hold high level discussions, they think we don’t have enough credibility to be called “senior or principal/staff” engineer
Principal Eng don’t code either ;)
They did work their way up there tho, to deserve that low to no code life