Oracle’s software engineers create and deliver the industry-leading technology that powers businesses worldwide. It’s a career path with endless potential for growth, impact, and innovation, and we’re giving you a deep dive into the role at every level. Keep reading to learn what makes a great software engineer and how you can secure the position.
Open to learning

Oracle Architect
What does a good software engineer look like? We spoke with Oracle Architect Jeff Ford to find out. With nearly two decades of experience in the software industry, he’s developed a detailed understanding of success at each level—starting with software engineering internships.
“We look for people who care about learning,” says Jeff. “The best interns are the ones who come in, who want to learn things, who want to talk to people.”
He notes that school and work are very different, so being in a professional setting for the first time can be a challenge. That’s why interns are given training and mentorship to help them navigate the corporate experience.
Interest in learning is a must for entry-level software engineers as well. There isn’t an expectation to know everything, but successful employees are good at asking questions and willing to get better at what they do. The tasks assigned at this level need to get done, so independence and self-awareness are critical.
“Entry-level engineers don’t need to have all the skills, but they should know what skills they have,” Jeff tells us. “They should be able to commit to pieces of work that they are capable of doing, and then they should be able to deliver that work on time. How much you can do isn’t as important as doing the things you said you were going to do. ”
Stepping up
Quality and quantity of code starts to matter more as engineers and developers advance in their career. They’re also given increased responsibility. While lower-level engineers are told what to do and provided with structure to do it, mid-level engineers should be confident prioritizing and breaking down challenges on their own.
“If a manager comes to you and says, ‘I need you to do this, this, and this,’ you have to be able to say to the manager: ‘I can do all of those things, but I can’t do all of them by next Friday,’” explains Jeff.
He suggests asking questions like: Which of those things do I need to get done first and which of those things can be done later? If they all have to be done by that date, who is helping me?
Upper-level software development engineers like Jeff may still be writing code, but it’s rarely their focus. Leadership, vision, and community take center stage. As the head of a service, they are judged on the success of the product rather than on their personal output.
“People skills really matter at the higher levels,” Jeff shares. “You’re expected to be able to talk to other people, to be able to reach out to other teams, and to be able to convince other teams to do things that you know you need for your team to be successful.”
Key qualities in getting hired
Jeff showed us what it means to be a successful development engineer—but what does it take to be hired as one? According to him, there are two key factors that bridge all levels. The first is high-quality code. Strong candidates can write code that not only works but can also be read and understood by others.
“It’s about making sure that your service is useful, and that means you’re careful with your code. It means you’re careful when you read other people’s code. It also means that you’re willing to jump in and figure out what’s going wrong when there’s a problem.”
The second factor is the ability to make co-workers better. There are many ways to demonstrate this, such as mentoring new employees, leading a team book club, or arranging demo days.
“We succeed at Oracle when everybody cares that everybody is succeeding, no matter what level you’re at.”
Stand out at every level
While each engineering and development role is different, there are some general qualities that hiring teams look for at each level. Entry-level candidates should have basic skills, but everything above that can be learned. Typically, hiring managers want to give newcomers a chance to show off their strengths and empower them to grow once they’re on the job.
A past internship is great asset on an entry-level resume and demonstrates a baseline level of skill development. But don’t be discouraged if you haven’t had the opportunity to do one. Classroom and personal projects can speak volumes about your skills and experience, so be sure to highlight them on your resume.
Jeff adds, “You’ll stand out even more if you have links on your resume to public code. Even if a recruiter isn’t sure exactly what the code does, or if it works, the fact that you’ve put yourself out there is a good sign.”
For mid-level candidates, hiring teams scan resumes for more tangible accomplishments. These should be personal achievements, not just projects the candidate has worked on.
“It could be, you know, I fixed a bug that saved our company $500,000. Maybe that was only a couple of weeks of work, but it was really important.”
On the flip side, people who are hiring for upper-level roles want to know about large projects as well as their outcomes. Candidates should also show evidence of strong leadership skills.
“They shouldn’t just say, ‘I built this piece of software.’ They should say why it mattered that they built that piece of software. What challenges were there along the way? How did they solve problems?”
Acing the interview
If you get the opportunity to interview for a developer or engineer position, it’s helpful to know what to expect. The process often includes a technical assessment that involves writing code. Hiring teams aren’t necessarily looking for someone who can find an instant solution to a difficult problem. More often, they look at the way you write—is it good, clean code? Interviewers will also want to know about your process.
“We make sure you have the ability to think about a problem and to discuss a problem because that’s what you’ll be doing at work. You’re not going to be going off and solving everything by yourself.”
Review past projects before your interview, and include as much detail as possible when answering discovery questions. For example, if you are asked about a time you had to fix a bug in code, break down each step from discovery to resolution. The more depth your answer has, the stronger you will come across as a candidate.
At any level, Oracle’s engineering and developer positions offer incredible opportunities for professional success and upward mobility. With so many talented, passionate employees taking on the world’s challenges with code, the sky’s the limit for the future of technology.
Do you want to reach your potential as a software development engineer? Explore our career opportunities and make a global impact with Oracle.