Questions entretien Backend Engineer chez Native Instruments |

Questions entretien Backend Engineer chez Native Instruments

Entretiens chez Native Instruments

1 Avis sur les entretiens d'embauche



Obtenir un entretien

Obtenir un entretien






Entretien de Backend Engineer

Candidat à l'entretien anonyme - Berlin (Allemagne)
Aucune offre d'embauche
Expérience positive
Difficulté moyenne


J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien à Native Instruments (Berlin (Allemagne)) en juillet 2019.


I applied for the backend developer position and had a skype interview a week or so later. immediately afterwards I was given a coding assignment to complete within a week. I received a reply about a week and a half after submitting the code but unfortunately I was unsuccessful.

Questions d'entretien d'embauche

  • Please develop a small containerised product service with an HTTP API. We would love to see your working solution including tests, a local development environment, and some documentation.

    The intended API can be interfaced via HTTP and should provide the following endpoints:

    GET /products
    POST /auth
    GET /user
    GET /user/products
    POST /user/products
    DELETE /user/products/{SKU}
    (SKU meaning a unique product identifier in this and following context)

    Users, products and previous purchases are provided as CSVs in the attached zip and need to be imported into the service once. For simplicity the user password is not hashed in the provided file.

    The `/products` endpoint should return all available product data.

    The API should offer some basic authentication to authenticate a specific user at the `/auth` endpoint. After a user is authenticated, the user should see user data (returns name) at the `/user` endpoint, the purchased products at `/user/products` (returns SKU (unique product identifier) + name). It should be possible to attach or remove purchased products to a particular user account.

    Please consider:

    The application should be containerised using Docker
    The solution should be provided as a single archive, containing a git repository and a Docker Compose file to start the application
    The application should log any output to stdout
    The application should use HTTP status codes to indicate success or failure of an operation
    The data stored should be persisted so a restart of the application does not clear it
    Try to focus on solving the problem and don’t over-engineer your solution. Please consider using a framework. Don’t worry if you don’t have time to finish everything, please address the potential optimisations and we can talk about that in the next step.   Répondre à cette question
Ne manquez aucun emploi que vous aimez
Ajoutez un CV pour postuler facilement à des offres depuis n'importe où. C'est simple à configurer.