Supero
Full Stack Developer (React, Python)
Employment
Not statedLevel
Not statedCategory
EngineeringCountry assessment
We could not tell whether this is doable from Austria because the posting says nothing about where the work can be done.
Our assessment is guidance. Confirm arrangements with the employer.
Skills mentioned in this posting
Job description
Fix a component here and you fix it in every application on the platform — which is exactly as powerful and as dangerous as it sounds. Why this role exists Supero generates front ends, and generated UI is exactly as good as the person who decided what “good” means. Somebody has to be the taste and the rigour on both sides of the wire: the React console our customers build in, the front ends the platform emits, and the API contracts that make both possible.
What you’ll own The Supero console. React 18 and Vite — where people create projects, design schemas, generate apps, wire connectors and deploy. Thousands of decisions about what an engineer should see when something has gone wrong. The generated front end. The React app Supero emits for every application, and the shared UI library behind it. Fix a component here and you fix it in every app on the platform — which is exactly as powerful and as dangerous as it sounds.
The public site. Next.js 14, static export — including the page you are reading. The API contract, from both ends. You will design an endpoint in Python and consume it in React on the same day, which is the fastest known cure for a bad API. What we look for 3+ years across both halves. You are comfortable owning an endpoint and the screen that calls it. Self-taught, bootcamp and agency backgrounds are all welcome — we care what you have shipped.
React at depth. State that does not fight you, rendering you can reason about, and an eye for the empty state and the error state, not just the demo state. Backend competence in Python or Node, enough to own an endpoint end to end. Design sense. You can tell the difference between a page that looks finished and a page that is finished. Curiosity about AI and MCP.
You would be building UI whose author is sometimes an agent. Nobody expects you to arrive knowing what that implies. Nice to have Next.js. Tailwind. Design systems. Accessibility done properly. Data visualisation. Having shipped a UI that a non-technical person used without you in the room.