Sign in Sign up

Interview questions · Engineer

Engineer interview questions

Engineering interviewers look for candidates who combine technical depth with sound judgment about when and how to apply it — they care as much about how you reason through trade-offs as about whether you know the right answer. They want evidence of ownership: engineers who treat the reliability, scalability, and maintainability of systems as personal responsibilities. Strong candidates communicate complex technical decisions clearly to non-technical stakeholders.

Describe a technically complex system you designed from scratch and the key architectural decisions you made.

System design ability predicts how an engineer will perform on ambiguous, high-stakes greenfield work.

Model answerI designed a real-time event ingestion pipeline to process 120,000 IoT sensor events per second with sub-200ms end-to-end latency. I chose Apache Kafka as the message broker for durability and replay capability, Flink for stateful stream processing, and ClickHouse for analytical queries. The key trade-off was Flink's operational complexity versus Spark Streaming's lower throughput — Flink won on latency requirements. The system has run at 99.97% uptime for 18 months and cut alerting lag from 4 minutes to 90 milliseconds.

Tell me about a significant production incident you were involved in resolving. What was your role and what did you learn?

Incident response reveals an engineer's composure, debugging methodology, and post-mortem discipline.

Model answerOur payment service went down during a Black Friday peak, affecting 14,000 transactions per hour. I was on-call lead. I isolated the issue to a database connection pool exhaustion caused by a slow query introduced in a deploy 47 minutes earlier. I rolled back the deploy, increased pool size as a temporary measure, and restored service in 23 minutes. The post-mortem led to mandatory query-plan reviews in our CI pipeline and a 40% reduction in slow-query incidents the following quarter.

How do you approach technical debt? Describe a time you balanced shipping features against addressing debt.

Engineers must navigate business pressure versus code quality; recruiters want principled, pragmatic judgment.

Model answerWe had a monolithic authentication module with no test coverage that was blocking three feature teams. I quantified the drag — approximately 6 engineer-days per sprint lost to workarounds — and presented that as an annualized cost of roughly €180,000. The product manager agreed to a six-week 'strangler-fig' refactor run in parallel with a feature sprint. We extracted auth into a standalone service, added 94% test coverage, and the three downstream teams reported a 35% reduction in integration bugs the following quarter.

How do you ensure the reliability and scalability of a service you own in production?

Ownership of production health is a core engineering expectation; this surfaces SRE thinking and observability practices.

Model answerFor a checkout API serving 8,000 requests per minute, I implemented structured logging with correlation IDs, four golden-signal dashboards (latency, traffic, errors, saturation), and SLO-based alerting with a 99.5% monthly availability target. I also ran quarterly game days — simulated dependency failures — to validate our fallback paths. Over 12 months the service's error budget consumption dropped from 68% to 22%, and we never triggered a user-facing outage.

Describe a time you had to push back on a product or business requirement for technical reasons.

Recruiters want engineers who engage as partners, not order-takers, and who can communicate technical risk clearly.

Model answerA product manager requested a feature requiring a full table scan on a 900-million-row dataset to run on every page load. I modeled the query cost — roughly 800ms at p95 and $4,200 per month in compute — and proposed a pre-aggregated summary table refreshed every 15 minutes, achieving the same UX goal at p95 of 12ms and $180/month. The PM agreed, and the feature shipped on the original deadline with better performance than originally specified.

How do you approach code review, both as a reviewer and as an author?

Code review culture is a proxy for team health, knowledge sharing, and quality standards.

Model answerAs an author I include a PR description with context, the problem being solved, alternatives considered, and a testing strategy — this cuts reviewer turnaround time by roughly half. As a reviewer I use a three-tier framework: correctness first, then maintainability, then style. I make exactly one blocking comment per real concern and use suggestions for everything else. After I introduced this framework to my team of eight, our PR cycle time dropped from 2.4 days to 18 hours.

Tell me about a time you had to learn a new technology or language under time pressure to deliver a project.

Engineering roles frequently demand rapid skill acquisition; recruiters want evidence of learning agility.

Model answerWe won a contract requiring Rust for a safety-critical embedded component, a language none of our five-person team knew. I spent two weeks on hands-on learning using the official Rust book and a small side project, then ran four two-hour internal workshops to upskill the team in parallel with early design work. We shipped a working prototype in week six of an eight-week sprint, and the client's safety review board cited the memory-safety guarantees of our implementation as a differentiator.

How do you collaborate effectively with product managers and designers who have limited technical background?

Cross-functional communication determines how quickly teams ship; recruiters want engineers who bridge the gap.

Model answerI use analogies and cost-benefit framing instead of technical jargon. When explaining why a real-time sync approach would cost three times more than polling, I compared it to the difference between a taxi waiting outside all day versus calling one when needed. That reframe led the PM to choose the polling approach without needing to understand WebSockets. I also schedule a voluntary 30-minute monthly 'under the hood' session for non-engineers on my team, which has measurably shortened our estimation meetings.

Tips for this role

Practise for THIS role

Paste your job offer, pick a recruiter, and run a mock interview with a detailed coaching report.

🎤 Start an interview

Everything you can do

Simulated interview

Practice out loud with an AI recruiter, in real conditions.

7 AI recruiters

From the friendly HR to the tough manager: pick your challenge.

ATS-ready CV

Generate a clean PDF CV that gets past automated filters.

Video interview

Facing a realistic video avatar: also work on your posture and presence.

Coaching report

A score out of 100, your strengths, areas to improve and quotes from your answers.

Personality analysis

Assess your Big Five traits with the IPIP-NEO test and get a summary to share with HR.

CV / job match

Measure how well your CV matches a job before applying.

Cover letter

A tailored cover letter, matched to the job and your CV, ready to send as PDF.

Prep brief

Likely questions, angles to prepare and recent info about the company.

Tailored CV for the offer

Your CV reworked for each offer: skills and experience prioritized to match what the role asks for.

Model answers (STAR)

Your interview questions rewritten as exemplary STAR answers.

Thank-you email

The perfect follow-up message, based on your interview strengths.

Retake & improve

Replay the interview as much as you like: each report tracks your progress.