실물 확인

실제 생성된 평가, 공개합니다

실제 공고(엔트리레벨 AI 소프트웨어 엔지니어)용으로 생성된 28문항 전체 평가를 리크루터 미리보기 그대로 공개합니다: 모든 문항 형식, 정답, 모범 답안, 채점 루브릭, 출제 의도까지. 뱅크에서는 영구 은퇴 처리되었습니다.

문항은 평가 언어로 생성됩니다 — 이 샘플은 영어와 일본어 언어 게이트 문항 1개를 포함합니다.

문항
27
문항
문항 형식
6
문항 형식
측정 필러
6
측정 필러
분 세션
60
분 세션

직무 기술서

엔트리레벨 AI 소프트웨어 엔지니어 · 도쿄 엔지니어링 허브 · 하이브리드 · 밴드 A

We are looking for an ambitious Entry-Level AI Software Engineer to help build and scale our core AI capabilities. You will build production-ready backend services with Python and FastAPI to securely interact with LLM APIs, design and relentlessly refine prompts, build fault-tolerant AI workflows with Temporal, and instrument everything with OpenTelemetry…

엔진의 결정

활성 필러 (실제 설정 기준)

BehaviouralSituationalCognitiveDomainAI Fluency

애드온

AI Sandbox · Starter+Japanese · JLPT · min. N4 · +10 min

스마트 가중치: 엔진이 직무와 연차로 가중치를 자동 계산 — 첫 후보자 시점에 잠금.

언어는 합격/불합격 게이트 — 종합 점수에 포함되지 않습니다.

생성된 평가

세션: 28Q · ~60min

시그니처 형식

테스트 라이브러리는 제공할 수 없는 3가지 형식 — 같은 평가에서.

AI SANDBOXUSP — 후보자가 AI와 함께 일합니다

Your team uses an AI assistant to summarise meeting notes for a public project channel. The current prompt produces summaries that are too long, unstructured, and — worse — repeat WHO said what, which the team agreed must never appear in the public channel. Fix the prompt so the summary is a short, structured digest of decisions and action items with no personal attributions.

스타터 아티팩트

Summarize these meeting notes.

TEST INPUTS

Meeting notes — Project Falcon sync, Tuesday. Priya said the vendor contract is delayed again and blamed the legal review backlog. Marcus argued we should switch vendors. After a long discussion, the group decided to (1) extend the current vendor contract by one month, (2) have the ops team prepare a fallback vendor shortlist by Friday, and (3) move the launch date to the 15th. Dana volunteered to update the customer FAQ. Priya will chase legal daily. There was also a side discussion about the office move that reached no decision.

AI 어시스턴트에게 보낼 프롬프트를 작성하세요…

합격 기준

  • Summary contains no attendee names or personal attributions
  • Summary keeps the three decisions (vendor extension, shortlist, launch date)
  • Summary is a bulleted or numbered list, not prose paragraphs
  • Summary is concise and readable at a glance (secondary)(secondary)

Verification Behaviour · 50%

강한 답변의 특징: Diagnosed the root cause aloud in the prompt structure (the original gave no output contract at all), fixed both failures in one targeted revision, and used a final run to confirm rather than explore

약한 답변의 특징: Resubmitted near-identical prompts without reading the failing test cases; no evidence of understanding WHY the summary leaked names or ran long

Prompt Craft · 30%

강한 답변의 특징: Well-structured prompt with delimited input, explicit inclusion AND exclusion rules, output format specification, and an edge-case instruction (what to do when no decisions were made)

약한 답변의 특징: Vague single-sentence prompts with no format, length, or exclusion constraints

Domain Grounding · 20%

강한 답변의 특징: Handled confidentiality like a practitioner: excluded personal attributions categorically, kept decisions actionable without blame, and the summary stays useful to someone who was not present

약한 답변의 특징: Ignored the confidentiality risk entirely — names or blame language survive in the output with no attempt to control them

LANGUAGE GATE · AUDIO오디오 · 1회 재생JLPT · ja

보너스: 언어 게이트 오디오 문항

音声の内容に基づき、新しい搭乗ゲート番号を選びなさい。

  1. 42番
  2. 58番
  3. 27番
  4. 73番

실제 평가에서는 오디오가 정확히 한 번만 재생됩니다(데이터베이스 수준에서 강제). 여기서는 다시 들을 수 있습니다.

VIGNETTE SET하나의 시나리오 · 세 가지 채점 판단

공유 시나리오

INCIDENT REPORT — 03:12 JST Checkout service error rate jumped from 0.2% to 14% over 20 minutes. The last deploy finished at 02:41. A dependency (payments-gateway SDK) released a new version yesterday. On-call engineer restarted one pod at 02:58; error rate briefly dipped, then returned. Black Friday sale starts at 09:00.

1.What is the FIRST action you take?

  1. A.Roll back the 02:41 deploy
  2. B.Restart all pods
  3. C.Pin the payments SDK to the previous version
  4. D.Page the payments vendor

정답 해설: The deploy is the most recent controlled change and rollback is reversible in minutes; pod restarts already showed the failure isn't process-local, and the SDK pin is a build-level change that takes longer than a rollback.

2.The rollback completes but errors stay at 14%. What does that MOST strongly suggest?

  1. A.The deploy was not the cause
  2. B.The rollback failed silently
  3. C.Traffic volume is the cause
  4. D.The database is corrupted

정답 해설: A completed rollback that changes nothing points away from the deploy — attention shifts to the environment change: yesterday's SDK release reaching production paths.

3.Given the 09:00 sale, which communication is MOST appropriate now?

  1. A.Wait until root cause is confirmed
  2. B.Notify stakeholders of impact, current status, and a next-update time
  3. C.Announce the sale will be delayed
  4. D.Post a public status page outage immediately

정답 해설: Structured stakeholder communication with a committed next update is the incident-management standard; premature public announcements or silence both create larger problems.

#1WRITTEN ANSWER

In Python 3.12, you are designing a utility function that needs to accept an arbitrary number of non-keyword arguments (e.g., item identifiers) and an arbitrary number of keyword arguments (e.g., processing configuration options). How would you define this function's signature, and how would you access both types of arguments inside the function body?

0 / 200 Words

모범 답안

To accept arbitrary non-keyword arguments, use `*args`, and for arbitrary keyword arguments, use `**kwargs` in the function signature (e.g., `def process_items(*args, **kwargs):`). Inside the function, `args` is a tuple containing all non-keyword arguments, and `kwargs` is a dictionary containing all keyword arguments passed by keyword.

Correctness · 60%Depth · 40%

당신의 직무 기술서로 생성해 볼까요?

대기자 명단에 등록하시면 실제 공고 중 하나로 평가를 생성해 드립니다.

당신의 직무 기술서로 생성해 볼까요?