Hosni Bey

Next.js vs NestJS vs Nuxt.js : #Next.js: A powerful React framework focused on building server-side rendered and static web applications with features like API routes, static site generation (SSG), and server-side rendering (SSR). It is ideal for React developers looking to optimize their app’s performance and SEO. #NestJS: A backend framework built with Node.js and TypeScript, inspired by Angular’s modular architecture. It is well-suited for building scalable, maintainable server-side applications, including microservices, RESTful APIs, and GraphQL services. #Nuxt.js: A framework for Vue.js that supports server-side rendering, static site generation, and building full-stack applications. It is perfect for developers working with Vue.js, providing a streamlined approach to SSR and modern web app architecture. Looking for expert development in Next.js, NestJS, or Nuxt.js? I offer customized solutions for web and backend apps. Let’s talk about your project!💬 #NextJS #NestJS #NuxtJS #WebDevelopment #BackendDevelopment #FullStackDevelopment #CustomSolutions #HighPerformanceApps #JavaScript #WebApps #DevelopmentServices

27

4 commentaires

▶ HOw to Write Code Like ✅ Pro ❎ Noob. ⭕ Follow for more WAQAR Ullah 👍 𝑯𝒊𝒕 𝒍𝒊𝒌𝒆, if you found it helpful ! 🔁 𝑹𝒆𝒑𝒐𝒔𝒕 it to your network ! 🔖 𝑺𝒂𝒗𝒆 it for the future ! 📤 𝑺𝒉𝒂𝒓𝒆 it with your connections ! 💭 𝑪𝒐𝒎𝒎𝒆𝒏𝒕 your thoughts ! #noobCode #ProCode #code #Frontend #backend #database #fullstack #MachineLearning #ArtificialIntelligence #DataScience #Technology #DataAnalytics #AI #DeepLearning #TechTrends #FutureTech #DataType #DataAnalysis #python #w3schools #json #web #token #jwt #javascript #js #frontend #backend #developers #html #css #react #cheatsheet #reactjs #project #freshers #resume #job #search #jobsearch #jobs #useful #techniques #tips #mastery #clean #code #guide #developer #web #development #nextjs #nextjs14 #roadmap #webdevelopment #mern #mean #angular #nodejs #expressjs #postgresql #sql #guide #useful #notes

8

3 commentaires

This takeScreenshot method is used to capture a screenshot of a running application with Selenium and save it to a file. 🤔 How it works: 📷 Taking the screenshot: The method uses Selenium's TakesScreenshot interface to capture the current screen of the application. 📄 Generating the file name: A timestamp is generated in the format 🖌️ yyyyMMdd_HHmmss to ensure that each screenshot has a unique name. The file name is then composed of stepName (step name, passed as an argument) and the timestamp, and it is saved in the screenshots/ folder. 📁 Creating the folder (if necessary): Before saving the image 🪪 , the method checks if the screenshots folder exists. If not, it is created using Files.createDirectories(). 💾 Saving the screenshot: Once the folder is created (or confirmed to exist), the screenshot is copied to the folder with the file name generated using Files.copy(). ❌ Error handling: If an error occurs while creating the folder or copying the file (e.g. insufficient permissions or a write error), an error message is displayed in the console.

17

1 commentaire

