Recent posts tagged coding-interview

Level UI • 23 hours • in Articles • 9 min read
Somewhere in the last year, "do we need an MCP server?" joined the list of questions that arrive in a brief before anyone has said what the thing is for. It is usually framed as MCP vs API, as though the Model Context Protocol were a newer kind of AP...
post-cover-33074
  • ai
  • api
  • webdev
  • security
James Dayalverified • Oct 9 • in Dev Stories • 10 min read
📝 DEV STORY
Featuring:Igor GanapolskyIgor Ganapolsky•Founder and Forward Deploy AI Engineer at ThumbGate
Interviewed by: Mehadi Hasanhttps://coderlegion.com/user/Mehadi+Hasan Guest: Igor Ganapolskyhttps://coderlegion.com/user/IgorGanapolsky Role: Founder & Forward Deploy AI Engineer, ThumbGate Location: Florida, USA Website: igorganapolsky.comht...
post-cover-30520
  • devstories
  • coding-interview
Steven Stuart • Oct 8 • in Articles • 9 min read
Coding tests can effectively filter out candidates who can't write working code. That's a legitimate purpose. The problem emerges when organizations test for timed algorithm-puzzle skills in roles that require entirely different capabilities: system ...
post-cover-30343
  • software-engineering
  • software-development
  • coding-interview
  • interview
linkjobai-max • Sep 15 • in Articles • 5 min read
A technical interview rarely follows a straight line. You suggest a solution, the interviewer changes a constraint, and suddenly the most important part of your original answer no longer applies. The challenge is keeping your explanation aligned with...
post-cover-27239
  • ai
  • jobs
  • coding-interview
  • rust
Frank-Four-Leaf • Aug 22 • in Articles • 6 min read
Four-Leaf's SQL Interview Guide1 Key takeaways A SQL interview is a translation test. The syntax is the easy half, and most candidates who fail were fluent in SQL. What sinks them is starting to type before the question is pinned down, or writing a...
  • sql
  • coding-interview
  • datascience
prakhar_srv • May 28 • in Articles • 4 min read
I had written recursive preorder, inorder, and postorder more times than I could count, three lines and a base case each. Then an onsite asked for postorder without recursion, and I blanked, pushing nodes onto a stack and popping them in the wrong or...
post-cover-19164
  • programming
  • coding-interview
  • leetcode
  • learning
prakhar_srv • May 26 • in Articles • 6 min read
I'd solved around 80 tree problems by the time my second on site interview wrapped up. Most were mediums. Preorder, inorder, postorder, level order felt like second nature. Tree height and BST validation, written from scratch, half a dozen times each...
post-cover-19004
  • algorithms
  • leetcode
  • coding-interview
  • programming
prakhar_srv • May 25 • in Articles • 7 min read
The tree round on my first onsite was Root to Leaf Paths. Enumerate every root-to-leaf path in a binary tree. Looked easy. The recursion took about four minutes to write. Running it on the sample input came back with a list where every path ended at ...
post-cover-18882
  • coding-interview
  • algorithms
  • leetcode
  • programming
prakhar_srv • May 25 • in Articles • 7 min read
Three months of practicing binary search trees on paper. Search procedure memorised. Insertion procedure memorised. Three deletion cases memorised. Then came the onsite. The interviewer drew a tree on the whiteboard, asked for an insertion walkthroug...
post-cover-18867
  • coding-interview
  • leetcode
  • algorithms
  • beginner
prakhar_srv • May 23 • in Articles • 5 min read
The Big O table was memorised before the first onsite. Binary search logarithmic, merge sort linearithmic, hash insert constant amortised. All recitable. Then a senior engineer wrote a recursive function on the whiteboard, asked for an analysis, and ...
post-cover-18747
  • leetcode
  • coding-interview
  • algorithms
  • beginner
prakhar_srv • May 22 • in Articles • 3 min read
For a long time I treated BFS and DFS as interchangeable. Two ways to visit every node, pick whichever came to mind first. Then an interview handed me a grid that wanted the minimum number of steps, and a recursive DFS felt faster to type, so that's ...
post-cover-18704
  • leetcode
  • coding-interview
  • algorithms
  • dsa
