Back to jobs

Senior AI Software Engineer (.NET)

Pay
Pay not listed
Work setting
Not stated
Employment
Not stated
Apply at Cargoo

Posting record

Report an error
Status in our records
Live
First seen by us
Oct 2, 202650 days ago
Recorded sightings
20
Last seen by us
Nov 21, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 50

Up longer than most. Similar jobs usually come down between day 1 and day 15.

From 1,368 similar postings that came down. Coming down is not always a hire.

Cargoo is hiring

1 open job

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • Python
Where the posting names them
- Experience with evals, prompt/version management or AI observability - Python for prototyping and data work - Logistics or other real-time operations domain experience

Your next step

Complete your application on job-boards.eu.greenhouse.io. The employer’s form will show what is required.

Applying through Greenhouse

  • No account needed: the form is one page, with an “Autofill my application” option that reads your resume.
  • Greenhouse doesn’t read resumes over 2.5 MB, or details placed in a header, footer, text box, table or second column. The file still attaches, but a recruiter has to type you in by hand.

Already applied? Track this application

Job description

View original posting ↗

 

Problem Space

Logistics operations today are still largely:

  • manual
  • reactive
  • fragmented across tools
  • running on incomplete or late data
  • full of conflicting constraints
  • under real-time decision pressure
  • driven by evolving business rules
  • a mix of legacy and new systems

Much of this is unstructured: emails, documents, free-text updates, exceptions nobody modelled. That is where AI changes the game.

We’re building a system that:

  • ingests real-time operational data, structured and unstructured
  • supports planning and execution decisions, with AI agents that act where it’s safe and hand over to humans where it isn’t
  • adapts to constantly changing constraints

What You’ll Work On

  • AI in production. Building LLM- and agent-powered features into production .NET services: tool calling, structured outputs, retrieval over operational data, document and message understanding.
  • The seams. Designing the boundaries between deterministic business logic and probabilistic AI: validation, fallbacks, human-in-the-loop.
  • Trust. Making AI measurable and trustworthy: evals, test sets, observability, guardrails and cost/latency budgets.
  • Ownership. Owning features end to end, from problem framing with product to running them in production.

 

Design Principles

  • keep things simple before scalable
  • prefer explicit logic over magic abstractions, and that includes AI: deterministic where you can, model where you must
  • optimize for change, not perfection (models, prompts and providers will change)
  • measure AI behaviour, don’t trust vibes
  • avoid “framework-driven architecture”
  • accept that some parts will be ugly, temporarily

Tech Stack

.NET · Vue.js · service-oriented architecture · relational + operational data storage · cloud-based infrastructure · LLM APIs and agent tooling (e.g. Semantic Kernel / Microsoft.Extensions.AI, MCP) · vector/semantic search · eval and tracing tools

How We Build

  • AI-native development is the default. You use coding agents (e.g. Claude Code, Copilot) every day.
  • You own what you ship, whoever typed it: you review AI-generated code critically, test it and understand it.

What We Expect

  • Strong, senior-level .NET engineering
  • Ability to navigate uncertainty and work in ambiguity
  • Willingness to challenge decisions
  • Focus on outcomes, not just code
  • Understanding of trade-offs and complex systems, including when not to use AI
  • Preferring ownership over comfort

Strong Plus

  • Having shipped LLM/AI features to production and kept them running
  • Experience with evals, prompt/version management or AI observability
  • Python for prototyping and data work
  • Logistics or other real-time operations domain experience

What You Won’t Find Here

  • over-engineering everything upfront
  • unnecessary microservices
  • “clean architecture” for the sake of it
  • process-heavy development
  • AI demos that never reach production
  • wrapping a chatbot around a problem and calling it solved

 

Demand for AI Engineer roles

New AI Engineer postings at the employers we follow are up 340% over the last 6 weeks compared with the 6 before.

Weekly new AI Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 78, the most 803, and the latest week had 438.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under AI Engineer, by the work the posting describes.

AI engineers build products on top of AI models that already exist, most often large language models: they connect a model to a company's data and tools and ship the assistants, agents and search features people use.

Postings ask for strong Python or TypeScript, experience with model APIs, retrieval and agent frameworks, and ways to test whether the model's answers are good enough.

An ML engineer trains and serves models; an AI engineer usually starts from a model someone else trained and builds the product around it, though titles often mix the two.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Yerevan, Armenia

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.