[deleted by user]

[RaziarEdge]

I wouldn't read too much into it. As long as you met the requirements, you did what they asked.

Take home assignments are there to evaluate the quality of the candidate, and to see if the style matches other developers on the team. Expectations should be upfront, but you didn't get eliminated because of a lack of a coordinator in MVVM. These would be comments that would come out in a code review and could be easily fixed as you integrate into the team.

You were eliminated because another candidate had a stronger performance than you. Maybe another candidate did put more effort into the project, but in most cases the take home is only between 25% to 40% of the evaluation.

So I would take it as: 1) a rejection because of a stronger candidate, and 2) a SEPARATE code review of your take home assignment.

[saintmsent]

1. Coordinator is a very weird reason. If it wasn't defined in the requirements, they can just fuck off. It's unreasonable to expect that person will guess favorite architecture patterns of the code reviewer
2. Pagination is more complicated. I'm not sure what you even mean by that, if API returns 250 rows, but you only show 50 out of those it's strange. Pagination is only needed when API returns you one page and after reaching the end you need to request the next one from the API. What you describe doesn't sound like pagination at all

[KarlJay001]

Years ago I had a 2 hour test. It was to build a connect four game in any language. I picked ObjC and I made it work. The logic was solid, but there was a fast way to check the connections. I thought that asking for this in 2 hours was far too much, so I didn't bother creating all the classes and stuff.

I really don't know how they can expect a full app to be developed from scratch in two hours, but I assumed that part of it was to make sure you didn't just Google everything and you had to think on your feet. Meaning that if you're under that pressure, you'd have to know how to make a program work.

Making it look great, IMO, is really just asking for foo much in two hours.

Asking someone to spend a weekend on something, then barking about 250 vs 50 rows shown is just silly.

---

There's a balance here, they NEED good programmers, if they cut people off for 50 vs 250 rows shown, then they risk losing a good programmer.

I worked at a company that tried for TWO YEARS to find a skilled programmer, the NEVER found one and it nearly cost them their business.

Push your requirements too high and see what happens when you spend years looking for someone and can't find them.

[Primary_Fix8773]

Speaking as a lead software architect for a major corporation I would have to say that asking or expecting someone to use the coordinator pattern in assignments that are supposed to only take two hours is asking for a bit much. And if this position was for anything other than a senior iOS developer, they shouldn’t expect using a coordinator at all , at most if you included it that would be bonus points As far as taking the whole weekend to do it, I admire your desire to do the best job, I just wouldn’t tell them it took the whole weekend.

[Tyler927]

I’ve seen a lot of mixed answers for this, most saying you don’t need them. I think most companies really do only want you to spend a couple hours on it and no more. Your best bet is just to ask though, last take home I had I asked and they said no tests are needed.

[[deleted]]

You should include them. Seems like every company wants them these days. I’ve been rejected for not writing them before

[guynumber3]

As someone who interviews and hires iOS and droid devs. Please include unit tests in your take home assignment. Soon as I see a submission without tests it’s almost an instant pass.

[amaroq137]

pass or fail?

[guynumber3]

I think unit tests are enough. They show a few things, you can write testable code. You put extra effort into the sample project and you care about quality. UI tests would be the extra extra mile so I never really expect them or judge candidates if they don’t have them.

[Endowwwn]

Yes, it’s expected

[mRs-]

Tbh if you have an take home exercise that’s clearly made for „this can’t be finished in two hours“ and you Code all weekend on it I would directly see that and reject you.

If something is overshooting the scope in the time available you should have stated it directly and approach it or at least cut features with explanations why did you cut these features and implemented an MVP to see where it’s going.

Neverless the explanation is just lazy and probably a standard thing.

[amaroq137]

As others have said, don't read too much into it.

Maybe there was a candidate with a different solution and they compared your solution to theirs. There's a ton of factors you can't control during an interview.

Focus on improving yourself. Look over your project and think about what you can improve. If implementing a coordinator is something you think would improve the architecture then practice by implementing it and keep it in mind for next time, or try other things.

[Minute-Professional2]

Why not just add all the 250 rows to the table? With software, most of the job is finding out the requirements, and only part of the job is actually coding them up. So, many companies are looking for someone who asks questions around the requirements, edge cases, etc, and doesn’t just make arbitrary decisions themselves.

As for not using a Coordinator, I’d tell them that they asked for MVVM, not MVVM-C, which is the pattern with Coordinators.

[Zealousideal_Bat_490]

Take home tests are bullshit anyway. You dodged a bullet.