Ready to Code? Unlock the Power of .NET 𝐋𝐞𝐚𝐫𝐧 𝐭𝐡𝐞 𝐁𝐚𝐬𝐢𝐜𝐬: HTML 📄, CSS 🎨, JavaScript 💻 – These are your building blocks! 𝐌𝐚𝐬𝐭𝐞𝐫 𝐅𝐫𝐨𝐧𝐭-𝐄𝐧𝐝 𝐅𝐫𝐚𝐦𝐞𝐰𝐨𝐫𝐤𝐬: Bootstrap 📱 for responsive design and Angular ⚡️ for dynamic SPAs. 𝗕𝗮𝗰𝗸-𝗘𝗻𝗱 𝗧𝗶𝗺𝗲: Learn C# 🧑‍💻 and ASP_NET 💻 to build your back-end. Master MVC 🏗️ and Web API 🌐 to handle data and requests. 𝗪𝗼𝗿𝗸 𝘄𝗶𝘁𝗵 𝗗𝗮𝘁𝗮𝗯𝗮𝘀𝗲𝘀: Use SQL Server 📊 to store your data. Entity Framework , ADO_Net 🛠️ is used to access and manipulate that data using C# objects. 𝗚𝗼 𝗖𝗿𝗼𝘀𝘀-𝗣𝗹𝗮𝘁𝗳𝗼𝗿𝗺 𝘄𝗶𝘁𝗵 .𝗡𝗘𝗧 𝗖𝗼𝗿𝗲: Build apps that run on Windows, Linux, and macOS. 🌍 𝐅𝐮𝐥𝐥-𝐒𝐭𝐚𝐜𝐤 𝐀𝐰𝐞𝐬𝐨𝐦𝐞𝐧𝐞𝐬𝐬: Combine Front-End + Back-End for full-stack superpowers! 🦸‍♀️ 𝐌𝐚𝐬𝐭𝐞𝐫 𝐭𝐡𝐞 𝐓𝐨𝐨𝐥𝐬: Use Visual Studio 🖥️, Git/GitHub 🧑‍🤝‍🧑, and CI/CD ⚙️. 𝐃𝐞𝐩𝐥𝐨𝐲 𝐭𝐨 𝐭𝐡𝐞 𝐂𝐥𝐨𝐮𝐝: Use Azure ☁️ and Docker 🐳 to deploy your app like a pro! 𝐹𝑒𝑒𝑙 𝑓𝑟𝑒𝑒 𝑡𝑜 𝑠ℎ𝑎𝑟𝑒 𝑡ℎ𝑖𝑠 𝑖𝑛𝑓𝑜𝑟𝑚𝑎𝑡𝑖𝑜𝑛 𝑡𝑜 𝑠𝑝𝑟𝑒𝑎𝑑 𝑡ℎ𝑒 𝑘𝑛𝑜𝑤𝑙𝑒𝑑𝑔𝑒.  𝐼𝑓 𝑦𝑜𝑢 𝑓𝑖𝑛𝑑 𝑖𝑡 ℎ𝑒𝑙𝑝𝑓𝑢𝑙, 𝑐𝑜𝑛𝑠𝑖𝑑𝑒𝑟 𝑟𝑒𝑝𝑜𝑠𝑡𝑖𝑛𝑔. 𝐹𝑜𝑟 𝑚𝑜𝑟𝑒 𝑠𝑢𝑐ℎ 𝑡𝑒𝑐ℎ 𝑐𝑜𝑛𝑡𝑒𝑛𝑡, 𝑓𝑜𝑙𝑙𝑜𝑤 Vaibhav Trikolikar 𝑅𝑒𝑚𝑒𝑚𝑏𝑒𝑟 𝑡𝑜 𝑙𝑖𝑘𝑒, 𝑓𝑜𝑙𝑙𝑜𝑤, 𝑎𝑛𝑑 𝑠ℎ𝑎𝑟𝑒 ✅ ! #𝐷𝑜𝑡𝑁𝑒𝑡𝐶𝑜𝑟𝑒 #𝑠𝑜𝑓𝑡𝑤𝑎𝑟𝑒𝑑𝑒𝑣𝑒𝑙𝑜𝑝𝑚𝑒𝑛𝑡 #𝑡𝑒𝑐ℎ𝑐𝑜𝑚𝑚𝑢𝑛𝑖𝑡𝑦

33

2 commentaires

Day 104 📅 🌟 Master JavaScript Like a Pro: Object Methods & the Magic of this 🌟 📜 Top Takeaways for Every Developer: Object Methods: Functions that bring life to objects! this Keyword: Your dynamic context wizard 🪄. Explore explicit bindings with call(), apply(), and bind() 🛠️. Unravel lexical scoping with arrow functions 🚀. Decode event handler contexts for real-world projects 🎯. 💬 Drop your thoughts, questions, or favorite use cases in the comments! Let’s learn and grow together. 👩‍💻👨‍💻 🔖 #JavaScript #WebDevelopment #ProgrammingTips #LearnToCode #FrontEndDevelopment #TechCommunity #CodeNewbie #DeveloperJourney #CodingLife #TechLearning #WebDesign

