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

Staff Engineer - Backend API

Company
Company Indxs Resources
Type
Opportunity Type Full-Time Job
Salary
Stipend / Salary 35-50 Lacs PA
Location
Location Delhi NCR, India
Posted Date
Posted Date Yesterday
Apply on Official Website β†— 🀝 Connect Recruiter β†—
IN
Indxs Resources Technical Recruiter
Talent Acquisition Partner
🏒 Indxs Resources β€’ Direct Recruiter Email: recruiter@indxsresources.com
.Net Core Core .Net Backend Microservices AWS API
πŸ“–
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 Indxs Resources 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: 7-12 Yrs. Open to matching qualifications.

1
Online Assessment / Technical Interview Rounds / HR Review
About AXS - India Development Center AXS (www.axs.com) connects fans with the artists and teams they love. Each year we sell millions of tickets to thousands of incredible eventsfrom concerts and festivals to sports and theaterβ€”at some of the most iconic venues in the world. Since our founding in 2011, we’ve consistently pushed the industry forward and improved experiences for fans, making it easier than ever to discover events, find the perfect seats, and enjoy unforgettable live entertainment. We’re passionate about improving the fan experience and providing game-changing solutions for our clients. We’re always looking for smart, motivated people to help make it happen. Bring your enthusiasm, your big ideas, and your desire to collaborate with some of the best and brightest in technology and entertainment. The Role AXS is seeking a Senior (7-10 years) & Staff Software Engineer (10+ years)– Back End to join our API and Platform team. This is a senior technical leadership role requiring deep expertise in .NET Core, C#, microservices, and AWS to architect and build the next generation of our high-performance API services. You will shape platform architecture, lead complex system design, build reusable services at scale, and mentor engineering teams. You will work closely with Product, Architecture, SRE, and cross-functional leaders to deliver seamless, secure, and scalable experiences across our ticketing platform. This role requires exceptional technical judgment, strong system design expertise, hands-on coding excellence, and the ability to influence engineering culture across the organization. What You'll Be Doing Architect and evolve modular, composable microservices and APIs using .NET Core and C# Lead design of core platform services including identity, payments, pricing, inventory, and distribution APIs Design for high availability, low latency, and global scale (multi-region AWS) Own services end-to-end, including design, implementation, testing, deployment, monitoring, and operational support Establish and promote engineering best practices for code quality, CI/CD, observability, and testing automation Serve as a technical expert and thought leader, providing architectural guidance and mentorship Partner with Product, Architecture, SRE, and Security to align roadmaps and create scalable solutions Lead modernization of legacy components into API-first, cloud-native microservices Build systems capable of supporting millions of users and peak ticket on-sales under extreme concurrency What to Bring 7+ years of hands-on software engineering experience with demonstrated technical leadership BS in Computer Science or a related technical field (or equivalent practical experience) Expert-level proficiency in C# and .NET Core, microservices architecture, RESTful APIs, and event-driven systems Deep knowledge of AWS services (Lambda, ECS/EKS, DynamoDB, RDS, S3, Kinesis, API Gateway, SNS/SQS) Proven experience designing and scaling high-performance, high-availability distributed systems Strong understanding of database systems (RDBMS & NoSQL) and caching strategies (Redis, Memcached) Experience with CI/CD, infrastructure as code (Terraform, CloudFormation), and DevSecOps practices Deep understanding of system resiliency patterns (circuit breakers, retries, rate limiting, idempotency) Experience mentoring engineers and influencing engineering standards Ability to make sound architectural decisions with incomplete information Excellent communication skills with the ability to translate complex concepts for technical and non-technical audiences Calm under pressure, especially during high-traffic events Nice to Have Experience with digital ticketing, e-commerce, or high-traffic consumer platforms Familiarity with containerization and orchestration (Docker, Kubernetes) Experience with domain-driven design (DDD) and event sourcing Experience integrating third-party APIs (payments, identity providers) Proficiency in leveraging AI/GenAI across the software development lifecycle

Indxs Resources β€” 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 🎯
Indxs Resources Interview Preparation Corner

Comprehensive guide covering typical interview formats, common questions, and preparation tips for Indxs Resources 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 (.Net Core, Core, .Net, Backend, Microservices, AWS, API) & 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
Indxs Resources 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 .Net Core. 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 Indxs Resources as a Staff Engineer - Backend API?
Preparation Tip: Highlight Indxs Resources's market reputation, recent tech innovations, and how your skills in .Net Core 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 β†—
Indxs Resources
Staff Engineer - Backend API
Recruiter Apply β†—
Chat Chat with Kashii