# hr Published articles for hr. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## LLM-судья для нейроразбора резюме на hh DevFeed: [LLM-судья для нейроразбора резюме на hh]() Original publisher: [Read original article]() Author: Mentalitet (hh.ru) Published: 2026-06-22T05:31:17Z Content type: article Language: ru Sources: [HeadHunter RU]() Topics: [Large Language Model](), [Machine learning]() Tags: [ai](), [ai-quality](), [eval](), [hh-ru](), [hr](), [llm](), [llm-10b5a83db3c5](), [llm-as-a-judge](), [llm-as-judge](), [quality-assurance](), [tag-61cd5a476b1d](), [tag-a939ae104bb0](), [tag-b6914c0b0244](), [tag-d96e238f1419](), [tag-e7e38deac50c]() ### AI overview This article describes how hh.ru designed an LLM judge for its resume-analysis feature in an AI assistant. It explains why reliable evaluation requires its own rubrics, datasets, quality metrics, operating-cost considerations, and controls for hallucinations and interpretation errors. The system assesses candidates against criteria relevant to a specific position, which may be extracted from a vacancy or defined by an employer. ### Source excerpt Создать LLM-судью легко. Гораздо сложнее сделать так, чтобы его оценкам можно было доверять. Мы убедились в этом на практике при разработке нейроразбора резюме для ИИ-помощника hh.ru. Быстро выяснилось, что хороший LLM-судья -- это отдельный продукт со своими рубриками, датасетами, метриками качества и стоимостью эксплуатации. Меня зовут Женя Орлов, я LLM Eval Lead. В этой статье расскажу, как мы проектировали систему оценки для нейроразбора резюме, почему отказались от наивных подходов и какие выводы сделали по ходу разработки. Читать далее ## How corporate politics actually work DevFeed: [How corporate politics actually work]() Original publisher: [Read original article]() Author: Dr Milan Milanović Published: 2026-05-07T15:03:00Z Content type: opinion Language: en Sources: [Tech World With Milan Newsletter]() Topics: [Job](), [meetings]() Tags: [advice](), [corporate](), [engineering](), [hr](), [job](), [manager](), [manipulation](), [mentor](), [relationships](), [remote](), [work]() ### AI overview An interview with former Amazon Vice President Ethan Evans about corporate politics and career advancement. It examines why strong technical work alone may not determine promotions, how managers evaluate visibility and collaboration, the role of influence and relationships, early warning signs before performance-improvement plans, and mentoring in remote teams. ### Source excerpt With Ethan Evans, a former Amazon Vice President. ## Six Tips for Interviewing Software Engineers When You Aren't Technical DevFeed: [Six Tips for Interviewing Software Engineers When You Aren't Technical]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-03-10T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Job](), [communications](), [Development](), [context](), [Code]() Tags: [communications](), [culture](), [development](), [hr](), [interview](), [interviewing](), [job](), [remote](), [startup](), [technical](), [tips]() ### AI overview An article offers six tips for nontechnical interviewers evaluating software engineers, covering relevant questions, communication, attitude, values alignment, work practices, and compensation or company details. It also briefly discusses the author's opposition to coding tests, especially for senior engineering roles. ### Source excerpt Interviewing engineers when you aren't one is a regular human resources task that tends to give non technical folk fits and for good reasons. 1. Focus on What You Can Interview them About To the non engineer, our job is all about coding but that's actually only a part of what an engineer does. Engineers exist in the same ecosystem as any employee and there are all kinds of questions about work practices that need to be asked. For example if remote work is a part of your work environment then dig down into how that person might function in a remote context. 2. Communications Ability Is Always Key Engineers do not work in a vacuum and the ability to communicate is a key ability that improves the quality of their work. Ask questions and see how the engineer communicates. 3. Look for Attitude A lot of engineers love to drown non technical people in what amounts to techno babel - it is a way for us (yes I am an engineer myself) to feel superior. Look for hints of that attitude during the interview and if you find it before they are an employee then you should expect it to be even worse once they are an employee. 4. Look for Values Alignment / Culture Fit When I'm an interviewer, I care most about whether or not the candidate can do the technical work because, honestly, I can work with anyone - in the end all I care about (mostly) is whether or not the code works. Now if you are non technical then you don't care about that but you likely care a lot about value alignment and culture fit so dig in there. 5. Look at Work Practices Even if you aren't technical, you likely have some idea around work practices in development from either past experience or media. It is ok to ask a general question like "I have a bug in what you are working on - how do you handle it?". And then what you are looking for is some kind of logical approach. Note: My first two answers on this one are: They either log the bug formally in the bug tracker / ticket system They try and reproduce it 6. Salar