5

  𝗦𝗲𝗮𝗿𝗰𝗵 𝗩𝗼𝗹𝘂𝗺𝗲 (𝗦𝗩) 𝗮𝗻𝗱 𝗦𝗲𝗮𝗿𝗰𝗵 𝗤𝘂𝗲𝗿𝘆 𝗦𝗰𝗼𝗿𝗲 (𝗦𝗤𝗦) Do you know the difference between 𝗦𝗩 & 𝗦𝗤𝗦? We mostly know the SV but we have never thought about SQS, it helps in the final selection of search queries from the search query performance report. I am here to help you... if you want to know both terms under the same roof then comment "𝗬𝗲𝘀" and I will share the difference with you. follow Engr. Ayyaz Shahbaz Butt for more information #Amazon, #AmazonSearchVolume, #AmazonSearchQueryScore

2

1 commentaire

API routes in Next.js allow you to build server-side functions that can handle requests from the client. These routes are defined within the /pages/api directory and follow the file-based routing system. Each file inside this folder becomes an endpoint, and you can easily create GET, POST, PUT, or DELETE requests. How API Routes Work: Files in the /api folder are treated as backend code. These routes are secure and do not get included in the client-side bundle. You can use them to interact with databases, handle form submissions, authenticate users, and etc.. Use Case: API routes are perfect when you need server-side functions like submitting forms, fetching data from a database, or handling webhooks. #APIRoutes #Nextjs #WebDevelopment #ServerSide

19

2 commentaires

JPA Paging vs. JDBC Cursor in Spring Batch: Choosing the Right Approach for Your Batch Jobs When processing large datasets in Spring Batch, the choice of data reading approach can significantly impact performance. Two commonly used methods are JPA Paging and JDBC Cursor, each with distinct characteristics suited for specific scenarios. Here's a quick comparison to help you decide: 1. Underlying Technology - JPA Paging: Leverages JPA (e.g., Hibernate) to query data in chunks, often using the “findAll(Pageable pageable)” method. - JDBC Cursor: Uses plain JDBC and database cursors to stream rows one by one via a “ResultSet”. 2. Performance - JPA Paging: Efficient for moderate datasets but introduces overhead due to entity management (e.g., dirty checking, object creation). Pagination may also require additional queries. - JDBC Cursor: Optimized for large datasets, streaming rows without loading them into memory all at once. Minimal overhead makes it faster for large-scale batch jobs. 3. Memory Usage - JPA Paging: Requires storing an entire page of data in memory, leading to higher memory consumption with large pages. - JDBC Cursor: Streams small chunks of data, keeping memory usage low. 4. Transactional Integrity - JPA Paging: Automatically manages entity lifecycle within a transactional session but requires careful transaction boundary handling for recovery. - JDBC Cursor: Offers flexibility for manual transaction management, which is beneficial for long-running jobs. 5. Database Independence - JPA Paging: Database-agnostic but performance depends on the database’s pagination implementation. - JDBC Cursor: Also database-independent, but queries might need optimization based on database-specific cursor features. 6. Error Handling and Recovery - JPA Paging: More complex error handling due to entity abstraction and potential issues like lazy loading. - JDBC Cursor: Straightforward error handling, as it directly interacts with JDBC. Proper management of the cursor’s lifecycle is essential. 7. Use Cases - JPA Paging: Ideal for moderate datasets that require ORM features like entity lifecycle management and automatic persistence. - JDBC Cursor: Best for large datasets where memory efficiency, speed, and low-latency data reads are critical. Conclusion Choose JPA Paging when working with small to medium datasets that benefit from JPA’s ORM capabilities. Opt for JDBC Cursor for performance-critical, large-scale batch jobs that demand efficient memory usage and minimal abstraction overhead. #Spring #JPA #Batch #Data #Database

4

