Teams and staffing

XSIS employs its own engineers, who lead projects, set the technical direction and are accountable for quality. Where a project needs more capacity or a specialist skill, we add engineers from vetted outsourcing partners. They work to the same standards, contracts and security rules, and you always know who is on your team and who employs them.

Link to this question

You interview every engineer before they join; no blind placements. If someone is not the right fit, we replace them at no cost. Tell your delivery lead, and we plan a handover so knowledge stays with the team. The same applies if someone has to leave the project for their own reasons.

Link to this question

Yes. Many clients want their engineers in the same repository from the start, so knowledge stays in-house. We agree the working rules together: code review, branching, the definition of done and who approves releases. Your engineers can join the iterations, pair with ours, or take over parts of the system when they are ready.

Read more: Custom software developmentLink to this question

That is the aim. Everything is defined as code and documented, and your engineers review and approve changes with us from the start. We pair with them on incidents and releases, write runbooks for the common tasks, and step back as they take over. If you prefer us to keep running the platform, that can continue under a support agreement.

Read more: Cloud and DevOpsLink to this question

Yes. We often join an in-house QA team to add automation skills, take on performance or security testing, or cover a busy period. We agree how the work is split, use the same tools and backlog, and train your testers to extend the suites we build.

Read more: QA and test automationLink to this question

In the same team and at the same rhythm. Designers join planning, hand over designs and components with their states and behaviour documented, and review what is built before it ships. Engineers join research and design reviews early, so ideas that are hard to build are caught before they are polished.

Read more: UX and UI designLink to this question

Yes, and that is common. We recover the knowledge from the code, the data, the logs and the people who use the system, and we capture what it actually does in characterisation tests. Those tests become the specification the new parts must meet, so undocumented behaviour is kept unless you decide to change it.

Read more: Legacy modernisationLink to this question

We start from the skills the work needs, not from who is free. Candidates go through technical interviews and practical exercises run by our senior engineers, and we check their experience against the kind of work you do. Then we send you their profiles, and you interview them yourself. Nobody joins your team without your approval.

Read more: Dedicated teamsLink to this question

You decide what the team works on: your product owner sets the priorities and accepts the work. We run the team day to day through a team lead who plans the work, removes blockers, looks after quality and reports to you. Line management, performance and replacement of people stay with XSIS.

Read more: Dedicated teamsLink to this question

You interview every engineer before they join; no blind placements. If someone is not the right fit, we replace them at no cost. Tell your team lead or your account contact as soon as you see it. We also look at the role and the briefing, which are sometimes the real cause, and we plan an overlap so that knowledge is handed over and not lost.

Read more: Dedicated teamsLink to this question

Yes. The team follows your roadmap. You can add roles when a new stream of work starts and release them when it ends. We agree each change with you in advance, with enough notice to bring people in properly or hand their work over cleanly. The notice terms are set out in the contract.

Read more: Dedicated teamsLink to this question

With staff augmentation, our engineers join your team and your managers direct their work day to day. With a dedicated team, we provide a whole team with its own lead, and we run it day to day while you set the priorities. Staff augmentation fits when you already have the management and the process. A dedicated team fits when you want us to carry more of that.

Read more: Staff augmentationLink to this question

Our senior engineers run technical interviews and practical exercises for each candidate against your role brief. We check their past work and the kind of systems they have built. Engineers from outsourced teams go through the same assessment as our own. You then interview them yourself, and only the people you choose join.

Read more: Staff augmentationLink to this question

Your managers direct the work: what to build, in what order, and how it is reviewed. XSIS stays the employer or the contracting party. We handle pay, leave, equipment, performance support and replacement, and our account contact keeps in touch with you and with the engineer.

Read more: Staff augmentationLink to this question

You interview every engineer before they join; no blind placements. If someone is not the right fit, we replace them at no cost. Tell us as early as you can, and we plan the handover so that work in progress is not lost.

Read more: Staff augmentationLink to this question

Yes. You can add people when a new piece of work starts and release them when it is done. The contract sets the notice needed on both sides, so that new engineers can be found and assessed properly and departing ones can hand their work over.

Read more: Staff augmentationLink to this question

It means our own engineers lead every engagement and carry the responsibility for it, and we add engineers from vetted outsourced teams when the work needs more people or a skill we do not hold in-house. The outsourced engineers work under our contract and our standards, inside a team that our people lead.

Read more: In-house and outsourced teamsLink to this question

Yes. The team map lists every person, their role and who employs them. You interview every engineer before they join; no blind placements. We do not add or swap people without telling you first.

Read more: In-house and outsourced teamsLink to this question

XSIS is. Your contract is with us, and our delivery lead answers for the work of the whole team, whoever employs each engineer. That is why our engineers review outsourced engineers’ changes before they are merged, and why one set of standards applies to everyone.

Read more: In-house and outsourced teamsLink to this question

Yes. Tell us before we propose the team. Some clients need certain work, such as access to production data, to be done only by XSIS engineers. We plan the roles around that and tell you plainly if it changes what we can deliver or when.

Read more: In-house and outsourced teamsLink to this question

It depends on the model, and we say so in writing. In project-based delivery, XSIS is accountable for delivering the agreed scope. In a dedicated team, XSIS is accountable for running the team well and you are accountable for its priorities. In staff augmentation, your managers direct the work and XSIS is accountable for the people it provides.

Read more: How we workLink to this question

Yes. A dedicated team can run your product while a separate project delivers a bank integration, or we can place a specialist in your own team beside a team we run. Each part has its own terms, and one XSIS contact coordinates them.

Read more: How we workLink to this question