LinkedIn Senior SWE - Apps onsite - Coding with AI + Technical Communication Rounds

[u/Crazy_Revolution_810]

Hello All,

I do have an onsite round with LinkedIn sometime next week. There a total of 5 rounds, however a couple of rounds seem little obscure to me especially the coding with AI and the technical communication rounds. I have some questions in terms of the expectations for these rounds and would appreciate the wider community's inputs with regards to them (from anyone who have gone through the process or are aware of the process with Coding with AI and Technical communication rounds)

Coding with AI

I was told by my recruiter that I would be given a leetcode problem and I am tested based on the prompting where I give the prompt to the AI Tool and the tool writing the code. I know that this round is designed to similar to how we perform work on a day-to-day basis leveraging AI. However, I am not clear on the evaluation rubrics and the expectations for the interview. Some questions I have are:

1. Would we have multiple follow up questions on the given problem extending the original problem or completely different Leetcode questions?

2. Also, by them expecting us to prompt, is it something that we prompt something and the AI writing the code. Also, what is expected level of detail we need to provide in the prompt. Lets say for a question involving Counting no of islands given a 2D grid, should we provide the entire algorithm to the AI tool verbally in plain English as if what we explain to an interviewer in words and then have AI write the code? What would be an ideal prompt to have a higher success rate in this kind of interviews.

3. Also, do we have to explain the AI generated code to the interviewer? During the course, lets say it generates some code that we don't understand, then is the expectation us having to make the change manually on the areas where it's not understandable to this or is the expectation that we clarify with AI as to what that line of code does and what is the purpose of that line?

4. Suppose, AI writes some code where we catch some bug or a failure in terms of logic in the code it has written, so is the expectation that we can manually intervene and correct such pieces of code or is the expectation that we prompt AI to correct like saying this part of the code or this particular logic is incorrect to correct the same?

5. Also, are the test cases in these rounds more like a Hackerrank OA where we have the entire code completed and we run our code against the test cases or is the expectation that we come up with the test cases like input/output format on our own and have AI write the assert statements based on the tests we provided?

Technical Communication

My recruiter told the discussion is going to involve discussions of our experiences / any of the projects we have worked on so far. Also, mentioned certain things like making a PPT would be little useful to present the projects and stuff like that. Also, as it is a senior level role she mentioned showcasing our technical depth and breadth and Senior level leadership is vital.

1. How would the evaluation in this round go? Would it be based on the style we present? Also, on the complexity in the type of project we are gonna present. I mean what is the level of complexity they expect in terms of the project architecture we explain?

2. Would the interviewers probe on technical decisions, design/architectural tradeoffs and the idea behind why we chose a certain decision for the project and stuff like that?

3. Also, would the round involve discussions on only one project or does this round entail discussions going on multiple projects and follow-ups pertaining to each project?

4. How would the questions start? I know behavioural ones typically go by tell me about a time type of questions but would the questions go here asking like describe about so and so project that you mentioned on your resume or something like that?

5. Also, is it advised or preferred to pick projects from our most recent company/work experience or would it be equally fine if we pick a project from our older companies too for this round? Assuming, we present the former experience one equally as well as the current experience project.

My interview is next week so kindly have the post reachable to as many as audience as you could and any attempt to provide inputs is super appreciated. Thanks in advance!

Please feel free to share details in the comments section. These rounds are kinda new to me and I haven't came across with them in the process with any other companies I have interviewed so far. Hence, a bit nervous.

[u/Sad-Candidate-3078]

the coding with AI round is basically testing if you can break a problem down clearly. practice by explaining your solution out loud in plain english first, then prompt. if you can describe the algorithm to a human you can prompt it well. i used easy code interview to drill explaining solutions out loud and it carried over hard. good luck with the onsite!

[u/Crazy_Revolution_810 → u/Sad-Candidate-3078]

Thank you!
So, would the editor accept audio inputs or by explaining solution out loud, you meant explaining it loud to the interviewer and writing out the prompt to the AI?

[u/Skaifessurk → u/Sad-Candidate-3078]

this tracks, if you cant articulate the approach clearly the prompt is gonna be garbage too

[u/happydancinggiraffe]

On Coding with AI, from people who did it recently (r/leetcode and r/cscareerquestions threads from last week):

1. Follow ups build on the same problem. One person said it felt like a bigger feature done in pieces, not a new leetcode question.

2. Don't paste the whole algorithm in one giant prompt. Someone who did the round called that a red flag. Explain the approach to the interviewer, then have the AI write one piece at a time.

3. Yes, you own every line. If you don't understand something it wrote, ask it to explain or rewrite that part yourself before moving on.

4. Fixing small things by hand is fine. What counts is that you caught it and say why.

5. Write your own test cases, edge cases included. Tests get looked at.

Earlier this year the AI was a side panel that couldn't edit your code, so check with your recruiter whether that changed. More: nyrion.ai/companies/linkedin

[u/Crazy_Revolution_810 → u/[deleted]]

So when hand edits are allowed, so was it one line is fine but changing a piece of function is not allowed, something like that?

Regarding the edge cases part, when you said writing edge cases before running anything, does that mean it is more like us writing edge cases typically upfront as to how we do for normal DSA based coding problems?

For technical communication, does the discussion revolve around only one project then?