Role TItle: Rust Architect / Backend Developer Location: Global, fully remote Job Type: Contract (~15 hours per week) Schedule: Flexible—you can choose the hours and days you work, including weekends if desired (As long as you're active) Required Skills: • Rust • DevOps We are looking for a highly skilled Rust Architect / Backend Developer to contribute to an AI-training project involving production Rust, backend architecture, asynchronous and concurrent systems, service design, infrastructure, and technical debugging. The role requires strong programming ability and the judgment to evaluate whether backend systems are correct, reliable, maintainable, and suitable for production use. Scope of Work: • Solve and validate Rust backend problems involving service behavior, APIs, persistence, concurrency, performance, and reliability. • Translate functional requirements, performance targets, and failure-handling expectations into reproducible implementation and testing workflows. • Prepare Rust crate workspaces, configuration files, test fixtures, dependency services, databases, and containerized environments. Preferred Qualifications: • Strong knowledge of Rust, backend service design, APIs, data systems, concurrency, and production software architecture. • Experience formulating and completing technical analyses involving backend correctness, performance, scalability, or reliability. • Practical proficiency with Rust in substantial professional, research, or open-source software • Clear Rust Architecture ownership Compensation Structure: Compensation is output-based; experts are paid per task that meets the project specifications. The time required to complete work may vary depending on the expert’s experience and workflow. Minimum submission requirements apply. Experts must submit a minimum of tasks per week. Start Timeline & Availability: We typically fill roles within 48 hours and are looking for experts ready to jump in right away. If selected, we expect you to start your first tasks within 24–48 hours of completing onboarding. Originally posted on Himalayas