Senior Android Telephony, Security & Blockchain Systems Engineer (Interview Required)

JOB TITLE Senior Android Telephony & Security Systems Engineer (INTERVIEW REQUIRED) READ THIS ENTIRE POST BEFORE APPLYING. FAILURE TO MEET ANY REQUIREMENT = IMMEDIATE REJECTION. OVERVIEW This is NOT a standard Android application. This is a highly technical, engine-based Android security platform with low-level telephony monitoring, network state detection, OTP correlation, and blockchain-related risk engines. This role is for SENIOR, SYSTEMS-LEVEL Android engineers ONLY. No rookies. No generalists. No “full-stack” developers. No improvisation. No assumptions. No mistakes. Every engine is isolated. Every engine is built one at a time. Every engine is tested individually. Every spec sheet must be followed EXACTLY. A LIVE INTERVIEW IS REQUIRED BEFORE HIRING. The interview will explicitly test your real telephony, architecture, and compliance knowledge. If you do not have genuine expertise, DO NOT APPLY. FLUENT SPOKEN AND WRITTEN ENGLISH IS MANDATORY. You must be clearly understandable when speaking. Poor communication = rejection. ──────────────────────────────────────── ABSOLUTE NON-NEGOTIABLE REQUIREMENTS ──────────────────────────────────────── 1. ANDROID TELEPHONY CORE EXPERIENCE (MANDATORY) You MUST have real, hands-on experience with: - TelephonyManager - SubscriptionManager - PhoneStateListener - ServiceState - SIM state transitions - Network registration changes - Multi-SIM handling - eSIM handling (EuiccManager) - Event-driven monitoring (NO polling architectures) If you have not worked at this level, DO NOT APPLY. ──────────────────────────────────────── 2. ENGINE-BASED ARCHITECTURE DISCIPLINE The application consists of TWELVE (12) INDEPENDENT ENGINES. Rules: - Engines are built ONE AT A TIME - Engines are ISOLATED and SELF-CONTAINED - No shared logic unless explicitly defined - No merging engines - No shortcuts - No refactoring or reinterpreting specs - No “better ideas” Each engine must be fully implemented, tested, and approved before moving to the next. ──────────────────────────────────────── 3. SPEC SHEET ABSOLUTISM All functionality is defined in PRE-WRITTEN, LOCKED SPEC SHEETS. Rules: - Specs are LAW - Zero interpretation - Zero deviation - Zero optimization - Zero alternative logic - If anything is unclear, you MUST ASK BEFORE writing code Any deviation = immediate rejection or termination. ──────────────────────────────────────── 4. ACCOUNT OWNERSHIP & ACCESS (NO EXCEPTIONS) ALL work must be done: - Inside MY Android Developer (Google Play Console) account - Inside MY Apple App Store Connect account - Inside MY GitHub repositories - Inside MY Figma workspace Rules: - No private repos - No local-only development - No delayed transfers - No ZIP files - No Google Drive uploads - No “we’ll transfer later” Everything is built directly in my accounts FROM DAY ONE. ──────────────────────────────────────── 5. GITHUB DISCIPLINE - All code committed to my GitHub - Clean, auditable commit history - Engine-by-engine commits - No bundled or hidden work Failure to follow this = immediate termination. ──────────────────────────────────────── 6. API & BLOCKCHAIN ENGINE EXPERIENCE You MUST have experience with: - External API integrations - Secure data ingestion - Risk, monitoring, and alert-driven systems - Blockchain-adjacent data (wallets, addresses, identifiers) This is NOT protocol or smart contract development. This IS correct ingestion, processing, and signaling of blockchain-related risk data. ──────────────────────────────────────── 7. GOOGLE PLAY & APPLE APP STORE RESPONSIBILITY (MANDATORY) You are responsible for: - Google Play Store submission - Apple App Store submission - App metadata and descriptions - Permission justifications - Compliance with Play Store and App Store policies - Handling and fixing rejections - Iterating until approval If you have not handled BOTH Google and Apple submissions before, DO NOT APPLY. ──────────────────────────────────────── 8. COMMUNICATION & PROFESSIONAL STANDARD - Fluent spoken and written English REQUIRED - You must clearly explain technical reasoning verbally - You must be able to follow long, strict technical specifications - You must accept engine-by-engine audits - You must accept zero-mistake tolerance ──────────────────────────────────────── INTERVIEW & HIRING PROCESS ──────────────────────────────────────── - Initial screening - Live technical interview (telephony, architecture, compliance) - Spec comprehension verification - Hiring decision The interview will expose lack of real experience. Do not apply if you plan to rely on AI-generated answers. ──────────────────────────────────────── COMPENSATION ──────────────────────────────────────── rate: $6,000 USD Final compensation increases ONLY with: - Perfect execution - Exact spec compliance - Zero rework - All engines completed correctly - All testing passed - Google Play & Apple App Store approvals achieved - All work delivered directly in my accounts ──────────────────────────────────────── FINAL WARNING ──────────────────────────────────────── If you are: - Junior - A generalist - Looking for creative freedom - Planning to redesign architecture - Planning to optimize specs - Wanting to work in your own accounts - Wanting to move fast and fix later DO NOT APPLY. This role is precision-driven, execution-only, strictly audited, and unforgiving of mistakes. Apply tot his job