> Markdown version of [/jobs/ext/2685420-software-engineer-1](https://www.wearedevelopers.com/jobs/ext/2685420-software-engineer-1). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Software Engineer 1 - **Company:** project 44, Inc. - **Location:** United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Code Review, Software Debugging, Monitoring of Systems, Software Engineering, Systems Integration, Datadog, Large Language Models, Multi-Agent Systems, Prompt Engineering, Event Driven Architecture, Apache Kafka, Stream Processing - **Published:** September 2, 2026 - **Apply:** https://job-boards.greenhouse.io/project44/jobs/8124404 ## About the Role * Prior experience in a forward-deployed, field engineering, or support engineering role * Experience with event-driven architecture and stream processing (Kafka, PubSub, or similar) * Familiarity with observability tooling for agent/LLM systems ## Description project44 is looking for a Senior Software Engineer 1 to join our engineering team. You will work in a fast-paced Agile environment designing, building, and implementing best-in-class integrations to accelerate how project44 connects to the world's logistics networks. The Role Most support engineers respond to tickets. Internally Deployed Engineers (IDEs) rebuild the response itself. You'll work directly with Customer Facing teams - Support, Customer Success, Solutions - to rapidly design and build multi-agent systems that resolve customer problems with speed and quality. This isn't about shaving minutes off response time. Your job is to replace the reactive, human-in-the-loop support model with autonomous agent workflows that diagnose, resolve, and escalate on their own. You embed with the teams closest to customer pain, learn exactly where the current model breaks down, and ship agents that fix it - in weeks, not quarters. What You'll Work On * Partner embedded with Support/CS/Solutions teams to identify recurring, resolvable customer issues and design multi-agent workflows that handle them end-to-end * Build and iterate on agent architectures - context retrieval, tool invocation, decision logic - that diagnose issues, pull the right data, and take action across internal systems * Feed agents the right context and debug failures, tracing a bad resolution back to the specific data point, prompt, or tool call that caused it * Instrument agent performance (accuracy, resolution rate, escalation rate) and iterate quickly based on real outcomes, not assumptions * Design and own team-level technical solutions end-to-end, not just the parts that are easy to hand off * Translate patterns observed in the field - what Support actually struggles with - into product and roadmap input for the broader engineering org Technical Aptitude * Writes meaningful code reviews for agent tooling and integration code. * Debugs systematically across distributed, non-deterministic, agent-driven workflows - sometimes with help from more senior engineers. * Helps improve monitoring and observability for agent decisions and outcomes. * Helps define testing processes for inherently non-deterministic agent behavior and keeps tests current. * Handles ambiguity well; makes reasoned tradeoffs on abstraction level, latency versus accuracy, and autonomy versus human-in-the-loop. * Approaches work with a security lens, particularly around agent write-access into customer-facing systems. * Independently scopes flexible technical solutions and breaks down specs into stories. * 6+ years in software engineering, ideally with some customer-facing or support-adjacent exposure * Experience building or integrating agentic/LLM systems - context feeding, prompt engineering, tool invocation, stateful agents, How You Work * You take ownership of outcomes, not just deliverables * You bring back what you learn from Support/CS and use it to make the agents - and the roadmap - better * You move fast, iterate in the open, and don't wait for perfect conditions * You can translate technical complexity to both engineers and support operators without losing either audience In-office Commitment: This position requires a commitment to contribute to our collaborative culture by working in-office Three days weekly. ## Related Videos - [Teaching an LLM to review code … like a Senior Engineer!](https://www.wearedevelopers.com/videos/100324-teaching-an-llm-to-review-code-like-a-senior-engineer) - [Debugging in the Dark](https://www.wearedevelopers.com/videos/1658-debugging-in-the-dark) - [How to Benchmark Your Apache Kafka](https://www.wearedevelopers.com/videos/76-how-to-benchmark-your-apache-kafka) - [Are Code Reviews Worth It? Insights from 16 Years of Review Data](https://www.wearedevelopers.com/videos/1135-are-code-reviews-worth-it-insights-from-16-years-of-review-data) - [The AI Velocity Trap: Shipping Faster Without Breaking More](https://www.wearedevelopers.com/videos/100326-the-ai-velocity-trap-shipping-faster-without-breaking-more) - [Completing the Feedback Loop](https://www.wearedevelopers.com/videos/100351-completing-the-feedback-loop) ## Related Articles - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 132 - Binging WADFlix?](https://www.wearedevelopers.com/magazine/473-dev-digest-132-binging-wadflix) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Fully Remote Software Engineer Jobs](https://www.wearedevelopers.com/magazine/447-fully-remote-software-engineer-jobs) - [Where To Find Software Engineering Jobs](https://www.wearedevelopers.com/magazine/396-where-to-find-software-engineering-jobs)