
Marqeta Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 145 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 145 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Marqeta.
Senior Software Engineer
It started with a recruiter call, then we moved to a coding round where I shared my screen, and finally, a chat with the Hiring Manager. The interviewers were super nice and even gave me tips on how to approach things. The recruiter mentioned three more sessions: two 45-minute behavioral interviews and a system design round using screen share with Lucid chart. The whole thing wrapped up in about 2.5 weeks, and the recruiter was quick to give feedback after every step, which was great. It all went really smoothly.
- Can you discuss distributed systems?
- What are the fundamental principles of system design?
- How would you build a Set data structure from scratch?
Data Engineer
The hiring process started with a recruiter screening call, followed by a hiring manager interview. Then there were two technical interviews and a team communication interview. Finally, they extended an offer. Overall, it was a pretty straightforward process that took about 3 to 4 weeks. The interviewers were friendly and helped create a relaxed atmosphere, making it feel like a regular working environment where we were just sharing ideas and solving problems together.
- Coding questions of medium difficulty, similar to LeetCode problems
- SQL related questions
Senior Recruiter
So I applied for a Senior Recruiter role and went through a total of 5 stages. It began with a screening call, then I had interviews with the hiring manager, a team member, and an HR partner, followed by a final chat with a director. Honestly, I had a better offer from another tech company that was remote-first, which was appealing since my current job was pushing for a return to office. After the interviews, I was ghosted for about two weeks. I'd actually let them know I had another offer with a deadline, and I regrettably declined it hoping for an offer from Marqeta based on the positive feedback I got. They finally emailed me in the third week to say they were going with another candidate who fit their needs better, no call. A month later, they reached out again saying a new spot opened up. I was sure I'd get it this time. I ended up doing another 4 rounds, starting with the senior director who is the manager of the director I spoke to before. Again, it seemed to go well until they ghosted me for three weeks after the final round, and my two follow-up emails got no reply. Finally, the recruiter contacted me, probably out of guilt, to tell me they were passing on me again because I was a sourcing recruiter two years ago instead of FLC. It's like they didn't know this from the first interview, and I had to really push for feedback both times. Such a waste of my time!
- What makes you interested in Marqeta?
Contractor
So the interview process at Marqeta for a software developer is pretty straightforward. It starts with a recruiter screen, then a technical phone interview where you do some live coding. They might also give you a take-home assignment, but it's optional. If you pass those, you move on to the final rounds, which include talking with the hiring manager, and then doing a system design, coding, technical deep dives, and some behavioral interviews. They really care about your technical skills, how you work with others, and if you vibe with Marqeta's goals and values.
- Can you tell me about practical Retool experience you have building internal tools?
- Describe how you've used Retool to connect to APIs or databases.
- How have you leveraged Retool to automate business processes?
Marqeta Interview Questions
Quoted word for word from Marqeta interview reports.
“Could you explain the purpose of the "PUT" method when using Postman?”
Read reports →“Could you define and structure a rate limiter based on specific conditions?”
Read reports →“Can you provide some SQL queries to locate specific data within a table?”
Read reports →“With three input lines for credit card transactions, can you implement methods for transactions like charging against the available balance and adding to the credit card balance?”
Read reports →“How would you redesign this system to address performance and scaling problems?”
Read report →“What are your thoughts on SDLC security practices like SAST, DAST, and SCA?”
Read report →“Were there Leetcode medium/hard questions that could be solved in any language of your choice?”
Read report →“In the design round, what are the expectations regarding bug fixes and potential enhancements?”
Read report →“Can you design a system for millions of users with low latency, considering database sharding and caching trade-offs?”
Read report →Formats, difficulty and experience
Across all 145 Marqeta interview reports.