Skip to main content

Recruiters

2023-08-02: This page is here mostly for historical reference. For the time being, I've taken myself off of the "mainstream" job market. I'm not interested in serving any for-profit venture, so please don't contact me regarding any such opportunities. If you happen to have found this page and are looking for a technical person to assist with a venture that is for public benefit or similar, you may contact me; some of what is below still applies, but we can get into specifics by directly communicating.

First and foremost, thank you for considering me. If you've come across my LinkedIn profile and want to talk about a position, the following information should be helpful in determining if I'm the right fit. In combination with what's posted to LinkedIn, the information below should help you to make an informed decision about whether to contact me for opportunities. I understand that some of what follows may discourage you from contacting me, and that's entirely by design; this is my filter, which will hopefully result in only the most appealing opportunities making it to my inbox, and prevent you from spending time on me that you could be using to contact better candidates for your position. If I send you to this page after a cold solicitation, a response (even to say that you're not interested) would be appreciated.

Professional Summary

I am an information security professional who tends to gravitate toward automation, deployment of security tools, API integrations between products, and all of the "DevOps" work that goes along with such tasks. In previous lives, I've run vulnerability management programs, been the technical owner of static code analysis tooling, SIEM, malware testing and general purpose labs, served as a mentor for new hires, and much more.

Priorities

Location

I'm presently only entertaining opportunities for full-time remote, 0% travel positions.

Work

I work best when given clear objectives and straightforward expectations. Things I'm going to be looking for when discussing any opportunity:

  • What do my first few months look like?
  • What kind of team would I be joining?
    • Size
    • Strategic vision
    • Process maturity
    • Inroads with C-suite / board-level decision makers?
    • Reporting structure

Strengths / Preferences

Cloud Platforms

These days, I spend most of my time writing code for deployments of microservices and vendor integrations into Amazon Web Services. I can get around in Azure but avoid it when possible.

Programming Languages

Most comfortable with

  • Python
  • PHP
  • C++ (including most of the Boost libraries I've dealt with so far)

Inexperienced but willing to learn

  • Go
  • Lua

Actively avoid

  • Java and related languages
  • Ruby

Miscellany

In general, there are at least a few things I'll want to see before accepting any offer. This is a list of those items:

  • A copy of your current employee benefits handbook, or, if you can't share the actual document, details on at least the following:
    • What options do you offer for medical, dental, and vision coverage?
    • Any written policies regarding the earning and appropriate use of paid time off.
    • 401(k) or other tax-advantaged accounts.
  • The pay scale and formal job description (if not already communicated) for the position(s) you're looking to fill.

Also understand that I'll want to take time to review these materials and may have questions about them, so the earlier in the process you can send me the information, the better.

Final Thoughts

Well done, you've made it through the whole thing! If you've read this page, please include the string '0x002A' prominently in any initial communications to me (preferably in the subject line).