Il ruolo di Mobile engineer è altamente qualificato e impegnativo. Durante il colloquio, dovrai dimostrare una buona conoscenza del software e dei linguaggi di programmazione utilizzati dall'azienda, ottime capacità di gestione dei progetti e una forte propensione a lavorare in un team dinamico e sotto costante pressione.
Ecco le 3 domande più frequenti nei colloqui di lavoro per Mobile engineer e consigli su come rispondere:
Come rispondere: Questa domanda ti offre l'opportunità di dimostrare le tue competenze. Elenca i linguaggi che conosci e fornisci qualche dettaglio sulla tua esperienza. Ad esempio, specifica da quanto tempo usi un linguaggio, come e perché l'hai imparato e aggiungi un esempio di un progetto su cui hai lavorato. Evidenzia eventuali studi svolti da autodidatta, in particolare sui linguaggi in cui sei meno esperto, poiché questo dimostra che sei disposto a continuare ad imparare.
Come rispondere: L'intervistatore desidera conoscere l'intero processo di risoluzione dei problemi da te adottato. Spiega come identifichi e classifichi i problemi o i bug, quali operazioni esegui per trovare una soluzione e come affronti gli ostacoli. Prova ad usare esempi specifici derivanti dalla tua esperienza, quando possibile.
Come rispondere: La gestione dei progetti o project management è un elemento cruciale per assicurare che un team lavori in modo coeso ed efficace. Elenca tutti gli strumenti che hai utilizzato e spiega perché li hai scelti e come hanno migliorato il tuo flusso di lavoro. Può essere una buona idea cercare e testare una varietà di strumenti di project management nel tuo tempo libero e provare a utilizzarli, in modo da parlarne facilmente durante il colloquio.
↳
Very, very helpful !!!!Can you send it to me ? lastripper@gmail.com
↳
I have applied for the mobile software engineer. do you think they can ask the same question for this post too? Meno
↳
Thanks for the review, it was really helpful. Can you send me the word document at johnycamanney@gmail.com Thanks! Meno
↳
Each iteration? You need just an iteration. Complexity o(n).
↳
my solution was still O(n) - 3n to be exact. i "iterate" over the entire matrix 3 times - once to check for duplicates in the rows, once to check for duplicates in the columns, and once to check for duplicates within sub matrices. During each of those iterations I visit each element of the matrix exactly once and just check whether it's already in a dictionary of seen numbers which would be a constant time operation, so this is in total would be O(n). I can't think of how to check all those in just one iteration , if that's what you were saying you could do. (at least without using O(n) extra space.. mine only uses constant extra space) i would appreciate if you could elaborate Meno
↳
I basically just checked for duplicate numbers in each row, column, and then each 3x3 inner matrix. each iteration, i reset a dictionary of "seen" numbers. "." characters wouldn't matter, if i saw a number 1-9 i would check if it was already in the dictionary, if it was return false. return true at the very end if never encountered repeat numbers in rows, columns, or inner squares. when I explained this approach to the interviewer and he seemed satisfied with it although it was not easy to tell what the hell he was thinking or saying. i was working in a shared text file (i think it was codepen?), and even though the interviewer could have typed too, he didn't (even when i had to ask him repeatedly to spell a word i couldn't make out).. Meno
↳
a xor a = 0 0 xor a = a so if we xor all elements 1 x 1 x 2 with all possible elements 1x2x3 = 0x3 = 3 still extra memory used but at least no overflow possibility. was it allowed to change the original input ? Meno
↳
1) Subtract each number from summation formula = N * (N+1) / 2 2) Hash table , zero out all entries when insert number -> 1 after all insert look for 0 entry 3) XOR all elems -> X XOR all # 1 to N -> Y XOR of X and Y -> missing # 15 ^ 12 ^ 15 = 12 Meno
↳
Stupid Math this is called stalking not algorithm
↳
Oooooh, this was a sneaky trick question and I'm sorry I fell for it. Under the pressure of an interview, you might accidentally think the angle between the small and the large hands of a clock will pointing at the number "3" and therefore the angle would be zero. If you can keep a clear head, you're likely to realize really quickly that the small (hour) hand is going to be *beyond* the 3 by some relatively small angle. To be more precise, it'll be 1/4th of the distance between the hour numbers "3" and "4". Meno
↳
With 360 degrees in a circle and 12 hours throughout each cycle the distance between each number is 30 degrees. If the minute hand is pointing at the 3 and is fifteen minutes, fifteen minutes is 1/4 of the total amount of minutes on the clock, this puts the hour hand 30/4 degrees passed the 3 at 7.25 degrees. They'll enjoy you thinking analytically. Meno
↳
The answer should be a right angle.
↳
to study for this interview I suggest rewriting all of the basic Java methods ;)
↳
can't u just parse char by char and use a bunch of shift operators and since ur just using charAt(i) to pick up a character u can use the same i and just raise it to the power of 10 and just or it with some bytes Meno
↳
public static int parseInt(String stringToConvert) { int i =0,num=0; int isNeg = 1; int length = stringToConvert.length(); if(stringToConvert.charAt(0) =='-') { isNeg=-1; i=1; } while(i Meno
↳
class Solution{ int ans[] = new int[1]; //O(n) public int efficientDia(TreeNode root) { if(root == null) return 0; int left = efficientDia(root.left); int right = efficientDia(root.right); ans[0] = Math.max(ans[0], 1 + left+ right); return 1+ Math.max(left, right); } //O(n^2) public int getDiameter(TreeNode root) { if(root == null) return 0; int leftHeight = getHeight(root.left); int rightHeight = getHeight(root.right); if(ans[0] < 1 + leftHeight + rightHeight) { ans[0] = 1 + leftHeight + rightHeight; } return Math.max(getDiameter(root.left), getDiameter(root.right)); } Meno
↳
int ans[] = new int[1]; //O(n) public int efficientDia(TreeNode root) { if(root == null) return 0; int left = efficientDia(root.left); int right = efficientDia(root.right); ans[0] = Math.max(ans[0], 1 + left+ right); return 1+ Math.max(left, right); } //O(n^2) public int getDiameter(TreeNode root) { if(root == null) return 0; int leftHeight = getHeight(root.left); int rightHeight = getHeight(root.right); if(ans[0] < 1 + leftHeight + rightHeight) { ans[0] = 1 + leftHeight + rightHeight; } return Math.max(getDiameter(root.left), getDiameter(root.right)); } private int getHeight(TreeNode root) { // TODO Auto-generated method stub if(root == null) return 0; return Math.max(getHeight(root.left), getHeight(root.right))+1; } Meno
↳
Indians at all companies always ask tree questions, it makes them giggle inside. I know, because I'm half indian and have interviewed people... tee hee hee Meno
↳
^ yes it can, but that is a memorized solution that you likely wouldn't implement if you hadn't seen it before. i'm sure they don't use recursion on clients and i'm not exactly sure what this problem says about the interviewer other than "he doesn't leet". Meno
↳
It's actually a pretty simple dynamic programming problem you can solve using constant space, do it iteratively rather than recursively. Check it out of LeetCode. Meno
↳
This can be calculated with a simple recursive Fibonacci
↳
public void printNumbers () { for (int i = 1; i <= 100; ++i) { if (i % 3 == 0 && i % 5 == 0) { System.out.println("FooBizz"); } else if (i % 3 == 0) { System.out.println("Foo"); } else if (i % 5 == 0) { System.out.println("Bizz"); } else { System.out.println(i); } } } Meno
↳
public void printNumbers () { for (int i = 1; i <= 100; ++i) { if (i % 15==0) { System.out.println("FooBizz"); } else if (i % 3 == 0) { System.out.println("Foo"); } else if (i % 5 == 0) { System.out.println("Bizz"); } else { System.out.println(i); } } } Meno
↳
Yes, Partial test case passed.
↳
Answer in JS- Trying to remove the duplicate tickets for each person then compare the tickets to get the desired number k. And then get the number of such friends. Not comparing Jay's own tickets. const getFriendsCount = (N, M, k, ticketsArr) => { const uniqueTktsArr = ticketsArr.map(tktsArr => Array.from(new Set(tktsArr))) let friendsNum = 0 const jaysTickets = uniqueTktsArr[N] uniqueTktsArr.forEach((tktsArr, i) => { if (i === N) { return true } let match = 0 tktsArr.every(tkt => { if (jaysTickets.includes(tkt)) { if (++match === k) { friendsNum++ return false } } return true }) }) return friendsNum } Meno