resume/notes/LINKEDIN-OPTIMIZATION.md

LinkedIn Profile Optimization Guide

Last Updated: March 18, 2026 Profile: Paul Halvorsen - linkedin.com/in/paul-halvorsen

---

Current Profile Status

What You Have

• Name: Paul Halvorsen ✓
• Pronouns: He/Him ✓
• Headline: "Software Engineer | Systems Tinkerer" ✓ (updated!)
• Location: Baltimore City County, Maryland, United States ✓
• Current Role: Abnormal AI ✓
• Education: University of Maryland Baltimore County ✓
• Connections: 93 (room to grow)
• About Section: ✅ Updated (see feedback below)
• GitHub Link: Included ✓
• Blog Link: Not yet included (should add)
• Experience Descriptions: ⚠️ Reviewed (mostly missing - CRITICAL)
• Skills Section: ✅ Reviewed (see feedback below)
• Activity/Posts: ⚠️ 0 posts (no activity yet)
• Followers: 96 (room to grow)
• Open to Work: (not yet checked)
• Education: ⚠️ Incomplete (missing honors, thesis, details)

---

Priority Changes (High Impact)

1. UPDATE HEADLINE (Do This First)

Current: "Software Engineer" Problem: Too generic, gets lost in recruiter searches, doesn't communicate expertise

Recommended Options:

Option A - Technical Focus:

Software Engineer | Backend Systems & APIs | Python, Go, Rust

Option B - Casual & Friendly (Recommended):

Software Engineer | Systems Tinkerer

Option C - Detailed:

Backend Engineer | API Design | Distributed Systems

Why It Matters:

• Recruiters search by keywords in headlines
• Shows what kind of engineer you are, not just that you code
• Better for Algorithm matching
• More memorable

---

2. ABOUT SECTION - CURRENT & FEEDBACK

Current Status: ✅ Updated! (as of March 18, 2026)

Your Current Text:

Software Engineer | Systems Tinkerer

15+ years shipping code. I build backend systems and APIs
that actually work—the kind that developers enjoy using and
scale without falling apart.

Currently at Abnormal AI working on distributed systems,
microservices, and infrastructure stuff. Before that I spent
time building APIs at Binary Defense and NSA, learning way
more about security than I bargained for.

Tech I work with:
Python, Go, Rust, Kubernetes, REST APIs, databases, Docker,
C, PHP, SQL. Always learning new things because honestly,
every few years there's something better.

What gets me excited:
Building systems that solve real problems. APIs that are
intuitive. Code that's reliable and performant. Remote work
where you can actually focus. Teams that communicate well in
writing.

https://github.com/malwhile

Assessment: 8.5/10 ✨ This is solid! You've already made good improvements.

What's Working Well:

• ✅ Headline is now specific ("Software Engineer | Systems Tinkerer")
• ✅ Casual, friendly tone (not corporate/boring)
• ✅ Shows personality and what you care about
• ✅ Mentions scale (15+ years, distributed systems)
• ✅ Lists relevant tech stack
• ✅ GitHub link included
• ✅ Emphasizes remote work preference
• ✅ Clear about what excites you

Suggestions for Improvement:

Option 1: Add Missing Sections (Recommended)

After "What gets me excited:" add these sections to complete your profile:

What I'm not interested in:
On-call rotations. Unnecessary meetings. Hype over substance.

Let's chat if:
You're building backend infrastructure, APIs, or platforms
that people genuinely want to use. Remote work preferred,
obviously.

Why:

• Filters out bad-fit recruiters immediately
• Saves time for everyone
• Shows you know what you want

Option 2: Add Blog Link

Add your personal blog after GitHub:

https://github.com/malwhile
https://flow.halvo.me (Personal Blog)

Why:

• Shows you publish technical content
• Adds credibility
• Recruiters can see your writing/thinking

Option 3: Make "Building Systems That Solve Real Problems" More Specific

Current: "Building systems that solve real problems."

Could be: "Building infrastructure that enables companies to scale reliably." Or: "Building backend systems that other engineers depend on."

Why:

• More concrete vision
• Helps recruiters understand your value
• Better for keyword matching

Recommended Final Version:

Software Engineer | Systems Tinkerer

15+ years shipping code. I build backend systems and APIs
that actually work—the kind that developers enjoy using and
scale without falling apart.

