Ingeniero De Software 2 Interview Questions

557 ingeniero de software 2 interview questions shared by candidates

Programs like remove the duplicate numbers in sorted array by scanning the array only once, means {1,1,2,3,6,8,8,8,8}-->{1,2,3,6,8}, producer and consumer problem, and finding the sum of diagonal elemts in array of any size, etc
avatar

Software Engineer With 2+ Years of Experience

Interviewed at Huawei Technologies

3.4
Nov 27, 2011

Programs like remove the duplicate numbers in sorted array by scanning the array only once, means {1,1,2,3,6,8,8,8,8}-->{1,2,3,6,8}, producer and consumer problem, and finding the sum of diagonal elemts in array of any size, etc

1st -- about yourself,family details,expected sal, previous company details , income details, reason for quitting previous job, 2nd day-- previous project details, .net architecture, mvc,joins,predefined functions in sql.
avatar

.NET Developer(1-2 Exp)

Interviewed at Focus Softnet

3.3
Oct 30, 2015

1st -- about yourself,family details,expected sal, previous company details , income details, reason for quitting previous job, 2nd day-- previous project details, .net architecture, mvc,joins,predefined functions in sql.

System Design Round – Design Twitter (1 Hour) Objective: Design a simplified version of Twitter, focusing on core features like posting tweets, timelines, and following users. What was assessed: Requirements gathering: Clarified functional (e.g., tweet, follow, timeline) and non-functional (e.g., scalability, latency) requirements. High-level architecture: Designed components like: User Service Tweet Service Timeline/Feed Service Follower Graph Service Data modeling: Discussed database schema for tweets, users, followers (SQL or NoSQL trade-offs). Scaling strategies: Sharding for tweet storage Caching popular tweets Fan-out vs fan-in timeline generation Tech choices: Talked about using message queues, databases, caching (e.g., Redis), etc. Bottlenecks & trade-offs: Handled questions on real-time delivery, rate limits, consistency vs availability. Interview Style: Conversational Interviewer guided parts of the discussion Follow-up questions tested understanding of distributed systems and design trade-offs
avatar

Software Engineer 2

Interviewed at Ambient.ai

4.1
Jul 31, 2025

System Design Round – Design Twitter (1 Hour) Objective: Design a simplified version of Twitter, focusing on core features like posting tweets, timelines, and following users. What was assessed: Requirements gathering: Clarified functional (e.g., tweet, follow, timeline) and non-functional (e.g., scalability, latency) requirements. High-level architecture: Designed components like: User Service Tweet Service Timeline/Feed Service Follower Graph Service Data modeling: Discussed database schema for tweets, users, followers (SQL or NoSQL trade-offs). Scaling strategies: Sharding for tweet storage Caching popular tweets Fan-out vs fan-in timeline generation Tech choices: Talked about using message queues, databases, caching (e.g., Redis), etc. Bottlenecks & trade-offs: Handled questions on real-time delivery, rate limits, consistency vs availability. Interview Style: Conversational Interviewer guided parts of the discussion Follow-up questions tested understanding of distributed systems and design trade-offs

Round 1: Managerial round -> Questions from my previous projects. -> Questions related to my area of expertise (Javascript and Node). -> Questions relating SOLID principles and my previous projects. -> Node packages used in my projects. Round 2: Technical round 1 -> I was asked to explain about my previous project and team work. -> How we efficiently used version control to manage our project. -> A trade off I made in previous projects. -> How good we were during our teamwork. -> A hurdle I faced in my project and how I solved it. Round 3: Technical round 2 -> Almost similar to Tech round 1
avatar

Software Engineer 2

Interviewed at Pluralsight

2.9
Aug 24, 2022

Round 1: Managerial round -> Questions from my previous projects. -> Questions related to my area of expertise (Javascript and Node). -> Questions relating SOLID principles and my previous projects. -> Node packages used in my projects. Round 2: Technical round 1 -> I was asked to explain about my previous project and team work. -> How we efficiently used version control to manage our project. -> A trade off I made in previous projects. -> How good we were during our teamwork. -> A hurdle I faced in my project and how I solved it. Round 3: Technical round 2 -> Almost similar to Tech round 1

Viewing 1 - 10 interview questions

Glassdoor has 557 interview questions and reports from Ingeniero de software 2 interviews. Prepare for your interview. Get hired. Love your job.