Rust Architect for Slint Code Audit and AI Development Guardrails

We are developing a modular, cross-platform business application using Rust, Slint, SQLite, Axum/Tokio, SQLx, Fly.io, and Neon Postgres. We use AI to write much of the application and we are looking for a Rust developer who can spend approximately 1–2 hours each business day reviewing recent work, improving the codebase, and teaching/commenting how to guide AI development effectively. This is a collaborative technical-lead and mentoring role. We do not want someone who simply follows instructions or quietly fixes code. We want someone comfortable challenging weak approaches, explaining better alternatives, demonstrating good Rust design, and helping shape practical development standards. The initial codebase may be rough because much of it was created through AI-assisted development. You will have room to evaluate its structure and recommend how it should be improved. Your work may include: - Reviewing, correcting, and refactoring AI-generated Rust and Slint code - Teaching idiomatic Rust architecture and development practices - Recommending workspace, crate, module, dependency, and testing structures - Identifying unnecessary complexity, duplication, poor performance, and weak boundaries - Reviewing SQLite transactions, migrations, synchronization, and data integrity - Demonstrating when to use structs, enums, traits, composition, async Rust, or simpler functions - Showing which patterns, abstractions, dependencies, and guardrails should be used or avoided - Creating reference implementations and repository guidance for AI - Turning recurring problems into automated checks and better AI instructions - Helping establish a fast, clean daily AI-development workflow The approved platform direction keeps business rules, validation, persistence, synchronization, and state in Rust while Slint focuses on presentation and typed user intent. Project documentation records current decisions, but thoughtful technical criticism is welcome. If you believe a documented approach should change, explain the tradeoffs and recommend a better direction rather than working around it silently. Strong production Rust, architecture, async development, SQLite, testing, profiling, refactoring, and code-review experience are required. Slint, Axum, SQLx/Postgres, offline synchronization, cross-platform applications, and AI coding-agent experience are preferred. The goal is to develop both a strong codebase and a repeatable AI-assisted development system. We are looking for someone whom would enjoy teaching, technical discussion, experimentation, and improving the process as much as writing code. Thank you.