Technical Support Engineer — Developer Platform

Why this role exists

Our users are engineers building production systems. When they open a ticket, “have you tried logging out and in again” is an insult. They need someone who can read the trace, reproduce the failure, and say what is actually happening — including when the answer is “that is our bug, here is the issue, here is the workaround today.”

This is a support role with root access to the truth.

What you’ll own

• Frontline technical support for developers building on Supero — schema design, connectors, RBAC, deployment, MCP, integrations, the generation flow.
• Reproduction. Turning a vague report into a minimal, runnable repro. This single skill is most of the value.
• Escalation with a diagnosis attached. Engineers here take your ticket seriously in direct proportion to how much of the work you have already done — and they are expected to.
• Docs, from the ticket queue. Every question asked twice is a documentation defect. You fix it at the source, in the docs and often in the product’s error message.
• The voice of the user in planning. You will know, before anyone else, which part of the product is quietly failing people.

About the late rotation — read this before you apply

Supporting engineers in the US means somebody in Bengaluru is awake when they are. We are not going to disguise that, so here is exactly what it is and what we provide for it.

The shift. Rotational, with a standard daytime rotation and a later one that overlaps US Pacific business hours. It rotates rather than landing permanently on the same person, and the late rotation carries a shift allowance on top of base. We will give you the exact hours, the rotation frequency and the allowance in writing on the first call - before you invest more time in us, not at offer stage.

Consent, and it is revocable. Nobody goes on the late rotation without giving written consent first, and you can withdraw it. Declining does not affect your application, your appraisal or your progression.

What remote changes, and what it does not. You would work the late rotation from home, so there is no late-night commute to arrange — which removes the single biggest risk in shift work. What does not change: the consent is written and revocable, the rotation is real, the allowance is paid, and our Internal Committee under the POSH Act 2013 is standing and reachable from day one.

What we look for

• 2+ years in technical support, solutions engineering, or an engineering role with real customer contact.
• You can code. Python or JavaScript, enough to read a stack trace, write a repro script, and call an API from a terminal without a GUI.
• SQL and API literacy — you can read a schema and a request/response pair and form a hypothesis.
• Writing under pressure. Clear, calm, specific, and never falsely reassuring.

Where this goes

Support here is a route into solutions engineering, developer experience or the platform team — not a terminal track. Two things get you there: reproductions nobody argued with, and docs that stopped the ticket from being filed again.

Build something on Supero and skip our take-home entirely

The most reliable signal we have ever had about a candidate is an application they built. So we made it the front door. Build a small system on Supero — over MCP from your own AI editor — and send us the link: it shows us you understand the platform far better than a résumé line can. Aim for 90 minutes, and note there are two equally valid ways to satisfy this, listed below.

• Bring your own idea, and scope it small. We build tooling that generates full-stack apps — it would be strange to ask you to interview without it. So bring your own idea, use whatever gets you there, and be ready to explain every decision inside it. Model something you actually know: a domain you have worked in, or a system that annoyed you. Three to five entities, two roles, one thing that can go wrong. Aim for 90 minutes; four hours is the hard cap.
• Turn multi-tenancy on when you generate — and notice that you had to. It is a generation-time flag, it defaults to off, and it is expensive to retrofit. We think that default is wrong. It is the same shape of problem we criticise elsewhere — opt-in per thing, someone has to remember, painful to add later — and it is on the list to change. We are telling you because you will hit it, because we would rather you hit it knowingly, and because what you would do about it is a question we would genuinely like your answer to. Meanwhile: switch it on, because we do look at whether your model survives a second tenant.
• Send a screenshot, the link, and your read on us. A screenshot of your application’s landing page is the one thing we always want — a running app can go down, and the screenshot survives. Send the live URL too, and optionally push the source to your own GitHub and send that link. Then a few paragraphs: what you were modelling, one decision you reversed, and two things about Supero itself — what you liked most, and what you would improve. That last one is not a courtesy question. What you notice tells us how you think, and we act on it.
• What you get back. A person reads every submission — not an auto-responder, and not a keyword screen. If it moves forward, an engineer writes back with what they saw in your model. And a completed build replaces our screening call and our take-home entirely: you go straight to a technical conversation with the people you would work with.