Currently at Abnormal AI working on distributed systems,
microservices, and infrastructure stuff. Before that I spent
time building APIs at Binary Defense and NSA, learning way
more about security than I bargained for.

Tech I work with:
Python, Go, Rust, Kubernetes, REST APIs, databases, Docker,
C, PHP, SQL. Always learning new things because honestly,
every few years there's something better.

What gets me excited:
Building infrastructure that enables companies to scale
reliably. APIs that are intuitive. Code that's reliable and
performant. Remote work where you can actually focus. Teams
that communicate well in writing.

What I'm not interested in:
On-call rotations. Unnecessary meetings. Hype over substance.

Let's chat if:
You're building backend infrastructure, APIs, or platforms
that people genuinely want to use. Remote work is required.

https://github.com/malwhile
https://flow.halvo.me

Why This Final Version:

• Completes the profile (shows what to avoid)
• Clear call-to-action for recruiters
• Adds blog link (proof of thought leadership)
• Slightly more specific about what problems you solve
• Remote work requirement is clear (not just preference)

---

Medium Priority Changes

3. EXPERIENCE DESCRIPTIONS

Current Status: (as of March 18, 2026)

Role	Status	Description	Priority
Abnormal AI (Current)	❌ Missing	None	🔴 HIGH
Binary Defense	❌ Missing	Tech list only	🔴 HIGH
Kyrus Tech	❌ Missing	Tech list only	🟡 MEDIUM
Parsons	❌ Missing	Tech list only	🟡 MEDIUM
DoD	⚠️ Weak	Generic, vague	🟡 MEDIUM

Assessment: 2/10 - This is a critical gap. Descriptions are missing or too vague.

Why This Matters:

• Recruiters read descriptions to assess fit
• Helps with keyword matching for searches
• Shows impact and scale of your work
• Differentiates you from other engineers
• LinkedIn algorithm favors detailed profiles

---

RECOMMENDED EXPERIENCE DESCRIPTIONS

1. ABNORMAL AI (Current - HIGHEST PRIORITY)

Current: No description

Recommended:

Software Engineer II | Abnormal AI | January 2026 – Present

Designing and maintaining distributed systems serving customers
across US, EU, and government regions.

• Architect and maintain 10 auto-scaling Kubernetes clusters in AWS
  supporting real-time data processing and long-term storage

• Build Python and Go microservices for data aggregation pipelines,
  processing millions of events daily with focus on reliability

• Design and optimize REST APIs for data transfer between services,
  implementing compression and intelligent scaling for efficiency

• Collaborate across 5-person engineering team in monorepo environment
  with heavy inter-team coordination and communication

• Improve system efficiency through auto-scaling strategies and data
  compression, reducing operational costs while maintaining performance

---

2. BINARY DEFENSE (Sr Software Engineer)

Current: Only tech list: "Linux, Python, +6 skills"

Recommended:

Sr Software Engineer | Binary Defense | May 2022 – October 2025

Developed Rust and Python backend systems protecting thousands of Fortune 500
company endpoints across Windows, Linux, and macOS platforms.

• Led Rust development for high-performance monitoring services using tokio
  and cargo, with focus on encrypted SQLite databases and secure key storage

• Built Python microservices and REST APIs for event aggregation, real-time
  threat detection, and data processing pipelines

• Optimized critical systems reducing CPU usage ~90%, memory ~60%, and
  network traffic ~80% through intelligent filtering and regex patterns

• Implemented secure API design patterns including public key pinning and
  certificate transparency logs to prevent MITM attacks

• Designed and built containment systems for compromised endpoints using
  Linux iptables, Windows firewall, and macOS IP firewall

• Established GitLab CI/CD pipelines for unit/integration testing, Docker
  containerization (Linux/Windows), and automated deployment

• Wrote RFCs and Architecture Decision Records (ADRs) to drive technical
  direction and inform platform design decisions

---

3. KYRUS TECH (Senior Software Engineer)

Current: Only tech list: "Linux, Python, +4 skills"

Recommended:

Senior Software Engineer | Kyrus Tech | December 2020 – May 2022

Developed Android-based router fingerprinting tools and covert communications
infrastructure using C, Python, and Docker.

• Built router fingerprinting and vulnerability analysis tools running on
  Android devices using HTTPS, TCP/IP, and encryption protocols

• Designed covert communications proxy supporting HTTPS, Apache Thrift, and
  REST APIs with multi-threaded routing through middle nodes

