[면접] 안드로이드 개발자 영어 면접 시 자주 쓰일 수 있는 영단어

출처

ChatGPT

나

---

기술 관련 용어

1. Lifecycle - 앱 컴포넌트의 생명주기 관리, 액티비티/프래그먼트 생명주기 관련 질문에서 사용
   • "Understanding the lifecycle of activities and fragments is essential for managing Android app resources effectively."
2. Architecture - 앱의 구조나 패턴을 설명할 때 (예: MVVM, MVI)
   • "Our team implemented Clean Architecture to make the codebase modular and easily testable."
   • Clean Architecture follows SOLID principles, which reduce coupling, improve testability, and enhance maintainability.
3. Dependency Injection (DI) - Hilt 또는 Dagger를 통한 의존성 주입
   • "Using Dependency Injection with Dagger allowed us to manage dependencies efficiently and improve testability."
   • DI reduces coupling by injecting object references from outside the object.
4. Repository - 데이터를 관리하는 계층, 데이터 접근 패턴 설명 시 사용
   • "The Repository pattern helps us separate data handling logic, making our code more maintainable and scalable."
   • In Clean Architecture, the repository belongs to the data layer
5. Asynchronous / Synchronous - 비동기/동기 처리 (예: Coroutines, RxJava)
   • "We used asynchronous processing with Coroutines to handle network requests without blocking the UI."
   • Asynchronous processing is often used for I/O tasks.
6. Concurrency / Parallelism - 동시성/병렬 처리
   • "Efficient concurrency management allowed our app to handle multiple tasks simultaneously without performance issues."
   • Concurrency appears as multiple tasks being processed at the same time.
   • Parallelism means multiple tasks are actually processed at the same time.
7. ViewModel - Android Architecture Component 중 하나로, UI와 데이터를 연결하는 역할을 설명할 때 사용
   • "The ViewModel in MVVM architecture holds UI data and survives configuration changes like screen rotations."
   • The Android framework provides a ViewModel component.
8. Data Binding / View Binding - 데이터 바인딩 및 뷰 바인딩 관련 설명 시
   • "With View Binding, we avoided null pointer exceptions and reduced boilerplate code in our UI."
   • When using View Binding in a fragment, the View Binding object should be set to null in onDestroyView()
9. Coroutine - 코루틴을 사용한 비동기 작업 관리
   • "Using Coroutines helped simplify asynchronous operations and make the code more readable."
10. Thread / Multithreading - 스레드 처리, 멀티스레딩에 대한 이해도 표현
    • "We implemented multithreading to perform background tasks without affecting the main thread."
11. Garbage Collection (GC) - 메모리 관리 관련 설명 시
    • "To optimize memory usage, we analyzed garbage collection logs and adjusted our code accordingly."
12. Retrofit / API Integration - 네트워크 통신, API 통합 관련 설명
    • "We integrated the server APIs using Retrofit, which simplified network requests and JSON parsing."
13. Testing / Test-driven development (TDD) - 테스트 관련 경험을 말할 때
    • "Our team follows Test-driven development (TDD) to catch bugs early and maintain high code quality."
14. Continuous Integration (CI) / Continuous Deployment (CD) - 지속적 통합 및 배포
    • "With CI/CD pipelines, our app was automatically built, tested, and deployed, reducing manual errors."
15. Gradle - 빌드 시스템 및 의존성 관리
    • "We customized our Gradle build scripts to automate dependency management and improve build efficiency."
16. Permissions / Security - 사용자 권한 및 보안 관리
    • "Ensuring permissions are correctly requested and handled is critical to maintaining app security and user privacy."
17. Jetpack Compose - 최신 UI 구성 라이브러리 설명 시
    • "Using Jetpack Compose allowed us to build UI declaratively, reducing XML layouts and improving development speed."
18. RecyclerView / List Adapter - 리스트형 UI 구성 관련 설명
    • "We used RecyclerView with a custom List Adapter to display large data sets smoothly and efficiently."
19. View Lifecycle - 액티비티/프래그먼트의 생명주기와 관련된 UI 관리
    • "Proper handling of the View Lifecycle in fragments helped prevent memory leaks and crashes."
20. Proguard / R8 - 코드 최적화와 난독화 도구
    • "We used Proguard/R8 to obfuscate and optimize our code, reducing APK size and improving security."
21. Profiling / Performance Optimization - 성능 프로파일링 및 최적화
    • "Performance profiling helped us identify and fix bottlenecks to ensure a smoother user experience."

업무 및 협업 관련 표현