Two ways to satisfy this — they are scored the same

• Build it over MCP — the one we prefer. Point Claude Code, Cursor or Copilot at Supero’s MCP server and drive the whole build from your own editor. This is the route we would rather you took: it is how the platform is meant to be used, it is the closest thing to the actual job, and it tells us the most about how you think. App Studio exists and works, but MCP is what we are looking for here.
• Send something you already built. Any stack, any age, any domain — plus one page on the data model and the decision you would now reverse. Scored exactly the same way. Nothing about this route is a lesser option.

Start with MCP →Create an account for your key →

The fine print

• You own what you build. Full intellectual property and copyright stay yours, and our platform terms do not override that. We receive only a limited licence to review your submission as part of your application.
• Do not submit anything that is not yours to submit. No current or former employer’s confidential information, proprietary code or data. No real personal data belonging to anyone, including yourself. Invent your test data. If a contract restricts outside development, tell us and take route 2 or 3 instead.
• Time-box it. Aim for 90 minutes and do not exceed four hours. We mean it: a submission built in 90 minutes is scored exactly like one someone spent a fortnight on, and the small sharp one usually wins. Spending longer does not help you.
• What happens to your data. The account you create stays yours. We delete our copy of your submission, and any repository access you granted, within 90 days of a final decision — or sooner if you ask. Write to [email protected] at any time.
• A human scores every submission. No automated screening decides whether you move forward.
• Where the line is on breaking things. Inside your own project — including across tenants you created yourself — break whatever you like. Probe the tenant boundary, try to read a field your second role should not see, send the state transition that should be rejected. That is the exercise, and telling us what you found is one of the things we score. Outside your own project — other people’s accounts, our infrastructure, our authentication, anything you were not given — please stop. No scanners. If you find something that reaches beyond your own project, do not keep pulling: write to [email protected] and we will thank you properly. Reporting in good faith is never held against you.
• What the account gives you. No credit card. A challenge account carries an allowance sized well above what this exercise needs — if you genuinely run out mid-build, write to us and we will top it up. Your submitted URL stays live for at least 30 days.
• No obligation either way. Doing this is not a condition of being considered, and we are not obliged to hire or pay for any submission.

How this goes

Every step, stated up front, so you can decide whether to start it. No fixed timeline — we go as fast or as slow as it takes to be sure, in both directions.

• STEP 1 — You apply. A person reads it. No keyword screen. If you did the build challenge, that is what we read first.
• STEP 2 — 30-minute conversation. With the person who would be your manager, about what you have built. Skipped entirely if you submitted a build.
• STEP 3 — 90-minute technical session. A real problem from our backlog, or a walkthrough of your build. No algorithm puzzles and no whiteboard trivia.
• STEP 4 — Two 45-minute conversations. With people you would work with. One is a design-review simulation, which is the closest thing to the actual job.
• STEP 5 — Founder conversation, then offer. We tell you where you stand after every stage, including when the answer is no.

Find us

• GitHub. github.com/supero-platform/supero-apps — Example applications built on Supero.
• LinkedIn. www.linkedin.com/company/supero-dev/ — Company updates and the people here.
• Docs. docs.supero.dev — The platform, in full technical detail.

Equal opportunity

Supero is an equal opportunity employer. We consider all applicants based on their qualifications, skills, and experience, without regard to race, color, religion, caste, sex, pregnancy, sexual orientation, gender identity or expression, national origin, citizenship or immigration status, age, disability, medical condition, marital or family status, veteran status, or any other characteristic protected by applicable law.

We maintain an Equal Opportunity Policy and designate a Liaison Officer in accordance with the Rights of Persons with Disabilities Act, 2016. We also maintain an Internal Committee in accordance with the Sexual Harassment of Women at Workplace (Prevention, Prohibition and Redressal) Act, 2013.