🎯 인프라 엔지니어 영어 면접 단어집
📑 목차
1. 기본 인프라 용어
💡 하드웨어 및 서버
| 영어 | 한국어 | 예문 |
|---|---|---|
| Infrastructure | 인프라 | ”I have experience building infrastructure at scale.” |
| Server | 서버 | ”We have over 100 servers in our production environment.” |
| Data Center | 데이터 센터 | ”Our data center is located in multiple regions.” |
| On-premise | 온프레미스 | ”We’re migrating from on-premise to the cloud.” |
| Virtual Machine (VM) | 가상 머신 | ”I use VMs for development environments.” |
| Bare Metal | 베어메탈 | ”Bare metal servers offer better performance for our workload.” |
| Scalability | 확장성 | ”Scalability is crucial for our growing user base.” |
| Availability | 가용성 | ”We aim for 99.99% availability.” |
| Reliability | 신뢰성 | ”System reliability is our top priority.” |
| Uptime | 가동 시간 | ”Our system maintains 99.9% uptime.” |
| Downtime | 다운타임 | ”We experienced significant downtime last week.” |
| Redundancy | 중복성 | ”Redundancy ensures system availability during failures.” |
| High Availability (HA) | 고가용성 | ”We implemented High Availability architecture.” |
| Disaster Recovery (DR) | 재해 복구 | ”Disaster Recovery planning is essential.” |
| Load Balancer | 로드 밸런서 | ”The load balancer distributes traffic across servers.” |
| Reverse Proxy | 리버스 프록시 | ”Nginx acts as a reverse proxy for our application.” |
💡 운영체제
| 영어 | 한국어 | 예문 |
|---|---|---|
| Operating System (OS) | 운영체제 | ”I’m proficient in Linux operating systems.” |
| Linux | 리눅스 | ”I have extensive experience with Linux administration.” |
| Kernel | 커널 | ”The kernel manages system resources.” |
| Process | 프로세스 | ”We need to monitor running processes.” |
| Thread | 스레드 | ”Each thread executes independently.” |
| Daemon | 데몬 | ”The daemon runs in the background.” |
| Service | 서비스 | ”We need to restart the service.” |
| Systemd | 시스템드 | ”We use systemd for service management.” |
2. 클라우드 관련
💡 클라우드 기본
| 영어 | 한국어 | 예문 |
|---|---|---|
| Cloud Computing | 클라우드 컴퓨팅 | ”I specialize in cloud computing.” |
| Public Cloud | 퍼블릭 클라우드 | ”We use public cloud services like AWS.” |
| Private Cloud | 프라이빗 클라우드 | ”We maintain our own private cloud.” |
| Hybrid Cloud | 하이브리드 클라우드 | ”Our hybrid cloud architecture combines both.” |
| Multi-cloud | 멀티 클라우드 | ”We adopt a multi-cloud strategy.” |
| IaaS (Infrastructure as a Service) | 인프라형 서비스 | ”AWS EC2 is an IaaS offering.” |
| PaaS (Platform as a Service) | 플랫폼형 서비스 | ”We use Heroku as our PaaS.” |
| SaaS (Software as a Service) | 소프트웨어형 서비스 | ”Gmail is a popular SaaS example.” |
| Serverless | 서버리스 | ”We implemented our API using serverless functions.” |
| Auto Scaling | 오토 스케일링 | ”Auto scaling handles traffic spikes automatically.” |
| Elastic | 탄력적 | ”Our infrastructure is elastic and adapts to demand.” |
💡 AWS 관련
| 영어 | 한국어 | 예문 |
|---|---|---|
| EC2 (Elastic Compute Cloud) | EC2 | ”I manage EC2 instances for our web servers.” |
| S3 (Simple Storage Service) | S3 | ”We store static assets in S3.” |
| RDS (Relational Database Service) | RDS | ”Our database runs on RDS.” |
| VPC (Virtual Private Cloud) | VPC | ”We isolated resources in a VPC.” |
| Subnet | 서브넷 | ”We divided our VPC into multiple subnets.” |
| Security Group | 보안 그룹 | ”Security groups control inbound and outbound traffic.” |
| IAM (Identity and Access Management) | IAM | ”We use IAM for access control.” |
| EKS (Elastic Kubernetes Service) | EKS | ”We run Kubernetes on EKS.” |
| Lambda | 람다 | ”We use Lambda for event-driven processing.” |
| CloudWatch | 클라우드워치 | ”We monitor metrics with CloudWatch.” |
| Route 53 | 라우트 53 | ”Our DNS is managed by Route 53.” |
| CloudFront | 클라우드프론트 | ”CloudFront delivers content globally with low latency.” |
💡 GCP 관련
| 영어 | 한국어 | 예문 |
|---|---|---|
| Compute Engine | 컴퓨트 엔진 | ”We use Compute Engine for our VMs.” |
| Cloud Storage | 클라우드 스토리지 | ”Objects are stored in Cloud Storage.” |
| Cloud SQL | 클라우드 SQL | ”Our database is managed by Cloud SQL.” |
| GKE (Google Kubernetes Engine) | GKE | ”We deploy to GKE for Kubernetes management.” |
| VPC Network | VPC 네트워크 | ”Our VPC Network provides private connectivity.” |
| Cloud Run | 클라우드 런 | ”We use Cloud Run for serverless containers.” |
| Cloud Functions | 클라우드 함수스 | ”Event-driven logic runs on Cloud Functions.” |
3. 컨테이너/쿠버네티스
💡 컨테이너 기본
| 영어 | 한국어 | 예문 |
|---|---|---|
| Container | 컨테이너 | ”We package applications in containers.” |
| Docker | 도커 | ”I’m proficient in Docker.” |
| Image | 이미지 | ”We build Docker images for deployment.” |
| Container Registry | 컨테이너 레지스트리 | ”We push images to the container registry.” |
| Orchestration | 오케스트레이션 | ”Orchestration manages container lifecycle.” |
💡 쿠버네티스 기본
| 영어 | 한국어 | 예문 |
|---|---|---|
| Kubernetes | 쿠버네티스 | ”I have 3 years of Kubernetes experience.” |
| K8s | K8s (쿠버네티스 약어) | “I deploy to K8s clusters daily.” |
| Cluster | 클러스터 | ”We have a production cluster with 10 nodes.” |
| Node | 노드 | ”Each node runs multiple pods.” |
| Pod | 포드 | ”The application runs in a pod.” |
| Deployment | 디플로이먼트 | ”I manage deployments using Deployment resources.” |
| Service | 서비스 | ”The Service exposes pods to the network.” |
| Ingress | 인그레스 | ”Ingress manages external access to services.” |
| ConfigMap | 컨피그맵 | ”We store configuration in ConfigMaps.” |
| Secret | 시크릿 | ”Sensitive data is stored in Secrets.” |
| Namespace | 네임스페이스 | ”We separate environments using namespaces.” |
| Persistent Volume (PV) | 퍼시스턴트 볼륨 | ”Persistent volumes provide storage.” |
| Persistent Volume Claim (PVC) | 퍼시스턴트 볼륨 클레임 | ”Pods request storage through PVCs.” |
💡 쿠버네티스 고급
| 영어 | 한국어 | 예문 |
|---|---|---|
| ReplicaSet | 레플리카셋 | ”ReplicaSets maintain pod replicas.” |
| StatefulSet | 스테이트풀셋 | ”We use StatefulSets for stateful applications.” |
| DaemonSet | 데몬셋 | ”DaemonSets run one pod per node.” |
| Job | 잡 | ”Jobs run tasks to completion.” |
| CronJob | 크론잡 | ”CronJobs schedule periodic tasks.” |
| Horizontal Pod Autoscaler (HPA) | HPA | ”HPA automatically scales pods.” |
| Vertical Pod Autoscaler (VPA) | VPA | ”VPA adjusts pod resource requests.” |
| Helm | 헬름 | ”We use Helm for package management.” |
| Helm Chart | 헬름 차트 | ”We maintain Helm charts for our applications.” |
4. 네트워크
💡 네트워크 기본
| 영어 | 한국어 | 예문 |
|---|---|---|
| Network | 네트워크 | ”I troubleshoot network issues.” |
| IP Address | IP 주소 | ”The server’s IP address changed.” |
| Subnet Mask | 서브넷 마스크 | ”We configured the subnet mask correctly.” |
| Gateway | 게이트웨이 | ”Traffic passes through the gateway.” |
| DNS (Domain Name System) | DNS | ”We have DNS resolution issues.” |
| DHCP (Dynamic Host Configuration Protocol) | DHCP | ”DHCP assigns IP addresses automatically.” |
| VLAN (Virtual LAN) | VLAN | ”We separate departments using VLANs.” |
| VPN (Virtual Private Network) | VPN | ”We connect to our network via VPN.” |
| Firewall | 방화벽 | ”The firewall blocked the connection.” |
| NAT (Network Address Translation) | NAT | ”NAT translates private IPs to public IPs.” |
💡 네트워크 프로토콜
| 영어 | 한국어 | 예문 |
|---|---|---|
| TCP/IP | TCP/IP | ”The application uses TCP/IP.” |
| UDP (User Datagram Protocol) | UDP | ”We use UDP for real-time streaming.” |
| HTTP/HTTPS | HTTP/HTTPS | ”The API serves over HTTPS.” |
| SSL/TLS | SSL/TLS | ”We enable TLS encryption.” |
| SSH (Secure Shell) | SSH | ”I connect to servers via SSH.” |
| FTP (File Transfer Protocol) | FTP | ”We use SFTP for secure file transfer.” |
| WebSocket | 웹소켓 | ”Real-time updates use WebSocket.” |
💡 네트워크 고급
| 영어 | 한국어 | 예문 |
|---|---|---|
| Latency | 지연 시간 | ”We reduced latency by using CDNs.” |
| Throughput | 처리량 | ”The system achieves high throughput.” |
| Bandwidth | 대역폭 | ”We need more bandwidth for the service.” |
| Packet Loss | 패킷 손실 | ”We’re experiencing packet loss.” |
| Jitter | 지터 | ”Jitter affects voice quality.” |
| Routing | 라우팅 | ”Routing determines packet paths.” |
| Switch | 스위치 | ”The network switch failed.” |
| Router | 라우터 | ”We upgraded the router firmware.” |
| CDN (Content Delivery Network) | CDN | ”We use a CDN for global content delivery.” |
| Load Balancing | 로드 밸런싱 | ”Load balancing distributes traffic evenly.” |
5. 보안
💡 보안 기본
| 영어 | 한국어 | 예문 |
|---|---|---|
| Security | 보안 | ”Security is our top priority.” |
| Authentication | 인증 | ”We implement multi-factor authentication.” |
| Authorization | 권한 부여 | ”Authorization controls access to resources.” |
| Encryption | 암호화 | ”All data is encrypted at rest and in transit.” |
| Decryption | 복호화 | ”The key handles decryption.” |
| SSL/TLS Certificate | SSL/TLS 인증서 | ”We renewed our SSL certificate.” |
| Private Key | 개인 키 | ”The private key must be kept secure.” |
| Public Key | 공개 키 | ”We share the public key with clients.” |
| Hashing | 해싱 | ”Passwords are stored using hashing.” |
| Salt | 솔트 | ”We add a salt to password hashes.” |
| Token | 토큰 | ”Users authenticate with JWT tokens.” |
| Session | 세션 | ”We manage user sessions securely.” |
| Cookie | 쿠키 | ”The cookie contains the session ID.” |
💡 보안 고급
| 영어 | 한국어 | 예문 |
|---|---|---|
| Vulnerability | 취약점 | ”We fixed a critical vulnerability.” |
| Patch | 패치 | ”We applied security patches.” |
| Intrusion Detection System (IDS) | 침입 탐지 시스템 | ”IDS monitors suspicious activity.” |
| Intrusion Prevention System (IPS) | 침입 방지 시스템 | ”IPS blocks malicious traffic.” |
| DDoS (Distributed Denial of Service) | DDoS | ”We mitigated a DDoS attack.” |
| Penetration Testing | 침투 테스트 | ”We conduct annual penetration testing.” |
| Security Audit | 보안 감사 | ”The security audit revealed issues.” |
| Compliance | 컴플라이언스 | ”We maintain compliance with regulations.” |
| GDPR | GDPR | ”We comply with GDPR requirements.” |
| SOC 2 | SOC 2 | ”We’re working on SOC 2 certification.” |
6. 모니터링/운영
💡 모니터링 기본
| 영어 | 한국어 | 예문 |
|---|---|---|
| Monitoring | 모니터링 | ”We use comprehensive monitoring tools.” |
| Logging | 로깅 | ”Logging helps us debug issues.” |
| Metrics | 메트릭 | ”We track key metrics for performance.” |
| Alert | 알림 | ”We receive alerts for critical issues.” |
| Dashboard | 대시보드 | ”The dashboard shows real-time metrics.” |
| Uptime Monitor | 가동 시간 모니터 | ”Uptime monitors track service availability.” |
| Performance Monitoring | 성능 모니터링 | ”Performance monitoring identifies bottlenecks.” |
💡 도구 및 기술
| 영어 | 한국어 | 예문 |
|---|---|---|
| Prometheus | 프로메테우스 | ”We use Prometheus for metrics collection.” |
| Grafana | 그라파나 | ”We visualize data in Grafana dashboards.” |
| ELK Stack (Elasticsearch, Logstash, Kibana) | ELK 스택 | ”We use the ELK stack for log analysis.” |
| Loki | 로키 | ”Loki provides lightweight log aggregation.” |
| Jaeger | 제이거 | ”We trace requests with Jaeger.” |
| Zipkin | 집킨 | ”Distributed tracing uses Zipkin.” |
| New Relic | 뉴렐릭 | ”We monitor APM with New Relic.” |
| Datadog | 데이터독 | ”Datadog provides infrastructure monitoring.” |
💡 운영 용어
| 영어 | 한국어 | 예문 |
|---|---|---|
| Deployment | 배포 | ”We have automated deployments.” |
| Release | 릴리스 | ”The new release includes bug fixes.” |
| Rollback | 롤백 | ”We performed a rollback after the issue.” |
| Rollout | 롤아웃 | ”We’re doing a gradual rollout.” |
| Canary Deployment | 카나리 배포 | ”Canary deployment tests new versions safely.” |
| Blue-Green Deployment | 블루-그린 배포 | ”We use blue-green deployment for zero downtime.” |
| CI/CD (Continuous Integration/Continuous Deployment) | CI/CD | ”We automated CI/CD pipelines.” |
| Pipeline | 파이프라인 | ”The CI/CD pipeline runs tests automatically.” |
| Build | 빌드 | ”The build failed due to syntax errors.” |
| Test | 테스트 | ”We write automated tests for all code.” |
| Integration Test | 통합 테스트 | ”Integration tests verify component interactions.” |
| Unit Test | 단위 테스트 | ”Unit tests check individual functions.” |
| Code Review | 코드 리뷰 | ”All changes go through code review.” |
| Pull Request (PR) | 풀 리퀘스트 | ”I submitted a PR for the feature.” |
| Merge Request (MR) | 머지 리퀘스트 | ”The MR was approved and merged.” |
7. 면접 질문 및 답변 템플릿
💡 자기소개
Q: “Tell me about yourself.”
답변 예시
“Hello, I’m [이름]. I have [숫자] years of experience in infrastructure engineering. I specialize in [기술 스택, 예: Kubernetes, AWS, Terraform]. In my previous role, I [주요 성과]. I’m passionate about [관심 분야] and I’m excited about this opportunity because [지원 동기].”
Q: “Walk me through your resume.”
답변 예시
“I started my career at [회사명] as a [직책], where I learned [주요 배움]. Then I moved to [회사명] as a [직책], where I led [프로젝트]. Most recently, I worked at [회사명] as a [직책], where I [마지막 역할의 주요 업무].”
💡 기술 질문
Q: “What is your experience with cloud platforms?”
답변 예시
“I have extensive experience with AWS and GCP. I’ve designed and managed [구체적인 예시]. I’m certified in [자격증] and I’m familiar with various cloud services including EC2, S3, VPC, and Kubernetes.”
Q: “How do you handle infrastructure as code?”
답변 예시
“I use Terraform for IaC. I follow best practices like module reusability, state management, and version control. I’ve implemented [구체적인 예시] using Terraform, which improved [개선된 점].”
Q: “How do you approach debugging production issues?”
답변 예시
“When debugging production issues, I first gather information from logs and metrics. I check [확인 항목]. Then I reproduce the issue in a test environment. Finally, I implement and test the fix before deploying.”
Q: “How do you ensure high availability?”
답변 예시
“I ensure high availability through redundancy, load balancing, and failover mechanisms. I implement [구체적인 방법]. I also regularly test disaster recovery procedures.”
💡 행동 질문 (Behavioral Questions)
Q: “Tell me about a time you faced a critical incident. How did you handle it?”
답변 예시 (STAR 방식)
- Situation (상황): “Last year, our database failed during peak traffic.”
- Task (과제): “I needed to restore service quickly.”
- Action (행동): “I identified the issue, implemented a failover to the replica, and communicated with stakeholders.”
- Result (결과): “Service was restored within 15 minutes, and we implemented preventive measures.”
Q: “Describe a situation where you had to work with a difficult team member.”
답변 예시
“I had a colleague who disagreed with my technical approach. I scheduled a meeting to understand their perspective. We discussed the pros and cons of each approach and eventually agreed on a hybrid solution. This experience taught me the importance of communication and collaboration.”
Q: “How do you stay updated with new technologies?”
답변 예시
“I follow tech blogs, attend webinars, and participate in online communities. I also take online courses and work on personal projects to learn new technologies. Recently, I’ve been learning [최근 학습한 기술].”
💡 회사 질문 (Questions for the Interviewer)
기술 관련:
- “What does your current infrastructure look like?”
- “What challenges are you currently facing with your infrastructure?”
- “How do you handle deployments and releases?”
- “What monitoring and logging tools do you use?”
- “What is your approach to security and compliance?”
팀/문화 관련:
- “How is the infrastructure team structured?”
- “What is the on-call rotation like?”
- “How does the team handle incidents and outages?”
- “What opportunities are there for learning and growth?”
- “How does the team collaborate with development teams?“
8. 자주 쓰이는 표현
💡 면접 중 사용하기 좋은 표현
| 표현 | 의미 | 예시 |
|---|---|---|
| ”That’s a great question.” | 좋은 질문이네요 | 질문을 듣고 시간을 벌 때 유용 |
| ”Let me think about that for a moment.” | 잠시 생각해볼게요 | 생각할 시간이 필요할 때 |
| ”Based on my experience…” | 제 경험에 따르면… | 경험을 바탕으로 답할 때 |
| ”In my previous role…” | 이전 직무에서는… | 과거 경험을 설명할 때 |
| ”I’m not entirely sure, but…” | 확실히는 모르겠지만… | 모르는 질문일 때 솔직하게 |
| ”From my perspective…” | 제 관점에서는… | 자신의 의견을 말할 때 |
| ”I believe that…” | 저는 ~라고 생각합니다 | 의견을 표현할 때 |
| ”I’ve found that…” | ~라고 경험했습니다 | 경험을 공유할 때 |
| ”To give you an example…” | 예를 들어보면… | 구체적인 예시를 들 때 |
| ”In other words…” | 다시 말하면… | 설명을 다시 할 때 |
| ”What I mean is…” | 제 말은… 의미입니다 | 설명을 명확히 할 때 |
| ”Let me clarify…” | 명확히 말씀드리면… | 설명을 다듬을 때 |
💡 긍정적인 표현
| 표현 | 의미 |
|---|---|
| ”I’m excited about…” | ~에 대해 기대됩니다 |
| ”I’m passionate about…” | ~에 열정적입니다 |
| ”I’m confident in my ability to…” | ~할 수 있다고 자신합니다 |
| ”I enjoy working on…” | ~작업하는 것을 즐깁니다 |
| ”I’m proud of…” | ~에 자부심을 느낍니다 |
| ”I’m eager to learn…” | ~배우는 것을 갈망합니다 |
💡 모호한 표현 피하기
| 피해야 할 표현 | 대체 표현 |
|---|---|
| ”I think…" | "Based on my data/experience…" |
| "I guess…" | "I believe that…" |
| "Maybe…" | "It’s likely that…" |
| "Sort of…" | "Specifically…" |
| "I’m not sure…" | "I don’t have that information, but I can find out.” |
🎯 실전 팁
준비 팁
- 단어 카드 만들기: 중요한 단어를 카드로 만들어 매일 복습하세요
- 롤플레이: 친구나 동료와 영어로 모의 면접을 연습하세요
- 기술 블로그 읽기: 영어 기술 블로그를 읽으며 용어에 익숙해지세요
- STAR 방식 연습: 상황-과제-행동-결과 구조로 답변을 준비하세요
- 녹음하기: 자신의 답변을 녹음해서 들어보며 발음과 속도를 조절하세요
주의사항
- 너무 빨리 말하지 마세요. 천천히 명확하게 말하는 것이 좋습니다
- 모르는 질문이면 솔직하게 인정하고 관련 경험을 말하세요
- 전문 용어를 남용하지 말고 설명을 곁들이세요
- 질문을 잘 못 들었으면 다시 물어보세요
면접 당일 팁
- 물 한 잔 준비하기 (목이 마르면 말하기 어려움)
- 노트북과 펜 준비하기 (중요한 내용 메모용)
- 인터넷 연결 안정성 확인하기
- 조명과 배경 확인하기 (비대면 면접의 경우)
📚 추가 학습 자료
마지막 조언
인프라 엔지니어 면접에서 가장 중요한 것은 기술 용어를 아는 것도 있지만, 자신의 경험과 지식을 명확하고 자신감 있게 전달하는 것입니다. 이 단어집을 참고하면서 자신만의 스토리를 만들어보세요!