Opportunity Backend Engineering work from LinkedIn, X, Reddit and Upwork, in one list. Find me work
remoteroles

Senior Backend Software Engineer – Agentic AI Workflows (Go/AWS)

Ontrac Solutions Open
Remote Chicago Contract Senior Backend Engineering

At a glance

Senior Backend Engineering role at Ontrac Solutions. Remote, United States · contract.

Pay not stated Backend Software Engineer salary

RoleBackend Engineering
SenioritySenior
LocationChicago
WorkplaceRemote
EmploymentContract
PostedAug 28, 2026
Role brief

remoteroles summary, based on the employer's posting.

What you'll do

  • Build and tune metadata suggestions until engineers accept them across active projects
  • Create safeguards that reassign ownership or retire systems left without an owner
  • Make agents and MCP servers across production and endpoint environments visible through the platform API
  • Improve or retire legacy code safely, with unit and integration tests for your changes
  • Deliver sprint work with program and customer teams

What you bring

  • At least five years in professional backend software engineering
  • You have shipped scalable Go services and APIs and can work with PostgreSQL, MongoDB and AWS
  • You have designed and tuned agentic workflows, such as suggestion systems or automated decision logic
  • You can navigate unfamiliar code, change legacy behavior safely, and test backend components
  • A computer science degree or comparable practical experience

Who this fits

This remote contract role suits a senior backend engineer comfortable extending a production codebase and delivering through Agile sprints. It is remote within the United States, with no relocation, and begins in mid-September 2026. The contract can be W2 or 1099.

From the employer

  • Senior Backend Software Engineer – Agentic AI Workflows (Go/AWS)

About the role

Most backend roles touching “AI” mean a chatbot bolted onto a CRUD app. This one is different: the agentic workflows are the product surface.

You’ll work on an established enterprise asset-and-metadata platform, building the AI engine that proposes metadata across the active project estate, the automated logic that reassigns or retires ownerless systems, and a live inventory of every agent and MCP server running across production and endpoint environments — all exposed through the platform API.

It’s Go on AWS, against a real production codebase with real users. A large part of the job is reading code you didn’t write, understanding how it behaves, and then extending, refactoring or decommissioning it without breaking anything.

What you’ll own

  • AI-suggested metadata engine — proposing metadata across the active project estate, then tuning it until engineers actually accept the suggestions.
  • Automated ownership reassignment and deprecation — logic that finds ownerless or relinquished systems and acts on them safely.
  • Agent and MCP inventory — complete coverage across production and endpoint environments, accessible programmatically.
  • First-party product inventory and critical-user-journey mapping — making ownership and metadata trustworthy enough to decide on.
  • Legacy refactoring and decommissioning — with unit and integration tests covering everything you ship.
  • Sprint delivery alongside program and customer teams.

Requirements — check yourself against this list

You should be able to say yes to essentially all of these:

  1. 5+ years professional backend software engineering
  2. Go as a working language — you’ve built and shipped scalable backend services and APIs in it
  3. PostgreSQL — schema design and real querying
  4. MongoDB — schema design and real querying
  5. AWS — working knowledge of the services plus their client libraries and APIs
  6. Agentic, AI-driven workflows you have designed, implemented and tuned — suggestion engines, automated decision logic, or assistant interfaces
  7. Asset discovery / ingestion tooling — open-source or commercial (e.g. CloudQuery) for aggregating cloud resources and metadata
  8. Data classification standards, dependency mapping, functional framework mapping
  9. Navigating a large, unfamiliar codebase to refactor or decommission legacy code without regressing existing behaviour
  10. Unit and integration testing for backend components, as standard practice
  11. Agile/Scrum delivery — sprints, stand-ups, retrospectives
  12. Bachelor’s in Computer Science or a related field, or equivalent practical experience — we care about what you’ve built

Nice to have — not required

  • IT asset management, CMDB, or configuration management platforms
  • Model Context Protocol (MCP) and related agent tooling patterns
  • Governance, risk or compliance workflows — findings management, risk remediation

Logistics

  • Remote, United States. No relocation.
  • Contract engagement, starting mid-September 2026 (W2 or 1099 — whichever suits you).
  • Compensation is competitive; we’ll discuss it openly on the first call.

Interested? Drop your resume and we’ll set up a call. If it isn’t the right fit we’ll tell you quickly — and tell you why.

Opportunity

Backend Engineering work from LinkedIn, X, Reddit and Upwork, in one list.

Each morning you get everything that fits, strongest first.

Backend EngineeringRemote

Find me work

By the team behind remoteroles.

Find me work
Opportunity

Backend Engineering work from LinkedIn, X, Reddit and Upwork, in one list.

Each morning you get everything that fits, strongest first.

Find me work

By the team behind remoteroles.