Interview Scorecards and a Structured Selection System for E-commerce software providers
What this looks like in your business
A selection system for an e-commerce software provider replaces a hiring habit that depends on who happens to be free. An engineer is interviewed by the founder's friend, a merchant support agent is chosen because the call felt friendly, and an onboarding specialist is rejected by one panel member and loved by another. GullyHR builds a stage map for each role family, a criteria grid, interview kits with rating anchors, a decision scorecard and offer templates for your adviser to review. The aim is that every candidate for the same role meets the same questions, and your decision rests on recorded evidence.
Why panels disagree in a platform company
Hiring in a software business pulls in people with different views of what matters. The engineering lead weighs technical depth, the head of support weighs patience, the founder weighs speed and cost. Without agreed criteria each interviewer scores a different thing and the debrief becomes an argument about who impressed whom. The roles also differ more than they look. A platform or back-end engineer must handle high-traffic order flows and incidents; a front-end or theme developer must care about merchants who are not technical; an integration developer lives in other companies' interfaces and documentation. Merchant onboarding specialists and support agents need to explain a technical problem calmly to someone losing sales. Partner and agency managers have to say no without damaging a relationship. When one question set is used for all of them, each role is judged on someone else's strengths. Sale-season pressure adds a further risk: the panel lowers the bar to fill the seat, and the person who then joins is the one the team did not agree on.
What the stage map and kits would contain
GullyHR begins by sitting with the people who manage each role family and writing down what good looks like in your business. For engineers the stage map can be a screening call, a practical exercise close to real platform work, a conversation with two engineers and a short meeting with the founder. For support agents and onboarding specialists it includes a role-play in which an anxious merchant cannot see their products after a store setup. Each stage has an owner, a time limit and a form. The criteria grid lists the few must-have skills and the weight of each, agreed before anyone is interviewed. Interview kits give every candidate for a role the same questions, with rating anchors that describe what a weak, adequate and strong answer sounds like, in your terms. Guardrails keep the panel from scoring on accent, schooling or confidence, and the scorecard asks each member to cite one thing the candidate said or did. The decision scorecard records each person's rating before the group talks, then the final choice, and the offer templates follow for your adviser to review.
A split panel for a support agent role
Take a hosted storefront company hiring a merchant support agent, with two final candidates. Nisha, the head of support, rates Imran highly: he stayed calm in the role-play with a merchant whose checkout had stopped, explained the problem in plain words and knew when to hand the ticket to an engineer. The engineering lead, Tomas, prefers Sunita, who diagnosed the fault quickly but spoke over the merchant and used technical terms the merchant did not follow. Under the old habit they would argue and the founder would break the tie on instinct. With the scorecard, each had scored the criteria alone before the debrief. The grid shows that patience with non-technical merchants was weighted higher than diagnosis for this role, because engineers handle the diagnosis. The scores favour Imran, and the notes record that Sunita could be considered for a technical support role later. The founder reads both scorecards and chooses Imran. The decision, the reasons and the scores are filed with the role, and a short note goes to Sunita explaining the outcome in terms of the grid.
Owners, records and what stays with you
Settle who owns each part of the system before the next search begins. The head of engineering owns the kits for developers and quality engineers, the head of support owns the kits for agents and onboarding specialists, and the founder or an operations lead owns the partner manager kit and the overall stage map. Settle who may sit on a panel, who trains new interviewers, and how long each stage may take, since a good engineer does not wait a fortnight. Settle where scorecards are kept, who can read them and how long they are held. Settle how feedback reaches declined candidates. GullyHR builds the stage map, grid, kits, scorecard and offer templates, and shows your managers how to use them. What stays with you is every selection and every offer, including pay and level. The offer templates go to your own adviser for review, because where a term touches employment law in your country, only your adviser can confirm it. Agree also that every panel member completes the scorecard on the day, while the interview is fresh.