Tech Topics: Microservice Architecture, Domain-Driven Design, Event-driven architecture, CQRS, Cloud services, Containerization, C# language (in-depth), Maintainable code, API design, RESTful services, CQS, Design Patterns, SOLID principles, Information hiding, Test-Driven Development, Unit testing, CI/CD, Specific services such as service bus, Redis, RabbitMQ, virtual machines, switches. DevOps. Azure/AWS. Database design, performance, versioning, and schema updates. iHerb current and future architecture. Dev/Collaboration Topics: Software Development Lifecycle: Analysis-Design-Implementation-Deployment, Code reviews, Scrum/Agile Practices, My strong points, My weak points. How I handle conflict or under-performing workmates. Do I enjoy mentoring and teaching? What are my objectives in applying for iHerb? Given a theoretical set of requirements, how would I translate those into an architectural design? How would I name methods and organize namespaces?
Principal Software Engineer Interview Questions
2,064 principal software engineer interview questions shared by candidates
Online Hackerrank coding test and 4 hour interviews
How JavaScript does certain operations
Find all sequences on a keypad that match specified criteria.
The 1.5-hour pair programming question was not like your typical LeetCode question. It simulated a type of problem that you would solve at a bank/credit card company. The focus was algorithmic implementation; not so much OOP concepts.
Given a string, check there are exactly 3 question marks b/w the digits and the 2 digits always add up to to 10 else return false.
Typical interview questions, nothing out of ordinary but you need to know what you are talking about.
The tech questions are very generic about software development principles: recursion vs iteration, heap vs stack, DI, TDD, time & space complexity, concurrency and multithreading, ... The home test is an absolute waste of time. Can't give much info but it was simple, it was more about the quality of the tests, handling highly concurrent scenarios and whatnot, but the funny thing is that the feedback they provided was not even about what I submitted. Is like they reviewed someone else's code. Asked for a second review or at least to double check they didn't mix reviews and didn't hear back from them. Very disrespectful and unprofessional.
Knowledge of software languages and proficiency with each.
Viewing 1901 - 1910 interview questions