1. Cross-functional Team - 다양한 기능을 가진 팀과 협업
   • "Working in a cross-functional team improved communication and collaboration across development, design, and QA."
2. Stakeholder - 프로젝트 관련자 (기획자, 디자이너 등)
   • "We gathered requirements from all stakeholders to ensure that our product met business and user needs."
3. Milestone - 프로젝트 주요 마일스톤 설정
   • "Each milestone was an opportunity to evaluate our progress and make necessary adjustments to the project plan."
4. Code Review - 코드 리뷰 과정
   • "Our team conducts regular code reviews to maintain code quality and share knowledge."
5. Documentation - 문서화, 코드 설명 및 가이드 작성
   • "Comprehensive documentation helped new developers onboard quickly and understand the project architecture."
6. Refactoring - 코드 구조 개선, 리팩토링
   • "We focused on refactoring legacy code to improve readability and reduce technical debt."
7. Debugging - 디버깅, 오류 해결
   • "Through systematic debugging, we identified the root cause of a performance issue and implemented a fix."
8. Backlog - 작업 리스트, 보통 스프린트 계획 시 사용
   • "Tasks are prioritized in the backlog, allowing us to focus on high-impact features first."
9. Sprint / Agile Development - 애자일 개발 방식에서 사용되는 용어
   • "Using Agile development and two-week sprints, we could quickly adapt to changing requirements."
10. Retrospective - 회고, 프로젝트 종료 후 성과 분석
    • "After each sprint, we held a retrospective to discuss what went well and what could be improved."

소프트 스킬 관련 표현

1. Problem-solving - 문제 해결 능력
   • "Strong problem-solving skills helped me debug complex issues and improve the app's stability."
2. Collaboration / Teamwork - 협업, 팀워크
   • "Effective collaboration with team members enabled us to deliver features on schedule."
3. Communication Skills - 의사소통 능력
   • "Clear communication skills were essential when discussing technical solutions with non-developers."
4. Adaptability - 적응력, 변화에 대한 대처 능력
   • "My adaptability allowed me to quickly learn new tools and adjust to evolving project requirements."
5. Attention to Detail - 꼼꼼함, 디테일에 집중
   • "Attention to detail in code and UI design ensured a polished and error-free user experience."
6. Customer-oriented / User-centric - 사용자 중심의 접근
   • "Our user-centric approach guided design decisions, ensuring the app met customer needs."
7. Ownership - 주도적으로 업무 수행
   • "I take ownership of my tasks, ensuring they are completed efficiently and meet quality standards."
8. Time Management - 시간 관리
   • "Effective time management enabled me to handle multiple tasks and meet tight deadlines."
9. Feedback - 피드백 수용 및 반영
   • "I value feedback from peers and stakeholders to continuously improve and deliver better solutions."
10. Continuous Learning - 지속적인 학습
    • "I believe in continuous learning to keep up with new technologies and enhance my skills."

 

소프트웨어 개발 관련 용어

1. Reliability - 안정성: 소프트웨어가 예상한 대로 일관되게 작동하는 성능을 의미합니다.
   • 예: "Our goal is to ensure high reliability for our application."
2. Maintainability - 유지보수성: 소프트웨어를 쉽게 수정하고 개선할 수 있는 능력을 의미합니다.
   • 예: "We prioritize maintainability to facilitate future updates and bug fixes."
3. Scalability - 확장성: 시스템이 더 많은 부하를 처리할 수 있도록 확장 가능한지 여부를 의미합니다.
   • 예: "The app is designed with scalability in mind to handle increasing user demands."
4. Resilience - 회복력: 장애 발생 시 빠르게 복구하여 시스템이 지속해서 운영될 수 있는 능력.
   • 예: "We focus on resilience to minimize downtime in case of unexpected issues."
5. Efficiency - 효율성: 자원을 최소화하면서 최대의 성능을 낼 수 있는지 여부.
   • 예: "Code efficiency helps improve overall application performance."
6. Flexibility - 유연성: 변경이나 확장 시 시스템이 얼마나 쉽게 적응할 수 있는지.
   • 예: "Our architecture allows for flexibility in feature development."
7. Performance Optimization - 성능 최적화: 시스템의 성능을 최적화하여 높은 응답 속도를 유지하는 것.
   • 예: "We continuously monitor for performance optimization opportunities."
8. Code Quality - 코드 품질: 코드의 가독성, 유지보수성, 그리고 오류 가능성을 최소화하는 것.
   • 예: "Good code quality is essential for maintainability and reliability."