What to do? My current job will suck very soon.

Thorkell wrote: ↑ Some context : I was in Finance before this role and this current role was a career change. The role involves systems analysis, configuration, maintenance, migration work, development, and user training . It was something I prepped for during the lockdowns last year and was very excited to land the role.

It looks like my role/title and pay will remain the same but they will change my tasks to something absolutely mundane towards master data stuff and reporting because our company got taken over by a MNC, with their IS people being in the UK. I really had to fight for myself but its an uphill climb and now there is little hope. It looks like my VP knew all along but didn't say anything to keep me going.

Do I stay? If I should move on, does a 1 year experience suffice after a career change? Or should I remain in the same role, and use the description of the 1st year of my duties, and leave out the new duties? Mind you the work is a lot easier, but at this stage I wanted to continue to challenge myself and not settle. I have until the end of this year when the duties start to slowly change.


Thanks

pandorazw wrote: ↑ I thought data is a buzz word right now and lots of people want to get into the field with employers misusing title like data scientist every where.

Care to elaborate why master data stuff and reporting is mundane?

Thorkell wrote: ↑ Depends on the company. Some companies its a buzzword and very few have a legitimate DS department. I find most of it being oversold and overhyped, specially in large and bureaucratic organizations who still rely a lot on excel. I interviewed for a Business Intelligence role not too long ago, sounded like DS stuff, but after clarifying with the recruiter the company needed someone good with PowerBI.

Reporting is mundane - once you have built a dashboard or a spreadsheet based report for the end users, you are done. On to the next or nothing at all until they require a minor change which could be once every 3 months.

Jon Lai wrote: ↑ As with any job, a successful employee creates value for themselves, and not just excel at what they do. Why would you wait for "them" to require a minor change? Talk to people, find out what their pain points are, and take the initiative to make those changes without anyone asking, then set up a meeting and show everyone what you've done and how to use your new tools/features.

motomondo wrote: ↑ I would agree with you, but the main problem that the OP mentioned is that the company was acquired by another organization.

With centralized IT teams in another country, eventually the OP may be left without a job. The time to start looking for something new is now.