₦airaland Forum

.

Savagethe21st:
bro can i have a conversation with you

Yes, you can.

My experience interviewing for Software engineering role with Amazon & Microsoft - 2019.

I have reached up to onsite stages interviewing with Amazon and Microsoft for software engineering roles.

Lesson learned.

0. Computer science fundamentals are very important to Silicon-Valley companies than been a pro in the X or Y framework

1. Practice makes perfection, perfection yield meaningful end goal(s).
Nearly all questions were copy and paste from LC [LeetCoce](with little modification).
Some problem focus on HashTable, Graph Algorithm, and others are subjected to real-life experience

2. I interviewed with the AWS team in Vancouver for SDE2 and AI Empowerment Team for MSFT.
Based on my own experience and the team I interviewed with,
Amazon interview process is far better and well organized than MSFT for the following reasons.

a.Hard screening process(You don't have the chance to for virtual interview with AWS team until you successfully pass the coding challenge with two scenarios (up to 90 min) unlike MSFT

b.AWS focus more on scalable algorithm/answers & core understanding of CS

c.Had my interview with two engineers for each stage with AWS, and one engineer for each stage with MSFT

d.AWS team focus more on coming up with an efficient and concise solution, while MSFT focuses on giving
extensive justification for anything that comes out from your mouth and not just coming up with the right solution.

e.AWS has great interviewing tools/resources than MSFT(Perhaps based on the team I interviewed with)
My interview with Amazon was conducted using Amazon Chime, and Team for Microsoft.

3. It's good to know that thing called HashTable, but not all problem requires HashTable

4. Know what you do, and do what you know. In my own opinion, CTCI(Cracking The Coding Interview) book is not
helpful and reliable to pass SWE II or SDE2 interview.

5. Hard work with real dedication works and experience matters.

If you really want to become a software engineer, you must have proper and adequate computer science fundamentals.

Hope you find this helpful.
Useful resources: https://www.algoexpert.io
https://leetcode.com/

unclemaths:
Your modesty is noteworthy.
I also hope GLO reciprocated in an equally worthy manner. (Please, don't accept recharge cards)

Compensation : Text
Compensation content : Good day, We thank you and appreciate your contribution . We always cherish brilliant minds like yourself , whenever situations permits in the near future ,such brilliant minds like yourself will always be acknowledge in line with laid down process. Thank you. DA

https://twitter.com/GloCare/status/1297901003031941120

How I caught and reported a vital bug that exposes GLO customer MSISDN(Mobile No.) to the third party?

Summary

Issue: GLO customer's mobile number is exposed to third party applications while browsing the internet.

Date reported: June-8-2020

Date fixed: August-11-2020

Priority: Internal classification not known to me

Classification: Validated and Resolved by GLO

OS: Android, iOS, Window, and Linux(Didn't check with Mac)

Protocol(s) : https & HTTP

My approach :

I always enjoy building API within my reach instead of relying on third party resources, and that led me into writing an API to capture user's information who access my web app(ww.scholarsinislam.com).

June-7-2020, I requested a friend to help review my project and that led me into checking his device information and was able to figure out that my friend access my web app using the GLO network and his mobile number was exposed to my web app without his consent(while he was thinking, I'm just browsing).

Wasting no time.
I quickly raised it on Twitter[ https://twitter.com/AmudaAdeolu/with_replies](my second tweet and third time logging into twitter).
Was contacted by GLO, following was a series of tests between me and their technical team.
GLO management/engineers appear good, friendly and smart and they were able to fix it on August-11-2020(Ceteris Paribus)

Lesson learned

1. Be yourself, and don't do what others are doing without knowing why and what lead them into such.
Do you what love and love what you do.

2. As a Software engineer or developer, don't be lazy and be completely dependent on using third party API that is within your reach, rather build things from scratch, own it, and keep making it better(That may not be advisable for some projects).
If I had used Google Analytics or related tool to track my user activities, such bug will never be revealed to me
, and various organizations will keep mining and spying on millions of GLO customer's information without their consent.

3. Computer science fundamentals make real software engineer/products.
Stick to it and don't be a master of X or Y framework without it.

Useful resources
1.MSISDN :
https://citizenlab.ca/2015/05/the-many-identifiers-in-our-pocket-a-primer-on-mobile-privacy-and-security/
https://ntnuopen.ntnu.no/ntnu-xmlui/bitstream/handle/11250/2459497/17622_FULLTEXT.pdf?sequence=1&isAllowed=y

2.HTTP HEADERS
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers#:~:text=HTTP%20headers%20let%20the%20client,before%20the%20value%20is%20ignored.