El proceso duró 2 semanas. Acudí a una entrevista en Salt Security
Entrevista
passed two technical interviews and home assignment, just to receive a whatsapp messages that I didn't pass even throu I am very good.
wasted my time and hours of home assignment.
I will not recommand you to start an interview there.
Preguntas de entrevista [1]
Pregunta 1
home assignment to write microservice and parse input
I had a 1.5-hour interview where I thoroughly shared details about my professional projects and experience. While I felt confident about my performance, I was disappointed to receive a generic rejection email with no constructive feedback. This left me feeling that the time and effort I invested were not truly appreciated. Candidates invest significant time preparing for interviews, and it would be respectful to provide feedback or at least a more personalized response.
Envié una solicitud electrónica. El proceso duró 2 semanas. Acudí a una entrevista en Salt Security (Tel Aviv)
Entrevista
First interview, design a feature.
Second interview, an assignment which you're meant have in front of you. The inexperienced team lead and interviewer scrolled through the question with the many details and then hid it away he was afraid it will be copied.
Then asked to define the spec. The spec is in the document dmmy but you're hiding it.
In a normal task you look at the task and define what you need 10 minutes let's day, then discuss. It was all upside down.
Additionally, assumptions were made by him like doing things in n^2 instead of using data structures, evidently a junior interviewing a senior....
The junior interviewer seemed to think that using nosql entries when nested objects are reused in other entries frequently, is always a better option than mysql go figure..
Preguntas de entrevista [1]
Pregunta 1
You must implemented a system which detect whether api calls to a certain path are valid.
Design 1 end point which will define the model of the apis, So
for example
path salt-sec path
method: post
query params: {name(string, int), required:true/false
header :name(string, int) ,required:true/false...
body params:name(string, boolean).. ,required:true/false
So basically defining the params and what is a valid type of param for the specific path and method for each of the header, query param segments.
Second part
Define another end point which receives a request and checks based on the models saved if its a valid request
What would the client using this type of system want?
Describe the type data base and type of storage you'll use.
"They want nosql but mysql can work if you reuse params frequently. They probably only work with nosql..."
Describe the scale of a system like this.
