You will either do well or not, from the company's perspective. I don't think that's what's most important, really, it's just a job. My main advice would be to look out for yourself. This sounds like it could get very stressful, and it sounds like the company might not be fully aware of what it's doing. You might end up making a big mistake, or a series of small ones that snowball into a big problem further down the road. That's all fine, they threw you into the deep end of the lake, so they can own the failures - but you still get to take credit for the successes.
There's no way not to learn from this, and there's things you can learn here that you wouldn't learn from years of being in a regular team. So just as you're missing out on valuable experiences here, you'll also be missing out on valuable experience if you change jobs.
The interesting part of a career is also all the non-technical people we meet, and if you're learning from them, that's also good. Maybe this road will take you somewhere more interesting than spending a lot of time on code reviews.
(PS: If this is actually in oil, make sure you're getting paid well.)
There's no way not to learn from this, and there's things you can learn here that you wouldn't learn from years of being in a regular team. So just as you're missing out on valuable experiences here, you'll also be missing out on valuable experience if you change jobs.
The interesting part of a career is also all the non-technical people we meet, and if you're learning from them, that's also good. Maybe this road will take you somewhere more interesting than spending a lot of time on code reviews.
(PS: If this is actually in oil, make sure you're getting paid well.)