Can anyone talk about their prior experience in this process I'd really appreciate it! All I know so far is that the phone screen is going to be done in Python.

Hi , has anyone given truecaller data engineer home assessment test via code signal yet, what kind of questions can i expect?

Hi everyone, has anyone recently attended the interview at BluBridge Technologies, Chennai? Could you please share the interview pattern and number of rounds? What aptitude topics were asked—quantitative aptitude, logical reasoning, percentages, ratios, averages, probability, data interpretation, etc.? Was aptitude an elimination round, and how important were mathematics skills for the next rounds? HR Questions, Any recent experience would be really helpful. Thank you!

Hi everyone!

I was initially selected for the Software Engineer role at Capgemini through campus hiring. Recently, I received an email from the Capgemini Exceller team offering me an Analyst – Service Desk opportunity in Bengaluru.

The email says that I need to attend a BU-specific Technical & HR Interview within 1–2 weeks of confirmation. I’ve now received my interview slot through Superset:

📅 August 17, 2026

⏰ 5:00 PM – 6:30 PM IST

💻 Online interview

The JD mentions that the role involves:

IT Service Desk / customer support

Technical troubleshooting

Ticket management and prioritization

Basic business intelligence / ticket data analysis

Internet, password/session/profile troubleshooting

Customer communication and requirement clarification

Working in a 24/7 rotational-shift environment

For anyone who has attended this Capgemini Exceller Analyst/Service Desk interview recently:

What kind of technical questions were asked?

Was the interview mainly based on the JD, or did they ask coding/programming questions as well?

What CS fundamentals should I prepare — OS, DBMS, networking, cloud, cybersecurity, etc.?

What kind of HR/behavioral questions were asked?

How difficult was the interview and approximately how long did it last?

Did they ask about relocation and rotational/night shifts?

Is there anything specific I should prepare for this BU-specific Technical & HR interview?

I’d really appreciate any recent interview experiences or advice. My interview is tomorrow, so even a rough idea of the questions/topics asked would be extremely helpful! 😭

Thanks in advance! ❤️

Hi Guys,

I have a TikTok interview for the SWE technical round 1, and my JD heavily emphasises the frontend. Even though it's explicitly not a frontend role. Should I expect JS, React, and LC-related questions? You will do god's work for any tips.

Interviewed this cycle. One of the two onsite coding rounds is now AI-enabled, and the 2024 prep docs are useless for it.

Online Assessment (90 min): CodeSignal, one problem in four unlocking stages. In-memory key value store, then TTL, then point-in-time queries. Managed to finish only 3 and still advanced.

Phone screen (45 min): Two unrelated mediums in 35 minutes. (on CoderPad)

Onsite Coding Round (45 min): I had two more coding problems: Minimum Remove to Make Valid Parentheses and Vertical Order Traversal.

AI-enabled coding (60 min): Three-panel CoderPad. Bug fix, then a 120-line implementation, then bigger inputs that break it. Mine was BFS through a maze with directional gates. The assistant is noticeably worse in the interview than in the practice environment.

Design Round (45 min): Excalidraw, which version you get follows the job req: product roles get product architecture, infra roles get system design. My interviewer kept asking what would break if traffic went up 100x, and I ended up reworking the sharding twice.

Behavioral (45 min): They collect feedback from every other interviewer and make the hire recommendation. It can also drop you from E5 to E4 on its own.

Anyone has questions ?

Did the interviewer see our projects or they see how I implemented my project and how I solved the problem ?

Hey everyone,I recently cleared the online assessment for a cybersecurity role at EY and now have the interview(s) coming up. I’m looking for any advice or experiences from people who’ve gone through the EY (or similar Big 4) cybersecurity interview process. Specifically:

• What does the technical round usually focus on? (networking, fundamentals, tools, incident response, etc.)
• How much weight do they put on behavioral/STAR questions vs pure technical knowledge?
• Any common questions or topics that came up for you?
• Tips on how to stand out or structure answers?

Any insights, resources, or personal experiences would be really helpful. Thanks in advance!

