Behavioral
Read this last. Keep answers to 2-3 minutes. End with the result, not the action.
STAR Framework
| Step | What to answer | Tips |
|---|---|---|
| Situation | What was the context / problem? | 1-2 sentences, no fluff |
| Task | What was your specific responsibility? | Be precise about your role |
| Action | What exactly did you do? | This is the meat — be specific |
| Result | What was the measurable outcome? | Quantify where possible |
Most Likely Questions
Prepare a STAR story for each of these before the interview:
About your experience:
- Tell me about yourself.
- Walk me through your most recent project.
- What is the most complex system you’ve built or maintained?
Challenges and growth:
- What’s the biggest technical challenge you’ve faced?
- Tell me about a time you had a production issue. How did you handle it?
- Tell me about a time you failed. What did you learn?
- Tell me about a time you had to learn a new technology quickly.
Collaboration:
- Tell me about a time you disagreed with a team member or decision. How did you handle it?
- Tell me about a time you dealt with a difficult stakeholder.
- Have you ever had a code review disagreement? How did you resolve it?
- Describe a time you mentored a junior engineer.
Prioritization and delivery:
- How do you prioritize when working on multiple projects?
- Tell me about a time you missed a deadline. What happened?
- How do you handle technical debt vs feature delivery pressure?
Role-specific:
- Why are you leaving your current role?
- Why are you interested in this role/company?
- Where do you see yourself in 3-5 years?
Role-Specific Talking Points
Why are you leaving your current role? → Frame around growth: “I’ve built meaningful systems and I’m proud of the work, but I’m looking for a role where I can work at a broader platform scale and take on more architectural ownership.”
Why are you interested in this role/company? → Reference tech stack alignment (Python, AWS, data engineering at scale), the scope of engineering challenges, and the company’s mission. Show you’ve done research.
Why this role specifically? → Connect your Airflow + ECS + Glue + Python experience directly to the JD requirements. Mention any full-stack or cross-functional aspects as deliberate growth areas.
Experience Deep Dives
These questions test your ability to explain projects from your resume clearly. Use the STAR method.
Explain a proof of concept you independently delivered and the technical decisions behind it. → Be prepared to discuss the problem, the options considered, why you made your tech choices, and the business outcome.
Tell us about a successful automation or open-source project you built (e.g., your Oracle Cloud project)—what problem does it solve, and how is it architected? → Discuss the motivation, the architecture, and the reception/adoption of the project.
Explain your role on a major enterprise project, what technologies you used, and what business value it delivered. → Focus on a large-scale project where you collaborated across teams, explaining the scale and the measurable impact.
Logistics
Salary: “I’m targeting Y based on my experience and market rate for a senior role with this scope.”
Notice period: “My notice period is [X] days per company policy and is non-negotiable. I’m happy to discuss earliest possible start dates and will do everything I can to transition smoothly.”
Counter-offer / still interviewing: “I believe in finding the right fit carefully. I’m actively exploring options to make a thoughtful next career move — not just the fastest one.”
Interview Dos and Don’ts
Do:
- Frame everything around growth and opportunity, not complaints
- Quantify results wherever possible ($, %, time saved, scale)
- Pause before answering — it shows thoughtfulness
- Ask clarifying questions in system design rounds before diving in
Don’t:
- Criticize your current employer
- Over-explain the situation at the expense of the result
- Give answers longer than 3 minutes without pausing to check in
- Say “I” for team accomplishments without acknowledging the team