𝗦𝘆𝘀𝘁𝗲𝗺 𝗗𝗲𝘀𝗶𝗴𝗻 𝗕𝗮𝘀𝗶𝗰𝘀: 𝗪𝗵𝗮𝘁 𝗶𝘀 𝗖𝗮𝗰𝗵𝗲 𝗜𝗻𝘃𝗮𝗹𝗶𝗱𝗮𝘁𝗶𝗼𝗻? Cache invalidation is the process of removing or updating cached data when it becomes outdated or no longer accurate. "Purge," "refresh," and "ban" are commonly used cache invalidation methods that are frequently used in the application cache, content delivery networks (CDNs), and web proxies. Here's a brief description of a few famous cache invalidation methods: ◇ 𝗣𝘂𝗿𝗴𝗲: The purge method removes cached content for a specific object, URL, or a set of URLs. It's typically used when there is an update or change to the content and the cached version is no longer valid. When a purge request is received, the cached content is immediately removed, and the next request for the content will be served directly from the origin server. ◇ 𝗥𝗲𝗳𝗿𝗲𝘀𝗵: Fetches requested content from the origin server, even if cached content is available. When a refresh request is received, the cached content is updated with the latest version from the origin server, ensuring that the content is up-to-date. Unlike a purge, a refresh request doesn't remove the existing cached content; instead, it updates it with the latest version. ◇ 𝗕𝗮𝗻: The ban method invalidates cached content based on specific criteria, such as a URL pattern or header. When a ban request is received, any cached content that matches the specified criteria is immediately removed, and subsequent requests for the content will be served directly from the origin server. ◇ 𝗧𝗶𝗺𝗲-𝘁𝗼-𝗹𝗶𝘃𝗲 (𝗧𝗧𝗟) 𝗲𝘅𝗽𝗶𝗿𝗮𝘁𝗶𝗼𝗻: This method involves setting a time-to-live value for cached content, after which the content is considered stale and must be refreshed. When a request is received for the content, the cache checks the time-to-live value and serves the cached content only if the value hasn't expired. If the value has expired, the cache fetches the latest version of the content from the origin server and caches it. ◇ 𝗦𝘁𝗮𝗹𝗲-𝘄𝗵𝗶𝗹𝗲-𝗿𝗲𝘃𝗮𝗹𝗶𝗱𝗮𝘁𝗲: This method is used in web browsers and CDNs to serve stale content from the cache while the content is being updated in the background. When a request is received for a piece of content, the cached version is immediately served to the user, and an asynchronous request is made to the origin server to fetch the latest version of the content. Once the latest version is available, the cached version is updated. This method ensures that the user is always served content quickly, even if the cached version is slightly outdated.

2

🚀 Dockerfile vs. Docker Compose: Understanding the Differences 🐳 In containerized development, Dockerfile and Docker Compose play crucial roles, but they serve different purposes. Let’s break down the differences and see when to use each. 📄 Dockerfile: Purpose: Defines how to build a Docker image. Contents: Includes instructions to install dependencies, copy files, set environment variables, and configure the container. Use Case: Ideal when you need to create a consistent, portable environment for a single application or service. Example: Building a Node.js app image with specific libraries and configurations. Key Features: Layer Caching: Efficient builds by caching layers that don’t change. Small Footprint: Helps create lightweight, self-contained images. 🔗 Docker Compose: Purpose: Orchestrates multi-container Docker applications. Contents: A YAML file that defines services, networks, and volumes for a multi-container setup. Use Case: Best when managing complex applications with multiple interconnected services (e.g., web server, database, cache). Example: Deploying a full-stack app with a React frontend, Node.js backend, and MongoDB database. Key Features: Volumes: Persist data outside containers to maintain state across restarts. Networks: Easily manage communication between services. Environment Management: Quickly switch between environments (development, testing, production) using different Compose files. 🛠 When to Use Each: Use Dockerfile when: You need to build a standalone image. Your application is a single service or microservice. You want to ensure consistency across different environments by building the exact same image. Use Docker Compose when: Your application requires multiple services that need to be orchestrated together. You want to streamline development and testing with a single command to spin up your entire environment. You need to manage shared data using volumes or define complex networking between containers. Understanding these tools’ roles will help you containerize and manage your applications more effectively! 💡 #Docker #DevOps #Containerization #SoftwareEngineering #FullStackDevelopment