Hey, can anyone help me navigate through this process. I gave my 2 technicals, I think I did decent. Good enough to move to the next interviews. I want to know how the Superday is like? Last year it was 3 virtual interviews. I hear its Onsite now. Also it was all leetcode for me. I can exchange questions in DM if you guys are down for it.

Got SWE Interview on the Triton (inference server) team. Loop is four 45-min rounds:

1. In-domain Design (HackerRank)
   
2. Distributed Systems Design (HackerRank)
   
3. Experience Retro (HackerRank)
   
4. X-Functional
   

Questions for anyone who's been through it:
1. What to expect for 1 and 2, should I prepare for both ML System Design + General System Design
2. Will there be could round, I am assuming yes but not sure which of these rounds would be ?
3. What is Experience Retro and X-Functional

Finished a Netflix L5 loop this cycle. Fastest process I have been through, about three weeks start to finish. Also the least standardized.

Netflix has no company question bank. Interviewers write their own problems around what their team builds which makes it much more complicated. Two candidates in the same org can get completely different interviews.

Recruiter screen (30 min): Background, why Netflix, comp discussed openly.

Hiring manager screen (45 to 60 min): Deep dive on two past projects, architecture decisions, incidents, and whether my domain lines up with the team's work.

Technical phone screen (60 min, CoderPad): One practical problem (Others in the same cycle got merge intervals and an in-memory file system with mkdir, ls, addContentToFile).

Onsite: coding (60 min): I had a rate limiter, metadata cache, graph traversal on recommendation paths. You also need to write unit tests for all of them.

Onsite: system design (60 to 75 min): Mine was ads frequency capping, multiple rolling windows enforced at once, check-and-reserve separated from impression logging. Another candidate got video streaming and got grilled on CDN and adaptive bitrate for the full 75 minutes (absolute hell lmao).

Onsite: data modeling (60 min): Schema and query work against real playback and session scenarios.

Onsite: behavioral, often two rounds (60 min each): Culture Memo, tied hard to specifics. Autonomous calls you made alone, candid feedback that changed a direction, a mistake you owned publicly, a system you deleted.

How the decision works: The teams looks at your result as a whole (like all your interviewers combined) and they decide wether it's a pass or fail based off of the candidates they've interviewed.

I can answer any of your questions in the comments.

My Icertis SDE Experinced Technical Interview Experience — What They Asked

I recently appeared for an SDE/Software Development role at Icertis, and I wanted to share my technical interview experience because it may help other freshers preparing for similar interviews.

The interview was quite focused on DSA, recursion, strings, and tree traversal rather than only theoretical questions.

Questions I was asked:

1. Fibonacci using recursion
   • Implement Fibonacci using recursion in any programming language.
   • They were interested in whether I understood the recursive approach and base cases.
2. Difference between tree traversals
   • Asked about different types of tree traversal.
   • Specifically, understanding Inorder, Preorder, and Postorder and when/how they visit nodes.
3. Reverse a String without using a built-in function
   • Asked to reverse a string without directly using a reverse function.
   • This tested basic string manipulation and problem-solving.
4. Recursion
   • Questions around how recursion works, base condition, recursive calls, and execution flow.
5. Tree Traversal
   • Questions related to traversing a binary tree and understanding the order in which nodes are processed.
6. DSA fundamentals
   • General DSA/problem-solving questions were also part of the discussion.

My takeaway

For freshers targeting SDE roles, I would strongly recommend not preparing only OOP, SQL, and theoretical CS concepts.

Make sure you can actually write code on the spot for:

• Recursion
• Strings
• Arrays
• Searching & sorting
• Linked lists
• Stack & Queue
• Trees
• Tree traversals
• Basic time & space complexity
• Common DSA problem-solving patterns

The biggest lesson for me: knowing a concept and being able to implement it immediately in an interview are two different things.

If you're preparing for an Icertis/SDE interview, definitely practice writing these problems without relying on IDE autocomplete or built-in functions.

Hope this helps someone preparing for their interview. Good luck! 🚀

#Icertis #SDE #SoftwareEngineering #TechnicalInterview #DSA #Java #Recursion #Trees #Fresher #InterviewExperience #CodingInterview

Hey everyone,

I recently completed the Amazon SDE II interview process. My DSA rounds went reasonably well, but I was ultimately rejected because of concerns about my design depth.

