Recent Slack Interview Questions

Istvan K. - "Thanks you for sharing insight about the app which I would liek to summarize in 2 structures: functional 2 technical requirement. Requirements: Functional requirement: Able to share messages, siles , and other content like photos, sounds Create groups for conversaion Size: 500 million users, 50m DAU -> 500M active chats daily Files not stored in the system but is can be shared.. Integaration with other APPs Technical requirement: Availability: Can you help me to understand the a"See full answer

Exponent - "This is one of the core behavioral questions that you should expect to cover in any interview. In particular, it asks you to justify why you want to work at a specific company that you've applied for. There's no right answer for this, however we do recommend you list at least three distinct reasons. Here's an example of what you might say: > Great question! There's so many reasons, but I'll keep it to the three biggest so that I don't just go on and on. Those reasons are:Building an impactful pr"See full answer

Exponent - "This is an Improve a Product question that's quite specific. Here, we're asking to not only improve Slack, but particularly how they allow collaboration on their platform. Let's first go over the Improve a Product formula: Ask clarifying questions Identify users, behaviors, and pain points State product goal Brainstorm small improvements Brainstorm bolder improvements Measure success Summarize Now, let's begin! Ask clarifying questions"See full answer

Exponent - "You should be able to easily identify this as a Measure Success question. These kinds of questions are used to test your analytical skills, as well as your ability to track project progress post-launch. It also provides the interviewer confidence in your ability to think about analytics pre-emptively. Recall the strategy for tackling them methodically and thoroughly: Ask clarifying questions State the goal of the feature / product Behavior Mapping / UX Flow Mapping **"See full answer

Kell K. - "This by far has been the best interview I've seen so far, granted I've watched 15 mock interviews. Great Job!"See full answer

Saurabh N. - "1) Have a common goal 2) Have a clear and fair accountability between teams 3) Ensure conflicts are resolved in time on common issues 4) Promote common Brain-storming , problem solving sessions 5) Most important , Have clear and effective communication established and practised"See full answer

Esther S. - "Generally during the planning phase, I work with various teams to identify milestones and high level target date based on affinity sizing of the work. Based on that, I build a roadmap and if there are unforeseen issues/risks that may impact our target date, I flag it as a risk. For instance, if the teams are working on a project and there's an issue where a team states they need to extend out their target date and that impacts a dependent team, this will surely change the deliverable date for th"See full answer

BC - "During my time at [x], we had the business objective of not only migrating existing but also eventually onboard new customers onto this new and improved product line. The end goal was self-serviceability but it became clear that the experience wasn’t ready for that just yet. At this point, it was known and documented through metrics that customer success managers and customers alike would stall in very predictable areas of the product experience. I took the initiative to audit and qualitatively"See full answer

Saket S. - "I will ask few clarifying questions to the interviewer: Is there any specific application that we are referring to (assuming B2C website/app) What are we Trading off here (assuming Requirements/Features) I will consider following criteria to prioritize Trade offs: Impact on User experience: In terms of usability, reliability, and efficiency Usability: Ease of Use, Intuitive UI Reliability: Functions as expected and produces desired results, tolerates user mistakes and prevents unauthor"See full answer

Abdurhman M. - "I enjoy it when a system works effectively and efficiently, but when a process frequently has problems or takes longer than expected, I think that it's a sign there's room for improvement."See full answer

Amparo L. - "The only time I felt unhappy at work was when I didn’t get to pick the job I want to do at the jobsite."See full answer

Saket S. - "I will use the following approach for this situation: Understand Current Status of the Program: Program Goals, Schedule, How many teams, what are their deliverables, dependencies between teams Team level view of progress: Through tools like Burn down charts, Gantt charts etc. Identify laggards (lagging teams). Trend analysis for lagging teams: Understand at what point, the decline started. If the decline has started around same time, then following may be the potential issues: -"See full answer

Amparo L. - "One time I refuse someone that I can’t help them because I was busy working on my task that required a long time for me to complete it but once I explain to them why I could NOT help them, they totally understand it and then they ask the front desk."See full answer

Roshan K. - "1. Understand Your Audience\: 2. App Quality and Relevance\: 3. Educational Content\: 4. User Reviews and Ratings\: 5. Integration Partnerships\: 6. Community Engagement\: 7. In-App Promotion\: 8. User Training and Workshops\: 9. Email Campaigns\: 10. Feedback Loop\: 11. Incentives and Rewards\: 12. Analytics and Iteration\: 13. Partnerships and Collaborations\: 14. Measurement and KPIs\:"See full answer

Srini K. - "performance issues and sudden spikes on input requests by scaling techniques and optimization."See full answer

Aabid S. - "We had a huge launch on September 1st of this year where we completely redesigned our application from the grounds up and also migrated to a new platform (React.JS). This project took us 8 months and the launch was a huge deal for the team. Unfortunately the launch wasn't as smooth as we expected and despite doing multiple rounds of QA, some major issues cropped up in the core part of the app right after launch and our client was quite upset since it was disrupting their day-to-day workflow. "See full answer

Anonymous Puma - "Assuming for the US Segment by size of businessNumber of employees per business sizePrice per employee=Revenue Price per employee should decrease with a larger employee base. 30M businesses in the US Small Business 60% of businesses are small=18M Average number of employees=50 Price per employee=$5 Small Business Revenue=$2.7B Medium Business 30% of them are medium=9M Average number of employees=1000 Price per employee=$3 Medium Business Revenue=$8.1B Large Business 10% of th"See full answer