Interviews and applying: how the Happydance process actually works

Where something is still being finalised, it is marked placeholder. We would rather admit a gap than let you plan around a guess.

What are the stages of the Happydance interview process?

Three stages, designed to be finished within a few weeks: a conversation, a technical session, and a meet-the-team final. First, a 30 to 45-minute call with a hiring manager about your experience, your questions and mutual fit, both directions. Second, a technical session built around realistic work, discussed below, not puzzle theatre. Third, a final conversation with team members and a founder-level voice about how we work and what you would own. This structure is placeholder-flagged for final confirmation, but the shape and the spirit are settled. The stage-by-stage detail lives on our interview process page.

How long does the whole process take?

Our target is two to three weeks from application to decision, and we tell you if we are running slower. Enterprise-grade honesty applies to scheduling too: if a hiring manager is on leave or a role is paused, you hear that in plain words rather than silence. You will never be left more than a week without contact once you are in process. If speed matters because you hold another offer, say so; compressing the stages for a strong candidate is a lever we will genuinely pull.

Will I have to do a whiteboard coding interview?

No, there is no whiteboard algorithm interview at Happydance. We think inverting a binary tree on a marker board mostly measures rehearsal and nerve, neither of which builds careers sites. The technical session uses realistic material: working through code together, discussing design decisions on the kind of multi-tenant, accessibility-bound problems the job actually contains, in an editor, with documentation available, like real life. You should still expect depth; the session is friendly, not soft.

Is there a take-home test, and how long does it take?

If a take-home exercise is used for your role, it is scoped to a stated time cap of roughly two to three hours, and we honour that cap when reviewing. Placeholder: whether your specific role uses a take-home or a live pairing session is confirmed per vacancy on its job page. Two commitments hold either way: nobody is asked to build free product features disguised as tests, and every submission that reaches review gets actual feedback, not a templated no. If your circumstances make take-home work hard, tell us and we will use the live alternative.

What should I prepare for the technical interview?

Prepare to talk honestly about real work you have shipped, including the parts that went wrong. The session explores how you think in TypeScript, React, Node.js or .NET territory, how you weigh trade-offs, and how you respond when someone questions your approach, because code review is daily life here. Refreshing the tech stack helps, but do not cram algorithms. The candidates who do best bring specifics: a system they own, a decision they regret, a constraint they navigated. The ones who struggle bring polish and no scars.

What questions will I be asked?

Expect questions about real decisions, not brainteasers: how you designed something, what you would change about it now, how you have handled disagreement in code review, what accessible front-end work you have done, how you keep quality up under deadline pressure. Expect at least one question inviting you to criticise something we do, because we mean it. And expect generous time for your questions; a candidate with none is a small red flag to us, and a process that leaves no room for them would be a red flag about us.

Can I ask for adjustments or accessibility support?

Yes, ask for whatever you need and it will be arranged without drama. That includes extra time, written questions in advance, breaks, remote instead of in-person stages, screen-reader-friendly materials, a different take-home format, or anything else that lets you show your actual ability. We build products to WCAG 2.2 AA as a hard requirement, and an inaccessible hiring process would make that a lie. You do not need to disclose a diagnosis or justify the request; naming the adjustment is enough.

Can I apply for two roles at once?

Yes, apply for both and tell us you have done so. Overlapping applications are common when someone sits between mid and senior, or between frontend and full-stack, and we treat them as one conversation about where you fit best rather than two competing processes. The honest mechanics: you will get one first-stage call covering both, and we will agree together which role to progress. Applying twice will never read as indecision; hiding it just creates admin.

Do you sponsor visas?

Placeholder: confirm policy. We will not publish a yes we cannot yet stand behind, because candidates plan lives around this answer. What we can say now: if you would need sponsorship, state it in your application and you will get a definitive answer at the first conversation, before you have invested in later stages. When Happydance finalises the policy, this answer will be replaced with specifics, including which roles and levels it covers.

I applied before and was rejected. Can I reapply?

Yes, and six months of new evidence is the honest guideline. A previous no was a reading of that moment, not a verdict on you; people close gaps, and we rehire our own rejections happily when they do. When you reapply, name what has changed since last time, because the reviewer will have your previous file and the comparison working for you is stronger than pretending it is your first approach. If your rejection came with feedback, addressing it directly is the fastest route back.

Will I get feedback if I am rejected?

Yes, anyone who completes a technical stage gets specific feedback, not a template. That is unusual and we do it because being rejected into silence is the single most-hated experience in hiring, and an employer brand company of all things should refuse to cause it. At application-sift stage, volume means feedback is briefer, but a human decision is still made. The trade we ask: take feedback in the spirit of usefulness. It is one team's honest reading, offered so your next attempt, here or elsewhere, is stronger.

What does the final stage involve?

The final stage is a conversation with the people you would actually work beside, plus a senior voice on where the company is going. It covers how squads run, what you would own in your first six months, and the mutual honesty check: we tell you the hard parts of the job again, specifically, and you tell us what would make you leave a job. Some candidates find that question odd. We find the answers the most useful thing in the whole process. It is also deliberately your best chance to interview us.

When would I hear back, and how are offers made?

You hear back within a week of your final stage, usually faster, and offers come by phone with the number stated plainly. The offer includes the salary, which sits inside the range published on the job ad, and written confirmation follows the call. If you need time to decide, take it and tell us how long; exploding offers designed to panic you are not something we use. If you are weighing us against another offer, say so, and you will get our honest best position rather than a bidding-war performance.

The application itself takes five minutes

No eleven-page portal, no retyping your CV into boxes. Pick a role from the live vacancies, send the essentials, and the process above starts. If you want to understand the day-to-day before you commit an evening to applying, the job FAQ is the honest place to spend it first.