Hiring
Full Stack Developer — FastAPI / SQL / Vue 3 Rules & Action system
Hiring evidence involving TypeScript, Python, FastAPI. First observed 3 Sept 2026; the response opens on vollna.com.
- Technology
- TypeScriptPythonFastAPIRedisDocker
- Budget
- Not provided by source
- Work format
- Hiring
- Role family
- Full-stack developer
- Seniority
- Level not stated
- Observed
- 3 Sept 202611 days old
- Response destination
- vollna.com
Source job details
Structured facts are published only when supplied by the source; missing values are never invented.
- Hiring organization
- Undisclosed established application owner
- Source reference
- OPP-20260903-544
- Location evidence
- US Eastern overlap requested
- Employment type
- part time
- Required skills
- Python, FastAPI, REST APIs, Microsoft SQL Server, Vue 3, TypeScript, Composition API, Pinia, Celery, Alembic/SQLAlchemy, Redis, Docker, Git
- Expected duration
- Part-time, variable hours; project-based with potential ongoing work; paid 2–4 hour task for shortlisted candidates
What this signal says
The observed opportunity titled “Full Stack Developer — FastAPI / SQL / Vue 3 Rules & Action system” 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 TypeScript, Python, FastAPI, Redis, Docker. 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 “Part-time, variable hours; project-based with potential ongoing work; paid 2–4 hour task for shortlisted candidates.” Work-location context is recorded as “Remote marketplace signal; Ukraine and agency/B2B eligibility not stated.”
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, TypeScript appears in 267 of 1244 observed opportunities (21.5%). Counts are multi-label, so one opportunity may contribute to several technology buckets. The comparison is dated through 2026-09-15 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
Leadiy first observed this signal on 3 Sept 2026, 22:33 UTC; at page render it is 11 days old. Its public eligibility time was calculated once from that observation using a deterministic 30.76-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: "Full-Stack / Data & AI Engineering Partner for Real-Time Sports Betting Platform", "AI Full-Stack Developer — RAG-based assistant platform", "AI Sales Operations Employee — autonomous CRM and outreach platform" 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 Vollna public Upwork index at vollna.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 vollna.com. That third-party page controls login, eligibility, proposal fields, privacy and the current status of the opportunity.