Long story short, I work as a data scientist in a small team. The working environment is quite unusual. Key facts:

• The lead data scientist's technical expertise wasn't checked during the interview (it turned out they didn't know how to use Linux, git, Python, never heard about concepts such as pull requests, never worked with a server before, etc.)
• Their managers don't know much about data science (admitted by themselves), so the lead data scientist has survived so far.

I am responsible for a specific project, related to a niche area where I am truly a SME. The project is in production and works fine.

The lead data scientist decided to replicate my project, they made some changes, and they were successful in selling a fair amount of hot air to the senior managers about the need to improve and revamp my models.

Now, the senior managers want me to review their code and improvement claims, and check if there is anything of value that could be merged into the project I am responsible for.

I don't see the benefit of reviewing thousands of lines of code, written without unit tests, and scrolling through functions 2,800+ lines long (According to the senior managers bad code is fine as long as it works).

In my view, it is not my duty as a junior coworker (who is at least one grade lower than the Lead data scientist) to review the code and modelling of the technical lead.

1. Should I directly refuse to analyse and review the twin project of the tech lead?

2. I feel annoyed about the existence of this twin project. Would I be right to complain about it, or is it normal in the industry to duplicate projects and step into other coworkers' shoes?

3. The compensation is competitive but I am concerned that I am not learning much in this team and a lack of technical development could come to haunt me later and might hinder my career. Should I leave even taking a pay cut, or even without a next job lined up?

Thank you.

Long story short, I work as a data scientist in a small team. The working environment is quite unusual. Key facts:

• The lead data scientist's technical expertise wasn't checked during the interview (it turned out they didn't know how to use Linux, git, Python, never heard about concepts such as pull requests, never worked with a server before, etc.)
• Their managers don't know much about data science (admitted by themselves), so the lead data scientist has survived so far.

I am responsible for a specific project, related to a niche area where I am truly a SME. The project is in production and works fine.

The lead data scientist decided to replicate my project, they made some changes, and they were successful in selling a fair amount of hot air to the senior managers about the need to improve and revamp my models.

Now, the senior managers want me to review their code and improvement claims, and check if there is anything of value that could be merged into the project I am responsible for.

I don't see the benefit of reviewing thousands of lines of code, written without unit tests, and scrolling through functions 2,800+ lines long (According to the senior managers bad code is fine as long as it works).

In my view, it is not my duty as a junior coworker (who is at least one grade lower than the Lead data scientist) to review the code and modelling of the technical lead.

1. Should I directly refuse to analyse and review the twin project of the tech lead?

2. I feel annoyed about the existence of this twin project. Would I be right to complain about it, or is it normal in the industry to duplicate projects and step into other coworkers' shoes?

3. The compensation is competitive but I am concerned that I am not learning much in this team and a lack of technical development could come to haunt me later and might hinder my career. Should I leave even taking a pay cut, or even without a next job lined up?

Thank you.

=======

Edit: Thank you for all your kind answers. They've brought clarity to my mind. I've gathered that:

1. It is my job duty and the professional thing to do to review models and code, no matter who has written it, or how poorly written it is.
2. Ultimately, the senior managers above the Lead are the ones who bought the Lead's hot air and authorized a cloned project (with or without being tricked into it, which is irrelevant), so they are responsible for the awkward situation, even more than the Lead.
3. I should choose my next company more carefully, not everything that shines is gold.
4. I should resign ASAP.

Long story short, I work as a data scientist in a small team. The working environment is quite unusual. Key facts:

• The lead data scientist's technical expertise wasn't checked during the interview (it turned out they didn't know how to use Linux, git, Python, never heard about concepts such as pull requests, never worked with a server before, etc.)
• Their managers don't know much about data science (admitted by themselves), so the lead data scientist has survived so far.

I am responsible for a specific project, related to a niche area where I am truly a SME. The project is in production and works fine.

The lead data scientist decided to replicate my project, they made some changes, and they were successful in selling a fair amount of hot air to the senior managers about the need to improve and revamp my models.

Now, the senior managers want me to review their code and improvement claims, and check if there is anything of value that could be merged into the project I am responsible for.

I don't see the benefit of reviewing thousands of lines of code, written without unit tests, and scrolling through functions 2,800+ lines long (According to the senior managers bad code is fine as long as it works).

In my view, it is not my duty as a junior coworker (who is at least one grade lower than the Lead data scientist) to review the code and modelling of the technical lead.

Q1. Should I directly refuse to analyse and review the twin project of the tech lead?

Q2. I feel annoyed about the existence of this twin project. Would I be right to complain about it, or is it normal in the industry to duplicate projects and step into other coworkers' shoes?

Q3. The compensation is competitive but I am concerned that I am not learning much in this team and a lack of technical development could come to haunt me later and might hinder my career. Should I leave even taking a pay cut, or even without a next job lined up?

Thank you.

Long story short, I work as a data scientist in a small team. The working environment is quite unusual. Key facts:

• The lead data scientist's technical expertise wasn't checked during the interview (it turned out they didn't know how to use Linux, git, Python, never heard about concepts such as pull requests, never worked with a server before, etc.)
• Their managers don't know much about data science (admitted by themselves), so the lead data scientist has survived so far.

I am responsible for a specific project, related to a niche area where I am truly a SME. The project is in production and works fine.

The lead data scientist decided to replicate my project, they made some changes, and they were successful in selling a fair amount of hot air to the senior managers about the need to improve and revamp my models.

Now, the senior managers want me to review their code and improvement claims, and check if there is anything of value that could be merged into the project I am responsible for.

I don't see the benefit of reviewing thousands of lines of code, written without unit tests, and scrolling through functions 2,800+ lines long (According to the senior managers bad code is fine as long as it works).

In my view, it is not my duty as a junior coworker (who is at least one grade lower than the Lead data scientist) to review the code and modelling of the technical lead.

1. Should I directly refuse to analyse and review the twin project of the tech lead?

2. I feel annoyed about the existence of this twin project. Would I be right to complain about it, or is it normal in the industry to duplicate projects and step into other coworkers' shoes?

3. The compensation is competitive but I am concerned that I am not learning much in this team and a lack of technical development could come to haunt me later and might hinder my career. Should I leave even taking a pay cut, or even without a next job lined up?

Thank you.