KASHII UPDATEZ Everyday Student Requirements & Python Coding Tutorials by Python Kashi
REQUIREMENT_ID_1573 • 3-DAY_ACTIVE_POLICY N

Platform Software Engineer

Company
Company Trigent Software
Type
Opportunity Type Full-Time Job
Salary
Stipend / Salary 20-35 Lacs PA
Location
Location Pune, India
Posted Date
Posted Date Yesterday
HR Contact Helpline +91 63631 88541 📞
Apply on Official Website ↗
Software testing RTOS Root cause C Root cause analysis System testing Analysis Hypervisor
📖
Aptitude Practice Questions & Mock Tests Open Resource ↗
Curated logical, quantitative, and verbal reasoning problems for the initial online screening round.
🎯
Company-Specific Interview Preparation Corner Open Resource ↗
Detailed interview experiences, exam formats, and previous test questions for Trigent Software and tech roles.
📝
Technical Placement Cheat Sheets & Question Bank Open Resource ↗
High-yield coding cheat sheets, core CS fundamentals (OOP, DBMS, OS, Networks), and rapid revision guides.
💻
Algorithm, DSA & Live Code Debugger Practice Open Resource ↗
Hands-on problem sets to improve coding speed and step-by-step memory debugging.

Experience: 8-13 Yrs. Open to matching qualifications.

1
Online Assessment / Technical Interview Rounds / HR Review
Job Title: Platform Software Engineer Embedded C / RTOS Experience: 7+ Years (5+ Years Relevant Experience) Location: Ahmedabad / Pune Work Mode: Onsite Domain: Aerospace Job Description We are looking for an experienced Platform Software Engineer with strong C programming skills and expertise in RTOS/Hypervisor-based embedded systems testing. The candidate will develop and execute black-box tests for aerospace platforms, support DO-178C compliance, analyze system defects, and build automated regression test suites. Key Responsibilities Develop and execute black-box tests for RTOS/Hypervisor products. Translate requirements and DO-178C DAL-A objectives into test procedures and scripts. Test thread performance, context switching, IPC, device driver latency, resource isolation, and stress scenarios. Analyze test failures, identify defects, and support root cause analysis. Develop automated test suites for regression testing. Collaborate with architecture, certification, and white-box testing teams. Required Skills Strong C programming and debugging skills. Experience testing RTOS/Hypervisor-based embedded systems. Black-box and white-box verification knowledge. Understanding of DO-178C and DAL-A objectives. Experience in system-level testing, defect analysis, and debugging. Mandatory: Aerospace domain experience. Good to Have Structural Coverage Analysis. Object Code Coverage Analysis. Embedded software verification and certification experience. For More Info Pls Contact on 6363188541 / Priyanshu_S@Trigent.com

Trigent Software — QA & Automation Testing 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 🎯
Trigent Software Interview Preparation Corner

Comprehensive guide covering typical interview formats, common questions, and preparation tips for Trigent Software 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 (Software testing, RTOS, Root cause, C, Root cause analysis, System testing, Analysis, Hypervisor) & 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
Trigent Software Core Values, Learning Agility & Offer Terms
Demonstrate passion, strong communication, and readiness for full-time collaboration.
What is the difference between Implicit Wait, Explicit Wait, and Fluent Wait in Selenium? Answer ▼
Model Answer: Implicit Wait sets a global timeout for all element lookups. Explicit Wait pauses execution until a specific ExpectedCondition (e.g. elementToBeClickable) is met. Fluent Wait allows defining polling frequency and ignoring specific exceptions like NoSuchElementException.
Explain the Page Object Model (POM) and its advantages in Test Automation. Answer ▼
Model Answer: POM is a design pattern that creates an object repository for web UI elements. It separates test scripts from page locators, reducing code duplication and making maintenance easy when UI elements change.
How do you handle dynamic WebElements whose ID changes on page reload? Answer ▼
Model Answer: Use dynamic XPath methods like contains(), starts-with(), text(), or XPath axes (ancestor, following-sibling, parent) instead of brittle absolute paths.
What is the difference between @BeforeMethod and @BeforeClass in TestNG? Answer ▼
Model Answer: @BeforeClass runs once before the first test method in the current class, while @BeforeMethod executes before each individual test method.
How do you validate REST API response codes and JSON payload using Postman / RestAssured? Answer ▼
Model Answer: In RestAssured: given().when().get('/endpoint').then().assertThat().statusCode(200).body('status', equalTo('ACTIVE')).
Why do you want to join Trigent Software as a Platform Software Engineer?
Preparation Tip: Highlight Trigent Software's market reputation, recent tech innovations, and how your skills in Software testing 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 ↗
Trigent Software
Platform Software Engineer
Apply ↗
Chat Chat with Kashii