The mission: I loved the main goal of the company, which is lowering international banking costs to minimum possible levels while being transparent on fees and waiting times. It is a worthy task, and they have millions of real users with real problems.
About company structure: The company is a fast-growing ex-startup, with a mixture of startup and corporate. Hierarchically speaking, it has a flat structure with tribes organized around many consisting teams. All these teams have KPIs to push.
Good part of company structure: Since it is not yet corporate, there is still flexibility: people can work on stuff they know best, as opposed to only the things in their contract. Also, there is a lot of trust and openness to recommendations outside of your own team.
Good part of engineering culture:
The best type of employee for the company (in engineering):
Mostly there are two sources of issue with the company: one is having autonomous teams in a flat structure at scale, which is a very new concept with not so many ready solutions. The second issue is coming from the fact TransferWise is being an ex-startup with breakneck growth; there was no time tackling them. So in detail:
Negative consequences of autonomy:
Negative consequences of being an ex-startup:
My two cents:
Invest in the "KPI-less" core infrastructure, from frontend to data engineering. Make sure teams are spending a reasonable amount of effort on their own productivity (by paying back tech debt). Unfortunately, it might not be easily measured, so let them have some "risk budget."
Invest in regular soft skill training for team leads, or at least have personnel who possess these skills. Talented people laid off due to basic interpersonal conflict is a waste.
Validate and QA the logic teams base their decisions on. Invest in a bulletproof data collection platform.
All in all, I wish the entire company my best. So, good luck, keep up the great work, and I wish you all the best!
Screening round with a recruiter, followed by a tech test with a senior engineer or two. The recruiter round is a straightforward screening, as standard. The tech test tends to be a practical problem based on a real-life scenario relevant to Wise, no
Had an interview with a recruiter, and it was one of the best experiences. The whole meeting took around 30 minutes. We talked about the company and the project itself I'm applying to work on, about my previous experience, and the future parts of the
5 parts: 1. Initial interview: getting to know your recruiter. 2. Yech screening: simple coding question. 3. System design: system design challenge with some coding questions. 4. Product mindset: questions about the product development life cycle. 5
Screening round with a recruiter, followed by a tech test with a senior engineer or two. The recruiter round is a straightforward screening, as standard. The tech test tends to be a practical problem based on a real-life scenario relevant to Wise, no
Had an interview with a recruiter, and it was one of the best experiences. The whole meeting took around 30 minutes. We talked about the company and the project itself I'm applying to work on, about my previous experience, and the future parts of the
5 parts: 1. Initial interview: getting to know your recruiter. 2. Yech screening: simple coding question. 3. System design: system design challenge with some coding questions. 4. Product mindset: questions about the product development life cycle. 5