prakhar_srv • May 21 • in Articles • 5 min read
For a long stretch, backtracking was the topic I quietly dreaded. The recursion was easy enough to write. The code ran. It even returned answers. They were just wrong, and not in a way that threw an error you could chase. A Combination Sum solution w...
post-cover-18581
  • leetcode
  • coding-interview
  • algorithms
  • data-structures
yogirahul • May 21 • in Articles • 1 min read
Recently while practicing interval problems, I noticed something interesting: A lot of interview questions are actually small twists of the same underlying pattern. Take the classic Merge Intervals problem: intervals = 1,3, 2,5, 6,8, 7,9 The fir...
post-cover-18565
  • python
  • algorithms
  • systemdesign
  • coding-interview
prakhar_srv • May 20 • in Articles • 3 min read
The first time an interviewer asked me to walk through an LR rotation on a whiteboard, the four-case table was memorised cold. LL, RR, LR, RL. The interviewer drew three nodes, asked which case it was, and the answer came out fast. Then they asked: "...
post-cover-18486
  • algorithms
  • coding-interview
  • leetcode
  • data-structures
Posted in open-fintech-builders group
Pocket Portfolio • May 18 • in Articles • 3 min read
Interview: Pocket Portfolio × CoderLegion 1. An Overview of Your Professional Trajectory in Software Development My introduction to programming commenced at age fifteen with Java, spanning from Standard to Enterprise editions J2SE to J2EE at Emerg...
post-cover-18220
  • coderlegion
  • programming
  • coding-interview
  • webdev
prakhar_srv • May 12 • in Articles • 6 min read
After treating every FAANG company like the same interview, Amazon exposed the gap in about twenty minutes. I'd built FAANG prep around a small set of pattern families that looked highest-frequency: predicate search, sliding window, hash table funda...
post-cover-17592
  • coding-interview
  • algorithms
  • dsa
  • leetcode
prakhar_srv • May 11 • in Articles • 7 min read
I thought solving the problem was the round. The last ten minutes turned out to be the part that counted. I'd put close to four months into Amazon prep by the time my onsite landed. Two coding rounds went fine. The third started fine too. I solved ...
post-cover-17439
  • leetcode
  • coding-interview
  • algorithms
  • career
prakhar_srv • May 10 • in Articles • 5 min read
It took an LRU Cache interview for me to realise the complexity table wasn't answering the real question. I'd been picking between arrays and linked lists for years before realising the table wasn't the answer to the question. Then LRU Cache came ...
post-cover-17281
  • dsa
  • leetcode
  • coding-interview
  • beginners
prakhar_srv • May 9 • in Articles • 7 min read
After 280 LeetCode problems, I realised “feeling ready” wasn’t a metric. A diagnostic was. I'd solved around 280 problems by the time the FAANG readiness question got serious, and the answer changed every week. Some weeks felt close after a clean ba...
post-cover-17163
  • leetcode
  • coding-interview
  • dsa
  • algorithms
prakhar_srv • May 7 • in Articles • 6 min read
I'd solved around 300 problems by the time my third senior screen wrapped up. The medium that had just bombed the call was something I could explain back to myself in 90 seconds once it ended. The constraints were familiar. The technique was one anyo...
post-cover-16965
  • programming
  • leetcode
  • coding-interview
  • algorithms
prakhar_srv • May 6 • in Articles • 5 min read
I'd written the BFS in about eight minutes. The interviewer ran the example I'd traced and said "ok, but how do you know this is right for any input?" My instinct was to point at the code. Pointing wasn't an argument. The silence stretched, and the r...
post-cover-16892
  • programming
  • coding-interview
  • leetcode
  • algorithms
chevron_left
🔥 30 posts • 👩‍💻 12 active writers

✨ Want to write in this topic?
Share your learning. Get discovered. Build your profile.
Join CoderLegion

💡 Why developers use CoderLegion
Track learning • Share posts • Get ranked publicly
Create your profile