I’ve been through the IPTV rollercoaster over the last 3 years.
If you’re in the US or Canada and have tried IPTV before, you probably know the drill: buffering during big games, random shutdowns, scammy sellers, and support that disappears the second you pay.

After wasting money on at least 7 different providers, I finally found one that actually works the way an IPTV service should: WeSellIPTV.com.

🔥 Why I Call WeSellIPTV the Best IPTV in the USA (and Canada)

• 36-Hour Free Trial (No Credit Card) → You can test the service risk-free before paying a dime.

• 22,000+ Live Channels → Full coverage of USA & Canadian local networks (ABC, NBC, FOX, CBS, CBC, CTV, TSN, Sportsnet, etc.) plus international.

• 160,000+ VOD Movies & TV Shows → Constantly updated library with HD & 4K quality.

• 100% Working EPG (TV Guide) → Looks just like a real cable guide with live programming schedules.

• Up to 5 Connections → Stream on Firestick, Smart TV, phone, and laptop at the same time.

• 24/7 Customer Support → Live chat + email support that actually replies within minutes.

• 99.9% Uptime Servers → I’ve watched NFL RedZone, NBA Playoffs, NHL, UFC PPV, and never had buffering.

• 7-Day Money-Back Guarantee → If you don’t like it, they refund you. No shady tricks.

This combination makes it (in my opinion) the #1 IPTV subscription for 2025 in North America.

📊 IPTV Pricing Plans (USA & Canada)

👉 Every plan includes 22K live channels, 160K+ VOD, EPG, 24/7 support, and PPV sports.
👉 Pro tip: The 1-year or 2-year plans save the most money.

📺 What You Actually Get with WeSellIPTV

• Local USA IPTV Channels → All major networks, news, and regional sports in HD.

• Canadian IPTV Channels → CBC, CTV, Sportsnet, TSN, and local stations.

• Sports IPTV Coverage → NFL, NBA, NHL, MLB, UFC, WWE, Boxing, PPV events included.

• VOD Streaming → 160K+ movies and TV shows on demand, no extra apps needed.

• Kids & Family → Disney, Nickelodeon, Cartoon Network, 24/7 cartoon channels.

• International Channels → UK, Europe, Latin America, Asia, Middle East.

For me, it literally replaced cable TV + Netflix + sports subscriptions all in one.

⚡ Device Compatibility

WeSellIPTV runs smoothly on:

• 🔥 Amazon Firestick / Fire TV

• 📱 Android & iOS smartphones

• 🖥️ Windows & macOS laptops

• 📺 Smart TVs (Samsung, LG, Android)

• 📦 MAG, Formuler, Enigma2 Boxes

• 🌐 Works with VPN (no IP lock)

Setup took me less than 10 minutes with IPTV Smarters and Tivimate.

🧠 FAQs (Quick Answers)

Q: Is this IPTV really reliable in the USA?
Yes. I’ve streamed in New York & LA with no buffering. Other users in Toronto and Vancouver report the same.

Q: Do they refund if I don’t like it?
Yep. There’s a 7-day money-back guarantee.

Q: How’s the sports coverage?
All major leagues (NFL, NBA, NHL, MLB) + PPV events. No extra fees.

Q: Does it work on Firestick?
Yes, it’s one of the best IPTV services for Firestick with full EPG support.

Q: Can I watch on multiple devices?
Up to 5 connections depending on your plan.

✅ Final Verdict

I’ll keep it simple:
If you’re looking for the best IPTV provider in the USA or Canada in 2025, with no buffering, huge VOD library, and reliable support — WeSellIPTV is the one.

Start with the free trial → WeSellIPTV.com
No credit card, no risk. Just test it out.

💬 Has anyone else here tried WeSellIPTV? I’d love to hear your experience and see how it compares to other IPTV providers you’ve tested.

Hi everyone,

I created aGithub repository (here)consisting all the resources that helped me get my dream role at one of the FAANG companies and wanted to share the list, so others can make the most out of it. I have shared the resources from scratch and it is a beginner friendly repository.

Please do check it out and let me know if it helps you with your prep, any feedback would be really helpful!

Hope it helps :)

I was invited to do a Byteboard interview and had trouble finding detailed testimonials in preparation, so I want to record my experience here for posterity.

