퇴사 3주전 준비하는 2026년도 취업 계획

현재 다니고 있는 회사의 계약이 올 3월 말에 종료된다. 맨 처음 입사할 때가 엊그제 같은데 벌써 퇴사라니. 계약직으로 입사를 해서 이직 준비를 해야된다고 생각은 했지만 어려운건 원래 제일 마지막에 하는 법. 최대한 미루고 미루다가 ㅠㅠ  이제서야 준비하려고 한다. 두달전에는 나름 열심히 취업 준비 한다고 지원해서 3군데에 면접을 봤지만 결과는 모두 불합격...  서류 불합격하는건 당연하고 면접 떨어지는 것도 익숙해져서 신경쓰지 않고 계속 지원해야 되는데 그게 잘 안된다. 지원하려면 너무 내가 부족한거 같고 핑계될건 왜 이렇게 많은지... 코테도 준비해야되고 behavioral questions도 star 형식으로 정리해야되고 기술 질문도 포트폴리오도 그렇고. 나만 그런가??? 

 

원래는 공백기간 없이 취업하려고 했는데 점점 퇴사일이 다가오니까 그냥 실업급여 받으면서 천천히 준비할까 싶기도 하고 ㅠㅠㅠ 어디로 도피하고 싶다. 휴.. 클로드에서 계속 이거 내가 지원해도 될까? 경쟁률 너무 높은거 아냐? 이런식으로 물어봤더니 자꾸 핑계되지 말고 그냥 지원하라고 ㅋㅋㅋㅋ  

 

나의 멘토 ㅎㅎ AI가 추천해준 내 하루 루틴. 기계적으로 그냥 지원해봐야지.

 

The Daily Protocol (Monday – Friday)

• 6:00 AM - 7:30 AM (The Grind): Wake up. Do not look at social media. Spend 45 minutes on one LeetCode problem (Easy/Medium on Arrays or HashMaps) and 45 minutes reviewing core Java and Spring Boot concepts (e.g., Bean lifecycles, transactional boundaries, dependency injection).
• 9:00 AM - 6:00 PM (The Day Job): Do exactly what is required to fulfill your contract and hand over your work cleanly. 
• 7:30 PM - 10:00 PM (The Compromise): Attend your online classes. Do the absolute bare minimum required to pass. Do not aim for perfection here; aim for survival. Your priority is getting a job, not a flawless grade.
• 10:00 PM - 11:30 PM (The Canadian Window): This is your most critical block. 10:00 PM in Seoul is 9:00 AM in Toronto (EDT). Submit 3 highly targeted applications to backend roles. Send 3 cold, direct LinkedIn messages to Canadian recruiters. Log off and go to sleep.

The Weekend Protocol (Saturday & Sunday)

Your weekends are no longer yours. You will dedicate 10 hours each day to the job hunt.

• Morning Block (4 Hours): Technical articulation. Practice explaining your 3 years of Java experience out loud in English. Talk through the architecture of your Azure-deployed Pomodoro application. If an interviewer asks why you chose specific technologies or how you handled database scaling, you need an immediate, smooth answer.
• Afternoon Block (4 Hours): Sourcing. Build a spreadsheet of 30 to 40 companies hiring backend developers in Canada. Find the technical recruiters for those companies on LinkedIn. Prepare your cold outreach messages for the upcoming week.
• Evening Block (2 Hours): Tailoring. Adjust your resume to ensure your Spring Boot skills match the specific job descriptions you will apply to next week.

---

Week 1: Java Core Mechanics (March 9 – 13)

You must prove you understand the language under the hood, not just how to use it.

