This message was deleted.
# general
s
This message was deleted.
s
This definitely sounds like a data engineering role. I think there's a risk of this being a "create the hard dashboards and reports" role. Your best bet is to ask questions to get a clear understanding of the role during the interview process. This definitely isn't SRE, DevOps, or Platform Engineering.
h
It's in a separate team to the DE team
I think they have essentially taken the orchestration & pipeline maintenance aspects of the role & out them onto a separate tema
Team*
s
Yeah... that's what worries me 😄
h
It won't be dashboards and reports though (there is a separate team for that 😂)
s
Whenever you have splits like this, you end up tossing work around - I bet when a dashboard or report gets really hard to do, they're going to ask you to sort it out. It will be a bit like first-line / second-line. (Possibly - you'll need to ask these questions and have a clear thought about whether you'll still proceed if they say that you "might be helping with more complex reporting requirements" - or other code words for this)
h
Can I DM you?
s
Sure - feel free to ping me a DM.
h
Thanks!
h
That does sound more like dataops
Almost like sre but for datamodels
l
Hey H, if you are thinking of accepting the role, I am guessing you have been through an interview process? Have you had the chance to ask the hiring manager exactly what the role will involve? Perhaps that's the next step, to deep dive into what you will be doing and what the main aim of the role is? It's probably the best place to start