7digital Interview Questions

Application

I applied online. I interviewed at 7digital.

Interview

Phone call and follow-up coding assignment.

In the phone call the guys had nice mannerisms but leapt straight into the technical questions of the interview without seeming to want to know anything about me or why I was applying to the role. That question only came later as something of an after-thought. Otherwise, they asked relevant technical questions.

As for the coding exercise, it was stimulating and required a bit of thought into how to implement a solution. I was expected to complete it within 75 minutes. The provided README stated:

"You are not expected to complete all of the rules in the time available: this
is based on a real piece of work we did that took several days of investigation
and implementation. Concentrate on doing the simplest thing you can at every
step, and please ask if something is unclear. This can be a complex problem to
 get your head round so do ask if you need more information."

Nevertheless I provided a simple solution in more or less 100 lines of code that allowed for all the provided tests to pass, and added some tests of my own for extra guarantee that the code was stable.

I was therefore surprised to receive the following feedback:

"The team have all reviewed the code and we all came to the same conclusion: the code submitted was over-engineered and very hard to follow."

My immediate questions about this feedback were the following:
1) How can I overengineer a solution when given only 75 minutes to do it? If anything, the solution was under-engineered given the time constraints.
2) If they wanted me to provide a solution that met the complex requirements that took themselves days to implement, how do they expect me to do the same in under 75 minutes in less than 100 lines of code?

The obvious reaction I had was confusion about what was expected of me. Second, I felt like I had been dismissed unfairly. My solution was pretty bare-bones and definitely not the kind of implementation I would give in my professional work, but to claim that a mere 100 lines of Java code (including bracket lines) is "overengineered" and "hard to follow" sounds almost like they simply couldn't be bothered to take the time to look at the code properly, and dismiss it.

As such, if I were someone applying to this company, I'd really persuade you to ask in the phone interview whether they actually have a strong need for any new talent, or if they were just asked to fill the role from higher-up and have no strong desire for expansion.

Interview Questions

Application

I applied through a recruiter. The process took a week. I interviewed at 7digital in July 2014.

Interview

The interview start by covering CV a bit.
Following is technical Questions covers Java basic, some database (optimization), some http (get/post method, tcp and udp ) and some xml (well form and validation form) etc.

Interview Questions

Application

I applied through a recruiter. The process took 2 weeks. I interviewed at 7digital (London, England (UK)) in February 2018.

Interview

Phone interview with some tech questions, followed by a small coding task, then face to face interview with a coding session where you have to implement some methods which have some pre written unit tests.

Interview Questions

Application

I applied through a recruiter. The process took 1 day. I interviewed at 7digital (London, England (UK)).

Interview

One of my more confusing interviews, their process:

Recruiter - contacted me via LinkedIn and email, but at no point in the process did we talk on the phone. Emails were very informal which was odd given we'd never met or even spoken. Salary and hours never came into it until I specifically brought those up.

Phone interview - I was put on speaker phone with the development team, which was awkward as their voices were quite muffled and I had to ask them to repeat themselves a few times. They seemed suprised and disbelieving I had been coding from a young age, and even when I went through my developer history they did not seem appeased. I was told this was a Nodejs role with TDD in which I responded my main strength is C# and TDD was new to me. They were ok with this as they said the language didn't matter, as long as I could adapt and show good code design. I was accepted for an interview after the call ended, via an informal email by the recruiter.

Face to face - To begin I went into the shared office building and was waved through by security. I went up to their floor but could not actually access the floor as the door was security locked. After deliberating for a few minutes someone walked out from their side to go downstairs, so I was able to slip through then.

I was next given a piece of paper with a coding task on it and told I had 5 minutes to make some notes about it. The exercise was a rather simple POS system, so I jotted down the steps involved to make it work. This was done with a TDD mindset so I of course planned out what I was going to do before writing any code. We then sat together at a desk and pair programmed the system. I was told at this point it was not so much about the problem, but a test of how good i was to work with.

As was known, Nodejs wasn't my strong point, and I made a few mistakes in the process which the pair pointed out and helped correct (syntax around .map or getting keys from a dictionary). TDD was done mostly successfully, and I was confident they were happy with my process of red, green, refactor. Surprising to me was that the test framework they set up for the interview randomly failed multiple times, and at one point we had to rope in another developer to fix the problem.

After the task was complete I talked to another HR rep, who seemed to be tasked with having to make small talk with me, apparent from the fact that my travel time was of great interest to her. The illusive HR rep who talked to me via email was nowhere to be seen.

The final stage of the interview was held in a meeting room with the 'tech team'. They started off by asking if their interview process could be improved, which again I internally thought was odd seeing as I was only halfway through the process myself. They next went through my CV and experience, and mainly just listened to me regurgitate what was already written down. They seem surprised of my experience with Agile processes, despite it being on my CV. I was also told at this point that I was expected to be on call every weekend, but there was no mention if I would be compensated for this. After the meeting the interview was concluded.

Refusal - The next day I was emailed to be told it would a no from them, and I quote 'he lacks the experience we're looking for at the moment'. Feedback was given in that I should not have pre-planned the POS system on paper, despite being given 5mins alone with the problem and a pen, and planning to be a first clear step of TDD (think out the design, think about the structure, write tests for that structure). It seemed I did not fit their custom style of TDD, which apparently involves no forward thinking and one should simply dive straight into writing tests.

The next piece of feedback was that I did not do enough research on the company, which reflected badly on me. This is despite me signing up to their 7digital website, and perusing the store and seeing how it all worked. When I brought this up in the meeting, it was dismissed as the 'front-end' which isn't really what the business is. Instead I was vaguely told they are a b2b company that provides an API that is consumed by start ups and radio 6.

Finally my CV was problematic, not concise enough and I should have tailored it the role. This is despite it already being tailored to a software developer role, and the recruiter not mentioning any problems with it, nor was anything mentioned during the phone interview.

All in all a very confusing process, in which no one wanted to point out to me I wasn't right for the role until they very end, after I had given up my time to do a face to face. This process should have ended at the phone interview stage, where I made it clear what my experience was. All in all a negative experience.

Interview Questions

Application

I applied through an employee referral. The process took 4+ weeks. I interviewed at 7digital (London, England (UK)) in December 2015.

Interview

1st round was an informal chat and meeting with the HR Manager, 2nd round interview involved a 1.5 hour long more in-depth interview with the HR Manager on-site. The final round interview involved another informal chat with the CFO.

The 1st and final interview were really relaxed - more like a friendly chat than an interview.

Interview Questions

Application

I applied online. The process took 2 days. I interviewed at 7digital (London, England (UK)) in May 2015.

Interview

Phone interview with technical manager and employee started off by asking me questions about what I work with now and what my skills are. Most questions were related to give detailed examples of tasks I worked on for the current employer. (As much as I could without breaching confidentiality.)
The technical manager seemed to dig very hard for details.

Interview Questions

Interview

Code Test and Review and upload and finally hired the interview was mostly technical all in all good technical guys come on give me a cofee break word word word word word

Interview Questions