4 ms·
Yeah I’m thinking of changing my title back to software dev instead of DE - it’s sort of getting a bad rep.
by ed_elliott_asc 3y ago
Yeah I’m thinking of changing my title back to software dev instead of DE - it’s sort of getting a bad rep.
- fifilura 3y agoHow do you define "bad rep"?
- opportune 3y agoA lot of “data engineers” are former db analysts and such that don’t know much of anything technically outside of SQL and even that might be something they only are “certified” to know rather than actually good at. It’s basically becoming a title I’d associate with being low-skill. I used to be a “software engineer in data” and never call myself a data engineer because people would think I don’t know how to write/maintain production services, just write ETL pipelines
- fifilura 3y agoOk I guess you neew to find the worplace that suits you. Just that I have had some recent experience with muti threaded java k8s services reading daily "streams" from Kafka. When a SQL query would have solved it.
- free_flintshire 3y agoMany such cases in the data space of CV building over problem solving
- fifilura 3y agoI guess you have to decide what you want on your CV. "I solve problems" or "I build complex stuff".
- DanielVZ 3y agoI made the change from SWE to DE a few months ago and several fellow SWEs saw it a first glance as if I was downgrading into a less technical role. They assumed it was some kind of modern DBA. I’ve always seen it as a Data Oriented Software Engineer but it seems that isn’t always the case, specially recently where I’ve been offered jobs that were basically analyst roles or BI roles.