Preparing for an interview? Check out Cracking the Coding Interview
Published on

LinkedIn | Staff | Phone + Virtual on-site | US | Reject

Author
  • Shared Anonymously

Phone - https://leetcode.com/problems/max-stack/description/ (Hard)

On-site -
https://leetcode.com/problems/all-oone-data-structure/description/ (Hard)
Implement JSON parser (Hard)

Craftsmanship - Refer https://leetcode.com/company/linkedin/discuss/4802112/LinkedIn-Onsite-or-Staff (copy-pasted below).

====================
Craftsmanship. Quality in the crafts. Outcomes matter. LinkedIn want engineers who are proud of their work and inspire their teams.

Define a quality product / system.

Talk about a time where you failed to show good craftsmanship and what you would've done better.

Describe your strategy regarding code reviews.

Talk about a project that had many junior engineers and how I kept their quality high.

Talk about a tine where you helped grow an engineers.

If your team keeps growing and you get more junior engineers, what do you do?

Hypothetical:
Imagine you join LinkedIn on a massive team that owns a legacy application. The application lacks adequate testing and monitoring and has slow response times. Consumers complain about this. Deployment of the application often contains bugs.

Rank the following in terms of priority: bugs, no testing, no monitoring, slowness

What do you tackle first?

How do you eventually turn this into micro services?

What kind of signals do you look for when prioritizing bugs?

Give examples of "P0" bugs.

What do you look for when determining the success of a service?

What are the pros and cons of microservices vs monoliths?

====================

Hiring Manager:
Who am I and what do I do?

Describe my day-to-day role.

How big is my team?

What is my tech stack?

Talk about a project that had large scale.

Answer specific follow up questions about the project.

What project do I consider the most significant?

What's the most challenging aspect of that project.

Hypothetical:
Suppose you join LinkedIn and you're asked to build a feature that sends suggested candidates to recruiters who have opened a new job profile.

What's your overall approach?

How do you organize the team?

What's your rollout / deployment approach?

======================

System Design - Design a system which identifies API requests as malicious using the request body by making a call to isMalicious(requestBody) that's available to you and then reject it. One of the non-functional requirement is to reduce the number of calls made to the isMalicious(requestBody) API by tracking IPs that send malicious requests.

ReportMark as Helpful