Loading...
Answers
MenuShould I allow external clients to conduct a technical interview of my employees, as we are an outsourcing company?
One client asked that they do a technical interview of my employees in order for them to see if they are a good fit. I am opposed to them, as I can't allow scores of potential clients to conduct interviews with my employees over and over again since I already did it myself. Am I wrong, or should I allow (all of ) my potential clients to interview my employees?
Answers


If it's a client you want to work with and this is part of the client's requirements then yes, you should allow this or politely decline the business. The client has the right to ask for anything and you have the right to approve or decline. I ran an offshore software services company in Costa Rica after being a Division Manager at Cognizant and now I advise and work with 50 software companies in 25 countries and this is a common request that is complied with. This isn't to say you shouldn't make the reasonable argument that it is preferred that interviews are conducted just with team leads who will then vet and manage the rest of the team. Even though you recruited, vetted, hired and trained your employees, the client wants to validate that your standards and definitions of capabilities are in line with theirs. That is a reasonable exercise assuming you want the business and you feel that this investment of time and validation will lead to a long, fruitful relationship.


I've never heard of this idea before. It horrifies me, because it says, "We don't trust your judgement."
In your shoes, I would definitely be open to including the client(s) in the drafting of the "Wanted" list of skills, experiences and talents.
But doing your work? That's what they're supposed to be paying you for.
And you're right, it would be so time-consuming nobody would ever get any work done.
I would check if this kind of thing is done in the defense industry; I'm not aware of it but it's the only place I can think it might happen.
"How am I creating value for you, then?" is the question I'd ask the prospective client if they pushed about this.


I completely understand your apprehension.
As an advisor to some virtual teams, this can sometimes stem from distrust of procedures and in other cases, it can be an 'order from upstairs' given in the name of 'quality control'.
Short answer - This cannot become standard protocol. It will cost you time, employee trust (they will feel let down by you) and give clients a sense of power that is unwarranted and may be misused.
That said - you must continue a conversation with the client on your level. Is the project high risk? Have they had a history of bad fits before? They have a right to be heard regardless, given reassurances to specific grievances, and exceptions can be made, but your employees need and expect your protection first.
Happy to continue the conversation!
Are you a commodity business or a value-add business? Because I'll give you a different answer.
When choosing a development shop, I advise my clients to figure out where in the organization technical leadership resides.
If you are a value-add business whose processes and procedures train developers how to deliver high-value, then the technical interview should be you and your technical leadership team, and should go into what you train, who you hire and why, etc.
If you are a simply providing access to developers as a commodity, then you need to expect people will want to do a technical interview of the developers to learn how they will approach their project.
I also advise clients to interview anyone they will work with directly, just to make sure they are good problem solvers and communicate well.
Clients are getting much smarter to the fact that there can be a huge difference in productivity and quality between seemingly identical developers, and a few carefully chosen interview questions can expose that difference. If you don't want to allow interviews, you need to figure out how can you proactively show productivity and quality standards to your prospects and clients.
Good luck!
Related Questions
-
How to find custom business application development projects (CRM, ERP, accounting software) etc?
You are facing a classic chicken and egg problem. You want premium projects but cannot get them because you haven't done any yet. To solve this, you need to think from your target customers standpoint. Why would a customer buy from you? What do you offer that others don't have? Once you define that, the second thing you need to understand is how companies acquire their services. The buying process in a company is different from consumer buying cycle. So you need to figure out how you will play this dance. Lastly, to acquire customers, you will need to do some marketing and network. LinkedIn would be a good starting point. Another option would be to start out small and bid for projects on oDesk, Guru or other similar sites All the best.... Happy to talk if you have more questions.
-
What is the best way to evaluate a candidate for product manager?
Some of this is stage dependent and all of it is highly dependent on the team above the product manager. The simplest answer of course is to find PM's from companies who have had exemplary success where the Product Manager candidate either led prior success or was exposed to it in a meaningful way. A simple starting point is to ask them to give you examples of conflicting opinions on a feature and how they evaluated the conflicting opinions and made a decision and tracked the success or failure of that decision. AirBnb actually gives PM's homework as part of the interview process where they have to actually present a unique idea (from scratch) to the interviewing team. Happy to talk to you about best process based on your stage and existing team.
-
What does it mean to 'grandfather you in' in the tech world?
It stands for allowing someone to continue doing or use something that is normally no longer permitted (due to changing regulations, internal rules etc.)
-
If an employee receives another job offer and can't make up their mind, what's the best way to force them to make a decision and stick to it?
It's great that this employee has been transparent about the fact another company wants him. The problem is that this employee is ambivalent about his connection to your Company. Really, under 100 employees at least, this is unacceptable. I would first reflect on why you think he's looking elsewhere. Then, I'd ask him that, admitting that you have failed to create an environment in which he has stayed engaged and motivated on what he's working on. If his answers seem reasonable and you can commit to making the changes necessary, then you won't need an employment contract, he'll stay on his own desire, because you listened to him and improved his situation. If his requests seem unreasonable or you know you won't be able to make those changes, fire him *today.* This situation can contaminate your entire company quickly. Yes, swapping someone out will always be a bit of a setback, but you want *everyone* on your team, feeling motivated and excited by what they're doing. It sounds like you're making your decision out of fear (having to find and hire another engineer) versus what's best for the Company, long term. Happy to talk to you in a call. Problems like this are within the sweet spot of my skills and passion.
-
We're developing a web product with a team of 10 developers. How can I protect my source code if anyone leaves the company?
If you're using source control, it's easy to track source and control access — or revoke access — if someone leaves the company. Also, your developers should have signed a contract about the project itself that clearly places the source code under your/the client's/the company's control, and if/when they leave, they release all rights to code created under that contract. You can never be 100% sure, but these small steps will at least ensure a legal high ground should anyone steal code. Good luck!