• Implemented encrypted data transfers and RSA key exchange for secure
  communications

• Practiced test-driven development (TDD) with C and Python, using Docker
  containerization and GitLab CI/CD pipelines

• Collaborated with team using SCRUM methodology for agile development

---

4. PARSONS CORPORATION (Senior Software Engineer)

Current: Only tech list: "Linux, Python, +5 skills"

Recommended:

Senior Software Engineer | Parsons Corporation | April 2017 – December 2020

Developed modular Windows application and backend file storage service for
data aggregation and secure communications.

• Built covert Windows application in C and C++ with plugin architecture,
  supporting library injection and dynamic plugin loading

• Designed custom API and serialization format for minimal bandwidth
  communications, aggregating/consolidating data from multiple nodes

• Developed Java/Tomcat backend file storage service with nginx, NiFi,
  Hadoop, MySQL, LDAP, and RBAC integration

• Implemented multi-level user access controls and RBAC for secure file
  uploads and metadata generation for search functionality

• Optimized storage efficiency through deduplication, allowing multiple
  users to share uploaded files while maintaining data integrity

---

5. DOD (Software Engineer → Security Software Engineer)

Current: "Started in IT, then moved to a Software Engineering position in 2011. That position transitioned into a Software Security Engineering position where I was the primary on a large security web framework."

Problem: Vague, doesn't show impact or scale

Recommended:

Security Software Engineer | United States Department of Defense
September 2009 – April 2017

Built browser security platform and backend services for Red Team operations
supporting military and government customers.

• Designed and maintained REST and JSON APIs for data transfer between
  exploitation targets and backend servers, supporting thousands of records

• Developed dynamic browser UI using jQuery and PHP for real-time data
  visualization, graphs, and charts showing target information across
  thousands of endpoints

• Architected MySQL database for enumeration and exploitation data with
  optimization for query performance under high load

• Implemented backend server infrastructure using PHP, JavaScript, Java, and
  Tomcat supporting concurrent exploitation and data processing

• Built browser exploits using CVEs and proof-of-concept exploits with
  obfuscation for evasion and detection avoidance

• Provided training and documentation for NSA RT operators and new developers,
  developing SOPs for exploitation tools and vulnerability mitigation
  strategies for military and government customers

• Mentored and trained team of 5+ contractors on exploitation techniques and
  system administration

• Collaborated with military branches, DoD, DoJ, and other government
  departments supporting their security operations

---

BEST PRACTICES FOR LINKEDIN DESCRIPTIONS

Format:

• Start with 1-2 sentence summary of role
• Use bullet points (easier to scan)
• Include metrics/scale where relevant
• Focus on impact, not just tools
• Aim for 5-8 bullets per role

What to Include:

• ✅ Technologies you used
• ✅ Scale/impact (customers, systems, metrics)
• ✅ Problems you solved
• ✅ Team/collaboration
• ✅ Achievements with numbers if possible

What to Avoid:

• ❌ Just listing tools ("Used Python, Docker, Kubernetes")
• ❌ Too long (keep it scannable)
• ❌ Vague language ("worked on stuff")
• ❌ Negative framing
• ❌ Too much jargon

---

ACTION ITEMS

Immediate (This Week):

