<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Arya Rai on Medium]]></title>
        <description><![CDATA[Stories by Arya Rai on Medium]]></description>
        <link>https://medium.com/@awrya?source=rss-55027f2c74cb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ZcCzpNN0nChqoC017aPk4Q.jpeg</url>
            <title>Stories by Arya Rai on Medium</title>
            <link>https://medium.com/@awrya?source=rss-55027f2c74cb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 22:13:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@awrya/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[my UBS internship (on-campus) drive experience (selected!)]]></title>
            <link>https://medium.com/@awrya/my-ubs-internship-on-campus-drive-experience-selected-cdf6c20fc226?source=rss-55027f2c74cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/cdf6c20fc226</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[summer-internships]]></category>
            <category><![CDATA[interview-questions]]></category>
            <category><![CDATA[resume]]></category>
            <category><![CDATA[campus-placements]]></category>
            <dc:creator><![CDATA[Arya Rai]]></dc:creator>
            <pubDate>Thu, 01 Oct 2026 14:18:34 GMT</pubDate>
            <atom:updated>2026-10-02T07:23:38.540Z</atom:updated>
            <content:encoded><![CDATA[<p><em>5 rounds, one very hectic day, and a result I’ll remember for a long time.</em></p><p>A few days ago, I went through the on-campus summer internship recruitment process for <strong>UBS</strong>, and I’m extremely happy to share that I was <strong>selected for the Summer 2027 Intern role!</strong> 🎉</p><p>The entire process was kinda lengthy and honestly a little unpredictable at times. So, I thought I’d document my experience for anyone preparing for an on-campus UBS drive or simply curious about what the process looks like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*FLZsreLY7XgMaE7lK2PQBw.png" /></figure><p>Hi everyone! I’m Arya, a third-year Computer Science student at Banasthali Vidyapith, and I’m incredibly excited to share that I’ve been <strong>selected for the UBS Summer 2027 Internship!</strong> :)))<br>In this article, I’m sharing my experience of the entire process: what each round looked like, the kind of questions I was asked, how I approached them, and a few things I learned along the way.</p><p>Hopefully, this helps anyone preparing for <strong>UBS, on-campus placements, or technical internship drives in general.</strong></p><p>There were <strong>5 rounds in total</strong>:</p><ol><li>Resume Shortlisting</li><li>MCQ + Technical Pen-and-Paper Round</li><li>Group Discussion + Solution Presentation</li><li>Technical Interview</li><li>HR Interview</li></ol><p>Here’s how it went.</p><h3>Round 1: Resume Shortlisting</h3><p>The process started with a Google Form shared by our placement cell where we had to submit our resumes. These details were then forwarded to UBS for shortlisting.</p><h4>Tips for Resume Shortlisting:</h4><ol><li>Keep your resume ATS friendly. Use Latex editors like OverLeaf for the same. You’ll find multiple popular templates there, to begin with.</li><li>Include properly seperated sections for Introduction (keep it brief), Experiences (hackathons etc. if any), Projects, Skills AND very importantly, Extra-Curriculars — something that banks esp UBS realllyyyy care about.</li><li>Use keywords about the tech used in your projects and also include stats wherever possible, eg: selected in the top 10 for xyz out of 3,000+ participants.</li><li>You must be able to defend your projects and stats pretty well. Know your projects inside out.</li><li>If the company explicitly asks you to attach a photograph, you do NOT overthink and just attach it.</li></ol><p>On <strong>7th August</strong>, we received the final shortlist, and <strong>33 students</strong> were selected for the in-person drive scheduled for <strong>13th August</strong>.</p><p>And that’s when the actual process began.</p><h3>Round 2: Pen and Paper (MCQ) Test</h3><p>The first round on the day of the drive was a <strong>pen-and-paper test</strong>.</p><p>We had exactly <strong>30 minutes</strong>.</p><p>There were around <strong>20 MCQs</strong>, covering topics like:</p><ul><li>DSA</li><li>Debugging</li><li>DBMS</li><li>Basic Python</li><li>Dry runs</li><li>Finding the correct output</li></ul><p>Along with these, there were around <strong>2–3 debugging/basic implementation questions</strong>, including some <strong>HashMap/Set-based pseudocode</strong>, and an OS theory question that I unfortunately don’t remember very well.</p><p>There was <strong>no elimination immediately after this round</strong>, so we moved on to the next stage.</p><p>The test was very strictly invigilated. Company officials and college coordinators were continuously monitoring us, so there was absolutely no scope for cheating.</p><p>Personally, the round went pretty well for me. I believe (and like to think that) I was able to solve most of the questions correctly, which gave me some confidence going into the next round.</p><h3>Round 3: Group Discussion</h3><p>The next round was the <strong>GD round</strong>.</p><p>We had already been divided into teams when the shortlist was announced, and all the teams received the <strong>same problem statement</strong>.</p><p>The company officials first explained the problem statement to us. We were then given exactly <strong>one hour</strong> to:</p><ul><li>Understand the problem</li><li>Research</li><li>Brainstorm a solution</li><li>Prepare our approach</li><li>Create a PPT</li><li>At the end of one hour, 15 minutes to present our solution.</li></ul><p>Although it was a <strong>group presentation</strong>, the evaluation was very much individual.</p><p>We were constantly being judged on our:</p><ul><li>Communication</li><li>Presentation skills</li><li>Teamwork</li><li>Collaboration</li><li>Contribution to the solution</li></ul><p>I was fortunate enough to get shortlisted after this round.</p><p>Interestingly, <strong>I was the only person from my team who got shortlisted</strong>, while there were also teams where more than one person got through and even teams where nobody got shortlisted.</p><p>So, even though the solution was prepared and presented as a group, your individual contribution really mattered. Although we had divided tasks within the group, it was really important you understood the entire solution as a whole and not just the part you were presented.</p><p>After the GD, we had around <strong>1.5 hours</strong> before the technical interviews.</p><p>Only <strong>7 students</strong> made it to the technical interview stage.</p><h3>Round 4: Technical Interview</h3><p>This was probably the most interesting round for me.</p><p>And surprisingly, my interview <strong>didn’t start like an interview at all.</strong></p><p>When I entered, the interviewer first asked me about my day, and naturally, I asked him about his.</p><p>I also asked him how he liked our campus and his experience here, and he genuinely seemed to really like it.</p><p>He then asked me:</p><blockquote><strong><em>“Why did you choose Banasthali for your education?”</em></strong></blockquote><p>I spoke about a few things that mattered to me, like the quality of education, safety, and the <strong>five-fold culture</strong> with its focus on academics as well as extracurricular activities.</p><p>That naturally led to questions about my extracurriculars.</p><p>He then started <strong>cross-questioning me on them</strong>, so I quickly realised that anything mentioned during the conversation &amp; on your resume is fair game!</p><p>After that, we moved straight into DSA.</p><h3>DSA Question 1</h3><p>The first question was:</p><blockquote><strong><em>If the input is 1, the output should be 0, and if the input is 0, the output should be 1. </em></strong>(i mean, easy, right?)</blockquote><blockquote>Plot Twist<strong><em>: do this without if-else, conditional statements, or loops.</em></strong></blockquote><p>I started thinking about different approaches and mentioned things like XOR and even string operations.</p><p>He immediately stopped me and basically said, <em>don’t complicate it that much.</em></p><p>The answer was actually a very simple mathematical operation:</p><p><strong>Output = 1-Input</strong></p><p>Because:</p><ul><li>1–1 = 0</li><li>1–0 = 1</li></ul><p>I was able to solve this one pretty quickly once I looked at it mathematically.</p><h3>DSA Question 2</h3><p>The next question was a variation of <a href="https://leetcode.com/problems/max-consecutive-ones/description/"><strong>Maximum Consecutive Ones</strong>.</a> (i don’t remember the exact variation now, sorry!)</p><p>I initially tried a brute-force approach, and the interviewer kept pushing me towards better solutions.</p><p>It became less about simply getting the answer and more about seeing <strong>how I thought about improving my approach</strong>.</p><p>We also discussed:</p><ul><li>BFS</li><li>DFS</li><li>Stacks</li><li>and the Real-life applications of these concepts</li></ul><p>He also asked me about my <strong>role in the GD</strong> and then went quite deep into the problem statement. He asked questions from <strong>my part of the presentation as well as other team members’ parts</strong>.</p><p>This was something he seemed particularly interested in, so I was glad that I had paid attention to the entire solution and not just my own section.</p><p>Another interesting question was about the <strong>mechanism behind URL shortening</strong>. However, I wasn’t able to answer this one completely, which was definitely one of the weaker parts of my interview.</p><p>There were also some questions around:</p><ul><li>Why UBS?</li><li>My family</li><li>UBS work culture</li><li>and finally, aptitude (he expected me to have a grasp on aptitude and give an instant response).</li></ul><p>Finally, he asked me if I had any questions for him.</p><p>Overall, my technical interview lasted around <strong>50–60 minutes.</strong></p><p>I wouldn’t say I came out feeling extremely confident about it. I wasn’t particularly happy with how I had performed, but I felt it was still a satisfactory experience.</p><p>Interestingly, the interviews varied quite a bit across panels. From what I heard, other interviewers focused more on <strong>resume projects, OOPs and DBMS</strong>, while my interview was more DSA and discussion oriented.</p><h3>Round 5: HR Interview</h3><p>And then came the moment that made me really, really happy.</p><p>Around <strong>5 minutes after my technical interview</strong>, I got a call asking me to appear for the HR interview.</p><p>At that point, I knew I had made it to the final stage, and I was <strong>so, so happy!</strong></p><p>The HR interview was much shorter, around <strong>10 minutes</strong>.</p><p>She asked me about the experiences I had mentioned on my resume and then asked me a few questions about my family.</p><p>And that was it.</p><p>Out of the 7 students who reached the technical interview stage, <strong>only 3 students reached the HR round.</strong></p><p>At this point, I was honestly just hoping for the best.</p><h3>The Result 🎉</h3><p>Around <strong>30 minutes after the HR interviews</strong>, the results were announced.</p><p><strong>2 students were selected for the UBS Summer 2027 Internship. </strong>And I was one of them!! (I was too stunned to speak xD).</p><h3>A Few Things I Took Away From The Process</h3><p>Looking back, there are a few things I think really helped me throughout the process:</p><p><strong>1. Know your resume.</strong><br>Anything you mention can become a question. Be prepared to explain every project, experience, extracurricular and achievement.</p><p><strong>2. Don’t overcomplicate simple problems.</strong><br>My first DSA question was a perfect example. I immediately started thinking of XOR and string operations when the solution was simply 1 - input.</p><p><strong>3. In a GD, don’t prepare only your part.</strong><br>The interviewer specifically asked me about other parts of our solution as well. Understanding the complete problem and solution is important.</p><p><strong>4. Communication matters.</strong><br>The GD wasn’t just about having the “best” technical solution. How you communicate, collaborate and contribute to the team matters a lot.</p><p><strong>5. Think out loud during technical interviews.</strong><br>Even when you don’t immediately know the optimal solution, explaining your thought process gives the interviewer something to work with.</p><p><strong>6. Don’t judge your interview too quickly.</strong><br>I personally wasn’t very happy with my technical interview. I walked out thinking it was just <em>okay</em>. And yet, I still made it to the HR round and eventually got selected.</p><p>Sometimes, your perception of how an interview went isn’t the same as the interviewer’s.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*8s8U_6gkAhznmMDAWlWHnQ.gif" /></figure><h3>Final Thoughts</h3><p>The entire process was <strong>lengthy, hectic, and definitely exhausting</strong>, but it was also incredibly rewarding.</p><p>From submitting a resume through our placement cell, to seeing my name among the 33 shortlisted students, to getting through the pen-and-paper test, surviving the GD, going through a nearly hour-long technical interview, and then getting that HR call. It was quite a journey.</p><p>I’m incredibly grateful to our <strong>placement cell, the UBS team, my lovely lovely seniors, my family and everyone who helped us throughout the process</strong>. Thank you so much to lovely you, who’s been reading so far. All the best for what lies ahead. You’ll be great!</p><p><strong>UBS Summer 2027, here we go! :D</strong></p><p>I can’t wait to see what the summer brings. :))</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*UUZQ7Z-deRSwLsuPKCx5zg.gif" /></figure><p><em>I hope you found this article helpful. If you have any queries, feel free to reach out to me on </em><a href="https://www.linkedin.com/in/arya-rai-818323318/"><em>LinkedIn</em></a><em>. More than happy to help!!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cdf6c20fc226" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Experience as the DESIS Ascend Educare Finalist, by D. E. Shaw]]></title>
            <link>https://medium.com/@awrya/my-experience-as-the-desis-ascend-educare-finalist-by-d-e-shaw-0dd08dd3f17a?source=rss-55027f2c74cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/0dd08dd3f17a</guid>
            <category><![CDATA[second-year]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[students]]></category>
            <category><![CDATA[desis-ascend-educare]]></category>
            <category><![CDATA[de-shaw]]></category>
            <dc:creator><![CDATA[Arya Rai]]></dc:creator>
            <pubDate>Sat, 14 Feb 2026 14:38:58 GMT</pubDate>
            <atom:updated>2026-02-14T14:38:58.971Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A Second-Year Student’s Honest Journey Through the Selection Process</em></p><p>When I applied for the <strong>DESIS Ascend Educare Program by D. E. Shaw</strong>, I knew it would be competitive. What I didn’t expect was how much the process would test not just my problem-solving ability, but also my composure, depth of fundamentals, and self-awareness.</p><p>Let’s know a bit about what the program exactly is and then, I’ll walk you through each phase, honestly and professionally, so that future applicants can prepare strategically.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/458/1*8oVhVNPV7dD_Z9uXQoXF2g.png" /></figure><h3>🎯 Eligibility Criteria</h3><p>Based on the program structure and previous years’ information:</p><ul><li>2nd and 3rd year female students (B.Tech/B.E.)</li><li>Strong academic record</li><li>Computer Science or related fields preferred</li><li>Programming (C/C++/Java/Python)</li></ul><h3>🌟 What Makes This Program Valuable?</h3><p>Students selected for DESIS Ascend Educare gain:</p><ul><li>Mentorship from industry professionals @ D.E. Shaw, India.</li><li>Enrollment in a 6-month long mentorship program.</li><li>A stipend of Rs. 50,000 for the entire program duration (so cool??).</li><li>Future internship opportunities at D. E. Shaw.</li><li>Networking with a high-caliber peer group.</li></ul><p>Interactive session with the team, reimbursements on books, chance to visit the DESIS office, goodies and what not! Pretty cool, isn’t it?</p><p>Here’s how it unfolded — phase by phase.</p><h3>🚀 Phase 1: Application &amp; Online Assessment (OA)</h3><p>The application deadline was in mid-November. By the end of November, online test emails were rolled out, and the assessment was scheduled for 29 November.</p><p>The OA was conducted on HackerRank with a strict 70-minute time limit.</p><p>It included:</p><h4><strong>Two coding questions:</strong></h4><ul><li>One medium-level (Linked Lists)</li><li>One hard-level (Trees + Dynamic Programming)</li></ul><h4>Aptitude questions (~8):</h4><ul><li>Quantitative aptitude</li><li>Permutations &amp; combinations</li><li>Probability</li><li>Logical reasoning and so on.</li></ul><p>The coding problems were not surface-level. The hard question especially required both conceptual clarity and calm execution under time pressure.</p><p>Time management was critical. There wasn’t room for hesitation.</p><p>I was able to solve both the coding questions with 12/15 testcases passing in the first question and 14/15 testcases passing in the second question.</p><p>When the results were declared at the beginning of December and I received my interview call on 4 December, I felt both relieved and anxious. The interview was scheduled for 7 December. Just three days away.</p><h3>Phase 2: Technical Interview</h3><p>The interview lasted around 40 minutes and was conducted on HackerRank.</p><p>It began with introductions . First the interviewer introduced himself, then I did. He was warm and professional, which helped ease some of the pressure.</p><p>Then came the main problem:</p><blockquote>An array that increases up to a certain element and then decreases. Find the maximum element.</blockquote><p>I began with a brute-force approach. When he asked about the time complexity, I explained it clearly. He seemed satisfied. But then came the real test.</p><p>He asked me to optimize it.</p><p>I paused. Thought. Tried.</p><p>At one point, I asked for a hint. Something I hesitated to do initially but that small nudge helped me reframe the problem. I eventually arrived at the optimized solution.</p><p>He then asked about edge cases. I listed everything I could think of . Single element arrays, strictly increasing arrays, strictly decreasing arrays, boundary conditions.</p><p>He was content and asked me to code it.</p><p>After writing the solution, he questioned my implementation decisions — variable usage, conditions, complexity, edge handling. Thankfully, I was able to justify everything clearly.</p><p>But the technical grilling didn’t stop there.</p><p>Since I had selected C and C++ as my preferred languages, he went deep into:</p><ul><li>Core C concepts</li><li>Memory and implementation-level questions</li><li>Detailed STL questions in C++</li><li>Data structures I had studied in college</li></ul><blockquote><strong>For aspirants</strong>: <strong>D. E. Shaw cares deeply about language fundamentals.</strong><em><br> </em>You should expect deep, conceptual questions, not just surface-level definitions.</blockquote><p>They don’t just test whether you can solve LeetCode problems . They test whether you truly understand the tools you claim to know.</p><p>As time ran out, he asked if I had any questions. I asked about the program and about my performance. He seemed satisfied overall.</p><p>The interviewer was genuinely kind and encouraging. I left that call feeling challenged, but in a good way.</p><p>It was one of the most intellectually engaging interviews I’ve experienced.</p><h3>🌱 Phase 3: Personal/Behavioral Interview</h3><p>This round was unexpected.</p><p>I received <strong>no prior email</strong> — just a sudden call saying:</p><blockquote><em>“You have an interview, right now.”</em></blockquote><p>I had just finished a semester exam that morning. I was drained. Mentally exhausted. Completely unprepared. Yet I decided to go ahead with the interview.</p><h3>Questions Asked</h3><p>The interview began with:</p><blockquote><em>“Tell me about a situation where you exceeded your own expectations.”</em></blockquote><p>I answered, but the interviewer expected more depth. I reframed and answered again.</p><p>The rest of the interview focused on behavioral questions:</p><ul><li>Growth mindset</li><li>Handling challenges</li><li>Demonstrating problem-solving beyond academics</li><li>Situations that show initiative and learning</li></ul><p>The key here was:</p><blockquote><em>They look for </em><strong><em>evidence of ownership, impact, and learning</em></strong><em>, not generic answers.</em></blockquote><p>The interview ended on a good note, but I personally wasn’t satisfied with my performance in this round.</p><p>And that honesty matters.</p><p>Because sometimes growth comes from recognizing where you could have done better.</p><h3>Final Thoughts</h3><p>Looking back, the DESIS Ascend Educare selection process tested:</p><ul><li>Technical depth</li><li>Optimization thinking</li><li>Language fundamentals</li><li>Composure under surprise situations</li><li>Self-awareness and articulation</li></ul><p>What stood out the most was the quality of the interviewers. They were respectful, calm, and genuinely interested in understanding how I think.</p><p>Even the behavioral round, though challenging for me, taught me the importance of structured storytelling and preparation beyond technical skills.</p><p>Even though I got eliminated in the last round, I’m so grateful to have had such an experience in my second year itself. It has taught me a lot that will surely stay with me while applying for futher opportunities.</p><p>Would I recommend applying?</p><p>Absolutely.</p><p>Even preparing for it elevates your level as a problem solver and communicator.</p><p>For second-year students considering it:</p><ul><li>Master your DSA fundamentals.</li><li>Know your preferred language deeply.</li><li>Prepare structured behavioral stories.</li><li>Stay mentally ready, interviews don’t always come with warnings.</li></ul><p>And most importantly, believe that <strong>you belong in rooms like these.</strong></p><p>The experience pushed me outside my comfort zone. And for that alone, I’m grateful. All the best to all those applying this year!</p><blockquote>If you found this helpful, feel free to connect or reach out on <a href="https://www.linkedin.com/in/arya-rai-818323318/">LinkedIn</a>. I’d be happy to help :&gt;</blockquote><p><em>This is my first tech article on Medium, I’ve tried to explain my entire experience here. Do let me know in the comments how I can improve.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0dd08dd3f17a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>