KASHII UPDATEZ Everyday Student Requirements & Python Coding Tutorials by Python Kashi
REQUIREMENT_ID_1651 β€’ 3-DAY_ACTIVE_POLICY

Assistant Engineer

Company
Company Ericsson
Type
Opportunity Type Full-Time Job
Salary
Stipend / Salary 4 LPA
Location
Location Noida, Uttar Pradesh, India
Posted Date
Posted Date Yesterday
Network Operations Incident Management ITIL GSM Call Flow Linux Charging Systems OneFM Grafana oneTM ITSM SLA Management Problem Management Communication
πŸ“–
Aptitude and Logical Reasoning Practice Open Resource β†—
Enhances analytical thinking and problem‑solving skills useful for incident analysis and trend assessment at Ericsson.
πŸ“–
Technical Interview Preparation Open Resource β†—
Provides insights into common telecom and NOC interview questions, helping candidates prepare for Ericsson’s technical rounds.
πŸ“–
Interview Strategy and Mock Tests Open Resource β†—
Offers mock interview scenarios and tips to boost confidence during Ericsson’s selection process.
πŸ“–
Coding Challenges and Algorithms Open Resource β†—
Improves logical reasoning and problem‑solving skills that can be applied to troubleshooting and automation tasks.

Bachelor’s degree in Electronics & Communication, Telecommunication, Computer Science, or related field. Minimum 60% in aggregate. No backlogs. Preferred batch years 2025–2027. Candidates should have 5+ years of telecom or NOC experience and be comfortable working in a 24/7 shift environment.

1
Round 1: Technical interview (NOC & telecom fundamentals)
2
Round 2: Technical interview (tools & scenario based)
3
Round 3: HR interview (cultural fit & motivation)
Ericsson, a global leader in telecommunications, has been a pioneer in delivering cutting‑edge network solutions for over 150 years. With a strong presence in India, the company focuses on innovation, sustainability, and customer‑centric services. Ericsson’s workforce is known for its collaborative culture, continuous learning, and commitment to digital transformation. The organization invests heavily in employee development, offering training programs, certifications, and opportunities to work on next‑generation 5G and cloud‑native networks. The Assistant Engineer role is a 1st Level Operations position based in Noida. As a key member of the 24/7 support team, you will monitor network services, manage incidents, and ensure that all operations meet the defined Service Level Agreements (SLAs). Your day‑to‑day responsibilities will include real‑time monitoring of alerts via tools such as OneFM and Grafana, creating and tracking tickets in ITSM platforms like oneTM, and collaborating with cross‑functional teams to resolve issues promptly. Key responsibilities: 1. Monitor network services and manage events at the 1st level. 2. Assess trends from customer complaints and provide actionable insights. 3. Resolve incidents within SLA, escalating when necessary. 4. Initiate problem management and support corrective maintenance. 5. Improve customer experience through use‑case analysis. 6. Support planned activities and manage group mailboxes. 7. Create tickets and track them using ITSM tools. 8. Work with NOC teams to maintain network stability. 9. Participate in shift rotations for 24/7 support. 10. Maintain documentation and knowledge base entries. Tech stack and tools: Ericsson Operations Engine, OneFM, Grafana, oneTM, ITSM, basic Linux, charging system fundamentals, GSM call flow. Growth path: Starting as an Assistant Engineer, you can progress to Senior Engineer, NOC Lead, or Operations Manager. Ericsson offers clear career ladders, mentorship, and exposure to global projects, enabling you to build expertise in telecom operations, network management, and cloud technologies. Why join Ericsson? You’ll work with industry‑leading technology, contribute to mission‑critical services, and benefit from a supportive, inclusive environment that values innovation and professional growth. The role offers competitive compensation, comprehensive benefits, and the chance to be part of a company that shapes the future of connectivity.

Ericsson β€” Software Engineering & Full Stack Interview Guide

Previously asked questions, exam syllabus, coding benchmarks & round strategy.