1. Update Abnormal AI with full description (CRITICAL - you're there now)
2. Update Binary Defense with achievements/metrics
3. Update Kyrus Tech with technologies and accomplishments

Soon (This Month):

1. Update Parsons Corporation description
2. Rewrite DoD description to show real impact and scale

Best Approach:

• Copy the recommended text above
• Adjust to match your actual work
• Add/remove bullets as needed
• Keep it honest but impactful

---

4. SKILLS SECTION

Current Status: (as of March 18, 2026)

Your Top 5 Skills:

1. Python (Programming Language)
2. Go (Programming Language)
3. Rust (Programming Language)
4. Docker Products
5. SQL

Assessment: 7/10 - Good foundation, but missing critical keywords for recruiter searches

What's Working:

• ✅ Python, Go, Rust in top 3 (your core strengths)
• ✅ Docker included (important for modern backend)
• ✅ SQL foundational skill
• ✅ Focused list (not bloated)

Critical Gaps (Add These):

• ❌ REST APIs / API Design - This is a MAJOR strength and very searchable
• ❌ Kubernetes - You manage 10 K8s clusters! This is huge.
• ❌ PostgreSQL - Specific database you use extensively
• ❌ Microservices - Core architecture you work with
• ❌ AWS - Cloud platform you use daily
• ❌ Git/GitLab - Essential version control
• ❌ Test-Driven Development - Mentioned in about, should be listed

Minor Issues:

• "Docker Products" → Just say "Docker" (cleaner)
• Missing MySQL (though PostgreSQL is more important)
• Missing JavaScript/TypeScript (you use React)

Recommended Skills List (Priority Order):

Tier 1 (Core - Must Have):

1. Python (Programming Language)
2. Go (Programming Language)
3. Rust (Programming Language)
4. REST APIs
5. Kubernetes
6. Docker
7. API Design
8. AWS

Tier 2 (Important - Should Have):

9. Microservices Architecture
10. PostgreSQL
11. Test-Driven Development
12. Distributed Systems
13. GitLab CI/CD
14. Git

Tier 3 (Nice to Have):

15. MySQL
16. JavaScript
17. C (Programming Language)
18. Linux
19. Authentication (OAuth, JWT)
20. YAML

Why This Order Matters:

1. Recruiter Searches: They search for "Python", "Kubernetes", "REST APIs", "AWS" - not "Docker Products"
2. Keyword Matching: ATS systems and LinkedIn algorithm match your skills to job descriptions
3. Your Actual Work: Kubernetes is way more important than just listing Docker
4. Endorsements: More common skills get more endorsements from colleagues

Action Items:

Immediate (This Week):

• Change "Docker Products" → "Docker"
• Add "REST APIs"
• Add "Kubernetes"
• Add "AWS"
• Add "API Design"

This Month:

• Add "Microservices Architecture"
• Add "PostgreSQL"
• Add "Test-Driven Development"

Nice to Have:

• Add MySQL, JavaScript, Git, C, Linux, etc. as you have space

How to Add Skills on LinkedIn:

1. Go to your Skills & Endorsements section
2. Click "Add a skill"
3. Type the skill name
4. Select from suggestions
5. Click Add

Get Endorsements:

• Ask colleagues from Binary Defense, Abnormal AI, NSA
• Ask them to endorse: Python, Kubernetes, REST APIs, AWS
• These 4 will help most with recruiter visibility

Pro Tip: LinkedIn shows your top 3 endorsed skills prominently. Encourage endorsements from:

• Abnormal AI teammates (for: Python, Kubernetes, AWS, Go)
• Binary Defense colleagues (for: REST APIs, Rust, Python, API Design)

---

Activity & Content Strategy

Current Status

Your Activity:

• Followers: 96 (room to grow)
• Posts: 0 (not yet started)

Assessment: 0/10 - No activity, but this is a quick win

Why LinkedIn Content Matters

LinkedIn's algorithm strongly favors profiles that post regularly. This means:

• More profile views for you
• Higher visibility in recruiter searches
• Shows you're active and engaged
• Demonstrates thought leadership

The Good News: You don't need to post constantly. Even 1-2 posts per month helps significantly.

What Paul Should Post About

Best Content For You:

1. Share Blog Articles (2-3x per month)

   • You have flow.halvo.me - leverage it!
   • Write about: Backend systems, API design, distributed systems, Kubernetes
   • Example: "Just wrote about scaling microservices on Kubernetes..."
   • Link to your blog post

2. Short Technical Insights (1x per month)

   • Quick tip about Python, Go, Rust
   • Performance optimization lessons
   • API design patterns
   • Example: "Just optimized our REST API response time by 30% using..."

3. Career Reflections (1x per month)

   • Why you prefer remote work
   • Lessons from 15 years of backend development
   • What makes good infrastructure
   • Example: "After 15 years building backend systems, here's what I've learned..."

4. Open Source Contributions (As applicable)

   • New feature in testct/ctclient
   • Project updates
   • Example: "Just released v1.0 of Certificate Transparency monitoring tool..."

5. Industry Takes (Occasional)

   • On-call culture, work sustainability
   • Infrastructure trends
   • Remote work benefits
   • Example: "On-call rotations are burning out engineers. Here's a better way..."

What NOT to Post

• ❌ Self-promotion spam ("Hire me!")
• ❌ Overly controversial politics/religion
• ❌ Repeated reposts of others' content
• ❌ Low-effort/no-substance posts
• ❌ Job complaints or negativity

Content Strategy (Recommended)

Frequency: 2-3 posts per month (perfect balance)

Mix:

• 50% Blog article shares (with your own commentary)
• 25% Technical insights/tips
• 25% Career reflections or industry takes

Example Monthly Schedule:

Week 1: Share blog article about distributed systems
Week 2: Short technical tip about Python performance
Week 3: Career reflection about what you've learned
Week 4: Either another blog share or industry take

How to Share Your Blog

Step 1: Write on flow.halvo.me

• You already have a blog - use it!
• Write about things you're working on/learning

Step 2: Share on LinkedIn

• Copy first few lines of article
• Add your own commentary
• Link to full article on blog
• Add relevant hashtags (#Python #Kubernetes #BackendEngineering)

Step 3: Engage

• Reply to comments
• Thank people for reading
• Builds your network

Expected Results

If you post 2-3x per month:

• Followers: Could grow to 200-300 in 6 months
• Profile Views: Increase by 50-100%
• Recruiter Interest: Significantly higher
• Credibility: Demonstrates active, engaged engineer

Next Steps

1. Write 2-3 blog posts on flow.halvo.me (schedule them)
2. Share first post on LinkedIn with commentary
3. Set calendar reminder for weekly/bi-weekly posting
4. Engage with comments

Example First Post:

LinkedIn Post:
"After 15 years building backend systems, I'm convinced
that API design is where engineering excellence shines through.

Just published a deep dive on building scalable REST APIs
that developers actually love to use. Link below.

What's been your biggest challenge with API design?"

[Link to blog post]
#SoftwareEngineering #APIs #BackendDevelopment

---

Sections to Add/Complete

5. PROJECTS SECTION

Add Your Open Source Work:

• testct & ctclient (Rust) - Certificate Transparency testing and monitoring tools

  • Link: github.com/malwhile

• sjles-pta-vote (Go, TypeScript, React) - Full-stack community voting platform

  • Link: github.com/malwhile

• baseball-nn (Python) - Machine learning with neural networks

• date-scanned-pics (Python) - EXIF metadata utility for photo organization

Why It Matters:

• Proves you actually ship code
• Shows breadth of skills
• Recruiters love seeing real projects
• Links directly to GitHub

---

6. OPEN TO WORK STATUS

Action: Turn on "Open to Work"

• Make visible to recruiters only
• Target: Backend Engineer, Systems Engineer, API Design roles
• Location: Remote preferred
• Job titles to target: Backend Engineer, Senior Backend Engineer, Platform Engineer, Systems Engineer

Benefits:

• Recruiters can find you in searches
• Shows active interest without broadcasting to current employer
• Can filter by role type, level, and location

---

7. RECOMMENDATIONS & ENDORSEMENTS

Action: Ask 3-5 colleagues for recommendations

• Binary Defense teammates
• Abnormal AI colleagues
• Previous managers
• Personal projects collaborators

What to Ask For:

• Specific example of work you did well
• Any positive personality trait (collaborative, reliable, etc.)
• 2-3 sentences is enough

Endorsements:

• Ask people in your network to endorse your top 10 skills
• Prioritize: Python, Go, REST APIs, Kubernetes, Docker

---

8. ADD FEATURED SECTION

Add Links To:

• GitHub profile (github.com/malwhile)
• Personal blog (flow.halvo.me)
• Notable project repos

Why:

• Immediately shows work samples
• Recruiters click through to see code
• Demonstrates active development

---

Optional But Nice-To-Have

9. CERTIFICATIONS

• Consider removing expired Security+ (expired 04/04/2024)
• Or add new certifications if you pursue any

10. VOLUNTEER EXPERIENCE

• Web Admin for PTA (shows leadership, community work)
• Could add this to show balanced profile

11. PUBLICATIONS / ARTICLES

• Link to blog posts at flow.halvo.me
• Technical writing shows thought leadership

12. VERIFY BADGE

• You mentioned this - LinkedIn verifies identity through ID verification
• Useful for credibility but optional

---

Action Checklist

This Week (30 minutes):

• Update headline to "Software Engineer | Systems Tinkerer" ✅
• Update About section with recommended text ✅
• Skills section reviewed (have recommendations) ✅
• ADD ABNORMAL AI DESCRIPTION (most critical - you're there now!)
• Add blog link (flow.halvo.me) to About section
• Update Skills: Add REST APIs, Kubernetes, AWS, API Design
• Change "Docker Products" → "Docker"

This Month (1-2 hours):

• Complete ALL experience descriptions (Abnormal AI, Binary Defense, Kyrus Tech, Parsons, DoD)
• Add remaining important skills (Microservices, PostgreSQL, TDD)
• Turn on "Open to Work" (recruiters only)
• Ask 3-5 colleagues to endorse: Python, Kubernetes, REST APIs, AWS

Next (1-2 hours):

• Add Projects section with GitHub links
• Add Featured section linking to GitHub & blog
• Ask colleagues for recommendations
• Link to blog articles in Featured section
• Add MySQL, JavaScript, Git, C, Linux skills

Content Strategy (Start Soon):

• Write 2-3 blog posts on flow.halvo.me
• Share first blog post on LinkedIn (this week if possible)
• Schedule 2-3 posts per month going forward
• Engage with comments on posts

Optional:

• Add volunteer experience (PTA)
• Add Certifications section
• Turn on "Open to Work" if not already done

---

LinkedIn Best Practices for Engineers

Profile Completeness

• Full profile → 40x more profile views
• Profile photo → 21x more profile views
• Headline + About → recruiters can quickly assess fit

Keyword Strategy

• Recruiter searches use headline keywords
• Include: Python, Go, Rust, APIs, Kubernetes, etc.
• Match to job descriptions you actually want

Networking

• With 93 connections, aim for 200-300+
• Connect with colleagues from past roles
• Connect with people in roles you want

Content Strategy

• Posts/articles help with visibility
• But focus first on profile completeness
• Sharing blog posts is fine

Avoid

• Generic headline ("Software Engineer", "Developer")
• Outdated experience descriptions
• Incomplete profiles
• Stale skills section
• No profile photo
• No contact links (GitHub, blog, etc.)

---

Profile Update History

March 18, 2026

Completed:

• ✅ Headline updated: "Software Engineer | Systems Tinkerer"
• ✅ About section reviewed and recommendations provided
• ✅ GitHub link in About
• ✅ Skills section reviewed (Python, Go, Rust, Docker, SQL)

In Progress:

• ⏳ Add blog link to About (flow.halvo.me)
• ⏳ Add critical skills: REST APIs, Kubernetes, AWS, API Design
• ⏳ Write Experience descriptions (template provided for all 5 roles)
• ⏳ Enhance Education section (add honors, thesis, training)

Not Yet Started:

• ⏳ Open to Work section
• ⏳ Projects section
• ⏳ Featured section
• ⏳ Colleague endorsements/recommendations

---

Next Steps to Review

Please Share:

1. Abnormal AI Experience Description

   • What's currently listed?
   • How long? What are the key achievements/bullets?

2. Skills Section

   • What skills are currently listed?
   • In what order?
   • Any outdated skills?

3. Other Experience Descriptions

   • Binary Defense: Sr Software Engineer
   • NSA roles
   • Any others you want reviewed?

---

JOB SEARCH STRATEGY (The Real Secret)

Key Insight: Most people apply through LinkedIn & Indeed. There's WAY less competition on company career pages and alternative job boards.

12 Job Boards Most People Ignore

General Job Boards:

1. Company Direct Careers Pages ⭐ THE GOLDMINE

   • Roles that never hit job boards
   • Apply directly: [company-name]/careers

2. Indeed - https://indeed.com

   • Aggregates across the web
   • Catches hidden roles from company pages

3. JobServe - https://jobserve.com

   • IT, finance, engineering
   • Less competition on contract roles

4. Cord.co - https://cord.co

   • Companies apply to YOU
   • Startup and scale-up focus

5. Totaljobs - https://totaljobs.com

   • UK reach, advanced filters
   • Fine-tuned location/salary/skills

6. LinkedIn - https://linkedin.com/jobs

   • World's largest professional network
   • Use for visibility + direct networking

Remote Job Boards:

7. WeWorkRemotely - https://weworkremotely.com

   • Curated, trusted by top remote companies
   • Engineering, product, design focus

8. RemoteOK - https://remoteok.com

   • Smart filters (AI, No Degree, Non-Tech)
   • Salary and time-zone info upfront

9. JustRemote - https://justremote.co

   • Time-zone friendly search
   • "Anywhere" roles

10. DailyRemote - https://dailyremote.com

    • Fresh listings daily
    • Design, dev, customer support

11. Built In - https://builtin.com

    • Startup and high-growth companies
    • Detailed company culture pages

12. Hiring Cafe - https://hiring.cafe

    • Community feel, curated roles
    • Networking with other remote workers

---

The Winning Strategy

Step 1: See Job on Job Board

• LinkedIn, Indeed, RemoteOK, WeWorkRemotely, etc.

Step 2: Verify on Company Website

• Search "[Company Name] careers"
• Confirm the job is posted there
• Get the direct application link

Step 3: Apply Directly on Company Site

• Less competition
• Your application goes straight to hiring team
• Often better ATS compatibility

Step 4: Follow Up

• Connect with hiring manager on LinkedIn
• Reference the role in your message
• Mention you applied directly

---

Job Board Strategy for Paul

Daily Check (5 minutes):

• Built In (relevant for your profile)
• RemoteOK (backend + python focus)
• WeWorkRemotely (startup focus)

Weekly Check (10 minutes):

• DailyRemote (fresh listings)
• Cord.co (might find you)
• Company career pages (Target companies: Stripe, GitLab, Automattic, Zapier, etc.)

Monthly Check:

• JobServe (contract opportunities)
• JustRemote (new options)
• Hiring Cafe (community roles)

---

Target Companies for Direct Applications

Based on your background, apply directly to:

High Fit:

• Stripe (stripe.com/jobs) - Multiple backend roles we found
• GitLab (gitlab.com/careers) - API/platform work
• Automattic (automattic.com/jobs) - Remote-first, backend focused
• Zapier (zapier.com/jobs) - You already applied!

Medium Fit:

• Cloudflare (cloudflare.com/careers)
• Vercel (vercel.com/careers)
• Shopify (shopify.com/careers/search)
• Twilio (twilio.com/careers)
• Segment (segment.com/careers)

Action: Check these 8 companies' career pages weekly

---

Why This Works

✅ Less Competition - Company sites get 10-20% of applicants vs. job boards ✅ Direct Pipeline - Your app goes to hiring team, not filtered by ATS ✅ Commitment Signal - Shows you researched the company ✅ Better Fit - You're finding roles that match your profile, not mass applying ✅ Faster Response - Direct applications get faster replies

---

Notes

• LinkedIn algorithm favors complete profiles
• Update your profile every 3-6 months
• Your GitHub and blog are your real portfolio - link them prominently
• Job search strategy: Ignore crowded job boards, apply directly on company sites
• Use alternative job boards (RemoteOK, WeWorkRemotely, Built In) for less competition

---

EDUCATION SECTION

Current Status: (as of March 18, 2026)

Your Education:

Master of Science - Computer Science
University of Maryland Baltimore County
Aug 2011 – May 2013
(No description)

Bachelor of Science - Computer Science
Salisbury University
Aug 2005 – May 2009
Activities: Math and Computer Science Club, Linux Lab Administrator
(No description)

Assessment: 6/10 - Good foundations, but missing important details

What's Missing:

1. Honors/GPA:

   • ✅ Salisbury: Magna Cum Laude (IMPORTANT - should highlight!)
   • ❓ UMBC: Not mentioned (what was your GPA?)

2. Thesis Information:

   • UMBC Thesis: "Stateless Detection of Malicious Traffic: Emphasis on User Privacy"
   • This is relevant to your security/backend work!

3. Additional Training:

   • Royal Military College (RMC Canada) - Training in OpenBSD development and administration
   • Not listed!

4. Descriptions:

   • No context on what you studied or why it matters
   • Could strengthen positioning

Recommended Updates:

Master's Degree

Master of Science in Computer Science
University of Maryland Baltimore County
Aug 2011 – May 2013

Thesis: "Stateless Detection of Malicious Traffic: Emphasis on User Privacy"

Focus on security, network analysis, and privacy-preserving systems.

Bachelor's Degree

Bachelor of Science in Computer Science
Salisbury University
Aug 2005 – May 2009
Magna Cum Laude

Activities and Societies:
• Math and Computer Science Club
• Linux Lab Administrator - Maintained dual-boot Linux labs (OpenSUSE/WindowsXP) with SSH access, user management (LDAP), backups, and updates

Additional Training

Add a separate education entry:

OpenBSD Development & Administration
Royal Military College (RMC Canada)
Training in OpenBSD development and administration, security hardening,
and system configuration

---

Why These Updates Matter

1. Honors: "Magna Cum Laude" is prestigious - should be visible
2. Thesis: Shows you did relevant security research
3. RMC Training: Adds credibility for security/systems work
4. Activity Details: Shows you had hands-on Linux experience early
5. Descriptions: Help LinkedIn algorithm and recruiters understand your background

---

Education Checklist

• Add "Magna Cum Laude" to Salisbury degree
• Add thesis title to UMBC degree
• Expand activity descriptions (especially Linux Lab Admin role)
• Consider adding RMC Canada as separate education entry
• Verify all dates are correct

---

RECOMMENDATIONS & ENDORSEMENTS

Current Status: (as of March 18, 2026)

Received Recommendations:

• ✅ 1 recommendation from Bobby Dorrance (Lead Software Engineer, Binary Defense)
• ✅ High quality (highlights technical expertise, collaboration, reliability)
• ❌ Only 1 (need more!)

Given Recommendations:

• ❌ 0 (haven't given any yet)

Assessment: 4/10 - Quality is good, but quantity is low

Why Recommendations Matter

LinkedIn prioritizes profiles with multiple recommendations:

• Shows credibility and social proof
• Recruiters trust peer endorsements
• Algorithm boosts visibility
• Demonstrates collaboration skills
• More recommendations = higher profile ranking

---

CURRENT RECOMMENDATION (Bobby Dorrance)

Quality Analysis:

• ✅ Specific examples (technical expertise, product releases)
• ✅ Personal qualities mentioned (kind, respectful, positive)
• ✅ Clear impact statement ("integral in helping...")
• ✅ Strong closing ("any team would be happy to have him")

Why It Works: Bobby was a peer/senior colleague, not a direct manager, which adds credibility. He can speak to Paul's work ethic and collaboration style.

---

STRATEGY: GET MORE RECOMMENDATIONS

Goal: 3-5 recommendations total (targeting 4 more)

Who to Ask:

Priority 1 (Abnormal AI - Current Role):

• Someone from your current team (1 person)
• A direct collaborator/teammate (1 person)

Priority 2 (Binary Defense):

• Another teammate besides Bobby (1 person)

Priority 3 (Earlier Roles):

• Someone from Kyrus Tech or Parsons (1 person)

How to Ask for a Recommendation

Email Template:

Subject: LinkedIn Recommendation Request

Hi [Name],

I'm updating my LinkedIn profile and would love to have a recommendation
from you based on our work together at [Company]. Your perspective on
[specific project/collaboration] would be really valuable.

It just takes a few minutes to add a recommendation on LinkedIn. If you're
open to it, I can send you the direct link.

Thanks for considering!

Best,
Paul

Make It Easy:

• Send them the direct LinkedIn link
• Suggest what they could mention (if helpful)
• Don't pressure - keep it light

---

WHAT MAKES A GOOD RECOMMENDATION

Strong Recommendations Include:

1. Specific Examples - "Paul optimized our API response time by 30%"
2. Personal Qualities - "Reliable, communicates clearly, problem-solver"
3. Impact Statement - "His work directly improved system performance"
4. Context - "We worked together on Kubernetes migration"
5. Strong Closing - "Highly recommend for any backend role"

---

GIVE RECOMMENDATIONS TO OTHERS

Important: You have 0 recommendations given. This is a missed opportunity.

Strategy:

• Give recommendations to 2-3 people from Binary Defense/Abnormal AI
• When you give one, it's a gentle ask for one back
• Shows reciprocity
• Helps your network

Who to Recommend:

• Bobby Dorrance (he gave you one - reciprocate!)
• Other good colleagues from Binary Defense
• Someone from Abnormal AI if you have a close colleague

---

ACTION PLAN

This Week (10 minutes):

• Send recommendation request to 1-2 people from Abnormal AI
• Send recommendation request to 1 person from Binary Defense

Next Week:

• Send recommendation request to 1 more person from earlier roles
• Give a recommendation to Bobby Dorrance (reciprocate his kindness)

Why This Matters:

• 4-5 recommendations will significantly boost profile credibility
• Much easier to ask now while you're actively job searching
• Shows you value peer relationships

---

RECOMMENDATION CHECKLIST

• Reach out to 3-4 people for recommendations
• Give recommendation to Bobby Dorrance
• Give recommendations to 1-2 others
• Target: 4-5 recommendations total
• Check recommendations weekly