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

      Form3

      Empresa activa

      Información
      Opiniones
      Sueldos y beneficios
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Opiniones sobre Form3 | Ofertas de empleos en Form3 | Sueldos en Form3 | Beneficios en Form3
      Entrevistas de Form3Entrevistas para el puesto de Senior Software Engineer en Form3Entrevista de Form3


      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 Senior Software Engineer

      18 ago 2020
      Empleado anónimo
      Oferta aceptada
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Envié una solicitud electrónica. El proceso duró 6 semanas. Acudí a una entrevista en Form3 en ago 2020

      Entrevista

      An in-house recruiter from Form3 reached out to me on LinkedIn in early July 2020. I researched the company then submitted my CV and a cover letter online. Their recruitment team reached out to me and I had a 30 minute phone call with a recruiter a day later. This was mostly them explaining Form3 and its practices, but a little about my experiences and my approximate salary expectations. I was then invited to undertake a programming exercise which I could complete in my own time, but which was expected to take around 8-12 hours. This required designing and implementing a client in Go which would communicate with an API server (which they provided, including the test environment in a Docker container to run locally). The client had to implement GET, POST, DELETE verbs for a resource, and implement paging for a collection of that resource. Asides from testing libraries, no other external libraries were allowed in the Go code. The instructions were otherwise open-ended, allowing me to make a number of design decisions. I undertook this exercise over 2 weeks; I reckon it took longer than the estimated 12 hours, mostly because I was context-switching over the 2 weeks. I liked that the take-home exercise was based on an actual, real-world like problem and it meant that there were no 'whiteboard' coding exercises in the interview process. It was more involved and comprehensive an exercise than some other take-home challenges I've done, and does take a longer time. I felt it was worthwhile putting the time into doing this exercise, even if my work didn't lead to the next stage in the interview, as it was good practice with working with a real-world API, and making design decisions about the client. In the meantime I had a further 30 minute phone call with the recruiter in late July, where they went further into Form3's compensation structure and benefits. We discussed a little bit more about me working as a contractor abroad, rather than a permanent employee. This was because they did not as yet have a legal entity in my country of residence. After I submitted the take-home exercise, it was reviewed by their engineers the following week. I was then invited to a 1.5 hour remote interview via video call in mid-August. This call was preceded by a 20 minute call a day or two earlier with the recruiter to explain their interview process. The interview consisted of three parts: - Part 1 (30 minutes): I had to discuss my submitted take-home exercise and parts of the code and my design decisions were challenged. - Part 2 (30 minutes): I was asked a number of questions about my knowledge of basic networking and API protocols. My experience with working remotely was discussed. - Part 3 (30 minutes): I was presented a schematic diagram of a backend system, a problem was described (an outage in the system reported by a customer) and I was asked to ask a number of questions with the goal of identifying the root cause and how to resolve it. This part of the interview focused on the fact that on-call duty would be part of the role. Each part was held with a different interviewer, either a senior engineer or engineering manager/director with Form3. In Part 3 I took the opportunity to ask the interviewer a number of questions about the company. We went into a lot of detail, and went over time - I appreciated the interviewer taking that additional time out of their schedule. I really appreciated the scenario in Part 3; this was based on a real-world scenario the engineer had encountered and allowed me to apply problem solving and systems knowledge. I received a follow up phone call from the recruiter to get my immediate feedback to the interview and to describe the next steps and timelines. I also had the opportunity to ask a number of further questions about Form3, including their approach to D&I, opportunities for career progression in the future, etc.. I received another call a week later with an offer.

      Preguntas de entrevista [8]

      Pregunta 1

      Describe TCP/UDP, and why you might use either?
      Responder pregunta

      Pregunta 2

      Would I start programming by writing unit tests or integration tests?
      Responder pregunta

      Pregunta 3

      What were the pros and cons of different ways of creating a Go object?
      Responder pregunta

      Pregunta 4

      Given a schematic diagram of a backend system (showing loadbalancers, ingress controllers, service mesh, service discovery, databases etc.), and a report that a customer had experienced an outage; what questions would I ask of the system to identify the root cause? How would I then resolve the issue? After each relevant question I asked, the interviewer provided more details in response.
      Responder pregunta

      Pregunta 5

      Explain authorization of a client connecting to an HTTP API server. Discuss Basic Auth and JWT in more detail.
      Responder pregunta

      Pregunta 6

      Have you worked 100% remote before?
      Responder pregunta

      Pregunta 7

      Imagine a situation where the developers of an API had altered the interface and broken the clients; how would you prevent this situation from occurring?
      Responder pregunta

      Pregunta 8

      Describe the benefits of Infrastructure as Code.
      Responder pregunta
      4

      Otras opiniones sobre las entrevistas para el puesto de Senior Software Engineer en Form3

      Entrevista de Senior Software Engineer

      14 mar 2023
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia negativa
      Entrevista fácil

      Solicitud

      Envié una solicitud electrónica. Acudí a una entrevista en Form3 en feb 2023

      Entrevista

      Homework assignment: They will ask you to create a library for their payment API. This task is pretty straightforward. However, it's a lot. From this assignment, you can tell that they don't assess your technical skill and ask you to invest tons of time in the beginning, then their reviewer will just say, "missing integration test," and then reject you. After the home assignment, they'll discuss this for the next round. Just like other reviews. It's not worth your time. They're not interested to see your quality. I abandon the test since I'm pretty sure with this kind of test, anyone can pass with just extra effort.

      Preguntas de entrevista [1]

      Pregunta 1

      check their github. it's publicly accessible
      Responder pregunta
      6

      Entrevista de Senior Software Engineer

      24 oct 2022
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia neutra
      Entrevista fácil

      Solicitud

      Solicité el puesto a través de un captador. El proceso duró 2 semanas. Acudí a una entrevista en Form3

      Entrevista

      Would not reccomend. Very streamlined process. I was approached by the HR via LinkedIn; they were extremely polite and described the position and the entire process from start to finish. It begins with a take-home exercise, a review and (if you passed the review) three quick technical interviews. There is no problem if you do not know their commonly used language, Golang. Apparently, they care for the talent and not the familiarity in the language which is an amazing "thumbs up" for company culture or at least that is the impressions you get in the begging. I submitted my exercise, and they replied in exactly 5 days. When it came to my review, my code was well written, documented and well tested and the feedback was positive about it. But the assignment was rejected without a further discussion for the below reasons: - Not liking the way data are passed into functions (in context you are asked to learn the language and get the job done) so using method A or method Z should not matter. - No retries policy implemented. This is a dealbreaker. Arguably, they create a myriad of services doing payment processes, of course they would want a standalone policy for each process, but they should give more context on what they expect. Retries policy are commonly handled manually. - Not enough assertions in the Create Response. Assert every single variable. That is a quite ridiculous statement to reject an assignment to. My final verdict, quite unfair handling. It is quite possible that they have passed lesser assignments just for the retry policy as it is quite important internally for the company but that does not judge a good software engineer. They should be more objective with their approach. In the code assignment they should judge code and ability to cover the assignment. Just for context, you are asked to learn a new language, create a package for that language, read their API documentation, make integration tests and finally have it containerized and tested against a fake version of their API in a provided docker-compose. So, outright rejecting an application from the coding assignment with mixed feedback is quite questionable. Knowledge should be judged in the technical interviews. Honestly, would not recommend. The impression from the engineers was like being "human-robots" - missing the forest for the tree. This is quite a red flag.

      Preguntas de entrevista [1]

      Pregunta 1

      You are being asked to create an HTTP client package which should be capable to be used out of the box in a production enviroment. The process is mainly judged on the tests.
      Responder pregunta
      11

      Entrevista de Senior Software Engineer

      30 nov 2022
      Empleado anónimo
      Londres, Inglaterra
      Oferta aceptada
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Solicité el puesto a través de la recomendación de un empleado. El proceso duró 2 semanas. Acudí a una entrevista en Form3 (Londres, Inglaterra) en nov 2022

      Entrevista

      I was referred by an ex-colleague who already worked at Form3. After referring the recruiter sent me an e-mail for an initial call. It was a nice and easy going conversation and got really excited by the fact that she was confirming what I already knew about their values, how they work, what life of a senior engineer looks like at Form3 etc. After the first call I've got a take home exercise to implement an API Client (in Go) for their Fake Account API. This is where you can show your quality (even though the exercise itself is not that challenging), you can show that you understand best practices, how to test your software and how to make it readable and understandable etc. After finishing your take home exercise an Engineering team of Form3 is gonna review the code and this code will, after a short introduction on Form3, be part of the discussion in Part 1/3 of the next interview steps, where you can explain your approach, your tradeoffs etc. But this depends on the review of your code. One other thing I liked about their approach is that they don't mind if you're not experienced with Go (as long as you write that in your README). They will take the lack of experience into account, as they're looking for problem solving ability and engineering standards. Interview part 2/3 is about System Design and how you would change an architecture if certain requirements would change (how would you plan for fault tolerance, resiliency, high availability, consistency etc.) to see if you understand the fundamentals of distributed systems. The final part is a debugging exercise where you're simulating an on-call rotation. You'll get scenario based questions based on an microservice architecture diagram and get to ask the interview all the questions you like (what's in the logs, what metrics are available, other characteristics that may lead to finding the simulated issue in the scenario. Before the aforementioned interview takes place, the recruiter will reach out to you to make sure you're well prepared and know what to expect. For some companies every candidate is just a number on the list and for some companies you're a person they care about and they want to give an equal opportunity. The latter is the case with Form3. This is something I really liked and many other companies could take this as a good example to learn from.

      Preguntas de entrevista [1]

      Pregunta 1

      - Form3 introduction & discussing Takehome exercise (review) - System Design exercise - Debugging exercise (on-call simulation) based with scenario based questions based on an microservice architecture diagram
      Responder pregunta
      2

      Las mejores empresas en cuanto a «Remuneración y beneficios» cerca de ti

      avatar
      Embracon
      4.0★Remuneración y beneficios
      avatar
      Cartão Elo
      4.3★Remuneración y beneficios
      avatar
      TakePayments
      4.0★Remuneración y beneficios