4

📓 JavaScript Interview Questions and Answers JavaScript Learning Roadmap: From Beginner to Pro. 💡 JavaScript Roadmap: 1. Learn the Basics: - Get familiar with variables, data types, loops, and functions. - Understand DOM Manipulation to interact with web pages. - Study Event Handling and how user interactions trigger actions. 2. ES6+ Features: - Master new JavaScript features like let/const, arrow functions, template literals, and destructuring. - Learn about modules and import/export to organize your code. 3. Deep Dive into Functions: - Understand higher-order functions, callbacks, and closures. - Get comfortable with async programming, including promises and async/await. 4. Understand JavaScript in the Browser: - Study Browser APIs (like Fetch, LocalStorage, etc.) for interactive web apps. - Learn about Cross-Origin Resource Sharing (CORS) and how it affects web applications. 5. JavaScript Frameworks/Libraries: - Learn a popular library like React or frameworks like Vue.js or Angular to build dynamic UIs. - Understand how state management works (Redux, Vuex). 6. Build and Deploy Projects: - Build projects like a To-Do App, Weather App, or E-commerce Site to apply your skills. - Deploy your projects using platforms like Netlify, Vercel, or Heroku. 7. Master Asynchronous JavaScript​: - Understand AJAX, APIs, and how to make HTTP requests. - Work with real-time data using WebSockets and API integrations. 8. Version Control with Git: - Learn how to use Git for version control and collaborate with other developers using GitHub. 9. Advanced JavaScript Concepts: - Study prototypes, inheritance, and this keyword. - Learn about closures, event loops, and hoisting for deeper JavaScript knowledge. 10. Testing and Debugging: - Master unit testing using frameworks like Jest or Mocha. - Practice debugging with browser tools and catching errors. 🎯 Bonus: - Keep building side projects and contribute to open-source. - Stay updated with the latest JavaScript trends and features (e.g., ES2023+). 🔍 Explore more with Devkant Bhagat for Web Development, Programming Tips & Tricks. 👍 𝗟𝗶𝗸𝗲 if you found it helpful! 🔁 𝗥𝗲𝗽𝗼𝘀𝘁 with your network! 🔖 𝗦𝗮𝘃𝗲 for future use! 📤 𝗦𝗲𝗻𝗱 to your connections! 💬 𝗖𝗼𝗺𝗺𝗲𝗻𝘁 your thoughts below! credit: respected owner #JavaScript #WebDevelopment #Coding #Devkantbhagat #Programming #FrontendDevelopment #JavaScriptDeveloper #TechCareers

134

24 commentaires

Top 5 TypeScript courses for Beginners 1. Understanding Typescript: https://bit.ly/3MbTIIN 2. Typescript: The Complete Developer's Guide: https://bit.ly/3Ngqnhu 3. Typescript Masterclass & FREE E-Book: https://bit.ly/3t6MkHZ 4. Introduction to TypeScript Development: https://bit.ly/3zfnPfw

2

Spring Boot Docker Compose Support : Local Development Made Simple https://lnkd.in/exEtmxYy #springboot #docker #dockercompose

40

🔔 SQL Tips : Do you know the different types of indexes in SQL ? #sql #csharp #dotnet

35

2 commentaires

5 Best Courses to learn Apache Kafka 1. Learn Apache Kafka - https://bit.ly/3GpfeH6 2. Kafka Streams - https://bit.ly/35UYPO7 3. Kafka for beginners - https://bit.ly/3LoMCS6 4. Kafka Cluster Setup - https://bit.ly/34x56yJ 5. Getting Started with Kafka - https://bit.ly/3osGIFM

11

5 Best Courses to learn Apache Kafka 1. Learn Apache Kafka - https://bit.ly/3GpfeH6 2. Kafka Streams - https://bit.ly/35UYPO7 3. Kafka for beginners - https://bit.ly/3LoMCS6 4. Kafka Cluster Setup - https://bit.ly/34x56yJ 5. Getting Started with Kafka - https://bit.ly/3osGIFM

11

