Most questions were straight out of a corporate handbook — predictable, painfully generic, and read with the charisma of a cardboard cutout. Think: “Tell me about a time when you managed multiple priorities.” It wasn’t a conversation. It was a checklist dance with people who already looked like they’d mentally checked out. “Can you give an example of aligning stakeholders across countries on a complex project?”
Several questions about Data science
What is my salary expectation? Why I applied for this position?
Given the main Monday.com boards product (similar to JIRA) working in prod, you'd like to add Automations part (similar to Automations in JIRA). Which interface will you use for those parts to communicate and why? What will you take into consideration from scale prospective? How will you choose a DB? How will you manage and handle exceptions? Which metrics/ KPIs will you look onto when deploying to prod?
how Docker works and what is pods
- Questions regarding experience - Conversations detailing relevant experience against requirements of the role - How would I react to several circumstances within the role - Questions regarding understanding and knowledge of the business
Technical part was as usual. but from team lead perspective I was asked to share the conflict happened in past and how I managed
difference between serializable and parcelable? different launch modes
How do you manage a stressful situation?
How do you handle stress? How do you take care of yourself? What do you want to get out of the position? Why are you applying for it?
Viewing 7981 - 7990 interview questions