Seems like you should test it on someone you think is competent to see if it’s clear for what you’re trying to test. It feels like I’m trying to help you cheat. More on reddit.com

Try and model the interview around what they will actually do on the job. Write algorithms Build an API (Flask, SQLAlchemy, FastAPI, SQL) / tests Integrate AI into an existing API Deploy web apps / Containerisation All of it (Take home test?) Then design your questions around that to be more representative. If someone is not going to be writing high-performance algorithms it's less fruitful to ask them to answer such questions in the interview. That said, basic knowledge of Python data structures and when to use Lists, Maps, Sets, Dicts, etc, should be tested along with good practices like Type Hinting, Logging, OOP, Unit Testing, SOLID principles etc. More on reddit.com

For a 2 years experienced position, you should probably be familiar with the internals. I'd especially be interested in things like Iterator vs Iterable Mutable data-structures vs Immutable the internal implementation of python datastructs like list, dict, set. You'd be expected to use this so you should be familiar with how efficient are these w/ r/t to different things like search, insertion etc. whether you are aware of useful Python tools like generators, Context managers which improve the efficiency and readability whether you are thorough with aspects of testing (unittest, TDD, mocking etc). There's no good Python code without good tests. be prepared to whiteboard simple exercises. Start with the most straightforward implementation and feel free to use Pythonic idioms (like list comprehension) as you optimize the code. you'd be expected to know the tools Python provides and know how to use them. More on reddit.com

It doesn’t work. Just converting to a set destroys information you need. For example consider “aba”, “a”. You’re halfway on the rails but you didn’t pick quite the right data structure.

You can use a - b rather than a.difference(b). Maybe you don’t have to, either, just making sure you know.

People will advise not to use string as a name since Python has a builtin module named string. I personally would use s, t (for string and next string, a la i,j,k,… for index and next indexes) but there are those who don’t like the mathy variable names too so it’s a judgment call. Regardless, I don’t like string_edited as a name. The string isn’t an edited string. It’s a candidate edited string.

More on reddit.com