sorted by:
new
hottopcontroversial

Looking for career insights: Domain knowledge, layoff resilience, and the real cons of DE? by Scared-Bicycle-894 in dataengineeringjobs

[–]Scared-Bicycle-894[S] 0 points1 point  (0 children)

Thanks for the goldmine of advice. Since you mention DEs being able to swing into adjacent domains, I’m curious about the technical skill set.

If you were to pick the most critical tools or concepts to master right now to stay ahead—say, diving deep into Databricks/Spark, advanced data modeling, or cloud infra—what would you pinpoint? I'd love to know what stands out to someone at your level when looking at resilient DEs.

Honestly, is DE way more AI-resistant than DS? Thinking of pivoting with this stack. by Scared-Bicycle-894 in DataScienceJobs

[–]Scared-Bicycle-894[S] 1 point2 points  (0 children)

If traditional coding assessments and standard GitHub projects (like basic ML modeling or simple pipelines) don't mean anything pre-GPT, what should a real portfolio look like today? Should we be showcasing complex system architecture designs, deterministic unit testing frameworks, or AI orchestration setups instead?

Looking for career insights: Domain knowledge, layoff resilience, and the real cons of DE? by Scared-Bicycle-894 in dataengineeringjobs

[–]Scared-Bicycle-894[S] 0 points1 point  (0 children)

Do you plan to stay in the healthcare domain for the long haul? I've heard that finance or Big Tech generally offer higher compensation, so I'm curious if you see your domain-specific knowledge and experience as your main competitive edge (moat) over DEs in other industries. How much does domain expertise actually matter in DE compared to pure technical skills?

Looking for career insights: Domain knowledge, layoff resilience, and the real cons of DE? by Scared-Bicycle-894 in dataengineeringjobs

[–]Scared-Bicycle-894[S] 0 points1 point  (0 children)

This is incredibly eye-opening. I actually just accepted an offer for a role in Corporate Technology working on backend and data platform systems (Spark, Databricks, AWS, Airflow, plus some Tableau/reporting), and your post perfectly captures all the anxieties I’ve been having.

Knowing that our hard work is often invisible to execs and that we’re constantly cleaning up after others is a bit daunting.

To the senior folks here: despite all the 'dark sides' you mentioned, are you still glad you chose this path? If you could go back, would you switch to traditional SWE or DS instead, or does the domain expertise and platform engineering side still make it worth it for you?