𝐒𝐡𝐚𝐫𝐢𝐧𝐠 𝐦𝐲 𝐝𝐞𝐭𝐚𝐢𝐥𝐞𝐝 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰 𝐄𝐱𝐩𝐞𝐫𝐢𝐞𝐧𝐜𝐞 𝐚𝐬 𝐚 𝐁𝐚𝐜𝐤𝐞𝐧𝐝 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐞𝐫 𝐚𝐭 𝐏𝐫𝐨𝐝𝐮𝐜𝐭 𝐁𝐚𝐬𝐞𝐝 𝐂𝐨𝐦𝐩𝐚𝐧𝐲 -> Domain: Backend [ java, Microservices, SpringBoot, Hibernate, javaEE et, Redis... ] Here's a complete breakdown of my journey: ✅𝐅𝐢𝐫𝐬𝐭 𝐑𝐨𝐮𝐧𝐝 - 𝐎𝐍𝐋𝐈𝐍𝐄 𝐓𝐄𝐒𝐓: 𝟏 𝐡𝐫 Online test was divided into two sections: 📍First Section contains 10 technical MCQs, belonging to OOPS, OS, DBMS, Networks, and SQL 📍Second Section contains 2 coding questions of medium-hard level. 𝐎𝐧𝐬𝐢𝐭𝐞 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰𝐬: After clearing the online test, I progressed to the onsite interviews, which consisted of 3 rounds. ✅𝐓𝐞𝐜𝐡𝐧𝐢𝐜𝐚𝐥 𝐑𝐨𝐮𝐧𝐝 𝟏: [𝐌𝐄𝐃𝐈𝐔𝐌] 𝟏𝐡𝐫 📍DSA question a) Given a stream of stocks, given that find the max value of stock for any given duration window. The window can be from extreme ends of time frames. 📍DSA question b) Implement stack in java OOPs questions with a real-life example 📍I'd answered them with Brute Force and Optimised solution with time and space complexity. ✅𝐓𝐞𝐜𝐡𝐧𝐢𝐜𝐚𝐥 𝐑𝐨𝐮𝐧𝐝 𝟐: [𝐌𝐄𝐃𝐈𝐔𝐌 - 𝐇𝐀𝐑𝐃] 𝟏𝐡𝐫 𝟑𝟎 𝐦𝐢𝐧𝐬 It was strictly based on my resume and my past projects 📍Project discussion in brief, technology used and why. Why each component design their usage and reason n all. 📍DSA question: Rob houses [leetcode based medium level difficulty] 📍Spring/Hibernate/JPA vs Hibernate/Redis/MultiThreading internal working 📍LinkedHashMap usage vs hashmap usage vs Treemap Usage 📍DI and IoC container in spring boot and  Inheritance in Spring Entity 📍3 Puzzles 📍Graph and Trees Basics. And then Binary Search Tree applications,Operations 📍Collection Framework related Questions 📍If we are choosing any service or logic then he asked about WHY only this and why not anything else. ✅𝐑𝐨𝐮𝐧𝐝 𝟑(𝐇𝐢𝐫𝐢𝐧𝐠 𝐌𝐚𝐧𝐚𝐠𝐞𝐫/𝐇𝐑 𝐑𝐨𝐮𝐧𝐝): 𝟏 𝐡𝐫 📍Git/maven/version control/Jenkins/branching/conflict in merge 📍Testing framework: regression testing, sanity testing, unit testing etc 📍Behavioural question a) A time when you made a mistake. b) A time when you resolved a group conflict (You first talk about the Situation, followed by your Behaviour towards it, concluded by the Impact) 📍Discussion on my college work, asked some leadership questions. All in all we had a very good discussion there. 📍At last the Manager gave honest feedback on areas I should improve regarding the interview but admired me that I was well prepared for the interview. May this be a valuable resource for those gearing up for this year! 🚀 🔽 If you have any kind of questions then comment below I'll try to answer all of them. #interviewexperience #job #hiring

145

23 commentaires

