DMV Company Research Vault

Daily Research Workflow

9 min read

Daily Research Workflow

Purpose: Systematic, repeatable research routine to identify high-quality job opportunities, track hiring signals, and keep the vault updated with actionable intelligence.

Time Investment: 30-60 minutes/day during active job search; 15-30 minutes/day for passive monitoring

Morning Routine (15-20 minutes)

1. Job Board Scan (10 minutes)

Objective: Identify new postings at target companies

Actions:

Output: List of 3-5 target applications for the day

2. Hiring Signal Monitoring (5-10 minutes)

Objective: Detect contract wins, funding, expansion signals

Actions:

  • Google News Alerts (set up once, review daily):

    • “AWS government contract”
    • “Booz Allen contract award”
    • “Leidos wins contract”
    • “[Target Company] hiring”
    • “[Target Company] expansion Northern Virginia”

  • LinkedIn Company Updates: Check 2-3 target companies for:

    • New office openings
    • Funding announcements
    • Contract win press releases
    • Employee growth trends (LinkedIn “See all employees” → note if growing rapidly)

  • Federal Procurement Sites (once/week, Fridays):

  • GovCon News (if pursuing defense roles):

Output: 1-2 hiring signals to document in company notes or /00_Inbox/

Midday Actions (15-20 minutes)

3. Application Submission (10-15 minutes)

Objective: Apply to 1-2 roles daily (5-10/week target)

Actions:

  • Tailor resume for role (emphasize relevant keywords: AWS, Python, data pipelines, ML, systems engineering)
  • Customize cover letter (2-3 sentences on why this company + role fits my background)
  • Submit application via company ATS or LinkedIn Easy Apply
  • Log Application in Obsidian:
    • Create note: Application - [Company] - [Role] - [Date Applied]
    • Include: Job description, key requirements, recruiter/hiring manager LinkedIn (if findable), follow-up date (7-10 days)
    • Link to company profile: [[Company Name - City, State]]

Output: 1-2 applications submitted, logged in vault

4. Networking & Outreach (5 minutes)

Objective: Build relationships and generate referrals

Actions:

  • LinkedIn Connection Requests (2-3/day):

    • Target: Data engineers, cloud engineers, hiring managers at top 10 companies
    • Personalized message: “Hi [Name], I’m a data engineer exploring opportunities at [Company]. I’d love to connect and learn more about your experience on the [Team Name] team.”

  • Informational Interviews (1-2/week):

    • Request 15-20 minute calls with engineers at target companies
    • Questions: Team structure, tech stack, interview process, culture, advice for applicants

  • Referral Requests (after informational interview):

    • “Thank you for the insights. I applied to [Role Link]. Would you be comfortable referring me?”

Output: 2-3 new connections, 1 informational interview scheduled/week

Evening Routine (10-20 minutes)

5. Skill Development (10-15 minutes/day)

Objective: Build portfolio, earn certifications, stay sharp

Actions (rotate daily):

  • Monday: AWS Certification Study (Solutions Architect Associate or Data Analytics Specialty)

    • Use AWS Skill Builder, A Cloud Guru, Tutorials Dojo
    • Goal: Certify within 4-6 weeks

  • Tuesday: Portfolio Project Work

    • Build AWS data engineering project (S3 → Glue → Athena → QuickSight pipeline)
    • Document on GitHub with clear README
    • Blog post or LinkedIn article explaining architecture

  • Wednesday: LeetCode / System Design

    • Practice coding problems (focus on Python, data structures, algorithms)
    • Study system design for distributed data systems

  • Thursday: Read Technical Content

    • AWS blogs, data engineering blogs, sector-specific content
    • Summarize key insights in Obsidian note: /00_Inbox/Learning - [Topic] - [Date]

  • Friday: Sector Research Deep Dive

    • Pick one company from Job Targeting Dashboard
    • Research recent news, glassdoor reviews, LinkedIn employee posts
    • Update company profile with new insights

Output: Incremental progress on certifications, portfolio, or knowledge

6. Vault Maintenance (5 minutes)

Objective: Keep research organized and actionable

Actions:

  • Move notes from /00_Inbox/ to appropriate folders:

    • Job leads → keep in Inbox until applied
    • Company updates → append to company profile in /01_Companies/
    • Sector trends → append to sector brief in /02_Sectors/
    • Application logs → move to /00_Inbox/Applications/ (create subfolder)

  • Update Job Targeting Dashboard if priorities change (e.g., contract win increases a company’s priority)

Output: Clean, organized vault ready for next day

Weekly Review (Friday, 30 minutes)

7. Weekly Retrospective

Objective: Assess progress, adjust strategy

Actions:

  1. Applications Summary:

    • Count: How many applications submitted this week?
    • Quality: Were they high-fit roles at target companies?
    • Goal: 5-10/week during active search

  2. Networking Summary:

    • New connections made?
    • Informational interviews completed?
    • Referrals requested/received?

  3. Interview Pipeline:

    • Any responses to applications?
    • Interviews scheduled?
    • Rejections? (analyze: was it skill mismatch, clearance, experience level?)

  4. Hiring Signals Identified:

    • Which companies announced contract wins, hiring, or expansion?
    • Update Job Targeting Dashboard priorities if needed

  5. Skill Development:

    • Progress on AWS certification?
    • Portfolio projects advanced?

  6. Next Week Priorities:

    • Which companies to focus on?
    • Any networking events, meetups, or conferences?
    • Skill gaps to address?

Output: Weekly summary note in /00_Inbox/Weekly Review - [Date]

How Claude Should Update the Vault

When I Ask Claude for Research

