Venmo Interview Questions
& Process

The interview for the Lifecycle Marketing Specialist job at Venmo had four stages. It kicked off with a chat with HR, then I talked to some team members. After that, I had to do a case study and present it, and the final step was a chat with the department head. It all felt pretty smooth and organized. The questions were straightforward, asking about why I wanted to join Venmo, what I'd bring to the table, and what I was looking to get out of the job. It was a clear way to show what I could do and how excited I was.

Applied for a senior mobile developer job. Had a first telephonic interview that went well. Then had a virtual coding round. Was slow to get follow-up for a month, then received an email about a hiring slowdown but that they were ready to proceed if I was still interested. Decided to continue. Cleared the coding round and moved to a final panel interview with 3 rounds: paired programming, app design, and behavioral. After the interview, there was again no communication for a week. After some follow-ups, I was told I cleared but there was another hiring slowdown and no business clearance. The next day, they decided to close the position. Strange to go through the whole process and not get an offer.

So they are into wasting your time, I made a mistake and didn't ask for my off-work compensation upfront before I made a trip for an onsite interview. I thought it was a decent company until I met their 'iOS Developer' who had set up a question with the intention of not hiring me. The question had nothing to do with iOS frameworks, Swift, or Algorithms. He asked me if I could come up with a solution similar to what he figured out after he squeezed his brain for god knows how many days. One thing you should not ask a candidate is a question about what you spent days and weeks to resolve, and it's specific to the company's business logic. You should present the problem in a general context that could be patterned with similar general solutions in CS and relatable to the candidate. Their developer was the least knowledgeable developer I have ever seen. The project he set up was just a single view application with 50 lines of sample code in an Enum about their business logic, but the Unit Tests didn't work. It was showing an error that it cannot find the XCTest framework, so he had to put his unit test in the viewDidLoad!!! Another question he wanted to ask was that this single view app is ugly and how can we make it more beautiful? I am not a UI designer, although I've been working for over 10 years since iOS came out, so I had some ideas for UIs. But when he ran the app, nothing materialized on the simulator; there was only a white screen. I jumped into the Visual debugger, and he looked at the view hierarchy and said, 'uh okay okay I know what is going on,' and he said he had another interview and had to go, and he darted out of the room with his sidekick. The whole time, another kid was sitting in the corner of the room, busy with his laptop, typing away and oblivious to anything going on. I guess he was the observer to ensure they had a fair interview; sure, they got that right. What a joke. I interviewed with two other iOS developers to get to this one, and they both gave me thumbs up, except this guy who had the least knowledge of the two others. He had no intention of giving a thumbs up because he already had my resume, and I guess he was concerned about the apps I have in the app store since 2011. Based on what I saw in his coding in that sample code, he was one of those developers who has no concept of object-oriented or clean coding since he had written most of the code in an Enum. I've seen projects where developers had written most of their business logic in one gigantic Enum with a size of 2000 lines of code, all in one enum, and they are afraid if someone with higher knowledge comes to the company, it's going to blow the whistle on what a swamp is there, called Venmo app. :) Make your decision.

I put in my application online, and about a week later, I got an email to set up a phone chat with a recruiter for that same week. The call was super straightforward, asking basic questions about my skills. She asked about metric tools, how I use organizational skills (said they're super important!), and also asked for real-life examples instead of general statements. She told me about the job and the company – she was really nice and super helpful! The same day, I got a call saying they wanted to move forward, and they scheduled me for an interview the Friday of the next week. It was at their downtown office and started with a group session where we got a quick presentation about the company and the role. Then, we split into smaller groups for a fun activity with the managers. After that, half of us went for one-on-one interviews while the others did a Wonderlic test and a writing sample. When it was all done, we could tour the place and ask any questions. The recruiter said we'd know if we got the job that same day. It was a pretty fun and easy interview. I really enjoyed it and loved the company from the start. My advice: pay attention to everything the recruiter says on the phone interview; they're a great resource throughout the whole thing.