<?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 Avi Srivastava on Medium]]></title>
        <description><![CDATA[Stories by Avi Srivastava on Medium]]></description>
        <link>https://medium.com/@srivastavaavi26?source=rss-378d4bb7911b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*DnKuKeduySRjVmvo</url>
            <title>Stories by Avi Srivastava on Medium</title>
            <link>https://medium.com/@srivastavaavi26?source=rss-378d4bb7911b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:43:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@srivastavaavi26/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[How I Got Into Evaratus (Formerly Scaler AI Labs) From a Tier-3 College]]></title>
            <link>https://medium.com/@srivastavaavi26/how-i-got-into-evaratus-formerly-scaler-ai-labs-from-a-tier-3-college-d37ce2996596?source=rss-378d4bb7911b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d37ce2996596</guid>
            <category><![CDATA[placement]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[interview]]></category>
            <dc:creator><![CDATA[Avi Srivastava]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 12:40:54 GMT</pubDate>
            <atom:updated>2026-11-17T12:40:54.732Z</atom:updated>
            <content:encoded><![CDATA[<h4>Every round, what my resume leaned on, and the JavaScript question that humbled me</h4><p>I recently got an internship at Evaratus (formerly Scaler AI Labs) as an MTS Intern. A few people asked how it happened, so I’m writing down the whole thing, no sugarcoating: the resume, the rounds, the question that caught me off guard, and what I’d tell anyone preparing for the same kind of process.</p><p>Some context first. I’m a 3rd-year B.Tech CSE student at Bennett University. Scaler AI Labs was the first company to come to campus this year. The semester was barely a month old when the mail dropped. Half the batch was confused, the other half was panicking. I was somewhere in between.</p><p>What followed was about a month of prep, pressure, and honestly a lot of self-doubt.</p><h3>The process at a glance</h3><ul><li><strong>Shortlisting:</strong> resume built on freelance work and one real project, not the college name.</li><li><strong>JavaScript round:</strong> write a Promise class from scratch.</li><li><strong>Final two rounds:</strong> DSA (dynamic programming), plus an in-depth resume discussion and a deep dive into my project, Strand.</li></ul><h3>What my resume leaned on</h3><p>My resume couldn’t lean on a college name. So it leaned on two things.</p><p><strong>1. Freelancing.</strong> Upwork, direct client work, a bit of everything, for national and international clients. I landed my first Upwork client right when my connects were almost over. The pay wasn’t great and the early work wasn’t glamorous.</p><p>But it taught me something no assignment did: how to ship something a real person is paying for. A graded assignment has a rubric. A client has a deadline, a budget, and opinions. That difference shows up in how you talk about your work in an interview.</p><p><strong>2. A project called Strand.</strong> Strand is an AI agent that checks AI visibility, basically figuring out how discoverable something is to AI systems. I built it on my own time. I broke it a few times, fixed it, broke it again.</p><p>That project ended up being the thing every interviewer wanted to talk about.</p><p>If you take one thing from this section: one project you actually built, broke, and understand end to end is worth more than five tutorial clones. Interviewers can tell the difference in about two questions.</p><h3>The interview rounds</h3><h4>The JavaScript round: write a Promise class</h4><p>Web is supposed to be my strength, so I walked into this round feeling fairly confident.</p><p>The question: <strong>write a Promise class.</strong> Not “use promises”, not “explain async/await”. Build the class itself.</p><p>That one question showed me how shallow my depth was in places I assumed I had covered. I had used promises for years. I’d never had to think about what actually happens inside one.</p><p>It genuinely humbled me. Since this is exactly the kind of question you can prepare for, I’ve written out a simple version further down.</p><h4>The final two rounds: DP problems and an in-depth resume grilling</h4><p>The last two rounds were DSA, and the problems were dynamic programming. No easy array warm-ups. DP is the topic where you either understand how to break a problem into smaller ones, or you’ve memorised solutions and get stuck the moment the question changes slightly. If you’re preparing, don’t just practise DP problems. Practise explaining how you’d go from the brute-force recursion to the DP version, because that reasoning is what they want to hear.</p><p>Along with DSA, they went through my resume in depth. Every line was fair game. Freelance work, the clients, what I actually did versus what the team did, and then a full discussion on Strand.</p><p>The Strand part wasn’t “tell me about your project”. It went deep into <strong>why</strong> I made the choices I made. Why this approach and not another. What broke. What I’d change. If you’ve actually built the thing, these questions are the easiest part of the interview. If you haven’t, they’re the hardest.</p><p>That’s also why I’d say: don’t put anything on your resume you can’t talk about for ten minutes.</p><p>Then the offer came. I was one of the first few from my 2026 batch to land something.</p><p>A simple Promise class, written from scratch</p><p>If you’re preparing for a JavaScript or frontend interview, practise this one. A promise only needs to do three things: remember whether it succeeded or failed, remember the value, and call the right function when it’s done.</p><pre>class MyPromise {<br>  constructor(executor) {<br>    this.state = &#39;pending&#39;;<br>    this.value = undefined;<br>    this.callbacks = [];<br>const settle = (state, value) =&gt; {<br>      if (this.state !== &#39;pending&#39;) return;<br>      this.state = state;<br>      this.value = value;<br>      this.callbacks.forEach((callback) =&gt; callback());<br>    };<br>    const resolve = (value) =&gt; {<br>      if (value instanceof MyPromise) {<br>        value.then(resolve, reject);<br>      } else {<br>        settle(&#39;fulfilled&#39;, value);<br>      }<br>    };<br>    const reject = (reason) =&gt; settle(&#39;rejected&#39;, reason);<br>    try {<br>      executor(resolve, reject);<br>    } catch (error) {<br>      reject(error);<br>    }<br>  }<br>  then(onFulfilled, onRejected) {<br>    return new MyPromise((resolve, reject) =&gt; {<br>      const handle = () =&gt; {<br>        queueMicrotask(() =&gt; {<br>          const callback = this.state === &#39;fulfilled&#39; ? onFulfilled : onRejected;<br>          if (typeof callback !== &#39;function&#39;) {<br>            if (this.state === &#39;fulfilled&#39;) resolve(this.value);<br>            else reject(this.value);<br>            return;<br>          }<br>          try {<br>            resolve(callback(this.value));<br>          } catch (error) {<br>            reject(error);<br>          }<br>        });<br>      };<br>      if (this.state === &#39;pending&#39;) this.callbacks.push(handle);<br>      else handle();<br>    });<br>  }<br>  catch(onRejected) {<br>    return this.then(null, onRejected);<br>  }<br>}</pre><p>And it works like the real one:</p><pre>new MyPromise((resolve) =&gt; setTimeout(() =&gt; resolve(1), 1000))<br>  .then((value) =&gt; value + 1)<br>  .then((value) =&gt; console.log(value)) // 2<br>  .catch((error) =&gt; console.log(error));</pre><h4>The five ideas behind it</h4><p><strong>1. It settles only once.</strong> A promise starts as pending and moves to fulfilled or rejected one time. The check at the top of settle ignores every call after the first.</p><p><strong>2. Errors in the executor become rejections.</strong> If the function you pass in throws, you get a rejected promise instead of a crash. That’s the try/catch around executor.</p><p><strong>3. </strong><strong>then returns a new promise.</strong> That’s what makes chaining work. Whatever your callback returns becomes the value of the next promise. If it throws, the next promise rejects.</p><p><strong>4. Callbacks always run later, never right away.</strong> Even if the promise is already resolved, .then callbacks run after the current code finishes. queueMicrotask does that. This is the detail most people miss:</p><pre>new MyPromise((resolve) =&gt; resolve(1)).then(() =&gt; console.log(&#39;second&#39;));<br>console.log(&#39;first&#39;);</pre><p><strong>5. Missing callbacks pass the value along.</strong> If there’s no onRejected, the error just moves down the chain. That’s why one .catch at the end catches an error from anywhere above it.</p><h4>Follow-up questions to expect</h4><ul><li>Why does then return a new promise instead of this?</li><li>What’s the difference between a microtask and setTimeout? Why does it matter here?</li><li>How would you add finally, Promise.all or Promise.race?</li><li>What should happen if a promise is resolved with itself?</li></ul><p>Write it once from memory, without looking. Using promises every day is not the same as knowing how they work. I learned that in the room.</p><h3>What I’d tell anyone preparing</h3><p><strong>Nobody cared which college I was from once I was in the room.</strong> They cared whether I could explain my own project under pressure, and whether I’d actually built things outside a classroom.</p><p><strong>Build one real thing and know it inside out.</strong> Every decision in your project is a possible interview question. “I followed a tutorial” is not an answer to “why did you do it this way?”</p><p><strong>Paid work counts.</strong> Freelancing, even small and unglamorous gigs, shows you can deliver to someone who isn’t grading you.</p><p><strong>Stress-test your strengths.</strong> The round that hurt me was in the area I was most confident about. Whatever you call your strength, go one layer deeper: write the Promise class, build an event emitter, implement debounce from scratch.</p><p><strong>Start before you feel ready.</strong> The company came a week into the semester. Nobody had time to feel ready. The people who already had projects and real work behind them had the advantage.</p><p>Tier 3 isn’t a ceiling. It’s just a starting point people underestimate.</p><p><em>I’m Avi Srivastava, a full-stack AI engineer and MTS Intern at Evaratus. I build web, mobile and AI products for startups. See my work at </em><a href="https://avicodes.tech/"><em>avicodes.tech</em></a><em>, or find me on </em><a href="https://www.linkedin.com/in/avi-srivastava26/"><em>LinkedIn</em></a><em> if you’re preparing for a similar process and have questions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d37ce2996596" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>