Senior Solana Infra Engineer Only – HFT / MEV Trading Bot (Pump.fun, Jito, Jupiter)

I’m running a production Solana trading bot that trades [login to view URL] tokens pre- and post-bonding curve. Version 1 is live. I’m hiring to build Version 2, focused purely on latency, throughput, and execution efficiency. This is NOT a general Solana dev role. This is infra / MEV-level engineering. If you haven’t built low-latency, high-throughput Solana systems in production, do not apply. Scope (High-Level) Aggressive transaction fee + execution path optimization Minimize frontend + backend latency Scale RPC throughput 10 rps → 100–250 rps Bulk transaction execution at high frequency Avoid / mitigate Jito Bundler detection Efficient account & sub-account creation at scale Detect [login to view URL] → DEX migration and automatically switch execution to: Jupiter (JUP) or equivalent swap aggregator System must remain stable under continuous high load Hard Requirements (No Exceptions) You must have hands-on production experience with most or all of the following: Jito Bundlers (behavior, risks, mitigation strategies) Jupiter (JUP) or other Solana swap aggregators [login to view URL] trading mechanics (bonding curve + migration) High-throughput Solana RPC (QuickNode or similar) Sustained 100–250 req/sec RPC workloads AWS infrastructure for low-latency services KMS / secure key management (no plaintext keys) Building latency-sensitive or MEV-style systems on Solana If your experience is limited to: Simple swap bots Retail trading scripts “I’ve used [login to view URL] a bit” This role is not for you. Application Rules Your proposal must include: What Solana trading or MEV systems you’ve built Your direct experience with Jito, Jupiter, or high-RPS RPC Real examples of systems running under load Anything vague or generic will be ignored. Screening Questions (Answer Required) 1. Jito / MEV Experience Describe exactly how you’ve used Jito Bundlers in production. What problem were you solving? How did you handle bundle behavior, ordering, or detection risks? (General or theoretical answers will be rejected.) 2. High-Throughput RPC Handling Have you run sustained 100–250 req/sec workloads on Solana RPC? Which RPC provider (QuickNode / private / other)? How did you handle rate limits, retries, and latency spikes? 3. [login to view URL] → DEX Migration Explain how [login to view URL] bonding curve trading differs from post-migration DEX trading. How do you detect migration? How would you switch execution to Jupiter without downtime? 4. Bulk Transaction Execution Describe a system you built that executed large batches of Solana transactions. How did you manage blockhash freshness? How did you handle transaction failures under load? 5. Fee & Latency Optimization What concrete steps have you taken to reduce Solana transaction latency? Mention compute units, priority fees, pre-signed transactions, or other optimizations you’ve actually used. 6. Key Management & Security How have you implemented secure key storage for automated Solana trading? Have you used AWS KMS or HSMs? How do you sign transactions without exposing private keys?

Projekt-ID: 40224111