Hiring
Chief Forward Deployed Engineer
PythonRAGAI agents and agentic workflowsTool/function calling
Lead AI Solutions Engineer — reusable Claude Code Skills
Hiring evidence involving AI agents and agentic workflows, Tool/function calling. First observed 9 Sept 2026; the response opens on justjoin.it.
- Budget
- Not provided by source
- Work format
- Hiring
- Role family
- AI / ML engineer
- Seniority
- Lead / principal
- Observed
- 9 Sept 202615 days old
- Response destination
- justjoin.it
Source job details
Structured facts are published only when supplied by the source; missing values are never invented.
- Hiring organization
- H2B Group / global consulting client
- Source reference
- OPP-20260909-1079
- Location evidence
- Client in New York; European business hours
- Employment type
- contractor
- Required skills
- Claude Code, AI agents, tool use, prompt/context engineering, MCP, promptfoo, LangSmith, helper scripts, validation
- Expected duration
- Long-term, full-time; ASAP start
What this signal says
The observed opportunity titled “Lead AI Solutions Engineer — reusable Claude Code Skills” enters this catalog as a market signal with a traceable source. Leadiy does not republish the original description. Instead, it separates a few decision-grade facts from the private operating record and adds context from the same demand dataset. That boundary matters: the public edition can help a developer or agency assess relevance, while the source remains responsible for complete requirements, eligibility, current status and the actual response flow. Any fact not shown here should be checked at that destination.
How the technology was normalized
The controlled technology reading for this record is AI agents and agentic workflows, Tool/function calling. That label is derived from explicit terms in the role, primary technology and stack fields; it is not inferred from the buyer’s identity or from private contact context. Normalization folds common spelling and naming variants into one catalog so this page can be compared with other records. A combination tag appears only when every required part of that combination is detected. The result is a search aid, not a guarantee that every named tool is equally central to the delivery scope.
Commercial format
The engagement classifier places this record in Hiring: an employment-oriented search for an individual contributor or team member. That decision comes from the supplied opportunity-type language, using the same categories as Hiring Pulse—project, contract, RFP or procurement, hiring, and other or unclear. It does not convert an ambiguous request into a stronger claim. The imported public-safe work-format field also says “100% remote, stable long-term B2B; Ukraine cross-border/named-candidate route remains unconfirmed across both recruiter listings.” The stated duration context is “Long-term, full-time; ASAP start.”
Reading the budget
No budget value was supplied in the imported source record. The page labels this plainly as “Budget not provided by source” so publication status cannot be confused with compensation coverage. An absent figure is not converted into zero and is not inferred from neighbouring opportunities. The original destination remains the authority for price, salary, rate unit, fees, milestones and any later updates.
Demand context from Hiring Pulse
The current 30-day Hiring Pulse does not expose a separate publishable bucket for this exact normalized stack. That absence is not a zero-demand claim: multi-label classification and the privacy threshold can keep a narrow bucket out of the public table. Hiring Pulse is the contextual layer Leadiy adds beyond aggregation. It places the record against a verified observation window while keeping counting rules visible: technologies can overlap, the feed is not a census, and sparse groups are not disclosed as exact numbers. This evidence can support prioritization, not a forecast. The record still needs source-level verification, and the aggregate view deliberately omits direct leads, personal information, private outreach content and arbitrary micro-segments that could reveal too much.
Observation and publication timing
Leadiy first observed this signal on 9 Sept 2026, 22:29 UTC; at page render it is 15 days old. Its public eligibility time was calculated once from that observation using a deterministic 37.88-hour delay inside the promised 24–48 hour window. The delay is not the source publication age and should not be presented as one. It creates a clear product boundary: authenticated customers can work from the live matched feed, while search engines and unauthenticated visitors receive a later evidence edition. The stored eligibility timestamp prevents an early publish after restarts or repeated syncs.
What looks similar
The related-record layer searches already published pages for overlap in the controlled technology catalog. It does not inspect private contacts and it does not use a buyer name as a recommendation signal. The closest current titles are: "Two production voice AI agents for Hygea marketplace", "Senior AI Engineer — conversational healthtech platform", "Mid AI / Backend Engineer — agentic B2B platform" Treat them as adjacent demand signals, not substitutes for reading the original post. Their engagement format, budget unit, eligibility and delivery expectations may differ even when a framework or platform matches. This page keeps that uncertainty visible rather than manufacturing a single “typical” opportunity from unlike records.
Where the response goes
The response button on this page opens Just Join IT — H2B canonical, ITLT corroborating route at justjoin.it. It leaves Leadiy and goes to the original opportunity URL; Leadiy is not the application destination and does not relay a response from this public page. The source may require its own account, profile, proposal form, geographic eligibility or platform terms. Check the destination address before entering information, and use the source’s current instructions rather than any summary here. This disclosure is intentionally repeated beside the button so the action is clear before a visitor clicks.
Public evidence versus earlier access
Leadiy sells timing, not a different truth: the same opportunities, one day earlier. Subscribers receive the fresh matched feed and private workflow before a record crosses its public time fence. The later page remains complete enough to stand alone, with provenance, classification, budget reading, aggregate context and related records. Subscription is not preferential treatment from the buyer, and it cannot guarantee availability or success. It is earlier awareness plus an operational workspace; the public catalog is the delayed evidence layer.
The same opportunities, one day earlier.
See the $39 / 30-day plan →Your response leaves Leadiy.
The button opens justjoin.it. That third-party page controls login, eligibility, proposal fields, privacy and the current status of the opportunity.