<?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 UIRound on Medium]]></title>
        <description><![CDATA[Stories by UIRound on Medium]]></description>
        <link>https://medium.com/@uiround?source=rss-4c20c8bc75d2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MnAN7K51e14FyMvkQQhF5g.png</url>
            <title>Stories by UIRound on Medium</title>
            <link>https://medium.com/@uiround?source=rss-4c20c8bc75d2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 06:00:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@uiround/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[Oracle Frontend Interview: Every Round, Every Question]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://uiround.medium.com/oracle-frontend-interview-every-round-every-question-f966469f3515?source=rss-4c20c8bc75d2------2"><img src="https://cdn-images-1.medium.com/max/1470/1*5uz1F3SgkUA1ZUnSzGHJfg.jpeg" width="1470"></a></p><p class="medium-feed-snippet">A HackerRank test, a LeetCode medium, a React search bar or paginated table, a song shuffler, and output questions on slides.</p><p class="medium-feed-link"><a href="https://uiround.medium.com/oracle-frontend-interview-every-round-every-question-f966469f3515?source=rss-4c20c8bc75d2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://uiround.medium.com/oracle-frontend-interview-every-round-every-question-f966469f3515?source=rss-4c20c8bc75d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/f966469f3515</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[UIRound]]></dc:creator>
            <pubDate>Sun, 22 Nov 2026 05:08:36 GMT</pubDate>
            <atom:updated>2026-11-22T05:08:36.977Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[15 JavaScript Promise Interview Questions Every Frontend Developer Should Practise]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://uiround.medium.com/15-javascript-promise-interview-questions-every-frontend-developer-should-practise-4cc8fc5f37da?source=rss-4c20c8bc75d2------2"><img src="https://cdn-images-1.medium.com/max/1470/1*EfKPjLGHlz4eFeVMXU0iWA.jpeg" width="1470"></a></p><p class="medium-feed-snippet">States, chaining, error handling, all vs allSettled vs race vs any, await in loops, timeouts, retries and promisify, with code whose&#x2026;</p><p class="medium-feed-link"><a href="https://uiround.medium.com/15-javascript-promise-interview-questions-every-frontend-developer-should-practise-4cc8fc5f37da?source=rss-4c20c8bc75d2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://uiround.medium.com/15-javascript-promise-interview-questions-every-frontend-developer-should-practise-4cc8fc5f37da?source=rss-4c20c8bc75d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/4cc8fc5f37da</guid>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[interview-questions]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[UIRound]]></dc:creator>
            <pubDate>Sun, 22 Nov 2026 05:07:35 GMT</pubDate>
            <atom:updated>2026-11-22T05:07:35.913Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[10 JavaScript Polyfills to Know Before Your Next Frontend Interview (Tested Code)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://uiround.medium.com/10-javascript-polyfills-to-know-before-your-next-frontend-interview-tested-code-825b827bc80e?source=rss-4c20c8bc75d2------2"><img src="https://cdn-images-1.medium.com/max/1470/1*S67fzFSqe8rV1sKls2xDww.jpeg" width="1470"></a></p><p class="medium-feed-snippet">map, filter, reduce, call, apply, bind, new, instanceof, Object.create</p><p class="medium-feed-link"><a href="https://uiround.medium.com/10-javascript-polyfills-to-know-before-your-next-frontend-interview-tested-code-825b827bc80e?source=rss-4c20c8bc75d2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://uiround.medium.com/10-javascript-polyfills-to-know-before-your-next-frontend-interview-tested-code-825b827bc80e?source=rss-4c20c8bc75d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/825b827bc80e</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[interview-questions]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[UIRound]]></dc:creator>
            <pubDate>Sat, 21 Nov 2026 18:28:08 GMT</pubDate>
            <atom:updated>2026-11-21T18:28:08.342Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[10 Custom React Hooks You Should Be Able to Write in an Interview]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://uiround.medium.com/10-custom-react-hooks-you-should-be-able-to-write-in-an-interview-1e6e6e411a51?source=rss-4c20c8bc75d2------2"><img src="https://cdn-images-1.medium.com/max/1470/1*z3GHckl-APpnDZ6MR6kU0A.jpeg" width="1470"></a></p><p class="medium-feed-snippet">useToggle, usePrevious, useDebounce, useLocalStorage, useFetch, useEventListener, useOnClickOutside, useInterval, useMediaQuery and&#x2026;</p><p class="medium-feed-link"><a href="https://uiround.medium.com/10-custom-react-hooks-you-should-be-able-to-write-in-an-interview-1e6e6e411a51?source=rss-4c20c8bc75d2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://uiround.medium.com/10-custom-react-hooks-you-should-be-able-to-write-in-an-interview-1e6e6e411a51?source=rss-4c20c8bc75d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e6e6e411a51</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[interview-questions]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[UIRound]]></dc:creator>
            <pubDate>Sat, 21 Nov 2026 18:27:34 GMT</pubDate>
            <atom:updated>2026-11-21T18:27:34.083Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Flipkart Frontend Interview: Every Round, Every Question]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://uiround.medium.com/flipkart-frontend-interview-every-round-every-question-1445fd13c04f?source=rss-4c20c8bc75d2------2"><img src="https://cdn-images-1.medium.com/max/1470/1*MaexdWHLPauAPUdKP6bLtw.jpeg" width="1470"></a></p><p class="medium-feed-snippet">Two hours of framework-free machine coding, a real DSA bar, UI tech depth, and sometimes a product sense round.</p><p class="medium-feed-link"><a href="https://uiround.medium.com/flipkart-frontend-interview-every-round-every-question-1445fd13c04f?source=rss-4c20c8bc75d2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://uiround.medium.com/flipkart-frontend-interview-every-round-every-question-1445fd13c04f?source=rss-4c20c8bc75d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/1445fd13c04f</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[flipkart]]></category>
            <dc:creator><![CDATA[UIRound]]></dc:creator>
            <pubDate>Sat, 21 Nov 2026 13:56:22 GMT</pubDate>
            <atom:updated>2026-11-21T13:56:22.749Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Accenture Frontend Interview: Every Round, Every Question]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://uiround.medium.com/accenture-frontend-interview-every-round-every-question-7d040cfff83d?source=rss-4c20c8bc75d2------2"><img src="https://cdn-images-1.medium.com/max/1470/1*7kAdlmXA-a3bEXlKb0Za0Q.jpeg" width="1470"></a></p><p class="medium-feed-snippet">Game-based aptitude, a coding round with a frontend task even for freshers, a communication test, and React internals for laterals.</p><p class="medium-feed-link"><a href="https://uiround.medium.com/accenture-frontend-interview-every-round-every-question-7d040cfff83d?source=rss-4c20c8bc75d2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://uiround.medium.com/accenture-frontend-interview-every-round-every-question-7d040cfff83d?source=rss-4c20c8bc75d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d040cfff83d</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[accenture]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[frontend-development]]></category>
            <dc:creator><![CDATA[UIRound]]></dc:creator>
            <pubDate>Sat, 21 Nov 2026 13:52:24 GMT</pubDate>
            <atom:updated>2026-11-21T13:52:24.334Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Atlassian Frontend Interview: Every Round, Every Question]]></title>
            <link>https://uiround.medium.com/atlassian-frontend-interview-every-round-every-question-45e7bfee6eb3?source=rss-4c20c8bc75d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/45e7bfee6eb3</guid>
            <category><![CDATA[atlassian]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[system-design-interview]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[UIRound]]></dc:creator>
            <pubDate>Sat, 21 Nov 2026 11:44:52 GMT</pubDate>
            <atom:updated>2026-11-21T11:44:52.814Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A vanilla JS filter round, an analytics SDK, a Trello-style design, and a values interview that goes to a hiring committee.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hg4Yh7OUVHGDZynMmRj35g.jpeg" /></figure><p>Atlassian is one of the few large companies that <strong>documents its engineering interview in detail</strong>, including a hiring committee and a separate values interview. Frontend candidates fill in the specifics: a vanilla JavaScript screen, a machine coding round, a JavaScript design problem and a frontend system design round.</p><p>Here’s what each round tests, put together from Atlassian’s own engineering interview handbook and public candidate write-ups. For every round, I’ve linked questions you can practise on <a href="https://uiround.com/companies/atlassian">UIRound</a> in a browser editor, with the tests an interviewer would run.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-qt0J72oS1kvvhqk8SoIdA.jpeg" /></figure><h3>The loop at a glance</h3><p>Atlassian’s handbook describes the core interviews:</p><ul><li><strong>Coding interview</strong>, in two parts: data structures and code design. You choose your language, and the handbook stresses your thinking and trade-offs over language tricks. A missed line isn’t a deal-breaker.</li><li><strong>Systems design</strong>: 60 minutes on requirements, constraints and fit.</li><li><strong>Manager interview</strong>: who you are, past projects and how you collaborate.</li><li><strong>Values interview</strong>: usually with <strong>someone outside the hiring team</strong>, such as sales, HR or support.</li><li><strong>Debrief and hiring committee</strong>: a committee reviews candidates independently of the interviewers.</li></ul><p>For frontend, a detailed account from a senior (P5) candidate in Bengaluru describes <strong>six rounds</strong>: a vanilla JS and DOM filter, machine coding, JavaScript problem solving, system design, values, and a final management round. Recruiters briefed him on each round in advance.</p><h3>Round 1: JavaScript and DOM screen</h3><p>This is a filter: vanilla JavaScript, DOM manipulation, and reading code carefully enough to predict what it does. In the P5 account, the task was <strong>implementing pagination in plain JavaScript</strong>.</p><ul><li><a href="https://uiround.com/questions/generate-pagination-page-numbers-with-ellipses">Generate pagination page numbers with ellipses</a> (reported)</li><li><a href="https://uiround.com/questions/implement-event-delegation-for-a-dynamic-list">Implement event delegation for a dynamic list</a></li></ul><p>Be ready to explain event bubbling and how the event loop orders your callbacks.</p><h3>Round 2: Machine coding (code design)</h3><p>Any framework was allowed in the P5 account, and the task was <strong>tic-tac-toe where the board configuration came in as props</strong>. Given the handbook’s focus on trade-offs, expect interviewers to look past “it works” to <strong>whether the code is easy to extend</strong>: a clear state model, a win check that doesn’t hard-code the board size, and sensible component boundaries.</p><ul><li><a href="https://uiround.com/questions/build-tic-tac-toe-on-an-n-by-n-board-with-m-in-a-row-to-win">Build tic-tac-toe on an N×N board with M in a row to win</a> (reported)</li><li><a href="https://uiround.com/questions/build-a-drag-and-drop-kanban-board">Build a drag-and-drop Kanban board</a></li><li><a href="https://uiround.com/questions/build-a-tree-view-with-expand-collapse-and-checkbox">Build a tree view with expand, collapse and checkbox selection</a> (reported)</li></ul><p>Read the <a href="https://uiround.com/guides/component-api-design">component API design guide</a> before this round.</p><h3>Round 3: JavaScript problem solving</h3><p>This round is about designing a small piece of JavaScript infrastructure. In the P5 account it was <strong>an analytics SDK that collects events from components and sends them to the server in batches</strong>, with a follow-up on which design pattern fits a single shared instance. Here’s a solid core:</p><pre>class Analytics {<br>  #queue = [];<br>  #timer = null;<br>  constructor(url, { maxBatch = 20, delay = 2000 } = {}) {<br>    Object.assign(this, { url, maxBatch, delay });<br>    addEventListener(&#39;pagehide&#39;, () =&gt; this.flush(true));<br>  }<br>  track(name, data) {<br>    this.#queue.push({ name, data, ts: Date.now() });<br>    if (this.#queue.length &gt;= this.maxBatch) this.flush();<br>    else this.#timer ??= setTimeout(this.flush, this.delay);<br>  }<br>  flush = (exit = false) =&gt; {<br>    clearTimeout(this.#timer);<br>    this.#timer = null;<br>    if (!this.#queue.length) return;<br>    const body = JSON.stringify(this.#queue.splice(0));<br>    if (exit) return navigator.sendBeacon(this.url, body);<br>    const init = { method: &#39;POST&#39;, body, keepalive: true };<br>    fetch(this.url, init); // retries: see the follow-ups<br>  };<br>}</pre><p>The follow-ups:</p><ul><li><strong>“Which pattern for one shared instance?”</strong> A singleton: export one instance from the module, or a lazy getInstance().</li><li><strong>“What happens when the tab closes?”</strong> pagehide plus sendBeacon, because a normal fetch may be cancelled.</li><li><strong>“The request fails.”</strong> Put the batch back at the front of the queue and retry with backoff, <strong>keeping order</strong>.</li><li><strong>“Why </strong><strong>flush as an arrow field?&quot;</strong> So setTimeout(this.flush) keeps this.</li></ul><p>Practise:</p><ul><li><a href="https://uiround.com/questions/implement-an-analytics-sdk-with-event-batching-and">Implement an analytics SDK with event batching and sendBeacon fallback</a> (reported)</li><li><a href="https://uiround.com/questions/build-a-serial-analytics-sdk-that-retries-failed-events-in-order-and-supports-flush">Build a serial analytics SDK that retries failed events in order</a></li><li><a href="https://uiround.com/questions/build-a-feature-flag-evaluator-with-targeting-and-stable-percentage-rollouts">Build a feature flag evaluator with stable percentage rollouts</a></li></ul><h3>Round 4: System design</h3><p>Atlassian builds collaboration tools, and the reported prompt looks like one: <strong>a Trello-style board</strong>. The discussion centred on the data model, request and response payloads, and state management with normalisation.</p><p>The P5 author reports <strong>failing this round because he couldn’t normalise the state</strong>. That’s the most useful warning in the whole loop: have a clear answer for how entities, ids and ordering are stored on the client.</p><ul><li><a href="https://uiround.com/questions/design-a-jira-style-issue-board-for-10-000-issues-virtualised-columns-rank-keys-live-updates-and-conflicts">Design a Jira-style issue board for 10,000 issues</a> (reported)</li><li><a href="https://uiround.com/questions/build-a-trello-like-kanban-app-supporting-nested-cards-drag">Build a Trello-like Kanban app with nested cards, drag-and-drop and undo</a> (reported)</li><li><a href="https://uiround.com/questions/normalize-nested-api-data-into-entities-with-memoized-selectors">Normalize nested API data into entities with memoized selectors</a></li></ul><p>Use the <a href="https://uiround.com/guides/frontend-state-management">frontend state management</a> and <a href="https://uiround.com/guides/client-server-api-design">client-server API design</a> guides.</p><h3>Round 5: Values interview</h3><p>Atlassian lists five values: <strong>open company, no bullshit; build with heart and balance; don’t #@!% the customer; play, as a team; and be the change you seek.</strong> The handbook describes this round as fairly informal, run by someone outside the hiring team. It still feeds the same debrief as the technical rounds.</p><p>Write one or two short, specific stories per value: what you did and what changed.</p><h3>Round 6: Manager interview</h3><p>Past projects, impact, and how you work with others. Be ready to go deep on one project: the problem, the options you rejected, what you’d change now, and how you brought people along.</p><h3>What makes Atlassian different</h3><ul><li><strong>The values interview counts.</strong> It’s a named stage in Atlassian’s own handbook.</li><li><strong>A hiring committee decides.</strong> Every round, values included, feeds it.</li><li><strong>Design for extension.</strong> Configurable games and SDKs reward code that survives the next requirement.</li><li><strong>Collaboration-tool prompts.</strong> Boards, issues and normalised client state.</li></ul><h3>A 4-week plan</h3><p><strong>Week 1: vanilla JavaScript and the DOM.</strong> Build pagination, event delegation and a small widget with no framework. Practise predicting output from code.</p><p><strong>Week 2: machine coding for extension.</strong> Build tic-tac-toe with a configurable board and a Kanban board. Then add one new requirement to each and note what you had to change.</p><p><strong>Week 3: JavaScript design.</strong> Write an analytics SDK with batching, flush and retry, plus an event emitter and a feature flag evaluator.</p><p><strong>Week 4: design, values, rehearsal.</strong> Practise board and issue-tracker designs with a focus on normalised state. Write your values stories and run an <a href="https://uiround.com/mock-interview?company=atlassian#mock">Atlassian-style mock interview</a>.</p><p><em>Loops vary by team, level and location. Treat single-candidate details as examples, not guarantees.</em></p><p>The full sourced breakdown, with Atlassian’s handbook and every candidate write-up linked, is in the <a href="https://uiround.com/companies/atlassian">UIRound Atlassian guide</a>.</p><p><strong>Interviewed at Atlassian recently?</strong> Drop your rounds in the comments. It helps the next person more than any guide can. And <strong>follow me</strong> for the next company breakdown.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45e7bfee6eb3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wipro Frontend Interview: Every Round, Every Question]]></title>
            <link>https://uiround.medium.com/wipro-frontend-interview-every-round-every-question-0dea1cdf9cd8?source=rss-4c20c8bc75d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/0dea1cdf9cd8</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[wipro]]></category>
            <dc:creator><![CDATA[UIRound]]></dc:creator>
            <pubDate>Sat, 21 Nov 2026 07:24:38 GMT</pubDate>
            <atom:updated>2026-11-21T07:24:38.049Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Elite NTH, TURBO and STAR for freshers, one combined business discussion, and HTML, CSS and JavaScript basics for experienced hires.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oGaNFJgGhAlxhngAaElyug.jpeg" /></figure><p>Wipro hires freshers as <strong>Project Engineers</strong> through <strong>Elite NTH, TURBO, STAR and WILP</strong>, which share one flow: an online assessment, then a single <strong>business discussion</strong> that combines technical and HR questions. Experienced <strong>UI, React and Angular developers</strong> get one or two technical rounds and HR, and reports stress <strong>HTML, CSS and core JavaScript as much as the framework</strong>.</p><p>Here’s what each round tests, put together from public candidate reports. For every round, I’ve linked questions you can practise on <a href="https://uiround.com/companies/wipro">UIRound</a> in a browser editor, with the tests an interviewer would run.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dSNPkQxV7HVmq3CdsEIh3w.jpeg" /></figure><h3>The loop at a glance</h3><p><strong>Freshers:</strong> online assessment, a voice assessment (TURBO only), the business discussion, a letter of intent, then the offer. TURBO also includes pre-skilling training.</p><p><strong>Experienced:</strong> one or two technical rounds, sometimes an assignment, then HR.</p><p>Wipro states a cooling-off rule: if you took part in a Wipro selection in the last three months you’re ineligible, and you can re-register 90 days after your last online assessment.</p><h3>Round 1: Online assessment (freshers)</h3><p>The Elite assessment is <strong>80 minutes</strong>: English (sentence ordering, synonyms, comprehension, grammar), logical reasoning (coding-decoding, blood relations, directions, series, clocks and calendars), quantitative aptitude (HCF and LCM, time and speed, profit and loss, ratios), a <strong>200-word essay</strong> in about 20 minutes, and <strong>two coding questions</strong>, easy and medium, on arrays, matrices, stacks, queues and strings.</p><ul><li><a href="https://uiround.com/questions/solve-classic-array-questions-second-largest-missing-number-duplicates-move-zeros-and-rotate">Solve classic array questions: second largest, missing number, duplicates, move zeros and rotate</a></li><li><a href="https://uiround.com/questions/solve-classic-string-questions-capitalize-words-character-counts-compression-and-anagram-groups">Solve classic string questions: capitalise words, character counts, compression and anagram groups</a></li></ul><h3>Round 2: Voice assessment (TURBO)</h3><p>Spoken English. Practise talking about yourself and your project for one to two minutes without notes.</p><h3>Round 3: Business discussion (freshers)</h3><p>One combined interview, so <strong>behavioural answers count as much as technical ones</strong>.</p><ul><li><strong>Technical:</strong> your projects, the technologies you use, your internship role, C versus C++, pointers, JVM, JRE and JDK, inheritance and OOP, and whether you’ll sign a service agreement.</li><li><strong>HR:</strong> handling a team member’s complaint, a client complaint, disagreeing with a senior, owning a mistake, relocation, and why Wipro.</li></ul><p>Read the <a href="https://uiround.com/guides/behavioral-interview-frontend">behavioural interview guide</a>.</p><h3>Round 4: Technical rounds (experienced)</h3><p>The reported JavaScript questions are classic and quick: <strong>deep-copying an object, whether spread deep-copies, swapping two variables in one statement</strong>, currying, promises and closures. Get these exactly right:</p><pre>let a = 1, b = 2;<br>[a, b] = [b, a]; // swap in one statement<br>const user = { name: &#39;Asha&#39;, address: { city: &#39;Pune&#39; } };<br>const shallow = { ...user };<br>shallow.address.city = &#39;Delhi&#39;;<br>console.log(user.address.city); // &#39;Delhi&#39;: spread is shallow<br>const deep = structuredClone(user);<br>deep.address.city = &#39;Mumbai&#39;;<br>console.log(user.address.city); // still &#39;Delhi&#39;</pre><p>The follow-ups:</p><ul><li><strong>“Why not </strong><strong>JSON.parse(JSON.stringify(obj))?&quot;</strong> It drops undefined and functions, turns dates into strings, and fails on circular references.</li><li><strong>“What can’t </strong><strong>structuredClone copy?&quot;</strong> Functions, DOM nodes and class prototypes.</li><li><strong>“When is spread enough?”</strong> For flat objects, or when you replace nested objects instead of mutating them, as in React state updates.</li><li><strong>“Swap without destructuring?”</strong> A temporary variable. Arithmetic tricks work but read poorly.</li></ul><p>Other reported topics:</p><ul><li><strong>HTML and CSS:</strong> semantic versus non-semantic elements, flexbox, the box model, identifying the HTML version, and <strong>embedding another web page</strong>.</li><li><strong>React:</strong> virtual DOM versus real DOM, and why you chose React over Angular for a project.</li><li><strong>Angular:</strong> stopping navigation from a child route, observables without subscribe, singleton services, parent and child data passing, observable versus observer, and TypeScript basics.</li><li><strong>UI developer:</strong> performance, challenges you faced, and how you built components.</li><li><strong>Assignment (one candidate):</strong> build a web app that <strong>locates a place on a map</strong>.</li><li><strong>Technical lead:</strong> real project architecture and React testing tools.</li></ul><p>Practise:</p><ul><li><a href="https://uiround.com/questions/predict-shallow-versus-deep-copy-results-spread-object-assign-json-and-structuredclone">Predict shallow versus deep copy results: spread, Object.assign, JSON and structuredClone</a> (reported)</li><li><a href="https://uiround.com/questions/predict-es6-results-destructuring-defaults-spread-optional-chaining-and-nullish-coalescing">Predict ES6 results: destructuring defaults, spread, optional chaining and ?? versus ||</a> (reported)</li><li><a href="https://uiround.com/questions/implement-infinite-currying-sum-1-2-3">Implement infinite currying: sum(1)(2)(3)()</a> (reported)</li><li><a href="https://uiround.com/questions/predict-closure-results-counters-loops-captured-variables-and-lexical-scope">Predict closure results: counters, loops and captured variables</a> (reported)</li><li><a href="https://uiround.com/questions/center-an-element-horizontally-and-vertically-five-ways">Centre an element horizontally and vertically five ways</a></li><li><a href="https://uiround.com/questions/mark-up-an-accessible-signup-form-with-labels-a-fieldset-hints-and-error-messages">Mark up an accessible signup form with labels, a fieldset, hints and errors</a></li><li><a href="https://uiround.com/questions/build-a-controlled-form-with-dynamic-validation">Build a controlled form with dynamic validation</a></li></ul><h3>Round 5: HR (experienced)</h3><p>Salary, location and joining. A technical lead candidate noted that a project interview may follow soon after joining, so the evaluation doesn’t fully end at the offer.</p><h3>What makes Wipro different</h3><ul><li><strong>One flow, several fresher tracks.</strong> Elite NTH, TURBO and STAR share it; TURBO adds a voice round.</li><li><strong>A combined business discussion.</strong> Technical and HR in one interview.</li><li><strong>Basics for experienced hires.</strong> HTML, CSS and core JavaScript as much as React or Angular.</li><li><strong>A cooling-off rule.</strong> Three months between selections, 90 days between assessments.</li></ul><h3>A 4-week plan</h3><p><strong>Freshers:</strong> two weeks of aptitude and the essay, one week of array and string coding, and one week of OOP basics plus behavioural stories for the business discussion.</p><p><strong>Experienced, week 1:</strong> copying, destructuring, currying, closures and promises from the <a href="https://uiround.com/interview-questions/javascript">JavaScript</a> set.</p><p><strong>Experienced, week 2:</strong> semantic HTML, the box model, flexbox and accessible forms from the <a href="https://uiround.com/interview-questions/html">HTML</a> and <a href="https://uiround.com/interview-questions/css">CSS</a> sets.</p><p><strong>Experienced, weeks 3 and 4:</strong> React or Angular fundamentals, a small map-based app as a practice assignment, and a <a href="https://uiround.com/mock-interview?company=wipro#mock">Wipro-style mock interview</a>.</p><p><em>Loops vary by track, team and year. Treat single-candidate details as examples, not guarantees.</em></p><p>The full sourced breakdown, with every candidate write-up linked, is in the <a href="https://uiround.com/companies/wipro">UIRound Wipro guide</a>.</p><p><strong>Interviewed at Wipro recently?</strong> Drop your track and rounds in the comments. It helps the next person more than any guide can. And <strong>follow me</strong> for the next company breakdown.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0dea1cdf9cd8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Infosys Frontend Interview: Every Round, Every Question]]></title>
            <link>https://uiround.medium.com/infosys-frontend-interview-every-round-every-question-2d414551e64f?source=rss-4c20c8bc75d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d414551e64f</guid>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[infosys]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[interview]]></category>
            <dc:creator><![CDATA[UIRound]]></dc:creator>
            <pubDate>Sat, 21 Nov 2026 03:57:58 GMT</pubDate>
            <atom:updated>2026-11-21T03:57:58.020Z</atom:updated>
            <content:encoded><![CDATA[<p><em>HackWithInfy for freshers, a small live React build for experienced hires, and a managerial round about real delivery.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e39EyHP_i_brGn9ZWnIUng.jpeg" /></figure><p>Infosys runs two different loops for frontend roles. <strong>Freshers</strong> reach the higher-paying <strong>Specialist Programmer (SP)</strong> and <strong>Digital Specialist Engineer (DSE)</strong> roles through <strong>HackWithInfy</strong>, a three-hour algorithm contest, so the coding score comes first. <strong>Experienced React and Angular developers</strong> get one or two technical rounds, often with <strong>a small live build</strong>, then sometimes a managerial round and HR.</p><p>Here’s what each round tests, put together from public candidate reports. For every round, I’ve linked questions you can practise on <a href="https://uiround.com/companies/infosys">UIRound</a> in a browser editor, with the tests an interviewer would run.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rsRRTHB-q8dY68yXUv9nWg.jpeg" /></figure><h3>The loop at a glance</h3><ul><li><strong>Online coding round</strong> (freshers): HackWithInfy, three problems of rising difficulty, about 180 minutes, proctored.</li><li><strong>Technical interview</strong>: DSA, projects and CS basics for freshers; JavaScript plus React or Angular for experienced hires.</li><li><strong>Managerial or behavioural</strong> (experienced hires): delivery and team management.</li><li><strong>HR</strong>: salary, role and location, or motivation and relocation for freshers.</li></ul><p>Fresher interviews are short, usually <strong>20 to 45 minutes</strong>.</p><h3>Round 1: HackWithInfy (freshers)</h3><p>Algorithms: dynamic programming, graphs and greedy. One SP candidate got <strong>three DP problems and fully solved two</strong>; a DSE candidate fully solved one and partly solved two. The InfyTQ route (2023 batch) was a certification exam, then an “advantage round” of three coding problems, then the interview.</p><ul><li><a href="https://uiround.com/questions/solve-classic-string-questions-capitalize-words-character-counts-compression-and-anagram-groups">Solve classic string questions: capitalise words, character counts, compression and anagram groups</a></li><li>Use the <a href="https://uiround.com/interview-questions/data-structures-and-algorithms">DSA question hub</a> for DP and graphs in JavaScript.</li></ul><h3>Round 2: Fresher technical interviews</h3><ul><li><strong>SP:</strong> explain the <strong>travelling salesman problem</strong>, code the DP solution in 40 minutes and discuss improvements; why you chose your project’s technology, what went wrong, and how you settled a disagreement.</li><li><strong>DSE (HackWithInfy, about 35 min):</strong> real-world stacks and queues, BFS versus DFS, a global maximum across two arrays, frequency counts with a map, SQL joins, what a kernel is, internet protocols, and two-tier versus three-tier architecture. Feedback: improve BFS and DFS coding.</li><li><strong>DSE (InfyTQ, about 20 min):</strong> a walkthrough of the candidate’s React project, C++ types, structs versus classes and polymorphism, then failure and relocation.</li></ul><h3>Round 3: Experienced React technical round</h3><p>One video-call interview asked for <strong>code that calls an API</strong>, then lazy loading, code splitting and debounce, data flow between components, and a <strong>live build: render one component inside another, fetch data in the second, and pass it to the first</strong>. Then: explain componentDidMount and componentWillUnmount, and <strong>replicate the latter in a function component</strong>.</p><pre>function UserPanel() {<br>  const [users, setUsers] = useState([]);<br>  const [error, setError] = useState(null);<br>  useEffect(() =&gt; {<br>    const ctrl = new AbortController();<br>    fetch(&#39;/api/users&#39;, { signal: ctrl.signal })<br>      .then((res) =&gt; {<br>        if (!res.ok) throw new Error(`HTTP ${res.status}`);<br>        return res.json();<br>      })<br>      .then(setUsers)<br>      .catch((err) =&gt; {<br>        if (err.name !== &#39;AbortError&#39;) setError(err);<br>      });<br>    return () =&gt; ctrl.abort(); // componentWillUnmount<br>  }, []); // [] runs once, like componentDidMount<br>  if (error) return &lt;p role=&quot;alert&quot;&gt;Could not load users&lt;/p&gt;;<br>  return &lt;UserList users={users} /&gt;; // data flows down<br>}<br>function UserList({ users }) {<br>  return (<br>    &lt;ul&gt;<br>      {users.map((u) =&gt; &lt;li key={u.id}&gt;{u.name}&lt;/li&gt;)}<br>    &lt;/ul&gt;<br>  );<br>}</pre><p>The follow-ups:</p><ul><li><strong>“Why check </strong><strong>res.ok?&quot;</strong> fetch only rejects on network failure. A 404 or 500 still resolves.</li><li><strong>“Why abort in the cleanup?”</strong> So a late response can’t update an unmounted component, and the request stops.</li><li><strong>“How would the child send data back up?”</strong> Pass a callback prop, or lift state to the nearest shared parent.</li><li><strong>“Lazy load </strong><strong>UserList.&quot;</strong> React.lazy with a Suspense fallback, so it&#39;s split into its own chunk.</li></ul><p>Other reported prompts: hoisting, closures, promises, call/apply/bind, the event loop, shallow versus deep copy, useState and useEffect, stateless versus stateful components, <strong>map versus </strong><strong>forEach</strong>, semantic tags, responsive design and a Redux task. A 2025 Pune candidate with three years&#39; experience had a one-hour round on JavaScript, React, Redux and Git, rated easy to medium.</p><ul><li><a href="https://uiround.com/questions/implement-usefetch-with-loading-error-and-cancellation">Implement useFetch() with loading, error and cancellation</a></li><li><a href="https://uiround.com/questions/convert-a-class-component-with-lifecycle-methods-to-hooks">Convert a class component with lifecycle methods to hooks</a></li><li><a href="https://uiround.com/questions/implement-debounce-with-cancel-and-flush">Implement debounce() with cancel() and flush()</a></li><li><a href="https://uiround.com/questions/predict-map-versus-foreach-results-return-values-chaining-mutation-holes-and-early-exit">Predict map versus forEach results: return values, chaining, mutation and early exit</a></li><li><a href="https://uiround.com/questions/predict-shallow-versus-deep-copy-results-spread-object-assign-json-and-structuredclone">Predict shallow versus deep copy results</a></li><li><a href="https://uiround.com/questions/implement-function-prototype-bind-including-partial">Implement Function.prototype.bind(), including partial application</a></li><li><a href="https://uiround.com/questions/predict-the-event-loop-order-of-settimeout-promises-queuemicrotask-and-await">Predict the event-loop order of setTimeout, promises, queueMicrotask and await</a></li></ul><h3>Round 4: Experienced Angular technical round</h3><p>Lifecycle hooks, pipes, @Input and @Output, passing data between components, directives, lazy loading, bindings, <strong>routing and guards</strong>, ngStyle syntax, media queries, CSS position, flexbox, authentication versus authorisation, and setTimeout output questions. Angular openings are common at Infosys, so check which framework the job description names.</p><ul><li><a href="https://uiround.com/questions/write-mobile-first-media-queries-for-a-product-listing-page-two-three-and-four-columns-and-a-filter">Write mobile-first media queries for a product listing page</a></li></ul><h3>Round 5: Managerial and HR</h3><p>The 2025 Pune candidate was asked how they’d handle <strong>a last-minute client change during UAT</strong>, and how to <strong>reuse a React web app’s payment feature in a mobile app without rewriting it</strong>. Others were asked how they managed tasks, what Agile is, and how they led a team. HR covers salary, role and location for experienced hires; role models, failure and relocation for freshers.</p><h3>What makes Infosys different</h3><ul><li><strong>The contest decides fresher roles.</strong> HackWithInfy scores lead to SP or DSE interviews.</li><li><strong>A small live React build.</strong> Fetching data and passing it between components comes up repeatedly.</li><li><strong>Angular is common.</strong> Read the job description before you prepare.</li><li><strong>Short fresher interviews.</strong> 20 to 45 minutes, so answers must be crisp.</li></ul><h3>A 4-week plan</h3><p><strong>Freshers:</strong> two weeks of DP, graphs and greedy in a timed contest format, one week of CS basics (OS, networks, DBMS, OOP), and one week on your projects and behavioural answers.</p><p><strong>Experienced, week 1:</strong> JavaScript fundamentals from the <a href="https://uiround.com/interview-questions/javascript">JavaScript</a> set: hoisting, closures, bind, the event loop and copying.</p><p><strong>Experienced, week 2:</strong> React or Angular fundamentals: lifecycle and hooks, data flow, lazy loading, routing and guards.</p><p><strong>Experienced, weeks 3 and 4:</strong> small live builds (fetch, pass data, handle errors) in 20 minutes each, two delivery stories, and an <a href="https://uiround.com/mock-interview?company=infosys#mock">Infosys-style mock interview</a>.</p><p><em>Loops vary by track, team and year. Treat single-candidate details as examples, not guarantees.</em></p><p>The full sourced breakdown, with every candidate write-up linked, is in the <a href="https://uiround.com/companies/infosys">UIRound Infosys guide</a>.</p><p><strong>Interviewed at Infosys recently?</strong> Drop your track and rounds in the comments. It helps the next person more than any guide can. And <strong>follow me</strong> for the next company breakdown.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d414551e64f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TCS Frontend Interview: Every Round, Every Question]]></title>
            <link>https://uiround.medium.com/tcs-frontend-interview-every-round-every-question-5f3408182af8?source=rss-4c20c8bc75d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f3408182af8</guid>
            <category><![CDATA[tcs-digital]]></category>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[UIRound]]></dc:creator>
            <pubDate>Fri, 20 Nov 2026 15:08:41 GMT</pubDate>
            <atom:updated>2026-11-20T15:08:41.631Z</atom:updated>
            <content:encoded><![CDATA[<p><em>One test, three fresher tracks, OOP and SQL for freshers, and a React or Angular scenario for experienced hires.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sclo8h6M_9pb1Zw8dY1jwQ.jpeg" /></figure><p>TCS runs two very different frontend interviews. <strong>Freshers</strong> take the <strong>NQT</strong>, and their score decides the track: <strong>Ninja, Digital or Prime</strong>. Their interviews are mostly OOP, databases and a language of their choice, not frontend. <strong>Experienced hires</strong> get a short, focused round on <strong>JavaScript and React or Angular fundamentals</strong>, often with a realistic app scenario to outline.</p><p>Here’s what each round tests, put together from public candidate reports from 2022 to 2024. For every round, I’ve linked questions you can practise on <a href="https://uiround.com/companies/tcs">UIRound</a> in a browser editor, with the tests an interviewer would run.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NIOBX15U9EiFoE8zxdRJXQ.jpeg" /></figure><h3>The loop at a glance</h3><ul><li><strong>NQT</strong> (freshers, proctored): aptitude, reasoning, verbal ability and coding. About three hours in a 2023 write-up.</li><li><strong>Technical interview</strong>: OOP, DBMS and a language for freshers; JavaScript plus React or Angular for experienced hires.</li><li><strong>Managerial interview</strong>: why TCS, teamwork, Agile, relocation, shifts and notice period.</li><li><strong>HR interview</strong>: documents for freshers; salary, location and joining date for experienced hires.</li></ul><p>Freshers sometimes meet the technical, managerial and HR panel <strong>in one sitting</strong>. A 2022 React technical round took 30 to 35 minutes; the managerial round, 10 to 15.</p><h3>Round 1: NQT (freshers)</h3><p>A 2023 candidate who cleared both Ninja and Digital describes <strong>part 1</strong> (aptitude, logical reasoning and verbal, easy to moderate, no going back) and <strong>part 2</strong> (harder versions plus <strong>two moderate-to-hard coding questions</strong>, optional for Ninja-only candidates). <strong>Coding is where Digital and Prime calls are won</strong>, so practise it seriously.</p><ul><li><a href="https://uiround.com/questions/solve-classic-array-questions-second-largest-missing-number-duplicates-move-zeros-and-rotate">Solve classic array questions: second largest, missing number, duplicates, move zeros</a></li><li><a href="https://uiround.com/questions/check-whether-two-strings-are-anagrams">Check whether two strings are anagrams</a></li></ul><h3>Round 2: Fresher technical interviews</h3><p>These aren’t frontend interviews:</p><ul><li><strong>Ninja (2023, virtual, 20 to 30 min, offer in 2 to 3 weeks):</strong> DBMS versus RDBMS, DDL and DML, indexing, basic Python, the four pillars of OOP, relocation and night shifts.</li><li><strong>Digital (2023, face to face, about three months to selection):</strong> Python lists versus tuples, decorators and slicing; the third-largest number with and without sorting; bubble sort; git stash and pull; SQL joins on example tables; projects.</li><li><strong>Prime (2024):</strong> a multiple-inheritance program, call by value versus reference, static, DELETE versus DROP, normalisation, views and indexes, internship work, and why TCS.</li></ul><p>The Prime candidate’s advice: <strong>know the basics of every skill on your resume, and list only what you can defend.</strong></p><h3>Round 3: Experienced React technical round</h3><p>A 2022 candidate with 3 to 6 years’ experience was asked about their React version, state and mutation, useEffect, Redux data flow, arrow functions, and spread versus rest. Then a scenario: <strong>design a loan management app</strong> where, after login, <strong>three side-by-side sections fetch user details, loan details and the next repayment date</strong>, with a button to a public loan types page. A clean outline looks like this:</p><pre>function LoanDashboard({ userId }) {<br>  const base = `/api/users/${userId}`;<br>  const user = useFetch(base);<br>  const loans = useFetch(`${base}/loans`);<br>  const next = useFetch(`${base}/next-repayment`);<br>  return (<br>    &lt;main className=&quot;dashboard&quot;&gt;<br>      &lt;Section title=&quot;Your details&quot; {...user}&gt;<br>        {(u) =&gt; &lt;p&gt;{u.name} · {u.email}&lt;/p&gt;}<br>      &lt;/Section&gt;<br>      &lt;Section title=&quot;Your loans&quot; {...loans}&gt;<br>        {(list) =&gt; &lt;LoanList loans={list} /&gt;}<br>      &lt;/Section&gt;<br>      &lt;Section title=&quot;Next repayment&quot; {...next}&gt;<br>        {(r) =&gt; &lt;Due date={r.dueDate} amount={r.amount} /&gt;}<br>      &lt;/Section&gt;<br>      &lt;Link to=&quot;/loan-types&quot;&gt;Explore loan types&lt;/Link&gt;<br>    &lt;/main&gt;<br>  );<br>}<br>function Section({ title, data, error, loading, children }) {<br>  if (loading) return &lt;Skeleton title={title} /&gt;;<br>  if (error) return &lt;ErrorCard title={title} /&gt;;<br>  return &lt;section&gt;&lt;h2&gt;{title}&lt;/h2&gt;{children(data)}&lt;/section&gt;;<br>}</pre><p>The follow-ups:</p><ul><li><strong>“Why three requests, not one?”</strong> They run in parallel, and one slow or failing API doesn’t blank the whole page.</li><li><strong>“Where does the login token go?”</strong> In the fetch layer, not in each component, and in an HttpOnly cookie rather than localStorage if you can.</li><li><strong>“The loan types page is public.”</strong> Keep it outside the authenticated route guard.</li><li><strong>“Caching?”</strong> A data-fetching library such as React Query, so going back doesn’t refetch everything.</li></ul><p>Other reported React prompts: pure functions, props versus state, closures, promises, <strong>writing a custom hook</strong>, an anagram check, <strong>adding two numeric strings</strong>, and <strong>building a carousel</strong>.</p><ul><li><a href="https://uiround.com/questions/implement-usefetch-with-loading-error-and-cancellation">Implement useFetch() with loading, error and cancellation</a></li><li><a href="https://uiround.com/questions/add-and-multiply-huge-integers-given-as-strings-digit-by-digit">Add and multiply huge integers given as strings</a></li><li><a href="https://uiround.com/questions/build-an-accessible-carousel-with-autoplay-that-pauses-on-hover-and-focus-swipe-and-reduced-motion">Build an accessible carousel with autoplay</a></li><li><a href="https://uiround.com/questions/convert-a-class-component-with-lifecycle-methods-to-hooks">Convert a class component with lifecycle methods to hooks</a></li><li><a href="https://uiround.com/questions/predict-the-output-of-loop-timer-promise-hoisting-and-closure-snippets">Predict the output of loop, timer, promise, hoisting and closure snippets</a></li><li><a href="https://uiround.com/questions/implement-promise-all-from-scratch">Implement Promise.all() from scratch</a></li></ul><h3>Round 4: Experienced Angular technical round</h3><p>Lifecycle hooks, @Input and @Output, data binding types, pipes, dependency injection, routing, the bootstrapping process and ES6. Prompts: <strong>write code using promises and observables</strong>, <strong>outline an Angular migration plan</strong>, and name features removed in HTML5.</p><h3>Round 5: Managerial and HR</h3><p><strong>Managerial (React, 2022):</strong> why you’re leaving, why TCS when you’re already at a large company, Agile or Waterfall, relocation and notice period. <strong>Angular:</strong> why you want a change, what you need to improve, and how you’d handle a delivery scenario.</p><p><strong>HR:</strong> for freshers, registration number, 10th and 12th marksheets, backlogs, ID checks, and willingness to work shifts anywhere. For experienced hires, salary. One HR call came the day after the technical and managerial rounds.</p><p>Read the <a href="https://uiround.com/guides/behavioral-interview-frontend">behavioural interview guide</a>.</p><h3>What makes TCS different</h3><ul><li><strong>One test, three tracks.</strong> NQT coding decides whether you’re interviewed for Ninja, Digital or Prime.</li><li><strong>Freshers aren’t asked frontend.</strong> OOP, DBMS, SQL and a language, unless your resume invites it.</li><li><strong>Experienced hires get a scenario.</strong> Outline a small app cleanly, not just answer trivia.</li><li><strong>Timelines vary.</strong> Some offers came in weeks; others took months.</li></ul><h3>A 4-week plan</h3><p><strong>Freshers:</strong> two weeks of aptitude and NQT-style coding, one week of OOP, DBMS and SQL, and one week defending every line of your resume.</p><p><strong>Experienced, week 1:</strong> JavaScript fundamentals: closures, promises, spread and rest, pure functions, and numeric-string addition.</p><p><strong>Experienced, week 2:</strong> React or Angular fundamentals: state, effects, Redux flow, or lifecycle hooks, DI and observables.</p><p><strong>Experienced, weeks 3 and 4:</strong> outline three small apps (a loan dashboard, a carousel, a data table) in 20 minutes each, then run a <a href="https://uiround.com/mock-interview?company=tcs#mock">TCS-style mock interview</a>.</p><p><em>Loops vary by track, team and year. Treat single-candidate details as examples, not guarantees.</em></p><p>The full sourced breakdown, with every candidate write-up linked, is in the <a href="https://uiround.com/companies/tcs">UIRound TCS guide</a>.</p><p><strong>Interviewed at TCS recently?</strong> Drop your track and rounds in the comments. It helps the next person more than any guide can. And <strong>follow me</strong> for the next company breakdown.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f3408182af8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>