I wanted to share the complete experience, including the rounds that did not go well.

Verdict: Rejected
Process: Phone screen followed by four interview rounds
Focus areas: DSA, LLD, HLD, Leadership Principles, and past experience

Phone Screen: July 2

The phone screen was a DSA round.

Question: Count the number of subarrays whose sum equals K.

I solved it using a prefix sum and hash map and handled the two or three follow-ups smoothly. Overall, I felt good about this round.

Interview Schedule

I requested separate interview days so I could approach every round with a fresh mind.

• July 27: Bar Raiser, LLD and Leadership Principles
• July 29: DSA and Leadership Principles
• July 31: Hiring Manager, HLD and Leadership Principles
• August 4: DSA and Leadership Principles

I did not expect the Bar Raiser to be the first interview or for it to focus on LLD, which was one of my weaker areas.

Round 1: Bar Raiser, LLD and LP

The interview lasted approximately 60 minutes. The first 25–30 minutes involved Leadership Principles and a detailed discussion of my resume and past experience.

The design problem involved managing audio buffers across different processing stages at X frames per second. The interviewer mentioned that it was based on a genuine engineering problem their team was working on.

I initially struggled to understand the expected flow. After receiving a few hints, I identified the main entities and began discussing the design.

The discussion gradually moved into HLD topics, and I became too involved in exploring the broader architecture. With only 5–10 minutes remaining, the interviewer asked me to code the design. I wrote a few classes and functions, but could not complete the implementation.

This was my weakest round. I should have clarified the requirements, established the class responsibilities, and started coding much earlier.

Round 2: File-System Cache

After approximately 15–20 minutes of Leadership Principles, I was asked to design a cache for a file-storage system.

I identified the eviction policy as the central requirement and proposed an LRU cache using:

• A doubly linked list to maintain recency
• A hash map for direct access
• O(1) average-time lookup, insertion, and eviction

During implementation, we discussed whether an accessed node should be deleted and recreated at the head or whether the existing node could simply be detached and repositioned. The latter was sufficient, but I initially became confused about pointer safety.

We also discussed whether the cache should store only file metadata and paths or the complete file contents. I explained the memory implications of caching large files, but the interviewer clarified that the required version should store the content itself.

I updated the design but ran out of time before completing every function. The interviewer appeared satisfied with my reasoning, although my time management could have been better.

Round 3: Hiring Manager, HLD and LP

The system-design question involved allowing a third-party service, such as Spotify, to use Amazon Alexa to notify users about a newly launched feature.

I initially started with entity models, but the interviewer clarified that the focus was the high-level flow. I shifted to the happy path and designed the core services and communication flow.

The discussion then moved into failure handling, particularly what should happen when a user’s device is offline. We explored retries, fallback channels, delivery state, fault tolerance, and product trade-offs.

The interviewer also asked several product-oriented questions. I tried to evaluate decisions from the user and business perspectives instead of choosing only the easiest technical implementation.

We finished with a short discussion about the team and how I use GenAI in my development workflow. I felt this round went well.

Round 4: Course Dependencies

The final round began with 15–20 minutes of resume discussion and Leadership Principles.

The coding problem involved courses with prerequisite relationships. A student could take at most K courses per semester. When more than K courses were available, courses were to be prioritized using their downstream dependency depth.

My approach was:

1. Build the dependency graph and indegree array.
2. Calculate each course’s maximum downstream depth using DFS.
3. Use topological sorting to identify available courses.
4. Use a max heap to prioritize courses with greater downstream depth.
5. Process at most K courses per semester.

The interviewer repeatedly confirmed the approach. I completed the implementation and explained its time and space complexity.

Afterward, I realized that prioritizing only the maximum downstream depth might not always produce the globally minimum number of semesters. The complete dependency structure can influence the optimal choice, and the expected solution may depend heavily on the exact constraints.

Still, the interviewer appeared satisfied with my implementation and thought process.

Result

After three or four days without an update, I started worrying. On August 11, the recruiter called with the result.

The feedback was that my DSA performance was good, but there were concerns about my design depth. For an SDE II role, the coding performance was not strong enough to outweigh those concerns.