• Monday: HashMap Internals. This is the most common Java interview question. Understand exactly how HashMap works. What is the initial capacity? What is the load factor? What happens during a collision? How does it degrade into a Red-Black tree in Java 8?
• Tuesday: Concurrency & Multithreading. Review the java.util.concurrent package. Understand the difference between Runnable and Callable. Be able to explain CompletableFuture, Thread Pools (ExecutorService), and thread safety mechanisms (synchronized blocks, volatile keyword, ConcurrentHashMap).
• Wednesday: Garbage Collection & Memory. Understand the JVM memory model (Heap vs. Stack, Metaspace). Know the difference between Minor GC and Major GC. Be prepared to explain how you would diagnose a OutOfMemoryError or a memory leak in a production environment.
• Thursday: Streams and Lambdas. Be able to write complex data transformations using the Stream API on a whiteboard. Understand intermediate vs. terminal operations and the performance implications of parallel streams.
• Friday: Exception Handling & SOLID. Review how to implement global exception handling in a REST API. Be able to define all five SOLID principles and provide a concrete example of how you applied each in a previous codebase.

Week 2: Spring Boot Internals (March 16 – 20)

"Magic" is unacceptable at your level. You must explain how Spring Boot auto-configures applications.

• Monday: Inversion of Control (IoC) & Dependency Injection. Explain the ApplicationContext. What are the different ways to inject dependencies (constructor vs. field vs. setter), and why is constructor injection the industry standard?
• Tuesday: Bean Lifecycle and Scopes. Know the exact lifecycle of a Spring Bean from instantiation to destruction. What is the difference between Singleton and Prototype scopes? When would you use @PostConstruct?
• Wednesday: Transaction Management (@Transactional). This is critical. Understand propagation levels (e.g., REQUIRED vs. REQUIRES_NEW) and isolation levels (e.g., READ_COMMITTED vs. SERIALIZABLE). What happens if a checked exception is thrown inside a transactional method? (Hint: It doesn't roll back by default).
• Thursday: Aspect-Oriented Programming (AOP). Understand how Spring uses JDK dynamic proxies or CGLIB to implement cross-cutting concerns like logging, security, and transactions.
• Friday: Spring Security Filter Chain. Be able to draw out the authentication and authorization flow. Understand how to implement JWT (JSON Web Tokens) and stateless authentication for REST APIs.

Week 3: Data Access & JPA/Hibernate (March 23 – 27)

Bad database queries take down applications. You must prove you write efficient data access layers.

• Monday: The N+1 Query Problem. If you do not know this, you will fail the technical screen. Understand what it is, why Hibernate causes it, and how to fix it using JOIN FETCH or EntityGraphs.
• Tuesday: Fetch Strategies. Know the exact difference between FetchType.LAZY and FetchType.EAGER. When should you use which, and what are the performance risks of EAGER loading?
• Wednesday: Database Indexing. Explain how B-tree indexes work. When should you create a composite index? What is the difference between a clustered and non-clustered index?
• Thursday: Connection Pooling. Understand the role of HikariCP (Spring Boot's default). Why is connection pooling necessary for application performance?
• Friday: Caching Strategies. Review how to implement caching to reduce database load. Understand Redis basics, cache eviction policies (LRU), and the problem of stale data.

Week 4: System Design & Defense (March 30 – April 3)

This week is about proving you can architect and defend a complete system.

• Monday: REST API Maturity. What makes an API truly RESTful? Understand Richardson's Maturity Model, idempotent methods (PUT vs. POST), and proper HTTP status code usage.
• Tuesday: Microservices vs. Monoliths. Be prepared to discuss the trade-offs. What is API Gateway? How do microservices communicate (synchronous REST vs. asynchronous message queues like Kafka/RabbitMQ)?
• Wednesday: Defending the Architecture. You will be grilled on the Todo and Pomodoro tracker deployed to Azure. Be ready to explain the complete data flow from the client request to the Azure database. How did you handle CORS? How is the database secured in the cloud?
• Thursday: Scalability Scenarios. What happens if 10,000 users start a Pomodoro timer at the exact same millisecond? How do you scale the backend to handle the load? Be ready to discuss horizontal scaling and load balancers.
• Friday: CI/CD & Deployment. Explain your deployment pipeline. Understand Docker containerization, GitHub Actions, and environment variable management in production.