求人情報インテリジェンスエンジン（無慈悲版）

Posting-[RESOLVED_COMPANY]-[RESOLVED_POSITION_NAME]-[CURRENT_YYYYMMDD].md ``` # JOB POSTING INTELLIGENCE REPORT # GENERATED BY: JOB POSTING INTELLIGENCE ENGINE v4.8.14 # DATE: [INSERT_CURRENT_DATE] #### 0. EXECUTIVE FIT SUMMARY **GO / NO-GO: [PENDING INPUT DATA]** This section requires runtime input data to render a verdict. The engine is ready to evaluate cultural, technical, and strategic alignment once [CANDIDATE_PROFILE], [JOB_DESCRIPTION_OR_BASELINE], and [DELTA_INTELLIGENCE] are provided. The analysis will weigh the candidate's baseline engineering profile against the position's inferred pain points, tech stack maturity, and organizational risk surface to produce a definitive go/no-go recommendation with a 3-4 sentence engineering justification. Source: [Pending Input] --- #### 1. SOURCE & COMPANY INTEL - [VERBATIM/INFERRED] Company: [Pending Input] - [VERBATIM/INFERRED] Location: [Pending Input] - [VERBATIM/INFERRED] Job ID: [Pending Input] - [VERBATIM/INFERRED] Posted Date: [Pending Input] - [INFERRED] Organization: [Pending Input - Scale/maturity overview, focus area, and Cybersecurity Value Stream impact rating (e.g., C: High) will be inferred from industry and company size once data is available.] Source: [Pending Input] --- #### 2. POSITION INTEL - **Position Identity:** [Pending Input - Exact target position name will be extracted from inputs.] - **Derived Title Intelligence:** [Pending Input - Market tier, scope of ownership, engineering domain context, and reporting line structures will be derived from the position title seniority.] Source: [Pending Input] --- #### 3. FISCAL - **Departmental Economics:** [Pending Input - Department-level budget allocation, tooling investment choices, financial run rates, and headcount pressures will be detailed once input data is provided.] Source: [Pending Input] --- #### 4. CULTURE - [Pending Input - Operational reality vs. stated intent will be contrasted, analyzing HR language against technical debt, legacy processes, and engineering velocity.] Source: [Pending Input] --- #### 5. TECH STACK | Tool | Category | Ecosystem | |------|----------|-----------| | [Pending Input] | [Pending Input] | [Pending Input] | [Pending Input - Detailed text breakdown of missing dependencies, legacy tooling, and integration friction points will follow the table.] Source: [Pending Input] --- #### 6. KEYWORD & INDUSTRY TAXONOMY - [Pending Input - Top 15-20 keywords for resume ATS optimization will be grouped by type (e.g., Core Tech, Methodologies, Compliance).] Source: [Pending Input] --- #### 7. STRATEGIC DECODER - [Pending Input - The strategic "Why" (pain, scale, audit, transformation) will be pinpointed with a multi-paragraph breakdown of the immediate operational crisis or growth vector driving this hire.] Source: [Pending Input] --- #### 8. INTERVIEW SIGNAL - [Pending Input - Deep dive into interviewer expectations, breaking down what the Hiring Manager, Peer Engineers, and Cross-functional stakeholders will filter for.] Source: [Pending Input] --- #### 9. ALIGNMENT VECTOR | JD Requirement | Candidate Evidence | Fit Level | |----------------|-------------------|-----------| | [Pending Input] | [Pending Input] | [Pending Input] | [Pending Input - Granular itemization of requirements with evidence-based fit levels.] Source: [Pending Input] --- #### 10. 90-DAY MODEL - **Days 1-30:** [Pending Input - Specific technical hurdles and expected **OUTCOMES** for the first month.] - **Days 31-60:** [Pending Input - Continued expectations and milestones.] - **Days 61-90:** [Pending Input - Final ramp-up period with bold expected **OUTCOMES**.] Source: [Pending Input] --- #### 11. RISK SURFACE > [!] RISK SURFACE > [Pending Input - Operational landmines including burnout vectors, architecture ambiguity, lack of executive buy-in, and operational support burdens will be detailed.] Source: [Pending Input] --- #### 12. KILL CRITERIA > [!] KILL CRITERIA > [Pending Input - Specific, granular rejection triggers during the interview loop will be listed.] Source: [Pending Input] --- #### 13. THE HUNT (AUTO-HUNT PROTOCOL) - **Pre-Processing Rule:** All template syntax variables will be resolved using explicit names and terms from input runtime data. No generic variables or brackets will exist in the final rendered output. No markdown code blocks will be used inside this section. - **Part A: X-Ray Blueprint:** **1. Direct Lead (Targeting the likely hiring manager):** site:linkedin.com/in ("current" OR intitle:at) "RESOLVED_COMPANY" ("RESOLVED_MANAGER_TITLE" OR "RESOLVED_ALT_TITLE") "RESOLVED_LOCATION_OR_SILO" **2. The "Hiring" Post (Targeting active updates from the team):** site:linkedin.com/posts "RESOLVED_COMPANY" "hiring" "RESOLVED_JOB_TITLE" **3. Skip-Level (Targeting the manager's boss or department head):** site:linkedin.com/in ("current" OR intitle:at) "RESOLVED_COMPANY" ("VP" OR "SVP" OR "Head of") "RESOLVED_SILO" **4. The Recruiter (Targeting the talent acquisition owner):** site:linkedin.com/in ("current" OR intitle:at) "RESOLVED_COMPANY" ("Recruiter" OR "Talent") "RESOLVED_SILO" **5. Team Peers (Targeting future colleagues for intelligence gathering):** site:linkedin.com/in ("current" OR intitle:at) "RESOLVED_COMPANY" ("RESOLVED_PEER_TITLE") "RESOLVED_SILO" **6. Company Alumni (Targeting warm connections who worked at your past companies):** site:linkedin.com/in ("current" OR intitle:at) "RESOLVED_COMPANY" ("RESOLVED_PAST_COMPANY_1" OR "RESOLVED_PAST_COMPANY_2") - **Part B: Target Matrix:** **#1 (Best Lead):** [Pending Input - Target profile title, Reply-Prob Score (0-10), and strategic justification based on Sec 7/8.] **#2:** [Pending Input - Target profile title, Reply-Prob Score (0-10), and strategic justification based on Sec 7/8.] **#3:** [Pending Input - Target profile title, Reply-Prob Score (0-10), and strategic justification based on Sec 7/8.] Source: [Inferred via Sec 7/8 Matrix Input] --- #### 14. THE HOOK - [Pending Input - Business impact value proposition focused on quantifiable ROI, risk reduction, or velocity optimization tailored to Section 7.] Source: [Pending Input] --- #### 15. RUBRIC - [Pending Input - Evidence-based scoring of candidate fit across Technical, Architectural, and Leadership vectors.] Source: [Pending Input] --- #### 16. CONSISTENCY & CONFLICTS - [Pending Input - Internal mismatches within the JD (e.g., Remote vs. Onsite contradictions, bloated scope vs. low title, tool stack mismatches) will be identified.] Source: [Pending Input] --- #### 17. DATA INTEGRITY - [Pending Input - Audit of evidence vs. assumption, mapping zones of highest ambiguity where the candidate must ask clarifying questions.] Source: [Pending Input] --- #### 18. INTERVIEW PRESSURE QUESTIONS - [Pending Input - 4-5 high-pressure, scenario-based technical/architectural questions targeting specific vulnerabilities from Section 7 or Section 11. Direct, challenging, and professional style.] Source: [Pending Input]