Android Native Behavior Specialist

We're looking for a specialist with deep knowledge of Android app internals to help us understand how certain early native behaviors affect runtime observability.The app we're analyzing uses early initialization blocks (static()) to load native libraries (System.loadLibrary()), which appear to include some form of self-verification or integrity assurance.We're interested in strategies for inspecting or monitoring these components during early runtime without disrupting their behavior — especially in environments where conventional runtime inspection tools may be noticed.

This is a highly technical role and would suit someone with experience in: Native code behavior analysis

Runtime instrumentation strategies

Working around early-stage initialization hurdles

Observability under constrained environments.

Deliverables: 

Technical insights into initialization flow

Suggestions for safe observation or behavioral mapping

Optional script or PoC for internal research purposes

https://play.google.com/store/apps/details?id=my.com.tngdigital.ewallet&hl=en&pli=1

We need to run this app on Rooted Emulator (using Android Stuid if possible), we need to be able to use Frida Hook to inject code into the app method

We need you to provide details report on how to bypass the Rooted Emulator/Tampering checking and prove on able to run Frida Hook.

As the app might force users to update their App Version, we need to know how to bypass the Rooted Emulator/Tampering detection in details so that we can bypass by ourself in the future even when the App gt updated