2 ms·
Maybe you have already, since it sounds like you've communicated your feelings, but if you haven't yet I'd specifically talk about when you'll be able to work t
by freedomben 8y ago
Maybe you have already, since it sounds like you've communicated your feelings, but if you haven't yet I'd specifically talk about when you'll be able to work the job description they hired you for. Might be worth sticking it out in the short term. I've seen people leave just a little too early many times and it's a shame.
- patagonia 8y agoAgreed, I insisted we finally talk timelines about 0.75 years ago, or just call it a bad fit no hard feelings. Expectations were set that were not followed through with on the company’s side, and so we had an additional series of escalating conversations. I have finally, about 2 months ago and 1.75 years after starting, been transitioned into tasking more in line with my hiring job description. However the technology our team manager has transitioned our team to during that time is a deal breaker for me. He has almost completed removing all Python code from our code base / tech stack (from what I can tell, because he doesn’t want to learn Python this late in his career despite it being the lingua fanca of data teams), has taken over and basically killed the version control set-up me and another (now ex) team member set up, and has us using a GUI based ETL software that basically no one in my job market is using, CloverETL (now CloverDX). With that as my recent experience it’s been difficult to find a new gig, so it’s back to nights and weekends refreshing my resume / skill set. It was all a lesson in how to professionally draw a line as to what I will do for a company. Lesson learned.