Hiring
Backend / Cloud Platform Engineer — FastAPI, PostgreSQL, MQTT, React
Hiring evidence involving TypeScript, React, Python. First observed 3 Sept 2026; the response opens on upwork.com.
- Technology
- TypeScriptReactPythonFastAPIPostgreSQLDocker+1 more in the evidence
- Budget
- Not provided by source
- Work format
- Hiring
- Role family
- Platform engineer
- Seniority
- Level not stated
- Observed
- 3 Sept 20269 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
- Undisclosed Romanian client
- Source reference
- OPP-20260903-446
- Location evidence
- Baia Mare, Romania / Europe-Bucharest
- Employment type
- contractor
- Required skills
- Python, FastAPI, Pydantic, SQLAlchemy, Alembic, PostgreSQL, MQTT/RabbitMQ/Kafka, React, TypeScript, OAuth2/JWT/RBAC, Docker, Linux, CI/CD
- Expected duration
- Initial 15–20 h/week for 4 weeks; potential 6+ month extension
What this signal says
This is a delayed public reading of the demand behind “Backend / Cloud Platform Engineer — FastAPI, PostgreSQL, MQTT, React.” 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
The controlled technology reading for this record is TypeScript, React, Python, FastAPI, PostgreSQL, Docker, React/Next.js + FastAPI. 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
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 “Initial 15–20 h/week for 4 weeks; potential 6+ month extension.” Work-location context is recorded as “Worldwide fully remote Upwork contract; freelancer route confirmed; agency eligibility not explicit.”
Reading the budget
The source did not provide a budget for this opportunity. “Budget not provided by source” describes that missing commercial field; it does not mean the opportunity page is unpublished or unavailable. Leadiy does not estimate a range from similar records because fixed projects, hourly work, contracts and salaries are not safely interchangeable. Confirm compensation, currency, rate unit, scope and payment terms at the response destination before deciding whether to proceed.
Demand context from Hiring Pulse
In the current 30-day Hiring Pulse, TypeScript appears in 242 of 1177 observed opportunities (20.6%). Counts are multi-label, so one opportunity may contribute to several technology buckets. 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 3 Sept 2026, 05:33 UTC; at page render it is 9 days old. Its public eligibility time was calculated once from that observation using a deterministic 42.49-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
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 Full-Stack Developer — RAG-based assistant platform", "Build an AI feature for an existing SaaS MVP", "AI-powered SaaS full-stack development" 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
The response button on this page opens Upwork at upwork.com. 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 upwork.com. That third-party page controls login, eligibility, proposal fields, privacy and the current status of the opportunity.