Tech Support Engineer (Node / API): TON Foundation

You are the "Tier 3" Support for the entire TON Ecosystem. This is not a customer service role. You are the technical lifeline for Exchanges (CEXs), DeFi Protocols, and Game Developers building on TON. When a major partner (like a top-tier exchange) cannot process withdrawals because their node is out of sync, or a Telegram Mini App fails to load because of API errors, you are the person who fixes it.

The "TON" Challenge: TON is an asynchronous, sharded blockchain. This architecture is radically different from Ethereum (EVM).

Ethereum: Synchronous transactions (simpler).

TON: Actor model, asynchronous message passing (complex). Your core value: Helping traditional developers "unlearn" synchronous habits and debug the unique race conditions and architectural quirks of TON.

## Key Responsibilities
The "Node Doctor": You troubleshoot the Native C++ Node. This is systems-level work. You need to diagnose why a node is lagging, why MyTonCtrl (the orchestration tool) failed, or why the database is corrupted.

Skill: Linux sysadmin, log analysis, systemd, hardware resource tuning.

The API Consultant: You aren't just fixing bugs; you are advising on Architecture.

Example: A partner is spamming getTransactions and getting rate-limited. You teach them how to use TON Indexers (PostgreSQL) to query data efficiently instead.

The Code Debugger: You troubleshoot SDK implementations. If a partner's JavaScript script (@ton/ton) is failing to sign a transaction, you need to read their code and spot the error.

## Strategic Analysis
The "PostgreSQL" Signal: The JD specifically mentions "Assist with building complex PostgreSQL queries."

Insight: This implies you will support partners using TON Indexer solutions. You need to be comfortable writing complex SQL joins to extract on-chain data, as standard APIs might not cover every edge case.

High Stakes: You are supporting "staking protocols for CEXs." A mistake here means an exchange might slash user funds or fail to pay rewards. Precision is non-negotiable.

The Bridge to Core: You are the filter for the Core Dev team. You must reproduce bugs with 100% accuracy so the core C++ engineers don't waste time.

## Candidate Profile: The "DevOps Support" Hybrid
The SysAdmin: You are comfortable in a Linux terminal. You know how to check disk I/O, memory usage, and network latency.

The Developer-Adjacent: You can read code (C++, JS, Java) even if you don't write it from scratch daily. You understand JSON-RPC and REST API structures perfectly.

The Diplomat: You are dealing with stressed-out partners who might be losing money every minute their system is down. You need to be calm, authoritative, and helpful.

## Critical "Knockout" Criteria
Infrastructure Experience: You must have experience running servers, nodes, or high-availability web services.

API Mastery: Understanding the difference between a 400 Bad Request (user error) and a 500 Internal Server Error (node error) and how to fix both.

TON Specifics (Bonus): If you know how FunC or Tact (TON smart contract languages) work, you are a top 1% candidate.