Full Stack Engineer

Trust In Soda — United States · Posted ~2 hours ago

Mid Full-time Remote Visa History ✓

Skills

frontend development backend development AI systems agent workflows software architecture Next.js Python AI agents

🔓 Log in to save this job, tailor your resume & track your apply process — 7 days free, no card needed.

Log in to add to target list

Summary ✨ AI‑Generated

A full stack engineer opportunity at an AI-focused organization building intelligent productivity solutions. The role covers frontend, backend, AI workflows, system reliability, and end-to-end product development.

Highlights

Remote engineering role with high ownership, work across frontend, backend, and AI systems, and opportunities to build innovative products from concept to production.

Description

Full Stack Software Engineer AI-native productivity start-up backed by $100mRemote across the USUp to $500k base + equity A $100m-backed AI company is rebuilding everyday productivity tools around agents that actually complete work for users. Their first product is rethinking email. The goal is to reduce roughly four hours of daily inbox work to 30 minutes by allowing AI to understand context, use tools and complete multi-step tasks rather than simply generate responses. What you’ll work on: Build end-to-end features across frontend, backend and AI systemsDesign agent workflows that plan, use tools and recover when things failBuild persistent memory and context across tasks and sessionsImprove streaming, latency, observability and workflow reliabilityTake features from idea through architecture and into production You could be building an approval experience in Next.js one day, then working on the orchestration behind a multi-step agent workflow the next. Tech: Next.js, Python, Node.js, OpenAI, Anthropic, open-source LLMs, SQL/NoSQL, Docker, Kubernetes and PyTorch. You’ll need: Strong full-stack engineering experienceSolid system design and API fundamentalsExperience with LLMs, agents, RAG or AI-powered productsEvidence of shipping features into productionComfort owning problems where the answer isn’t already defined If this sounds relevant, I’d love to chat!