🎯 Frontend Interview Experience with Tessell

tessell logo
tessell
Frontend Developer1 years
May 6, 20253 reads

Summary

I recently interviewed with Tessell for a frontend developer role, completing several technical and behavioral rounds. Although I received a verbal offer, I ultimately declined it for a better opportunity that aligned with my long-term goals.

Full Experience

Hi everyone, I'm a frontend developer with over 1+ year of experience working with React, Next.js, and JavaScript. I recently had the opportunity to interview with Tessell, a startup I’ve always admired, and wanted to share my interview journey here on LeetCode Discuss to help or inspire others preparing for frontend roles.

🧩 Interview Rounds at Tessell

  1. Initial HR Screening The process kicked off with an HR call where we discussed basic details like current/expected CTC, notice period, and availability. It set the tone for what turned out to be a long yet well-structured process.

  2. Technical Round – JavaScript & React Focus This round went deep into JavaScript fundamentals and React concepts. Topics included:

Lifecycle methods

State management approaches (Redux, Context API)

Performance optimizations (memoization, lazy loading, etc.)

Best practices in component architecture

  1. DSA Round – Medium-Level Challenges The second round tested my algorithmic skills through JavaScript coding. Problems were medium level and tested my approach to clean and efficient code. This is where consistent LeetCode practice helped a lot.

  2. Engineering Manager Round – Tech + Behavioral This was a mix of system-level questions and behavioral discussion. I had to walk through:

Key decisions in past projects

Real-world optimizations and architecture choices

A hard-level DSA question on trees, 📌 One of the similar types of problems discussed was Binary Tree Maximum Path Sum https://leetcode.com/problems/binary-tree-maximum-path-sum/description/ – definitely worth practicing!

  1. Final HR Discussion After clearing all rounds, the HR shared a verbal offer. However, shortly after, I received another offer that aligned better with my long-term goals and recognized my value based on skill, not just current CTC.

✨ Reflections & Learnings Although I ultimately didn’t accept Tessell’s offer, I left the process with immense respect for their team and interview structure. It helped me grow technically and reaffirmed some key career truths:

🧠 Key Takeaways Know your worth: Your skills are more important than your current salary.

Stay interview-ready: Balance your DSA prep with real-world frontend knowledge.

Explore options: More offers = better clarity and confidence.

Communicate professionally: Whether it’s a yes or no, always respond with maturity.

Think long-term: Choose opportunities aligned with your values and growth path.

🙌 Final Thoughts This experience was a reminder that interviews are not just about getting an offer — they’re opportunities to reflect, improve, and clarify your goals. I'm grateful to Tessell for the chance, and who knows — our paths might cross again in the future.

Good luck to everyone preparing — keep learning, keep coding!

Interview Questions (1)

Q1
Binary Tree Maximum Path Sum (Similar Problem)
Data Structures & AlgorithmsHard

In the Engineering Manager round, I had a hard-level Data Structures & Algorithms question on trees. I noted that one of the similar types of problems discussed and worth practicing is Binary Tree Maximum Path Sum.

Preparation Tips

Consistent LeetCode practice helped me a lot with the DSA rounds.

Discussion (0)

Share your thoughts and ask questions

Join the Discussion

Sign in with Google to share your thoughts and ask questions

No comments yet

Be the first to share your thoughts and start the discussion!