APTITUDE & LOGIC πŸ“–
Aptitude Practice Questions & Online Mock Tests

Curated logical, quantitative, and verbal reasoning problems to sharpen reasoning skills required for the initial screening test.

Open Resource β†—
COMPANY GUIDE 🎯
Ericsson Interview Preparation Corner

Comprehensive guide covering typical interview formats, common questions, and preparation tips for Ericsson and off-campus tech roles.

Open Resource β†—
MOCK TESTS & PAPERS πŸ“
Comprehensive Interview Prep Resources & Syllabus

Collection of previous year questions, company-specific test patterns, and interview experiences for technical and HR rounds.

Open Resource β†—
CODING PRACTICE πŸ’»
Algorithm and Data Structure Problem Set

Practice problems to improve coding proficiency and algorithm problem-solving speed for technical rounds.

Open Resource β†—
Round 1: Online Assessment (OA)
Aptitude, Quantitative Logic & 2 Coding Problems
Focus on accuracy and speed. Practice arrays, strings, and standard arithmetic puzzles.
Round 2: Technical Interview 1
Core Tech Stack (Network Operations, Incident Management, ITIL, GSM Call Flow, Linux, Charging Systems, OneFM, Grafana, oneTM, ITSM, SLA Management, Problem Management, Communication) & Live Code Tracing
Explain your thought process aloud. Analyze time & space complexities before coding.
Round 3: System Design & Problem Solving
Database Schemas, APIs & Architecture Basics
Clarify edge cases, diagram schemas cleanly, and discuss scalability trade-offs.
Round 4: HR & Cultural Fit Discussion
Ericsson Core Values, Learning Agility & Offer Terms
Demonstrate passion, strong communication, and readiness for full-time collaboration.
Explain OOP (Object-Oriented Programming) principles with real-world examples in Network Operations. Answer β–Ό
Model Answer: 1. Encapsulation (data hiding via private fields/getters). 2. Abstraction (hiding implementation complexity). 3. Inheritance (code reusability). 4. Polymorphism (method overriding/overloading).
What is the time and space complexity of QuickSort vs MergeSort? Answer β–Ό
Model Answer: QuickSort: Average O(N log N) time, O(log N) space. Worst O(N^2). MergeSort: Guaranteed O(N log N) time, but requires O(N) auxiliary space.
Explain the difference between SQL Indexing (B-Tree vs Hash) and when not to use an index. Answer β–Ό
Model Answer: Indexes speed up SELECT queries via B-Trees. However, they slow down INSERT, UPDATE, and DELETE operations because indexes must be updated on disk. Avoid on low-cardinality columns (e.g., boolean flags).
What happens under the hood when you enter a URL in a browser? Answer β–Ό
Model Answer: 1. DNS lookup (resolves IP). 2. TCP 3-way handshake (SYN, SYN-ACK, ACK). 3. TLS negotiation for HTTPS. 4. HTTP GET request sent. 5. Server responds with HTML/CSS/JS. 6. Browser renders DOM & CSSOM tree.
What is the difference between REST and GraphQL APIs? Answer β–Ό
Model Answer: REST uses multiple fixed endpoints with possible over/under-fetching. GraphQL uses a single endpoint allowing clients to query exact fields in a single request.
Why do you want to join Ericsson as a Assistant Engineer?
Preparation Tip: Highlight Ericsson's market reputation, recent tech innovations, and how your skills in Network Operations directly solve their team's objectives.
Describe a challenging bug or academic project roadblock and how you resolved it.
Preparation Tip: Use the STAR method: Situation (project context), Task (what needed solving), Action (specific tools/logic applied), Result (quantifiable positive outcome).
How do you handle strict deadlines or sudden scope changes?
Preparation Tip: Explain your prioritization strategy, proactive communication with mentors/peers, and agile mindset.

More Fresh Requirements in Software Engineering

View Category Feed β†—
Ericsson
Assistant Engineer
Apply Apply Now β†—
Chat Chat with Kashii