
Teamwork Ios Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 5 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Teamwork.
IOS Developer
HR first, then a code challenge for 8-12 hours. I'm really disappointed with this process. I spent 12 hours spread in some days and it seems the guy evaluating it didn't spend much. I got a really vague answer and they didn't even want to talk about it first, before rejecting me. I am pretty confident I sent a great code and a good app but I was rejected like I sent a stupid code. it was 12 hours I spent (the maximum suggested) and it wasn't continuous, I had to take a lot of breaks. What are they expecting anyway... I suggest you asked a lot of questions before starting this code, like, what structure are you expecting for the code, because when they say "it's up to you" that won't hellp, because they're not open minded to be flexible to each candidate, it seems the developer that evaluates us is expecting a person exactly like him...
- Sallary Expections
IOS Developer
So first I had like a recruiter call, just asking basic stuff about like, what do you know about the company, and why do you want to work there. Nothing technical at all. Then before I could even talk to an engineer, I had to do this coding project. It was like an 8 to 12 hour coding assignment where I had to build a sample app using Teamwork's API. They gave me a list of requirements and I did all of them. Then the day after I submitted it, I just got the usual rejection email, you know, the one that says they won't be moving forward with your application and will keep your CV on file. No reason was given, and when I asked for more details, they just gave some vague response like, "the code structure wasn't at the level of that submitted by other candidates".
- Coding assignment.
- No problem solving questions, no software engineering questions or even a hint of what they are looking for in their coding styles.
iOS Developer
I had an initial email interview with some basic questions like what I'm looking for and why I'm interested in Teamwork. Then there was a screening interview with the same basic questions, which I found a bit odd. The next step was supposed to be a development test, but for no given reason, I wasn't allowed to do it. I built a full application connected to the Teamwork API, which they likely didn't even review. It felt like a waste of time. Teamwork says they don't give feedback during early stages, and they even say that months after the interview. This shows the lack of recruiter and human quality there. Teamwork boasts about its great atmosphere and people, but they should realize that candidates who prepare for weeks and study their company deserve some basic respect and explanations. I'm a person, not a robot.
- What are your career aspirations?
- What motivates your interest in joining Teamwork?
- Propose a minimum of two suggestions for enhancing Teamwork's products.
Teamwork Ios Engineer Interview Questions
Quoted word for word from Teamwork interview reports.
“No problem solving questions, no software engineering questions or even a hint of what they are looking for in their coding styles.”
Read reports →“Propose a minimum of two suggestions for enhancing Teamwork's products.”
Read reports →“What are your career aspirations?”
Read reports →“What motivates your interest in joining Teamwork?”
Read reports →“Tell me about your previous roles and projects.”
Read report →Formats, difficulty and experience
Across all 5 Teamwork interview reports.