Intro
Why AWS/Amazon?
Questions for interviewer:
- What do you think that the interns who do not convert lack?
- If I was to be hired, will I be working with you or your team?
- Whats your favourite thing at amazon?
#1 Kapture - Orient travels
- Situation:
- Technical PM at Kapture (Customer Support CRM for support agents) - reported to CTO
- Orient Travels - Wanted a dashboard for call agents to view the status of the ticket in the Call centre on a TV
- Frontend team was not able to deliver the dashboard within the given time, and they were nearing the deadline.
- The backend team had given all the end points for the reports & dashboard.
- Task:
- I was assigned to this critical project to deliver the dashboard within 2 weeks
- Action: 3 Phase Implementation -
- Phase 1: Spoke to client to clearly understand the requirements
- Phase 2:
- Built the UI on Retool(no-code low code platform) using Vanilla JS and connected the APIs that the backend team provided
- Delivered functionality of one dashboard in the first week
- Phase 3:
- Delivered multiple dashboards
- Made changes to the UI and design to match their palette - in the next 3 days
- Result:
- Cleared the 2nd part payment of the $75K Annual contract within 6 days after delivery
- Client - Ticket resolution time reduced by 30% (from creation to being resolved)
- Client - This helped them increase the agent efficiency by 15%
- 2000+ tickets were displayed on this dashboard, used by the client in 20+ locations
- What I Would Do Differently:
- Clear Documentation:
- Documenting the process since the signing of the contract - saves time
- documenting the Implementation process - tech
- Proactive Risk Management:
-
I would have identified potential risks (e.g., frontend team delays) earlier
-
using no-code tools from the start.
Full Story
Follow up Q
#2 Kapture - Query manager
- Situation:
- Technical PM at Kapture (Customer Support CRM for customer support agents) - reported to CTO
- So the team was rapidly growing - hiring 2-3 engineers every week.
- We were using an SQL DB and all the engineers were accessing it directly and almost everyone had write access.
- Data Manipulation - by mistake
- Task:
- I was assigned to lead this project
- I needed to secure the DB by reducing direct access and design an architecture to test new queries
- Action: 3 Phase Implementation
- Phase 1:
- No brainer - Created a Testing & Staging DB using the snapshot of the Live DB
- Phase 2:
- I designed and built a Query Manager - converts SQL queries into the DB as an API that can be called from anywhere
- I had one backend engineer assigned
- write query that needs be approved by the EM
- Phase 3:
- I used Retool to build the UI and embedded this into our CRM with authorized SSO login
- Result:
- Eliminated unauthorized DB modifications & Reduced direct DB access from 70 to 7 engineers (90% reduction)
- DB breaches reduced by 100% post-implementation (number of data requests reduced from 4 to 0 per month)
- Productivity of engineers improved by 20% → $75k in cost saved annually
- 20% of 30 backend engineers salary per month
- The team has over 100 engineers now and the entire backend team uses my tool to write and test queries
- The average time to execute queries - went from 10-15 hours to just 1-2 hours improving the efficiency
- What I Would Do Differently:
-
Stakeholder Buy-In Earlier:
- involved the Engineering Managers (EMs) earlier in the design process to address their concerns and ensure smoother adoption of the Query Manager.
-
User Training:
- created a comprehensive training program for engineers to ensure they fully understood the tool’s capabilities and security protocols.
Full Story
Follow up Q