Modus is a continuous workforce compliance and planning platform that enables various employees throughout the organization to stay compliant with labor laws, visualize and execute workforce plans, and make data-driven decisions to ensure fairness and equity. You can think of us as Vanta for HR. Our mission is integrity. We've all been through the pains of levels, benchmarks, compensation inequities. Why can't HR tech be intuitive, easy to use, and encompass workflows for everyone in the org?
While we are just at the beginning, both founders have an extensive experience in the industry. One of the co-founders was early Google engineer and built multiple companies in the past, writing significant amount of code at each company. Joining early means you have a significant say into tech and design choices.
We are looking for curious and motivated colleagues to turn our vision into a reality. All positions are 100% remote with no on-site requirements of any kind. We are currently looking for:
- Javascript/frontend developers
- Designers
- Backend developers
If interested, please reach out to hire@himodus.com
I've had several bad experiences with those where I waste dozens of hours of my own time only to be rejected or have to decline the offer shortly afterwards.
So now I pretty much don't apply anywhere that uses take home projects in the interview process.
I am not sure about other firms, but we personally look for how the candidate thinks about the problem more than anything. Did they handle exceptions well. Are they focusing on efficiency, readability, speed, or?
We found out that from a simple assignment that shouldn't take more than 30 min, we learn more than sitting with the person for hours. Plus they can do at their own pace without someone breathing down on their neck.
Imagine a file with endless list of URLs. For each URL check if it contains an image. If it does, identify the top 6 colors and store it memory so it can be printed/stored later.
In something like python this can be as short as 20 lines of code: - open the file - read line by line - validate if the URL is valid - call the URL - check if it's image - if image, read pixel by pixel and check the color - store it in dictionary/hashmap
Here is what I look for: - does it compile/work? - what language did you choose? (like python is fast to write this in few lines but hard to introduce concurrency) - have you introduced some kind of caching for the URLs? (so you don't waste resources) - are you checking if the URL is valid or you just run them all and wait for errors/timeouts? - are you checking the file type from HTTP header or body of the file? - how do you handle errors? - are you attempting concurrency? If yes, how?
I actually done this exercise myself in dozen or so languages to see what choices I make based on the language. Obviously one can spend significantly more time on it if they really desire, but the design choices are visible from the beginning.