Principal Member of Technical Staff

As a Principal Software Engineer, you will be responsible for helping design, build, test, deploy and operate highly scalable services for Oracle Cloud Infrastructures Operator access division (OCI Bastion). You should be a rock-solid coder, and a distributed systems generalist who can dive deep into any part of the stack and low-level systems and design broad distributed system interactions. Your passion for excellence combined with your experience to be an outstanding technical contributor, also help you mentor more junior engineers. You should be able to work independently and as part of a team in an Agile environment. You should be an expert communicator to both technical and non-technical stakeholders in multiple locations around the globe. You should also be able to manage multiple projects and priorities in a fast-paced environment, be results-driven, and thrive even when faced with ambiguity and uncertainty. Most importantly, you should be a team player, someone who is eager to learn, and willing to do whatever it takes to help the team succeed.

Required Experience

BS or MS degree in Computer Science or equivalent
Minimum 7 years in a software-engineering related position, at least half of which was in an Agile/DevOps environment
5+ years of Java development or OO language
5+ years of experience in building and operating distributed systems
Strong knowledge of microservices, data structures, algorithms, operating systems, and distributed systems.
Solid understanding of relational databases, NoSQL systems, storage, and distributed persistence
Excellent troubleshooting, debugging, and performance tuning skills
Excellent written and verbal communication skills with the ability to present complex information clearly and concisely to all audiences.
Strong knowledge of Linux/Unix fundamentals is highly desirable
Knowledge and working experience in go-lang is highly desirable.

Career Level - IC4

• Builds entire systems & services. A leader on their team. Improves their director s organization in some subset of shared code, engineering practices, ops practices, development process, ownership, hiring, mentoring. May often collaborate closely across teams.
• Writes correct, secure, maintainable, robust code and appropriate tests. Drives design of their features & subsystems. Drives operational readiness & excellence of their features & subsystems. Collaborates on planning and identifying and mitigating risks in their project and on architecture of their system/service.
• Works independently on their project. May occasionally need guidance when working on cross team projects. Seeks input and collaboration when appropriate, e.g., on tradeoffs that may affect customers or business goals.
• Trusted to serve as Tier0 or specialized escalation point for operations events. Serves as primary point of contact for resolving complex operations issues. Develops new metrics and dashboards to improve situational awareness. Leads operational assessments for complex systems ensuring operational issues and potential failure modes are accounted for. Participates in cross - organizational programs like incident reviews, architecture discussion, building cloud regions, standards and best practices for operations, resiliency, and availability.