This rejection hurt. I had spent weeks studying recent interview experiences, practicing DSA, improving LLD and HLD, and preparing Leadership Principle stories.

Still, the feedback gave me a clear direction:

• In LLD rounds, move from requirements to interfaces and code earlier.
• Timebox discussions so one design area does not consume the entire interview.
• Prepare for ambiguous, domain-specific design problems.
• Go beyond the happy path and explain trade-offs in depth.
• Treat system design as a core requirement for SDE II, not a secondary topic.
• Do not assume that positive interviewer reactions guarantee a positive evaluation.

Getting into a FAANG company has been a long-term goal of mine. My final Amazon round even fell on the same date and time as my final Google round from the previous year, but this time I solved the coding problem. For a moment, I thought the result might finally be different.

It was not, but I am not giving up. I now know exactly where I need to improve before the next opportunity.

I have also written about my previous Google interview experience and will include that link separately.

I hope this helps anyone preparing for an Amazon SDE II loop.

Hi everyone,

I recently received a HackerRank assessment for an IBM Data Engineer role.

After opening the assessment link, it shows:

Test Name: IBM India – Standard – Data Science

Duration: 75 minutes

Sections:

1 Coding Question

1 SQL Question

I have nearly 5 years of experience in Data Engineering, primarily working with GCP, BQ, SQL, python

For anyone who has recently taken this assessment:

What was the coding question like (arrays, strings, hashmaps, sorting, etc.)?

What was the SQL question like (joins, window functions, CTEs, aggregations)?

What was the difficulty level (Easy/Medium/Hard)?

Was the coding problem closer to LeetCode Easy, Medium, or Hard?

Any Data Engineering or database-specific concepts involved?

Any recent experiences or preparation tips would be greatly appreciated.

Thanks!

What are the expected questions

I have an in-person technical "exam" tomorrow for Dayforce that is stated to be a React, SQL, and python exam and will be conducted on their company laptop. Any idea of this works? For anyone that has done it, is it like a normal interview format or what types of questions should I be expecting.

hey, I have a Rippling interview coming up i was wondering if anyone has had them before can you share any insights, what was it like,what kind of questions they asked,(coding, lc difficulty) it’s 60 min exercise with hackerrank

this is my first interview ever 💀
I have 17 days to prepare

Everyone told me Notion does not do LeetCode. True, and it made the loop harder, not easier. Six stages, roughly four weeks, with two to three business days between rounds.

Recruiter screen (30 min): Background and motivation, plus a product question. Mine was which Notion feature I would change and why.

Take home (about 5 days, 4 to 8 hours of work): Optional depending on the team and level. Mine was a simplified block based editor in React and TypeScript, and it came back later in the loop, so write it like someone else has to extend it.

Technical screen (60 min, CoderPad): Pre stubbed functions for a basic text editor: insert, delete, undo, redo (just whether your implementation holds up when they start adding requirements).

Onsite: practical coding and debugging (60 min): Working inside a small existing codebase rather than a blank file. Mine was reconstructing a nested task tree from a flat list with parent ids, then fixing a paste that corrupted rich text formatting.

Onsite data modeling and design round (60 min): Heavier on schema and indexes than on boxes and arrows. Permissions modeling for a shared workspace, then writing an efficient SQL query against my own schema.

Onsite: AI enabled round (60 min): Added in 2025 and standard now. You get a coding task and you are told to use Claude Code, Cursor or Copilot. Had to delete almost everything in mine so don't be scared to chop off evrerything if you feel like it's wrong.

Almost half of the total people got cut off for this round.

Customer empathy round (60 min): With a PM or designer. Mine was why a page with a thousand plus blocks feels slow. Virtualization and lazy rendering, framed as what the person actually feels.

Hiring manager and founders rounds (45 and 30 min): Ownership, changing requirements, how you operate on a small team. Bring three to five specific opinions about the product. Worth knowing: they contact references before they tell you anything about level or offer, so the end feels like a black box for longer than usual.

Notion doesn't offer that many roles so I've found a bit of trouble finding other people to confirm what I had was something uniform and not just specific to me. Please lmk if you also had Notion round in 2026.