Example Prompts:

  • “Claude, update the Booz Allen Hamilton profile with recent contract wins.”
  • “Claude, research hiring trends at AWS for data engineers.”
  • “Claude, create a new company profile for [Company X].”
  • “Claude, summarize this week’s defense contracting news relevant to my job search.”

Claude’s Actions:

  1. Update Existing Notes:

    • Use the Edit tool to append new information to company profiles or sector briefs
    • Add timestamp and source links
    • Maintain existing structure (don’t rewrite entire file unless requested)

  2. Create New Notes:

    • Use the Write tool to create new company profiles, sector analysis, or research notes
    • Follow templates in README
    • Place in appropriate folder (/01_Companies/, /02_Sectors/, /04_Maps & Networks/)

  3. Summarize and Link:

    • Provide concise summaries of findings
    • Link related notes using Obsidian wikilinks ([[Note Title]])
    • Tag appropriately (#company, #sector, #hiring-signal, etc.)

  4. Hiring Signal Format:

    • When reporting contract wins or hiring signals, include:
      • Date of announcement
      • Contract value (if disclosed)
      • Agencies/customers involved
      • Implications for hiring (e.g., “Likely to hire 50+ data engineers over next 12 months”)
      • Source link

Identifying Hiring Signals

What to Look For

Strong Positive Signals:

  • ✅ Contract Wins: Large federal contracts ($100M+) typically drive hiring sprees (3-6 month lag)
  • ✅ Office Expansion: New office openings, lease expansions in DMV (indicates growth)
  • ✅ Funding Rounds: SaaS/startups raising Series B+ (usually hire aggressively post-funding)
  • ✅ LinkedIn Employee Growth: 10%+ headcount growth over 6 months (check LinkedIn “See all employees”)
  • ✅ Glassdoor Reviews Mentioning Hiring: Recent reviews noting “rapid growth”, “lots of open roles”
  • ✅ Recruiter Outreach: Recruiters actively messaging candidates on LinkedIn (signal of urgent hiring)
  • ✅ Job Posting Volume: 50+ open roles in a single department (e.g., “Cloud Engineering” or “Data & Analytics”)

Caution Signals:

  • ⚠️ Layoffs or Restructuring: Recent workforce reductions (wait 3-6 months before applying)
  • ⚠️ Hiring Freezes: News of hiring pauses or budget cuts
  • ⚠️ Executive Turnover: C-suite departures (especially CTO, CFO) can indicate instability
  • ⚠️ Negative Glassdoor Trends: Sharp decline in ratings, complaints about culture or pay
  • ⚠️ Old Job Postings: Roles posted 60+ days ago may be fake, frozen, or extremely selective

Neutral/Ongoing Signals:

  • 🔄 Contract Recompetes: Incumbent re-winning contract (maintains status quo hiring)
  • 🔄 Backfill Hiring: Replacing departing employees (not net growth, but still opportunity)

Weekly Summary Template

Use this template every Friday to document progress:

# Weekly Review - [Date Range]
 
## Applications Submitted
- [Company] - [Role] - [Date] - [Status]
- [Company] - [Role] - [Date] - [Status]
- **Total:** X applications
 
## Networking
- New LinkedIn connections: X
- Informational interviews: X
- Referrals requested: X
 
## Interviews
- Screening calls: X
- Technical interviews: X
- Onsite/final rounds: X
 
## Hiring Signals Identified
- [Company]: [Contract win / Office expansion / etc.] - [Impact]
- [Company]: [Signal] - [Impact]
 
## Skill Development
- AWS Certification: [Progress %]
- Portfolio projects: [Status]
- LeetCode: [Problems solved]
 
## Insights & Adjustments
- What worked well this week?
- What should I change next week?
- Any new companies to add to [[Job Targeting Dashboard]]?
 
## Next Week Focus
- Top 3 companies to apply to
- Networking goals
- Skill development priorities

Tools & Resources

Essential Job Boards

Hiring Signal Sources

Skill Development

Networking

  • LinkedIn: Primary platform for connecting with engineers and recruiters
  • Meetup.com: DMV tech meetups (AWS, data engineering, Python)
  • Eventbrite: Tech conferences and workshops in DMV

Automation Ideas (Optional)

Google Alerts (Free)

Set up email alerts for:

  • “AWS Herndon jobs”
  • “Booz Allen contract”
  • “Leidos wins”
  • “Capital One data engineer”
  • “Northern Virginia tech hiring”

IFTTT or Zapier (Paid)

  • Auto-save LinkedIn job postings to spreadsheet or Notion
  • RSS feeds from GovConWire → Slack or email
  • Company LinkedIn posts → aggregated feed

Python Scripts (DIY)

  • Scrape company career pages daily, notify if new “data engineer” roles appear
  • LinkedIn API (if available) to track employee growth
  • Parse USASpending.gov for contract awards above $10M

Key Principles

  1. Consistency Over Intensity: 30-60 min/day beats 4-hour weekend binges. Daily momentum is critical.

  2. Quality Over Quantity: 2 tailored applications to high-fit roles > 10 spray-and-pray applications.

  3. Referrals are 10x Multipliers: Warm introductions dramatically increase interview rates. Invest in networking.

  4. Track Everything: Log applications, follow-ups, interviews, signals. Data reveals patterns and guides strategy.

  5. Adapt and Iterate: Weekly reviews identify what’s working. Double down on success, cut what’s not yielding results.

  6. Vault is a Living System: Continuously update company profiles, sector briefs, and job targeting priorities based on new intelligence.

Sector Intelligence

Company Profiles (Top 10)

Tags: workflow job-search research daily-routine hiring-signals

Graph View

Backlinks