Real, anonymous reports from people who interviewed for Software Engineer at Occidental Petroleum, newest first and distilled into what to expect across the loop.
Get your personalized Occidental Petroleum Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
After talking with a recruiter, the process moved into multiple online rounds with engineering leaders, peers, and HR—spanning several weeks and feeling more like an effort to understand how I worked with people than to probe deep technical knowledge. Most of the conversations followed a behavioral structure, often framed with STAR-style prompts. I got asked about times I’d struggled, how I handled difficult people, and how I approached personal goals and accomplishments, with a recurring emphasis on safety and being a team player. The overall vibe was friendly and fairly smooth, and the sessions I had were online with engineers and HR rotating in, including a peer interview that helped me better “see” the team and what success looked like for an individual contributor.
One thing that stood out was how little there was in the way of technical questioning. I did hear a small handful of technical questions at one point, but the bulk of the process stayed anchored in collaboration, communication, and personal decision-making. I also had opportunities to ask questions during the process, and everyone I spoke with stayed professional and easy to talk to, even when the panel size grew to several people taking turns. When I measured the timeline, it felt like a deliberate sequence rather than a single conversation—about a week to a couple of weeks between touchpoints—and while I didn’t end up getting an offer, the feedback loop felt respectful and grounded in fit rather than puzzle-solving.
> 1 year
Difficult Positive Houston, TX
My process felt the most intense when it became highly structured and multi-round. It started online, and I moved through several stages with small groups of interviewers, where each round had multiple people asking questions in a fairly organized way. The atmosphere stayed friendly, but it wasn’t casual in the sense of being unstructured—interviewers took notes and seemed focused on confirming the same qualifications from different angles.
I was asked a mix of technical and behavioral questions, and the behavioral prompts were still very STAR-oriented, like they were trying to map my experience to specific competencies. What really raised the difficulty was that I also had to do something beyond a typical conversation: after additional rounds, I had to give a presentation about how I would bring value to the group. That component shifted the tone from “tell us about your past” to “show how you think and what you’d do.” Even though the technical part wasn’t framed as brain-teaser difficulty, it still felt challenging because it required more than just rehearsed stories.
> 1 year
Easy Positive Huston, ID
I had a noticeably calmer interview experience that mostly leaned on straightforward behavioral prompts and light structure. The first contact set up …
> 1 year
Average Positive Houston, TX
I applied for several software engineering–related openings across different Occidental facilities, including production and reservoir roles, since my…
> 1 year
Average Neutral Houston, TX
After applying, I went through an interview process that ended up feeling a bit uneven. I interviewed with two people, and the styles were very differ…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Behavioral Focus
The interview process heavily emphasizes behavioral questions, often using STAR-style prompts to assess how candidates handle challenges, teamwork, and personal goals. Candidates should prepare specific examples that highlight their experiences in these areas.
STARBehavioralTeamwork
Technical Assessment
While technical questions are present, they are generally less intense and more focused on practical application rather than theoretical problem-solving. Candidates should be ready to discuss their technical skills and past projects in detail.
TechnicalPracticalProjects
Structured Interview Process
The interview process is organized into multiple rounds with various interviewers, often involving both HR and engineering staff, which helps assess fit from different perspectives. Candidates can expect a series of structured conversations rather than a single panel interview.
Multi-roundStructuredHR
Presentation Component
Some candidates may be required to give a presentation on how they would add value to the team, which shifts the focus from simply answering questions to demonstrating thought processes and problem-solving abilities. Preparing a clear, concise presentation is advisable.
PresentationValue-addDemonstration
Timeline and Communication
The overall timeline can vary significantly, with some candidates experiencing long gaps between interview stages. Clear communication about timelines and expectations is not always consistent, so candidates should be proactive in seeking updates.
TimelineCommunicationFollow-up
Cultural Fit Emphasis
There is a strong emphasis on cultural fit and personality throughout the interview process, with interviewers looking for candidates who align with the company's values and team dynamics. Candidates should be prepared to discuss their work style and how they contribute to a positive team environment.