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

      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

      Ramp

      ¿Esta es tu empresa?

      Información
      Opiniones
      Sueldos y beneficios
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Opiniones sobre Ramp | Ofertas de empleos en Ramp | Sueldos en Ramp | Beneficios en Ramp
      Entrevistas de Ramp Entrevistas para el puesto de Software Engineer - Backend en Ramp Entrevista de Ramp


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empresas

      • Cuenta gratuita de empresa
      • Centro de empresas

      Información

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

      Trabaja con nosotros

      • Anunciantes
      • Empleo
      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 de primera mano.

      Búsquedas de empleo

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

      Entrevista de Software Engineer - Backend

      10 may 2024
      Candidato de entrevista anónimo
      New York, NY

      Otras opiniones sobre las entrevistas para el puesto de Software Engineer - Backend en Ramp

      Entrevista de Backend Software Engineer

      21 sept 2025
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia neutra
      Entrevista difícil

      Solicitud

      Envié una solicitud electrónica. Acudí a una entrevista en Ramp en sept 2025

      Sin oferta
      Experiencia neutra
      Entrevista difícil

      Solicitud

      Envié una solicitud electrónica. Acudí a una entrevista en Ramp (New York, NY)

      Entrevista

      They make you take a 1-1.5 hr coding test to weed out candidates. I’ve heard of people acing it and not making it to the next steps. Kind of seems like a waste of time.

      Preguntas de entrevista [1]

      Pregunta 1

      They give a coderamp coding test.
      Responder pregunta
      El proceso duró 2 semanas. 

      Entrevista

      I completed an online assessment where I was asked to build a banking system using OOP. The first two steps were not too difficult but they got progressively harder in the 3rd and 4th steps.

      Preguntas de entrevista [1]

      Pregunta 1

      Build a banking system where you can initialize users, update their balances, withdraw money and send them between users. Also add a method to find the most frequent senders ect.
      1 respuesta

      Entrevista de Software Engineer, Backend

      12 feb 2025
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia negativa
      Entrevista normal

      Solicitud

      Envié una solicitud electrónica. Acudí a una entrevista en Ramp

      Entrevista

      The interview process heavily relies on CodeSignal with leetcode-style questions, which feels excessive and misaligned with the actual role. While these algorithms might be relevant at FAANG companies, this approach wastes candidates' time and doesn't reflect real-world work. The company should reconsider their interview strategy.

      Preguntas de entrevista [1]

      Pregunta 1

      We want to query an API endpoint to receive data about currently available apartment listings from a rental website. Among the data fields is a column called num_bedrooms, which takes the value of 1 for a "1-bedroom" apartment and 0 for a "studio". Note: This rental agency only works with studios and 1-bedroom apartments, so there will never be 2+ bedroom listings. Each listing includes information about a "studio" or a "1-bedroom" apartment, so there will never be a listing with both a "studio" and "1-bedroom" offerings in one posting. The algorithm used occasionally mistags the num_bedrooms value. Specifically, sometimes a "studio" is tagged as having num_bedrooms = 1 or a "1-bedroom" is tagged as num_bedrooms = 0. Further investigation revealed it to be an issue with one of the data fields, description, and the way our algorithm parsed the field to extract a num_bedrooms value. For example: "description": "Beautiful 1-bedroom apartment with nearby yoga studio." was detected as a yoga studio instead of 1-bedroom and incorrectly had num_bedrooms = 0. Your task is to write a function that takes in the jsonData and corrects this problem. The GET request retrieves the data as a string which looks like this: jsonData = [ { "id": "3", "agent": "Ton Jett", "unit": "#12", "description": "Beautiful 1-bedroom apartment with nearby yoga studio.", "num_bedrooms": 1 }, ... ] While correcting the problem, remember the following edge cases: If the word "studio" or "1-bedroom" is preceded immediately by any of the words: "yoga", "dance" or "art", don't consider it for num_bedrooms value. If the description does not contain the word "studio" or "1-bedroom", do not change the value for num_bedrooms. The rules above should be applied regardless of punctuation or letter casing within the description field. Your end goal is to return an array of integers representing num_bedrooms for each rental listing, example: [0, 1, 1, 1, 0, 0]. Example For jsonData = "[{"id": "1", "agent": "Radulf Katlego", "unit": "#3", "description" : "This luxurious studio apartment is in the heart of downtown.", "num_bedrooms": 1},{"id": "2", "agent": "Kelemen Konrad", "unit": "#36", "description": "We have a 1-bedroom available on the third floor.", "num_bedrooms": 1},{"id": "3", "agent": "Ton Jett", "unit": "#12", "description": "Beautiful 1-bedroom apartment with nearby yoga studio.", "num_bedrooms": 1},{"id": "4", "agent": "Fishel Salman", "unit": "#13", "description": "Beautiful studio with a nearby art studio.", "num_bedrooms": 1}]" the output should be solution(jsonData) = [0, 1, 1, 0]. The above jsonData represents the following JSON: [ { "id": "1", "agent": "Radulf Katlego", "unit": "#3", "description": "This luxurious studio apartment is in the heart of downtown.", "num_bedrooms": 1 }, { "id": "2", "agent": "Kelemen Konrad", "unit": "#36", "description": "We have a 1-bedroom available on the third floor.", "num_bedrooms": 1 }, { "id": "3", "agent": "Ton Jett", "unit": "#12", "description": "Beautiful 1-bedroom apartment with nearby yoga studio.", "num_bedrooms": 1 }, { "id": "4", "agent": "Fishel Salman", "unit": "#13", "description": "Beautiful studio with a nearby art studio.", "num_bedrooms": 1 } ] Explanation: In the first listing, description = "This luxurious studio apartment is in the heart of downtown." "studio" should have num_bedrooms = 0; In the second listing, description = "We have a 1-bedroom available on the third floor." "1-bedroom" should have num_bedrooms = 1; In the third listing, description = "Beautiful 1-bedroom apartment with nearby yoga studio." "1-bedroom" should have num_bedrooms = 1. Ignore "studio" since it is followed by "yoga". In the fourth listing, description = "Beautiful studio with a nearby art studio." "studio" should have num_bedrooms = 0. Ignore the second appearance of "studio" since it is followed by "art". Input/Output [execution time limit] 4 seconds (py3) [memory limit] 1 GB [input] string jsonData String in JSON format. It's guaranteed that each listing contains the fields "id", "agent", "unit", "description" and "num_bedrooms". Guaranteed constraints: 136 ≤ jsonData.length ≤ 15366. [output] array.integer Return an array that contains the correct values for num_bedrooms for all of the listings in jsonData. Note for Python3 users: if you use a numpy array, casting to a list creates a list of numpy.int64 integers. Your returned array needs to be an array of standard Python int types. [Python 3] Syntax Tips # Prints help message to the console # Returns a string def helloWorld(name): print("This prints to the console when you Run Tests") return "Hello, " + name
      Responder pregunta
      5

      Entrevista de Software Engineer, Backend

      2 abr 2025
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia negativa
      Entrevista normal

      Solicitud

      Envié una solicitud electrónica. El proceso duró 1 semana. Acudí a una entrevista en Ramp en feb 2025

      Entrevista

      Got a code signal assessment where I solve 1 coding problem. Got a full score but was rejected. I never knew the reason as to why I got the rejection mail. Also applied to other SWE position but same thing

      Preguntas de entrevista [1]

      Pregunta 1

      I got a priliminary coding assessment
      Responder pregunta