Все категории

Переводчики и ин.языки

Поиск клиентов для переводчиков, лингвистов, преподавателей осложнен спецификой профессии. Мы предлагаем не тратить время зря, а лишь периодически просматривать отобранные запросы от тех, кому могут понадобиться ваши знания, навыки и услуги. Подпишитесь на всегда свежую информацию!
591 объявление найдено за последние 3 дня
Здесь показаны примеры поиска клиентов недельной давности.
Подписывайся, чтобы получать информацию обо всех новых клиентах в режиме реального времени!
Our SaaS platform already serves millions of visitors across 300+ branches, and new features keep piling up. I need a reliable developer who can stay with us for the long haul, taking ownership of backend work in Laravel and Python while pushing new UI pieces in React. You’ll also help wire advanced AI/LLM functionality into existing services, so being comfortable with tools like ChatGPT and Claude is important. Day-to-day you’ll: • Extend and refactor APIs, queues, and micro-services in Laravel or Python. • Build or enhance React components that consume those endpoints. • Prototype and integrate AI/LLM features (content generation, semantic search, agent workflows). • Ship to Ubuntu 22.04 VPS instances and keep an eye on performance, ideally with PostgreSQL on the back end. What makes you a good match – 3–5 years solid experience with React (your strongest area), plus competent Laravel and Python. – Habitual use of ChatGPT, Claude, or similar assistants to speed up research, testing, and documentation. – Clear English, quick responses, and predictable availability. Nice extras PostgreSQL tuning, Docker, DevOps on VPS, prior LLM production work. When you apply, please: 1. Summarise your JavaScript/TypeScript background. 2. Explain exactly how you rely on AI tools in your workflow. 3. Tell me the soonest date you could start and how many hours a week you can commit. 4. Add links or repos that best showcase past work relevant to this stack. I’m aiming for 30+ hours per week but can flex to hourly milestones once we’re rolling. If you thrive in a fast iteration environment and want a stable, ongoing partnership, let’s talk.
9 апреля 01:08
На постоянную основу нужен человек со знанием Русского языка Работа в горячем кошельке Trust Wallet/ MetaMask Полный рабочий день (14:30–20:30) — 370$ в неделю Для получения информации напишите "+" 👉🏻 @sergey_burovv
9 апреля 17:44
Alyonka♡Vitalievna, если вас интересует список переводчиков для сопровождения на термины, то его можно найти в закрепленных сообщениях [Ссылка: https://t.me/hilfe_ukraine_chemnitz/51667]
9 апреля 20:03
Германия, Хемниц
Добрый вечер. Нужен переводчик в Джобцентр в Аусбурге на 14.04.
9 апреля 21:36
Германия, Аугсбург
ищу репетитора по русскому языку для подготовки к огэ.
9 апреля 10:20
Копейск
На постоянную основу нужен человек со знанием Русского языка Работа в горячем кошельке Trust Wallet/ MetaMask Полный рабочий день (14:30–20:30) — 370$ в неделю Для получения информации напишите "+" 👉🏻 @sergey_burovv
9 апреля 16:13
Здравствуйте , есть ли тут бахгалтеры? Напишите в лc пожалуйста
9 апреля 23:11
Венесуэла, Барселона; Венесуэла, Валенсия; Испания, Мадрид; Испания, Барселона
IMPORTANT: Read every word carefully. Automated bids and generic proposals will be permanently ignored. If you are looking for a simple "bot job," move on. This is a system engineering challenge. READY-TO-UPGRADE 1. The Reality & The Partnership (Human to Engineer): I am the project owner, but I am NOT a programmer. This framework was built on a solid foundation by a brilliant mind who is no longer with us. I am managing this legacy using AI tools and limited technical knowledge. I don't need a freelancer; I need a proactive partner. You must be someone who initiates ideas, asks "What if?", and treats this system as if your own reputation is on the line. If we don't catch tickets during a 1-million-user traffic spike on April 23, 2026, the system is worthless. You must be prepared to explain every technical move to me in plain English so I can understand the "Why" behind the "How." 2. The Target Ecosystem (Webook + Seatcloud): We are targeting a dual-layered, high-security environment: • The WebSocket Layer (Seatcloud): We bypass all frontend abstractions. We connect directly to raw WebSockets, maintaining persistent, multiplexed streams to monitor and "hold" up to 30 seats in milliseconds. • The REST API Layer (Webook): We orchestrate mass-checkouts using curl_cffi to impersonate high-entropy Chrome fingerprints (TLS/JA3/HTTP2). 3. The Technical Core: Hybrid Master/Receiver Distribution We are moving away from standard Python concurrency. We need a Low-Latency Hybrid Engine (latency < 1ms): • C/Rust Shared-Memory Ring Buffer: You must architect a Ring Buffer in POSIX shared memory via a C or Rust extension. • Lock-Free Concurrency: The Master node must write "Session Packages" (JWT, Cookies, holdTokens) using Atomic Head/Tail Pointers. There must be zero mutex contention. • GIL Elimination: The distribution pipeline must reside outside the Python Global Interpreter Lock. Even with 300+ session packages in flight, the Master network loop must remain untouched. • Zero-Copy Logic: Receivers must consume data directly from memory offsets without serialization or copying. 4. Defensive & Stealth Engineering (The Invisible Predator): • Dynamic Mutation Defense: At the moment of the drop, the platform mutates JS files and API signatures. You must implement a Real-time Discovery Engine (AST-based or regex-dynamic) to adapt our payloads in milliseconds. Static keys mean instant failure. • Behavioral Jitter: We need a heuristic layer that applies micro-delays (50ms–150ms) to outward traffic to mimic human behavior, while our internal hand-off remains at sub-1ms speeds. • Captcha Token Pooling: tokens must be pre-solved via 2Captcha/CapMonster and cached in memory for 0ms injection latency. • Autonomous Proxy Management: I use DataImpulse Residential (Sticky Sessions). The system must proactively handle 407, 403, and 5xx errors. If a proxy fails, the bot must rotate and re-auth without me lifting a finger. 5. Non-Blocking Control Layer (The Dashboard): • Isolated GUI: A lightweight FastAPI/Websocket dashboard. • Strict Constraint: The GUI must run in a completely isolated process. It must have zero shared resources with the core sniping loop. If the GUI crashes, the bot must keep hunting. 6. What I Expect from You (The Proactive Partner): • Initiative is Mandatory: Don't wait for me to find a bug. Stress-test the system, find the bottlenecks, and propose the fix. • Educational Support: Since I am not a coder, you must provide detailed documentation and walkthroughs for every update. I need to know the system is ready before the "combat" starts. • Live Combat availability: You MUST be live with me on April 23, 2026. We will be monitoring logs in real-time, adjusting jitter, and adapting to server-side changes on the fly. How to Apply: Show me your brain, not your resume. Address these 4 points: 1. How will you handle Cache-Line Alignment in the Ring Buffer to avoid "False Sharing" during a high-speed burst? 2. How will you ensure the Master process remains 100% stable if the C-extension encounters a memory fault? (Explain the Watchdog/Safe Wrapper logic). 3. Given that I'm not a technical expert, how will you visualize real-time performance metrics so I can see the bot's health during the drop? 4. Confirm your availability for the April 23 live operation. If you are a "regular" developer, please don't apply. I am looking for a systems engineer who wants to win.
10 апреля 00:55
Подписывайся, чтобы получать информацию обо всех новых клиентах в режиме реального времени!
 Попробовать бесплатно
© 2015-2026, SHIKARI
Контакты
Пользовательское соглашение
Политика конфиденциальности