Hiring
Senior Python & React Developer — Brussels, 60% remote
Hiring evidence involving React, Python, FastAPI. First observed 4 Sept 2026; the response opens on freelancermap.com.
- Technology
- ReactPythonFastAPIPostgreSQLRAGAI agents and agentic workflows+1 more in the evidence
- Budget
- Not provided by source
- Work format
- Hiring
- Role family
- Software engineer
- Seniority
- Senior
- Observed
- 4 Sept 202611 days old
- Response destination
- freelancermap.com
Source job details
Structured facts are published only when supplied by the source; missing values are never invented.
- Hiring organization
- joyIT Recruiting GmbH
- Source reference
- OPP-20260904-616
- Location evidence
- Brussels, Belgium
- Employment type
- full time
- Required skills
- Python, FastAPI, React, AI agents, LLM, MCP, A2A, RAG, RabbitMQ, PostgreSQL, SQL Server, SQLAlchemy, SAML/OAuth/Entra ID, Pytest, LangChain/LangGraph, Kubernetes, Azure DevOps, ArgoCD, NX
- Expected duration
- 100% workload; 15 months; start 2026-09-14
What this signal says
The observed opportunity titled “Senior Python & React Developer — Brussels, 60% remote” 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
For comparison across sources, Leadiy maps the visible stack to React, Python, FastAPI, PostgreSQL, RAG, AI agents and agentic workflows, React/Next.js + FastAPI. Source marketplaces often mix frameworks, platforms, infrastructure and delivery language in one line, so a literal string would fragment the market view. The controlled catalog keeps stable concepts together while retaining the original stack as a concise fact below. Detection is multi-label: several technologies may be valid at once, and a stack combination is admitted only when its required components appear. Buyers and suppliers should still use the source page to confirm versions, depth and mandatory versus optional skills.
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 “100% workload; 15 months; start 2026-09-14.” Work-location context is recorded as “Only 60% remote; mandatory 40% onsite in Monnoyer/Belgium; incompatible with Ukraine-only remote delivery.”
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
In the current 30-day Hiring Pulse, React appears in 333 of 1254 observed opportunities (26.6%). Counts are multi-label, so one opportunity may contribute to several technology buckets. The comparison is dated through 2026-09-16 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
Timing here is explicit: observed by Leadiy on 4 Sept 2026, 08:32 UTC, 11 days old at the current request, then admitted to the public catalog after 25.33 hours. The system never recomputes a shorter delay because a page is requested frequently. This is an evidence timestamp, not a promise that the source remains open, and not a reconstruction of when the buyer first posted. Visitors who need the freshest matched records use the authenticated product; the public page is intentionally the later, indexable edition.
What looks similar
Similarity is based on shared normalized technology tags and then recency, not on company identity or copied source prose. "AI Engineer & Automation Developer — LLM agents and flow optimization", "AI Automation & AI Agent Developer", "Healthcare AI Automation Expert — EHR/EMR and FHIR integration" These neighbours are useful for comparing delivery shape, budget visibility and technology overlap. They are not duplicates and they do not imply that the same buyer, scope or qualification rules apply. When no suitable public neighbour exists, the page says so instead of padding the section with unrelated links. New public records can change this comparison set after their own delay and quality checks pass.
Where the response goes
This page’s action route is explicit: it opens Freelancermap on freelancermap.com. Leadiy provides context and provenance, not an application proxy. A click can therefore lead to a third-party login or proposal workflow governed by that service’s own privacy, eligibility and payment rules. The public catalog never replaces those instructions and never publishes a hidden email address as an alternate route. Review the destination hostname, confirm that the opportunity is still active, and respond only through a path you trust.
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 freelancermap.com. That third-party page controls login, eligibility, proposal fields, privacy and the current status of the opportunity.