WATCH · Choosing a Tech Partner_
The Real Reason Software Teams ‘Go Offshore’ (And What to Ask About It)
Saleem Beg · Founder, Teque
● 1:40 · Posted 4 months ago
KEY TAKEAWAYS_
- The problem isn't offshore — it's transparency about who's actually working
- Ask for specific names and CVs, not "our team"
- The red flag isn't location — it's vagueness
TRANSCRIPT_
We use a global team is often code for something you should know about. Look, I'm not here to bash offshore development. Some of the best engineers I've worked with are based overseas. The issue isn't location. It's transparency.
And here's the pattern I've seen destroy projects. You meet an impressive team during the sales process. smart people, great uh portfolio, reassuring accents, you sign the contract and then different people start showing up to meetings. The senior developer who sold you becomes a project advisor you never see. The actual work gets done by junior developers you weren't introduced to.
Quality drops, communication gets harder, and when you complain, you were told, "Uh, this is how we scale to meet your needs." See, this isn't an offshore problem. It's a bait and switch problem. So, here's what to ask before signing up. Who specifically will work on my project? Not our team, but I mean names and CVs. Where are they located? Not the company, but the individuals. What
happens if I'm not happy with someone? Can you replace them without derailing the project? Will the people I meet in sales be the people who do the work? The red flag isn't we have developers in another country. The red flag is vagueness. If they can't tell you exactly who's building your software, ask yourself why.
“The senior developer who sold you becomes a project advisor you never see.”
Prefer to read? This take is also a written article.
Read the article →


