Contract
AI Automation & AI Agent Developer — Claude, OpenAI, Python & APIs
Hiring evidence involving Python, OpenAI API, RAG. First observed 29 Aug 2026; the response opens on upwork.com.
- Budget
- Not provided by source
- Work format
- Hiring
- Role family
- AI / ML engineer
- Seniority
- Level not stated
- Observed
- 29 Aug 202611 days old
- Response destination
- upwork.com
Source job details
Structured facts are published only when supplied by the source; missing values are never invented.
- Hiring organization
- Confidential US Virgin Islands client
- Source reference
- OPP-20260829-262
- Location evidence
- US Virgin Islands / Atlantic
- Employment type
- contractor
- Required skills
- Claude; OpenAI; Python; AI agents; RAG; chatbots; APIs; data processing
- Expected duration
- Under 1 month; less than 30 hours/week; contract-to-hire
What this signal says
This is a delayed public reading of the demand behind “AI Automation & AI Agent Developer — Claude, OpenAI, Python & APIs.” It is deliberately smaller than the private workspace record and deliberately more interpretive than the source listing. The page identifies the work, translates its technology language into Leadiy’s controlled catalog, names the commercial format and preserves the original application destination. It does not publish personal contacts, internal qualification, prepared outreach or hidden source fields. Read it as an evidence note about one observed opportunity, with the source link retained for the current authoritative details.
How the technology was normalized
This record contributes to the normalized topic set Python, OpenAI API, RAG, AI agents and agentic workflows, Data processing and AI/data workers. The mapping is evidence-based and intentionally conservative. It looks for named technology terms in the public-safe opportunity fields, resolves aliases, then checks any combination as a set of requirements rather than a loose keyword. This makes the page discoverable under stable technology hubs without pretending that a tag replaces technical due diligence. The source may contain additional context, but no unpublished contact or outreach field is used to create the public classification.
Commercial format
Leadiy reads the buying motion as Hiring. This matters because the response shape for a deliverable, contractor seat, formal proposal and employment application is not interchangeable. The category is a classifier output rather than a legal characterization, and the original post wins if its terms change. The available duration wording is “Under 1 month; less than 30 hours/week; contract-to-hire.” Work-location context is recorded as “Worldwide remote; agency not prohibited, but commercial terms are incompatible.”
Reading the budget
Budget data is unavailable from the source for this record. That is a statement about one missing field, not about whether the opportunity itself is public: this evidence page is published and indexable. Leadiy keeps the gap visible instead of inventing a midpoint or borrowing a number from another listing. Ask the source to confirm amount, currency, unit, inclusions and payment schedule before treating the opportunity as commercially qualified.
Demand context from Hiring Pulse
In the current 30-day Hiring Pulse, Python appears in 250 of 1093 observed opportunities (22.9%). Counts are multi-label, so one opportunity may contribute to several technology buckets. The comparison is dated through 2026-09-10 and describes Leadiy’s observed sample, not the whole software market. It helps answer whether this record sits beside other visible signals, but it does not prove future demand, market share or buyer intent. The individual page and the aggregate Pulse use the same public-safe vacancy and project scope, while direct leads and personal data remain excluded from both.
Observation and publication timing
The first-observed timestamp is 29 Aug 2026, 13:00 UTC, which makes this record 11 days old when this page is rendered. Public release waited 34.75 hours, selected deterministically between 24 and 48 hours from the record identifier. That rule survives process restarts and does not drift with each request. It also separates two clocks that are easy to confuse: the source may have published earlier, whereas Leadiy records when its own system first saw the opportunity. Paid access is to the earlier matched feed, not to a claim about the source’s original posting time.
What looks similar
To build a useful neighbourhood around this record, Leadiy compares normalized technology IDs and favours the strongest overlap among pages that have already cleared the public delay. The current result is: "AI agent for financial document and back-office automation", "Senior AI knowledge and governance architect for multi-store ecommerce", "AI full-stack engineer for scalable AI applications" This method makes relationships inspectable and avoids copying descriptive text from the source. Similarity means shared technical vocabulary, nothing more. It does not assert shared ownership, equal scope, equivalent seniority or an identical application process, and it can evolve as later records become publicly eligible.
Where the response goes
Applying means leaving Leadiy for upwork.com, identified here as Upwork. The link is the normalized direct source URL stored with the opportunity. No public form on Leadiy submits an application, and no contact detail is exposed as a shortcut. The destination can impose login, marketplace credits, identity checks, location limits or other terms that are outside this catalog. Verify the hostname and the current post before sharing information. If the source has closed or changed the opportunity, its live state is authoritative.
Public evidence versus earlier access
The commercial distinction is one sentence: the same opportunities, one day earlier. The paid workspace is for acting on newly matched signals with private workflow tools; this public edition is for later discovery, citation and market context. Paying does not improve the source’s terms or guarantee a response. It changes when the Leadiy record becomes available and adds the operating context needed to triage it. That boundary keeps the open catalog genuinely useful while preserving a simple reason to subscribe without hiding where the original response must be submitted.
The same opportunities, one day earlier.
See the $39 / 30-day plan →Your response leaves Leadiy.
The button opens upwork.com. That third-party page controls login, eligibility, proposal fields, privacy and the current status of the opportunity.