I got a rejection from my Stripe interview, they mentioned it was due to the coding round but refused to provide more feedback. Stripe folks, can you please shed some light -what is the criteria used for coding rounds? I did 2 iterations on the question and had to look up some APIs.
Looking up API is not an issue. Problems are not typical leetcode, so they look at your problem solving, testing and communication.
That’s what confuses me - I gave good examples of what the data structures would look like and what data they’d contain before I started coding. Wrote several test cases for edges and bases, assertions for expected behavior and lack of side effects. The only thing I can think of is that I wrote 2 method skeletons as placeholders that I ended up discarding because they weren’t necessary. Is the expectation that there will be no detours or changes all?
Did you name your variables properly? Did you keep your code flexible for future changes? Did you write code in way that is easy to understand to someone else?
DM me the code you wrote (if you have it), I can tell you my opinion on it.
Was it phone screen or onsite ?
It was the phone screen
I’ve read you have to make it to at least part 3/4 on the phone screen. So maybe your code and testing was fine but you didn’t make it through enough parts?
What were youbasked in the final round?
What is 3/4 parts? is it like part -> success -> part2 -> success -> part3-> .... part4? and if part2 -> fail, reject? Also will it be coderpad like env or they have their own sw env?
Use your own env because you need to write tests. And you need the speed of autocomplete. The question has 4 parts and apparently you have to make it to the third. They paste a new part after completing the previous one and you have to refactor your code. So it pays to have good coding design at the start.
Do you have to make it to part 3a or 3b?
I had exact same experience, i solved all 3 parts with all test cases passing. I was more focused on speed. Thing with Java, the code looks very verbose, may be it was not concise enough. At the end of the interview I told the interviewer what I would do better to make it concise, looks like he was expecting them at first place. The interview pattern was different from other companies.
Phone screen or onsite ? In my screen I solved 3 parts with clean Java code. 4 th part with less than 10 mins remaining I wrote quick hacky code and got the test to pass. It's been a week haven't heard back from recruiter.
Phone screen, I got standard templated feedback after 1 day
Fwiw I made it to part 3 (didn’t finish) and passed. I think they care a lot about unit tests and not having to be told test this or that. Also my background really aligns with the role so that probably had something to do with it.
When you write tests, do they expect you to write test cases using proper toolkits or test cases written as part of code is fine.
Can anyone answer above question?
I had a really similar experience. This is literally the worst interview experience i ever had this year. The recruiter also could not provide any feedback afterwards. My interviewer was some ex-googler that acted really aloof during the whole process. I passed many other interviews that were harder that this previously, tested in many other way. This is by far the worst experience.
I got a rejection and they gave me a short feedback. They said they were impressed by the collaboration/pairing session, but I failed on... Debugging the code? I'm pretty disappointed with the result. I solved the problem, created tons of tests, changed the code as the new requirements came up etc. I was 100% I've passed in the test but the following day I got an email saying no. The experience ended up being awful.
I have onsite next week, would it be possible to share what kind of questions specifically debugging question was there ? I can DM you
Yeah sure you can, but tbh I don't have much to add because I don't know what exactly they meant with it. I didn't want to follow-up because they also seemed they didn't really care and wanted to just say "aye you didn't make it in the way we were expecting, so good luck with your other interviews".
What were the questions?
Do you still remember the questions?