For background, I have worked as a software developer for 2 yrs and did a lot of coding before that, but I'm not a CS major and tend to suffer from "brain freeze" on technical screens. I took the assessment in C++.

The interview was around 1.5 hrs. The first shorter part was a project description with some questions to answer, e.g. which deployment strategy would you choose out of 3 options (no right answer) and some implementation questions with various levels of detail. It was a surprisingly high-level project with the strategy question veering into management.

The second part was coding and was loosely based on the first, though there were significant simplifications/assumptions. There was already a lot of code in place (though nothing that was difficult to understand--mainly laying out the objects) and a testcase provided that would automatically assess your code. There were 3 tasks of increasing open-endedness. I thought the requests were pretty reasonable given the time constraint. I finished the first task, got most of the way through the second task (I couldn't get one library function to work), and made a bit of progress on the third--mostly spent time commenting on the approach and laying the groundwork.

I also spent some time commenting on simplifications they made that I didn't feel were realistic and explaining how I would change the code structure to accommodate.

After time was up, there was up to 15 minutes to tell them what you would have worked on next (optional).

Overall, I loved this format. It was much more similar to my work as a software developer than traditional tech screens: greater focus on open-ended decision-making than algorithm tricks. I also liked the written format because it allowed me to polish my answers before anyone saw them (on the spot I would have rambled a lot). I spent more time speculating on implementation trade-offs than writing code and giving concrete answers, but according to the recruiter I did very well! I would 100% choose this option again over a tech screen if given the choice and recommend it for people with more "real-world" experience who struggle with tech screens.

I have been lucky to crack the interviews at Google, Facebook & Amazon at different times in my career. Here are my four cents on the preparation.

Data Structures & Algorithms :

I gave lot of importance to building the technical depth on data structures during my university.

To build technical depth and learn how to solve problem gradually, GeeksforGeeks and Cracking the coding interview book are good resources. I solved all the problems from cracking the coding interview book and went through around 200 questions on GeeksforGeeks.

Real Interview Questions :

To practice further, solve real interview questions from companies that you are targeting. LeetCode is a very good resource for that. I solved around 100 easy, 300 medium and 50 hard problems from LeetCode.

Coding speed :

Many people think that interviewers would challenge them with a couple of questions and if they provide the answer maybe with code, and then it was done. So it’s all about whether they can solve the problem or not.

People don’t realize the importance of coding speed until they fail several coding interviews in a row with very similar reason. People were pretty good at coming up with solutions, however, it could take them half an hour to complete the code. There are many people with the same frustration.

Normally, candidates will be asked one to two questions per interview (~45min) and most likely coding is required. In other words, we only have less than 20min per question (removing “trash time” in the beginning and end), which is more challenging than it seems to be.

In addition, a lot of people don’t even pay attention to coding speed. They don’t have the mindset that finishing the code in a short period of time is equally important as solving the problem itself. This is because if we don’t have enough time to code in an interview, it’s as bad as we fail to solve the problem.

Mock Interview :

Depending on how you learn stuff, you can take mock interviews throughout or take mock interview at the end. It's a great experience for you to practice in a way where you can't fail. Personally mock interview is the most effective approach.

I did several mock interviews during my preparation, sometimes with a friend, sometimes I took paid service and interviewed with professionals. There are many such services available online. I used ExpertMitra which provides System Design mock interview along with Coding & Data Structures and objected oriented design interview.

The first and most important thing to do is to master the fundamentals. For technical interviews, there are only so many topics you can prepare.

These topics generally:

Data Structures and Algorithms

Systems Design

Behavioural problems

Being fluent in one of the coding languages is one of the conditions for getting started with technical interview preparation. Different companies/teams utilise different languages depending on their needs, but you don't have to be fluent in all of them. Rather, choose the one with which you are most comfortable, prepare everything in that language, and study the rest as needed. However, if the job description specifies which language an excellent applicant for that post should be fluent in, you may need to concentrate on that.

When studying for DSA (Data Structures and Algorithms), you should concentrate on the following topics:

• Data Structures: Linked Lists, Trees, Stacks, Queues, Heaps, Graphs, Hash Tables, etc.

• Algorithms: Breadth-First Search, Depth-First Search, Binary Search, Merge Sort, Quick Sort, etc.

• Concepts: Big O Time & Space, Bit Manipulation, Memory (Stack vs Heap), Dynamic Programming, Recursion, String Manipulation, etc.

There are t****wo methods for putting them into practice.

1. Choosing a single topic for a set period of time, like a week, and only practise questions on that topic for that week. This will assist you in thoroughly preparing for that topic and provide you with a complete understanding of all the simple, medium, and difficult questions that may be asked.

2. In a single day/week, choose numerous topics and answer multiple questions about them at the same time. While you may not have in-depth knowledge of every topic right away, you will have covered a wide range of topics and become acquainted with them.

There are numerous approaches to putting these concepts into practice. You can practise these problems by participating in contests on websites like Leetcode and Hackerrank. While studying, you might also work on your own projects to gain hands-on experience with the areas you've selected. You can opt for the course which primarily focuses on Interview preparation for fanng companies like Logicmojo. They help with the preparation of technical questions, behavior questions, resume building, and mock interviews. You can choose any one of these based on your capabilities.

Hi all,

I wanted to write about my experience, because before I went through my coding round, I read and searched for many others experience, and it helped me a lot. I will try to keep an eye on this thread in case people have questions I can answer, but I will try to be as detailed as I can.

Role

The role I interivewed for was the Meta Rotational Program. Information about this role can be found here: https://www.metacareers.com/careerprograms/pathways/re

Basically it looks for software engineers with 2+ years of work experience and non tradiational background. This was me. I did a coding bootcamp, and I have a little over 2 years on job experience.

Coding Interview/Experience

My interviewer was about 5 minutes late, but he made sure he included this time in my interview. He didn't ask for a brief introduction that I read usually initiates the meeting(my guess would be because he was slightly late), but he instead he just copied and pasted the first question.

First Question

My first question was this medium question: https://leetcode.com/problems/custom-sort-string/description/. I read the question to myself a few times. Then I read the question out loud. Then i asked/reiterated to the interview what I think the problem is asking, and he said yes that's correct. Once he confirmed I did understand the problem, I wrote psuedo code. The interviewer did not seem to get some of my steps on my psuedo code, but I continued to actually coding the problem. Then as I was coding and talking out loud about my code, I realized I wasn't quite doing it correctly. This increased my nerves. The interviewer attempted to throw a hint my way, but this made me more confused. I politely voiced this, and then he tried saying what he was trying to hint at me by giving another test case. This helped way more and I saw what I was missing in my thought process. Then I was able to solve the problem! I also gave the time and space complexity too.

Note: I think something I could've done better here is present other test cases. Because he did this himself, I just used the ones he gave to run through my code. I'm not sure if this hurt me or not, but it's not something I did, and I wonder if that was noted.

Second Question

My second question was this easy question: https://leetcode.com/problems/valid-word-abbreviation/description/

I did the same process that I explained above, but I ran out of time in completely solving this problem. However I think the interviewer could understand what I was planning to do because of my psuedo code and what I did end up coding. I did have a bug that I caught, but it also seems like he was drawing my attention to another bug, but like I said i ran out of time.

Feelings after interview

I prepared for this interview for about a month. I was nervous, but I knew I knew a lot with what I studied, but I also knew that I didn't know everything. I just wanted to do my best, and I felt I did that. I answered one competely, and I am fairly confident that I answered it right, and then the second question I didn't fully complete, but I was happy with what I did show I knew on the problem.

Result

I unfortunately did not get to proceed to the next round which would be the final round, Full Loop. I was pretty bummed because I felt I did pretty well. I knew it wasn't perfect, but I felt like I showed that I knew quite a bit on coding and problem solving. This was disappointing, but I am not going to give up and defintley will try again!

Salary

I was told the base salary was 173k, the signing bonus was 30k, the relocation package was 16k, but there was no stock options. I was told the location was in Menlo Park, California, and it was 3 days in the office. The program was a year with a solid chance of becoming a permant engineer at Meta.

If you have any questions please feel free to ask and all the best in your interview journey!!

Lots of aspiring Software engineers work hard to excel in the coding interviews. They spend hours after hours on Leetcode or reading up on DSA but end up without the job offer. I think a majority of the preparation strategies are fundamentally flawed.

First, some background to add credibility. In college, I applied for internships at Google, MSFT, Amazon and Goldman but did not get into any of them. A year later, I applied for MSFT, Uber, Goldman and got offers from all of them. A year after that, I got an offer from Google.

For most tasks, output = input * (efficiency). Most people try to optimize for input by working hard. But, what you really want to optimize is output. You do this by working smart, i.e, improving efficiency.

For example, people try to solve lots of problems with the hope that they'll see the same problem in an interview. This is a sub-optimal strategy. Most interviewers are armed with tweaks to the problem as follow ups and are good at identifying if you have the solution memorised.

Solving lots of problems isn't bad. In-fact, I recommend it. However, the reason to do that is not to memorize solutions. Instead it is to identify common patterns across problems which are extensible to a larger set of problems.

Do not memorize how to find the maximum of the sum of values for all root to leaf paths in a tree. No one wants you to do that. Instead, understand how and why Dynamic programming (DP) works and learn to recognise the situations in which DP on trees can be helpful.

There are countless resources on the web to help you understand these concepts. Most programming platforms these days allow you to group problems by these concepts. Once you think you understand them, try to see if you're able to solve problems that involve these concepts.

Another key mistake I see on the part of candidates is failure to calibrate themselves, i.e, evaluating the effectiveness of their approach during preparation. This is crucial to know if your countless hours of effort is turning into meaningful output.

Do this by involving a friend and scheduling mock interviews. Try to ensure the setup resembles actual interviews as much as possible. Take notes on which aspect requires attention and focus to train harder on that. Then iterate on this whole process again.

Interviews are stressful situations for lots of candidates and the stress can lead you to be off your game. Mock interviews help you get some early experience of that environment so that you're comfortable when the real thing comes along.

Finally, Job interviews go beyond just code. The way you approach a problem is important. Interviewers are looking at how effectively you communicate to resolve ambiguities. Making rational trade-offs in solutions is critical. End result matters, but how you get there counts just as much.

I’ve been a software engineer going on six years. I can do the job. I mostly enjoy it. But fuck, I HATE interviewing. I just absolutely suck at coding interview challenges and it’s been killing my confidence. I practice, and study, and blah blah blah. I do what I’m supposed to do. Seems like nothing helps.

For anyone who has been through this and come out on the other side, what has been the one thing that helped you overcome this challenge? Whether before, during, or after the interview. What helped you finally get good at them? Of course practice, I’m sure, but like, any mental shifts that helped? Or procedures/processes you go through before the interview? Anything other than just grinding away at it? I’m looking for some encouragement.

Thanks in advance.

My friend and I from uni (we both work at Google now) built www.meercode.com, a free AI-powered mock interview tool. Instead of just grinding problems solo, it's designed to help with the real interview experience — not just getting the right answer, but how you communicate, problem-solve under pressure, and explain your thinking.

It also gives you a score which we based off of faangs real marking rubric.

Think it could be a great tool to practice leetcode for coding interviews, all feedback's very welcome, thanks.

As I have been preparing for Coding Interviews, I found it difficult to manage resources, everything is scattered randomly over the internet, so I thought why not combine everything in one place, if even one person benefits from my work, I will be so glad that I made an impact in somebody's life.

I have created a GitHub readme, which contains all resources, be it for Learning Data Structures & Algorithms, or for preparing Theory Subjects like, Operating Systems, DBMS, Computer Networks, OOPs Concepts, System Design (which are often neglected by students, and find difficult to what to study as these topics are so vast) at one place

It is a one-stop solution for the preparation for product-based companies, from beginners to placement-ready candidates.

If you like my work or want to contribute to help others, STAR⭐, FORK🍴 the repo
Or SHARE🔗 with friends, students

https://github.com/sachuverma/DataStructures-Algorithms

I also daily add code solutions for some of the questions list given in the readme, currently, it's not complete but will be complete in a few days

If you have suggestions, what more things I can add to the resources list, I will be glad to hear you out

Just given an assessment in CodeSignal. Like WTF? This is for a front end developer position at uber with 2+ years of experience.

I had to answer 20 questions 16 quiz (basically programs that you gotta read line by line and select mcq's) 4 programs( every program was a medium to high leetcode program )

All this under 1 he 20 mins. Time flew by and I couldn't even attempt most of the questions.

Why is this test designed to hire superhumans?

It was my dream company I was interviewing with, I felt like I did not get a fair chance.

Hi everyone, I’m preparing for an AI engineer or Agentic AI Developer role as a fresher in Bangalore, Pune, or Mumbai. I’m targeting a package of around 8–10 LPA in a startup.

My skills right now:

1. LangChain, LangGraph, CrewAI, AutoGen, Agno

2. AWS basics (also preparing for AWS AI Practitioner exam)

3. FastAPI, Docker, GitHub Actions

4. Vector DBs, LangSmith, RAGs, MCP, SQL

Extra experience: During college, I started a digital marketing agency, led a team of 8 people, managed 7–8 clients at once, and worked on websites + e-commerce. I did it for 2 years. So I also have leadership and communication skills + exposure to startup culture.

My question is — with these skills and experience, is 8–10 LPA as a fresher realistic in startups? Or do I need to add something more to my profile?

1. Please.Come.Prepared. You won't believe the amount of people coming in with some experience and think they can just wing it. An interviewer is usually someone very technical that is not making progress in his own project and instead trying to clear you, the candidate. When you demonstrate zero knowledge in basic questions like: how do you use a HashMap? What's the runtime complexity of iterating a list? etc. you show that you really did not come prepared. Coming prepared also means getting some mock interviews by friends or via a paid service.

2. Don't get stuck, ask questions. It's ok to get stuck, it's actually the basic premise at a coding interview. You just can't remember or understand everything in your own. And when that happens it's completely ok to ask 'i thought I'd doing X, what do you think about that approach?' or 'i just can't remember how to get the time in milliseconds, can you remind me?' It's better to get over the hump and ask help than to show the interviewer that given enough time you could solve everything.

3. Have a plan before you start coding. If you think you know how to solve the question, it's always a good idea to try and write down a little plan. It doesn't have to be detailed but it has to keep you focused on how you want to solve it. For example: A. Traverse the list and check for values greater than 5. B. If True: copy to another list. C. Return the list.

This plan ensures that if you're stuck on part A. You'll know exactly what to do next.

4. Listen!!! Your interviewer will give you clues, signs and directions if you are actively speaking with them. If you calm yourself down, you'll be able to hear, understand and then implement those clues. It takes some effort from your side but it's worth it. To get better at being relaxed see section 1 of this post 😉.

I had an interview yesterday and I had to do a live coding challenge, the app we used had a built in search bar so if you need to look up any documentation or stuff they can keep track of it. I appreciate that. The challenge was to make a get call in Java and retrieve the number of items in the list returned. I usually use Java to expose endpoints not make calls (more used to doing this from the front end) so I obviously looked up some documentation and stuff using their search bar and quickly got everything done and submitted in the allotted time, I walked him over the code, he had no questions, asked me some brief stuff about OOP which I answered pretty well and that was it. I got the feedback today that BECAUSE I USED STACK OVERFLOW I WAS MORE OF A JUNIOR DEVELOPER so they’d screen other candidates and get back to me. Guys I have been coding for 6 years, I don’t know a single guy that memorizes all this specially now. I am honestly very infuriated by this feedback. They are getting back at me for using a built in feature of the app they chose to test with, which I honestly think it’s dumb if you don’t! The recruiter literally said “The manager is big on mentorship and people who are willing to learn”. What drives me nuts is that I completed the challenge without issues, on top of that on something that I don’t really use often so if anything that shows capacity to adapt but maybe I need to textbook a little bit more (big rant thx for reading)

Hi everyone! I’m excited to share something I’ve been working on—Interview Monster https://interviewmonster.com, a platform designed to help you ace coding interviews like never before. It's the first completely undetectable interview copilot in the world, created to give you the edge in coding interviews without anyone noticing.

What Inspired Me?

The idea for Interview Monster came from an unexpected source — game cheats. Just like some tools enhance gaming experiences without disrupting the flow, I thought, “Why not apply this concept to coding interviews?” Interviews can be as stressful as high-stakes boss fights, so why not have a “secret weapon” to support you when you need it most?

How It Works

There is a quick demo: https://www.youtube.com/watch?v=ERrVh4rXA0U

At its core, Interview Monster provides real-time, AI-powered hints while remaining invisible to everyone except you. Here’s how it can help:

1. Fully Undetectable Hints: With the HDMI Fuser, hints are displayed directly on your screen in a way that’s invisible to the interviewer. It’s like having a coach whispering advice in your ear during the interview.

2. Flexible Options: Don’t want to use additional hardware? No problem. You can:

• Use a second monitor or device like a tablet.

• Use Picture-in-Picture (PIP) mode on an external monitor

3. Customizable AI Support: Whether you need a quick solution or a detailed breakdown, Interview Monster’s AI adjusts to your preferences.

4. Built-in Chrome Extension: This extension automatically captures screenshots and sends them to the platform for processing. The results are instantly displayed to help you answer questions on the fly. We are using the latest AI LLM models to generate the best solutions. https://chromewebstore.google.com/detail/interview-monster-ai-inte/geedhnolmcdfeghjkihhbmiaomlglabc

Why Use Interview Monster?

• No Experience Required: Even if you’re new to coding interviews, you’ll have the confidence to tackle tough questions.

• Efficient Prep: Save time and focus on learning, rather than getting stuck on tricky problems.

• Tailored for FAANG and Beyond Whether it’s LeetCode-style questions or real-world problems, Interview Monster has you covered.

See It in Action

Check out the https://interviewmonster.com with my demo video to see how it works! Whether you’re a beginner or an experienced developer, Interview Monster is here to help you succeed in coding interviews.

Let me know what you think—I’d love to hear your feedback!

Hello guys,

Today a google recruiter contacted me for a software engineer profile in LinkedIn, I'm not prepared for the interview how long can I ask as preparation time ? And how should I start preparing ? Please help me. Thanks in advance

Handy reference on common binary search interview questions, pseudocode, and space/time complexity.

I have cleared OA and Basic Phone Screen round for Uber

Recruiter scheduled DSA and LLD round next week. What type and level of questions should I expect? Also are there any important topics I should focus more on?

I was messing around with this thing called Interviewcoder and it kinda blew my mind. It’s basically a little coding overlay that pops up during live interviews and OAs but doesn’t show up on Zoom or Meets. You can move it around with hotkeys, toggle it on/off, and it spits out Leetcode solutions plus time complexity on the fly.

Tested it on a couple problems just to see and ngl, it works. The wild part is it’s totally invisible on screen share, interviewer only sees your code editor, not the overlay. Feels like cheating but also like… companies keep forcing these grindy algorithm tests, so I get why people are using stuff like this.

Curious if people actually pulled offers with it and how smooth it went for them.

I have jotted down notes from my sys design preparation into this article linked below.

I hope you find it useful if you are currently preparing for interviews.

Hardware's Influence on Software Performance in Big Data Systems

I'm a developer that was laid off at the beginning of September of this year. I started in a junior role in Oct 2018 and was promoted to a senior role in 2022 and tech lead role in July 2023 before the layoffs. This is my first experience with layoffs, and my first time interviewing for senior roles given my increased experience.

I was hoping to ask for some advice from this community. I'm really struggling to enter interviews feeling confident because of the DSA questions I may face. I get in my head and create a mental block because of the unknown and large # of questions that can be asked (leading to doubt my worth, knowledge and capabilities that I've gained over my years of experience). If I'm given a take home project, or am asked a real world simulated question, generally I have no issues. But if it's anything related to questions similar to those found on leetcode, my mind goes blank and I sometimes really struggle to even identify what the question is asking. Even practicing leetcode questions makes me anxious and I usually struggle completing them if they are harder than easy. Once I see a solution though I have no issue understanding what it does or how it was implemented, but doing it myself is a real problem.

What strategies if any can I use to deal with this? Is this something I need to see a therapist for? This sort of feeling is really hard to explain to anyone who isn't in the technical world and doesn't deal with technical interviews. I am definitely starting to doubt my abilities and it's impacting my confidence as a developer and my ability to interview confidently.

Edit: I am employing strategies such as writing pseudocode, or trying to explain my thoughts and ask clarifying questions of what is being asked in interviews, but doing so doesn't help me feel prepared at all or deal with the anxiety in an interview for the unknown and going blank on coding a solution.

Hi all! I'm Nick and I work at Adzuna - we're a job search site. We've just launched a free interview tool powered by AI, to help people prepare for job interviews: www.adzuna.com/prepper

This is a bit of promotion for the tool obviously, but it is free and I genuinely think it would be of interest to this sub - so I hope it is ok!

The AI can simulate interview questions for any role at any company in the UK and US, as well as giving feedback to coach you on giving the best possible answers.

Would love for people to give it a try a see what they think - hopefully it helps you land your next job!