Ruby
Because we deal with people's money, any outside tech we use needs to go through a long security review process. Often, we end up building things ourselves that already exist as external products because it's easier than getting them approved.
Stay developer-focused! Stay focused on simplicity! As we try to accommodate a larger variety of customers and use-cases, we need to remember that what made us successful was how simple we were for developers to use.
OA, technical interview, virtual onsite then hiring manager. The tech interview was a 3-part LeetCode implementation style. The VO has tech (same as the previous round), integration, and bug squash. The bug squash is probably the hardest among the th
The process began with a phone screen, followed by an online technical interview that focused on coding and problem-solving. The final round took place in person and included back-to-back interviews with approximately five team members. Each intervi
The first call was with a recruiter, and the second was a technical phone screen. I was rusty with string parsing and interviews, so unfortunately, I didn't make it past this round. The interviewer was kind and helped debug when needed. I was reject
OA, technical interview, virtual onsite then hiring manager. The tech interview was a 3-part LeetCode implementation style. The VO has tech (same as the previous round), integration, and bug squash. The bug squash is probably the hardest among the th
The process began with a phone screen, followed by an online technical interview that focused on coding and problem-solving. The final round took place in person and included back-to-back interviews with approximately five team members. Each intervi
The first call was with a recruiter, and the second was a technical phone screen. I was rusty with string parsing and interviews, so unfortunately, I didn't make it past this round. The interviewer was kind and helped debug when needed. I was reject