8 Comments

I signed in just to say this.

1. You’re simultaneously complaining about data engineers being lone wolfs, and also having their hands held.

2. You then complain about DE’s not seeing the bigger picture? Are in those meetings? Is their input included in those meetings? Or, are they just given a ticket and expected to move on.

3. You assert that data engineers make a mess. That’s an engineering culture issue, and not an individual issue.

4. Having a generic CV is the best way to get through an ATS system. That’s a feature, not a bug

5. Half of these are organizational issues, and it looks like you work for or run a crappy organization.

Expand full comment

Appreciate your thoughts!

Expand full comment

Uhm, given the flak on generic CVs in the intro, what do you recommend to stand out?

Expand full comment

I get this question a lot. It depends on the person, but it takes minimal effort ... say a GitHub profile with some actual code and personal stuff in it. I pretty much straight delete any CV that doesn't have this ... and 90%+ do not.

Expand full comment

Well sir you’ve just described myself to the tee. Especially the lone wolf bit.

Expand full comment

Working on it !

Expand full comment

Sorry!

Expand full comment

Wait, what? I'd definitely put someone with those traits in the junior section. I mean, I understand skill levels can vary depending on the company. Still, I assume that someone in a mid-level position would, at least, be capable of mid-term planning.

Expand full comment