↳
Didn't envision myself getting into this situation but would mitigate if all else failed. Menos
↳
I would first determine how far away the deliverables were from completion to see if the situation could be salvaged. Would additional resources help? Longer hours? If the situation was not salvageable, I'd do an impact assessment and estimate the time to correct, meet with my direct supervisor and plan to notify the shareholders as soon as possible Menos
↳
Well I respectfully disagree that they are goons or fraud. I wrote the feedback as thought I was rejected for not right reasons and they can definitely improve on their hiring process and TA team but I would absolutely NOT endorse your feedback. Menos
↳
Very nice review. This is very helpful. I appreciate such honest people like you who takes their time out to help many. Thanks Menos
↳
You are lucky that you are not trapped by them. Its a company of frauds and HR/TA are goons. Thanks for such candid review. All the very best. Menos
↳
I feel this question is mainly to understand how much you know yourself. Do you come up with cookie cutter answers or are you responding by being true to yourself. Menos
↳
Luckily, I studied this beforehand!
↳
I'd honestly pause and ask what the goals of the question are. If they're asking this to see if I'm going to treat it like a project management question, a project manager shouldn't ever hurry the answer. If they're asking this because they think it's just a great question, I'm not entirely sure I'd want to work with a team they hired. Menos
↳
You said "after sending your resume initially, they called after couple of weeks.." couple of weeks means after how many weeks ? Menos
↳
After I sent the resume in, I received a call from the hiring manager about 2-3 weeks later. After that phone interview I didn't hear anything from them for about 6-8 weeks. Menos
↳
My answer was along the lines of knowing the requirements of the product and testing to those. That includes understanding any federal, medical, and industry regulations and guidelines that must be followed for a product. Identifying requirements from all sources is key and that includes safety and regulatory requirements. Menos
↳
Did they give you a tour?WHat was the expectation from you?DID they convey you?
↳
Was there any question On Automotive division or programming?
↳
Explained a time where my personal life made my exams a lot harder.
↳
Hi, what kind of questions were asked in the interview at the assessment centre?
↳
Piping systems are sloped to prevent material from pooling in the lines and creating a place for bacteria to grow. If material is allowed to pool, CIP/SIP may not be effective. Menos
↳
Yes
↳
Total seconds in 2 days = 172800 Divide total users 4320000/172800(seconds) = 25 users processed every second global start_time = unix_timestamp(start date noon) global users_per_second = 25 global total_users = 4320000 function can_use_new_feature(user_id) { var current_timestamp = unix_timestamp(current_time) var elapsed_seconds = timestamp_diff_to_seconds(current_timestamp, start_time) var processed_users = total_users - (users_per_second * elapsed_seconds) return (bool) user_id >=processed_users } Menos
↳
There's a lot of elements to typically cover in these questions, clarifications, scoping, making sure you're answering the actual question the interviewer is looking for you to answer, etc. Could be worth doing a mock interview with one of the Prepfully Tumblr Director of Site Reliability Engineering experts... they've worked in the role so they clearly know how to get through the interview. prepfully.com/practice-interviews Menos
↳
Assume that gmail has 2 bln of users (there are 3 bln internet users around the world and almost every internet user around the world has a gmail account). Assume that average size of mailbox is 500Mb (I've worked at many email services and know what I'm saying). 2 bln by 500Mb is 1000pb (petabytes). If gmail stores each email 3 times (2 times is a good choice, but since users' mailboxes are scattered around the storage cluster then 2 collapsed hard disks at the same moment could result in some data lost while the possibility of 3 hard disk have collapsed in the different data centers at the same time is negligibly low) then total is 3000pb. But I'm completely sure that gmail has deduplication and gmail has text parts of emails zipped. The first measure can save around 50% of space (the most of the mail store - it's attachments, and attachments are usually sent by person, so an attachment appears twice - in an inbox folder and in a sent folder). The second measure can save around 20% of space (this is the approximate total size of all text parts of mailings that could loose their weight by times). So 3000Pb are reduced by 70% to again 1000Pb. A 36x4Tb storage server has a 144Tb capacity. 1000Pb divide by 144Tb is about 7000. Why is it 36x4Tb? Because 36 is as far as I know economically feasible maximum number of disks per server. And 4Tb is economically feasible maximum disk size. I mean here that the more disks per server the less is the cost of the server other-than-disk parts per byte of storage but to the limit after that other-than-disk parts become more expensive. So is about the disk size - the bigger the disk size the cheaper is the byte stored on it, but to the limit of 4Tb. Of course gmail is not only storage service. There are also web services, smtp, imap, pop3, MX, antispam and so on. All of these services just process data and they don't have to store anything large (maybe there are some databases negligible compared to the email storage to store user credentials for example). A service does not necessarily needs a separate server. And storage servers luckily have a plenty of CPU time and some memory. So, the storage server's CPU time, memory and small portion of the disk could be used for data processing and for some small databases needed to web services, smtp, pop3, imap and so on. Google would not be Google, if they used a lot of additional servers for the life of the email system, except the email storage servers. That's why the correct answer is 7000 servers. Menos
↳
These sorts of questions don't have answers. The real answer is to think out loud about what would be required in terms of bandwidth, storage, computing power, etc. for all of the different elements: receiving, sending, website, spam filtering, addressbook lookup, ... Menos
↳
...I took the day off of work and got to SF early to ensure I would be on time for the onsite Menos
↳
Had Similar experience.