Oracle · Primly Community

Oracle frontend engineer interview, 2026, here's what they tested and what surprised me

market_realist · 5 replies

Did the Oracle frontend engineer interview loop earlier this year for a role on one of their cloud dashboard products. Wanted to share because frontend at big enterprise companies often looks really different from frontend at startups and the prep is different too.

Full loop was 4 technical rounds plus one behavioral panel.

Round 1: JavaScript fundamentals. I was expecting React component questions and instead got a deep dive on core JS. Closures, how the event loop works, difference between == and ===, prototypal inheritance, this binding in arrow functions vs regular functions. This felt more like a systems programmer testing JS than a frontend-native interviewer. I'd recommend actually knowing how the engine works, not just React patterns.

Round 2: DOM manipulation and browser APIs. We built a small interactive UI without any frameworks, just vanilla JS. Had to implement infinite scroll behavior from scratch. This round surprised me most. If you've only worked in React for the last 4 years you might struggle here. Brush up on IntersectionObserver, requestAnimationFrame, localStorage vs sessionStorage.

Round 3: React-specific round. This is where you'd expect most of the interview to be but it was only one of four technical rounds. We covered hooks: useEffect cleanup, stale closure issues, when to use useCallback vs useMemo. They also asked about rendering performance, how to avoid unnecessary re-renders, what triggers reconciliation. One question on how you'd handle global state without Redux, so know Context API tradeoffs.

Round 4: system design (frontend focus). Design a component library for an enterprise design system. We talked about API contract design for components, accessibility considerations (WCAG basics), theming with CSS variables vs styled-components, how you'd handle versioning and breaking changes. I liked this round, it felt real.

Behavioral panel. Standard Oracle behavioral stuff, same STAR format as everyone else reports. They asked specifically about working with backend teams to define API contracts, which was relevant to the role.

Comp: I'm in Seattle, mid-level L3 equivalent, offer was around $145k base. Total with stock was around $185k first year.

Honest take: Oracle's frontend bar is higher on fundamentals than I expected. They don't care that much if you know the trendy framework, they want to know if you understand the web platform. That's actually a good sign for the engineering culture.

5 replies

ux_uma

The accessibility question in round 4 is interesting. Did they seem to actually care about it or was it just a checkbox? Asking because a lot of enterprise tech companies say the right things about a11y and then ship inaccessible products.

frontend_fran

Honest answer: felt more like a bar-raiser question to see if I'd thought about it than a deep culture commitment. I mentioned contrast ratios, keyboard nav, ARIA labels, focus management in modals. They seemed satisfied. Whether the actual product team prioritizes it day-to-day I can't say.

market_realist

The vanilla JS DOM round would wreck me. I've been in React-land for 5 years straight. I know how to build UIs but if you asked me to write IntersectionObserver from memory on a shared screen I'd embarrass myself. Good to know before walking into something like this.

sec_sasha

Did XSS or CSP come up at all in any of the frontend rounds? Wondering if they probe on the security side for their cloud dashboard stuff.

frontend_fran

No explicit security questions in my loop but the DOM round covered sanitizing user input when manipulating innerHTML, so kind of. I mentioned XSS when I brought up why I'd avoid innerHTML and use textContent instead. They seemed to like that I raised it without prompting.