questions

Q) Basics of Http

• What are the main http coes and their meaning(2xx, 3xx...). What is 3xx(client redirecting)
• Request & Response cycle
• What headers are used(auth header etc)

Q) Authorization Token management. What if I decode the token manupulate it and encode it and send to service. How does service handle this ?

Q) What coding patterns do you know

Q) What design patterns

Q) Clean code principles

Q) Dependency Inversion

Q) Dependecny Injection Control

Q) What are the solid principles ?

Q) How to assure high availability ?

• Within infra via scaling, Shardinign the or dublicating the ebrokers
• Within the service layer via circuti breaker
• How is it managed when one service call another service and if that services is not avaialbe ? Tight vs Loose coupling

Q) How to assure resiliance
Q)
Questions on Core Java
(Handling date, time, text, numeric and boolean values, Controlling Program Flow, Utilizing Java Object-Oriented
Approach, Handling Exceptions, Working with Arrays and Collections, Working with Streams and Lambda expressions)

Questions on Concurrency, Memory Management and Garbage Collection
Coding task in candidate’s preferred IDE (via screen sharing) or one of online code sharing tools if no IDE
Code review task.

Math/logic problem solving task.
Based on candidate background, following areas may be covered: Linux basics, Kotlin, SQL basics, Design patterns

• DFS question to find the shortest path

Q) Questions on algorithms

• understand the time & space complexity of your solution. Be able to reason throught tade ofss between the optimum solution

What to expect in AWS SDE interviews

Coding problems on arrays, strings, hashing, trees, graphs, dynamic programming, and greedy patterns.
A mix of single-file solutions and small system-design/architecture prompts at higher levels.
Expect time-pressure practice, clear problem statements, and justifications of complexity.
Strong emphasis on writing clean, testable code and explaining your approach aloud.

• ** Hard sliding window** problem ?
• Tree based problem ismilar to "Burn Binary Tree"

1. Algorithm / Pattern Focus

The response mentions the typical SDE I patterns they saw:

• tree traversel, greedy algortimhs, dynamic programming, sortin g, sets, lists, maps, arrays
• Sliding Window on Strings/Arrays → work on substring/subarray problems, max/min window, dynamic lengths.
• two pointers, backtracking
• BFS/DFS on Grids/Graphs → classic grid traversal, connected components, shortest paths.
• Heaps for "Top K"-style problems → priority queues, Kth largest/smallest, merge K sorted arrays.

Q) 1. Core Java concepts:

• OOP principles (inheritance, polymorphism, encapsulation, and abstraction)
• Data structures and algorithms
• Collections framework
• Exception handling
• Multithreading and concurrency
• Java 8+ features (streams, lambdas, Optional, etc.)

2. Frameworks and libraries:

• Spring and Spring Boot
• Hibernate or other ORM frameworks
• JUnit and Mockito for testing
• Apache Kafka or other messaging systems
• Cache systems like Redis or Memcached
• Databases and data storage:

3. SQL and NoSQL databases (e.g., PostgreSQL, MySQL, MongoDB, Cassandra)
   ACID properties and CAP theorem
   Database schema design and normalization
   Query optimization and performance tuning
   Web services and APIs:

RESTful API design principles
HTTP methods, status codes, and headers
Authentication and authorization (OAuth, JWT, etc.)
API versioning strategies
Microservices and distributed systems:

Microservices architecture patterns and best practices
Service discovery and load balancing
Fault tolerance, resilience, and scalability
Event-driven architectures and CQRS
Deployment and DevOps:

Docker and containerization
Kubernetes or other container orchestration platforms
Continuous Integration/Continuous Deployment (CI/CD)
AWS, GCP, or other cloud platforms
Performance and optimization:

Performance monitoring and profiling
Garbage collection and memory management
JVM tuning and optimization
General software engineering: