<?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 Gowtham Sai Putti on Medium]]></title>
        <description><![CDATA[Stories by Gowtham Sai Putti on Medium]]></description>
        <link>https://medium.com/@gowthamsai.workspace?source=rss-2b4bb14a0871------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Gowtham Sai Putti on Medium</title>
            <link>https://medium.com/@gowthamsai.workspace?source=rss-2b4bb14a0871------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 03:10:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gowthamsai.workspace/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[CRED backend developer —  interview experience]]></title>
            <link>https://medium.com/@gowthamsai.workspace/cred-backend-developer-interview-experience-8d932b142e76?source=rss-2b4bb14a0871------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d932b142e76</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[placement]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[backend]]></category>
            <category><![CDATA[cred]]></category>
            <dc:creator><![CDATA[Gowtham Sai Putti]]></dc:creator>
            <pubDate>Thu, 26 Jan 2023 18:44:30 GMT</pubDate>
            <atom:updated>2023-01-26T18:44:30.637Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>CRED backend developer — interview experience</strong></h3><p>it started on a fine day when i woke up late as usual. getting ready for the first round of the hiring process was a little hasty, just as the time demanded.</p><p><strong>the first round</strong></p><p>the hiring process was a part of their campus hiring program for the backend developer role at IIT Dharwad; the first round was at 8:00 am, which was a coding round. there were 3 questions which were of medium to hard difficulty. solving them tested more of our problem-solving skills. the test lasted for 90 minutes. after finishing the test, i could sense the change in my surroundings, with people discussing their approach to the problem.</p><p>after a heated discussion of possible solutions, we were tensed and eagerly waiting for the results. it was around 11 am, the results were out, and i was still in the game :)</p><p><strong>the second round</strong></p><p>the next round was a project round which started at noon; a template was given to us, which we needed to complete. this round was for 150 minutes. the project was a credit card management system designed by people at CRED. there were 4 language options: python, node.js, java, and c++. i chose python as i am comfortable with it. the initial functions were to do some basic crud operations. if you have a good grip on the concepts of OOPs and the programming language, you should be comfortable with it. i completed the project in around 60 minutes and focused the rest of the time on making the code more readable and clean. this round ended at around 2:30 pm.</p><p>i was initially sceptical about whether i could get this opportunity, but when the results were out, i got to know that there was a good enough chance for me to win.</p><p><strong>the third round</strong></p><p>the interview round started at around 4:30 pm. the first interview was purely technical and was focused more on the fundamentals. the interviewer asked some questions regarding extending the project from the second round and what algorithms we could use to attain them.</p><p>most of the questions were to determine how clear our fundamentals were and how we could modify an existing algorithm to fit our needs. the interview was for 90 minutes.</p><p>we waited for some 60–90 minutes for the results. meanwhile, we were handed out some cool CRED merchandise :)</p><p><strong>the final round</strong></p><p>the results were out, and it came down to the last 3. the next round of interviews started at around 8 pm and lasted for 60 minutes. this round was managerial and was with the head of engineering (backend). they asked me about what i did in my 3 years at IIT. most of the time went in talking about my past internships and projects; then, there were a few questions regarding how CRED works, followed by some personality questions.</p><p>after the interview, we all had dinner and waited for the final results. they came with the good news that all 3 of us who made it to the final round were selected. Woohoo!!</p><p><strong>Summary</strong></p><p>if you have read the whole article till here, kudos!! if not, the next few lines are for you.</p><p><strong>company:</strong> CRED</p><p><strong>role:</strong> backend developer</p><p><strong>rounds:</strong></p><ul><li><strong>coding round</strong>: 3 medium — hard questions, 90 minutes</li><li><strong>project round:</strong> 1 question, 150 minutes</li><li><strong>technical interview:</strong> focuses more on your fundamentals, 90 minutes</li><li><strong>managerial interview:</strong> focuses more on your experience and idea about the company and some personality questions</li></ul><p>to know more about me and my experience, check out my <a href="https://www.linkedin.com/in/gowtham-sai-putti-ba6a611b1/">linkedin</a>.</p><p>for more such exciting content, follow me. cheers, and have a nice day xD.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d932b142e76" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>