I’d probably reach out to some 20-30 senior QA engineers on LinkedIn whether they have a friend who’s reliable, good & looking for a job.
Hi undergrad and new to clojure , I recently had an interview and after the interview they sent me an assignment which a small program so that I do a code review, any hints on how to do this would be really helpful
it's quite an open-ended assignment @leftzav - but, off the top of my head, some things you might consider - does the code perform according to spec (if there is a spec), is it comprehensible, does any of it cause confusion, is it no more complicated than it needs to be, are there tests and do the tests provide sufficient coverage, is it sufficiently documented, is its purpose clear, does it separate pure and side-effecting aspects well, does it log sufficiently to aid debugging in production, are error conditions handled well, are resource acquisition and release handled well, are dependencies and configuration handled well
I'd go even more basic than this - does the code open and run in an editor? If there are tests, do they pass? I suspect for an undergrad they're also looking at your communication skills. Are you able to offer constructive feedback in a professional manner? Good luck @leftzav !
I added my thoughts to this question asked in beginners channel https://clojurians.slack.com/archives/C053AK3F9/p1598381692308300?thread_ts=1598374789.303500&cid=C053AK3F9
methods functions to distribute a given budget for salaries to the workers of a company? probably based on some evaluation of their individual work.
Interesting. Shouldn't you determine that during hiring based on experience and role? I would use the same criteria after the fact
let's say you have some kind of bonus system and you think about having some incentives and self-management
Do you have some KPIs / targets to hit? If yes, those should be the bench mark IMO - then increase for those who go above and beyond