Optum SE-1: 2024 On-Campus Interview Account

The candidate-reported on-campus story

One candidate documented a three-round Optum Software Engineer-1 campus process in a GeeksforGeeks post titled "Optum Interview Experience, Software Engineer-1 | On-Campus (3 Rounds)". The source establishes the candidate's reported process, not Optum's office footprint, corporate structure, or a universal fresher intake pattern.

Round 1 was an online assessment. It combined logical and quantitative aptitude, technical MCQs covering operating systems, DBMS, and basic programming, and one DSA problem the candidate described as medium difficulty. The candidate noted that the problem required an optimised solution rather than brute force. The source does not compare this screen with other employers or current cycles.

Round 2 was an HR and behavioral conversation. The interviewer asked about the candidate's motivation for joining Optum, requested a project explanation without technical jargon, and asked how the candidate would teach programming to a young child. These questions support preparation for plain-language communication and structured explanation. The source does not publish the interviewer's scoring rubric or connect the questions to a healthcare-specific competency.

Round 3 was the technical deep-dive. It opened with a self-introduction and resume discussion, moved into OS and DBMS fundamentals, and then presented a DSA question with a narrative wrapper. The candidate also reported C++ data-structure usage, time-complexity questions, and software-engineering practices. Practise extracting constraints from wordy prompts, but do not assume a healthcare or data scenario unless the actual question says so.

The candidate reported receiving an offer. The post does not provide the offer terms, joining timeline, or panel feedback, so the result should not be used to infer selection odds or the reason any stage was cleared.

No CGPA cutoff or package figure was disclosed in this account. The round structure, questions and outcome above reflect one candidate's reported experience for one hiring cycle, and patterns can vary by batch, campus and year. Always cross-check with your college's TPO and the official Optum careers page for the current cycle.

Round-by-round breakdown

The table below summarises the candidate-reported structure. Treat it as a pattern reference, not a guaranteed 2026 template.

A few patterns worth internalising:

• Aptitude appeared in this assessment. Review logical and quantitative reasoning if the current invite confirms the same component.
• DSA appeared in the assessment and technical interview. Practise requirement extraction, brute-force analysis, optimisation, complexity, and tests without inventing a target speed.
• Plain-language explanation was asked directly. Prepare a concise project explanation that removes acronyms and still preserves the problem, your contribution, and the result.
• Story-wrapped problems. The technical DSA question came with a narrative wrapper. Practise extracting the inputs, required output, constraints, and allowed operations before selecting an algorithm.

For the plain-language project prompt, prepare two layers from the same evidence. The first should explain the user's problem, what changed, and your personal contribution without framework names. The second should expose architecture, data flow, failure modes, tests, and trade-offs when the interviewer asks for depth. Both versions must describe the same work. Do not add users, scale, accuracy, or impact numbers that the project cannot support.

For a story-wrapped coding prompt, write down the actual inputs, required output, constraints, and allowed operations before choosing an algorithm. Test the interpretation against the prompt's examples, then state a simple solution and the evidence that motivates optimisation. This method is useful even though the source does not disclose the exact story or problem.

The prep playbook for Optum Software Engineer-1

Use the candidate-reported process as a gap checklist, then follow the current role description and assessment invite where they differ.

Aptitude and core CS MCQs

• The account names logical and quantitative aptitude but does not publish its subtopics. Use the current assessment scope to select concepts, then practise translating each question into variables and checking the result.
• The account names OS, DBMS, basic programming, and C++ data-structure usage. Prepare definitions, mechanisms, examples, and trade-offs for the concepts required by the current role without attributing an invented subtopic list to this interview.

DSA practice

• Practise a direct solution, state its complexity, and then improve it only when the constraints justify doing so. The candidate reported that an optimised solution was expected in Round 1.
• Practice time and space complexity analysis out loud, as the technical round reportedly probed complexity questions directly.

Resume project defence

• Prepare a plain-English explanation for each resume project. Avoid acronyms and framework names unless they are necessary.
• Prepare a technical deep-dive for each project: architecture, your specific contribution, trade-offs, failure modes, and what you would change.
• Prepare an honest answer on why the current Optum role fits you, using only the role description and Optum's own current pages.

Mock interviews

• Run mock behavioral and technical interviews with a peer or senior, using the reported question types as prompts rather than a guaranteed script.
• Record yourself explaining a project in simple terms and review whether a non-CS friend would understand it.
• Practice the "teach programming to a child" style creativity question with a structured response: pick a relatable analogy, break the concept into steps, use a concrete example.

Final review

• Revisit your strongest DSA topics rather than learning new ones.
• Protect enough rest before the assessment to read and calculate carefully.
• Carry a printed resume and a notebook for any in-person component.

Common mistakes and red flags

• Ignoring a disclosed section. The historical assessment included aptitude, but the source does not publish its weight or cutoff.
• Stopping at brute force. The candidate says an optimised solution was expected. State the direct approach, its complexity, and the reason for any improvement without claiming an unpublished scoring consequence.
• Jargon-heavy project explanations. The reported HR round asked the candidate to explain a project without technical jargon. Practise a plain-language version that keeps the real requirement and contribution intact.
• Weak OS and DBMS explanations. Round 3 reportedly went in depth into both. Practise definitions, examples, trade-offs, and follow-up reasoning rather than memorising one-line answers.
• Unprepared self-introduction. Keep it concise and structured around relevant background, projects, and interest in the live role.
• Using stale company claims. Build your motivation answer from the current role description and Optum's own pages, not copied claims about scale, offices, or products.

Real-world data points

• 3 rounds in the candidate-reported on-campus process (per the GeeksforGeeks account, one hiring cycle).
• 1 medium-difficulty DSA problem in Round 1 (candidate-reported, requiring optimized approach).
• 1 LeetCode-style medium DSA problem in Round 3 (candidate-reported, with a story wrapper).
• 2 core CS subjects probed in depth: OS and DBMS (candidate-reported).
• 1 creativity question on teaching programming to a child (candidate-reported).
• No CGPA cutoff or package figure disclosed in the source account.
• Outcome: candidate reported receiving the offer.

Sources & credits

• https://www.geeksforgeeks.org/interview-experiences/optum-interview-experience-software-engineer-1-on-campus-3-rounds/
• https://www.optum.com/careers