𝐒𝐡𝐚𝐫𝐢𝐧𝐠 𝐦𝐲 𝐝𝐞𝐭𝐚𝐢𝐥𝐞𝐝 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰 𝐄𝐱𝐩𝐞𝐫𝐢𝐞𝐧𝐜𝐞 𝐚𝐬 𝐚 𝐁𝐚𝐜𝐤𝐞𝐧𝐝 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐞𝐫 𝐚𝐭 𝐏𝐫𝐨𝐝𝐮𝐜𝐭 𝐁𝐚𝐬𝐞𝐝 𝐂𝐨𝐦𝐩𝐚𝐧𝐲 -> Domain: Backend [ java, Microservices, SpringBoot, Hibernate, javaEE et, Redis... ] Here's a complete breakdown of my journey: ✅𝐅𝐢𝐫𝐬𝐭 𝐑𝐨𝐮𝐧𝐝 - 𝐎𝐍𝐋𝐈𝐍𝐄 𝐓𝐄𝐒𝐓: 𝟏 𝐡𝐫 Online test was divided into two sections: 📍First Section contains 10 technical MCQs, belonging to OOPS, OS, DBMS, Networks, and SQL 📍Second Section contains 2 coding questions of medium-hard level. 𝐎𝐧𝐬𝐢𝐭𝐞 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰𝐬: After clearing the online test, I progressed to the onsite interviews, which consisted of 3 rounds. ✅𝐓𝐞𝐜𝐡𝐧𝐢𝐜𝐚𝐥 𝐑𝐨𝐮𝐧𝐝 𝟏: [𝐌𝐄𝐃𝐈𝐔𝐌] 𝟏𝐡𝐫 📍DSA question a) Given a stream of stocks, given that find the max value of stock for any given duration window. The window can be from extreme ends of time frames. 📍DSA question b) Implement stack in java OOPs questions with a real-life example 📍I'd answered them with Brute Force and Optimised solution with time and space complexity. ✅𝐓𝐞𝐜𝐡𝐧𝐢𝐜𝐚𝐥 𝐑𝐨𝐮𝐧𝐝 𝟐: [𝐌𝐄𝐃𝐈𝐔𝐌 - 𝐇𝐀𝐑𝐃] 𝟏𝐡𝐫 𝟑𝟎 𝐦𝐢𝐧𝐬 It was strictly based on my resume and my past projects 📍Project discussion in brief, technology used and why. Why each component design their usage and reason n all. 📍DSA question: Rob houses [leetcode based medium level difficulty] 📍Spring/Hibernate/JPA vs Hibernate/Redis/MultiThreading internal working 📍LinkedHashMap usage vs hashmap usage vs Treemap Usage 📍DI and IoC container in spring boot and Inheritance in Spring Entity 📍3 Puzzles 📍Graph and Trees Basics. And then Binary Search Tree applications,Operations 📍Collection Framework related Questions 📍If we are choosing any service or logic then he asked about WHY only this and why not anything else. ✅𝐑𝐨𝐮𝐧𝐝 𝟑(𝐇𝐢𝐫𝐢𝐧𝐠 𝐌𝐚𝐧𝐚𝐠𝐞𝐫/𝐇𝐑 𝐑𝐨𝐮𝐧𝐝): 𝟏 𝐡𝐫 📍Git/maven/version control/Jenkins/branching/conflict in merge 📍Testing framework: regression testing, sanity testing, unit testing etc 📍Behavioural question a) A time when you made a mistake. b) A time when you resolved a group conflict (You first talk about the Situation, followed by your Behaviour towards it, concluded by the Impact) 📍Discussion on my college work, asked some leadership questions. All in all we had a very good discussion there. 📍At last the Manager gave honest feedback on areas I should improve regarding the interview but admired me that I was well prepared for the interview. May this be a valuable resource for those gearing up for this year! 🔽 If you have any kind of questions then comment below I'll try to answer all of them. 𝗝𝗼𝗶𝗻 𝗺𝘆 𝗧𝗲𝗹𝗲𝗴𝗿𝗮𝗺 𝗖𝗵𝗮𝗻𝗻𝗲𝗹 - https://t.me/rani_dhage1 𝐁𝐨𝐨𝐤 1:1 𝐰𝐢𝐭𝐡 𝐦𝐞 - https://lnkd.in/dCpvsVJp #interviewexperience #job #backenddeveloper #java

713

27 commentaires