Ir al contenidoIr al pie de página
  • Empleos
  • Empresas
  • Sueldos
  • Para empleadores

      Impulsa tu carrera profesional

      Averigua cuánto podrías ganar, encuentra el empleo perfecto y comparte información sobre tu vida laboral y personal de forma anónima.

      employer cover photo
      employer logo
      employer logo

      Beyond

      Empleador activo

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Beyond | Empleos en Beyond | Sueldos en Beyond | Prestaciones en Beyond
      Entrevistas en BeyondEntrevistas para el cargo de Remote Senior Backend Engineer en BeyondEntrevista en Beyond


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empleadores

      • Cuenta de empleador gratuita
      • Centro de empleador

      Información

      • Ayuda
      • Pautas
      • Condiciones de uso
      • Privacidad y opciones de anuncios
      • No vender ni compartir mi información
      • Herramienta de autorización de cookies

      Trabaja con nosotros

      • Anunciantes
      • Oportunidades laborales
      Descargar aplicación

      • Buscar por:
      • Empresas
      • Empleos
      • Ubicaciones

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor", "Worklife Pro", "Bowls" y sus logotipos son marcas comerciales registradas de Glassdoor LLC.

      Empresas seguidas

      Sigue a tus empresas favoritas para estar al tanto de las últimas oportunidades y disponer de información desde adentro.

      Búsquedas de empleo

      Recibe recomendaciones y actualizaciones personalizadas al iniciar tu búsqueda.

      Entrevista para Remote Senior Backend Engineer

      13 feb 2022
      Candidato de entrevista anónimo
      Oferta rechazada
      Experiencia negativa
      Entrevista promedio

      Solicitud

      Me postulé en línea. El proceso tomó 6 semanas. Acudí a una entrevista en Beyond en dic 2021

      Entrevista

      I applied online and then recruiter reached out to me. We had an online call regarding the my experience, what company does, my notice period, salary expectations and such. Later I had a call with the Engineering Manager which went well as well and proceed to the next stage. Next step was home assignment. Assignment was purposely made time consuming by blocking usage of ORMs or any database and asking you to work with a file for database. My assignment reviewed by the team and it was positive therefore I progressed with the next stage. This stage consisted of two meetings, one is tech challenge which is discussing over the home assignment, the other is the architecture. I had both of those interviews also and got positive feedback. In the end I got the offer. I asked a few details regarding the offer and then in the reply I got, they mentioned that my notice period is long and could be problem. After all of these interviews and for an information I provided in the first call!!! Anyways I wanted to accept the offer therefore I told them I can discuss with my current employer and possibly shorten my notice period and we can sign the agreement if I can manage it but they still pulled the offer back without any other information. Totally dishonest, unprofessional company. I still have no idea why they pulled the offer back even when I tried my best to help them with the notice period.

      Preguntas de entrevista [2]

      Pregunta 1

      Home assignment: Create endpoints in a flask API application. Your solution **must persist data into a file** without using an ORM library or a DB system. Your solution **must use [open exchange rates][open-exchange-rates]** to get the exchange rates. The free plan is enough to complete this task. The response format of your API **must be JSON** and a proper use of HTTP status codes and error handling is expected. - `POST /listings` endpoint - Send JSON data in the body, for example: ``` { "title": "Comfortable Room In Cozy Neighborhood", "base_price": 867, "currency": "USD", "market": "san-francisco", "host_name": "John Smith" }, ``` All fields are required except for `host_name`. - Return: the listing information (including its ID) in a JSON format. - `GET /listings/:id` endpoint - Return: the listing information (including its ID) in a JSON format. - `PUT /listings/:id` endpoint - Send JSON data in the body - Update only the fields present in the request - Return: the listing information (including its ID) in a JSON format. - `DELETE /listings/:id` endpoint - A successful response must mean a listing was deleted. - `GET /listings` endpoint - Return: a list of listings in a JSON format. - This endpoint should allow to filter by market and base price/currency. Those filters must be implemented as query parameters: - `market` - optional - A single market or a list of markets separated by commas. It uses the market codes. - E.g.: `?market=paris` or `?market=paris,san-francisco` - `base_price.[e|gt|gte|lt|lte]` - optional - The comparison type is part of the query parameter. - E.g.: `?base_price.gt=500` or `?base_price.lte=300` - `currency` - optional but required when base price is specified - It uses the currency codes. - E.g.: `?currency=usd` - `GET /listings/:id/calendar` endpoint - This endpoint returns the listing's calendar (365 days starting from today). - It must allow to return the calendar in any currency. The default being the listing's currency. This parameter must be implemented as a query parameter: - `currency` - optional - It uses the currency codes. - E.g.: `?currency=usd` - Format for dates: `YYYY-MM-DD` - Calendar rules: - For the Paris and Lisbon markets: Saturday and Sunday => 1.5x of base price - For the San Francisco market: Wednesday => 0.70x of base price - For the rest of the markets: Friday => 1.25x of base price - Example of response: ``` [ { "date": "2019-01-01", "price": 500, "currency": "USD", }, { "date": "2019-01-02", "price": 550, "currency": "USD", }, ... ] ```
      Responder pregunta

      Pregunta 2

      Design Question: Your customers are short term rentals ho might have multiple rental places and working with multiple service providers such as booking, airbnb. Design a system where you will get the information of a booking from one system and block availability in other system.
      Responder pregunta
      1
      avatar
      Respuesta de Beyond
      4y
      We understand your frustration and agree we could have done a better job identifying the 3 months notice period as an issue earlier in the interview process. We care deeply about our employee and candidate experience, and are always striving to improve where we can. We have since then changed our approach and ask for notice period on the first call to properly asses against the intended start date for the position. We are truly grateful for your feedback as it has helped us to iterate, improve, and prevent that situation form happening again in the future. -Francois Toubol VP, Engineering