# Ben Balter (@ben.balter.com)

Profile: https://sifa.id/p/ben.balter.com
Headline: Product leader for developer platforms and open source
Location: Washington, District of Columbia, United States

## About

I'm a product leader for developer platforms and open source, and a lawyer who ships code. For five years I was a GitHub product manager for trust and safety, shipping 500+ features and policies, plus the github.com API endpoints behind them, on a platform with 50M+ users and 100M+ projects. Before that, I led a bottom-up rewrite of GitHub Pages (250,000+ pages a minute) and wrote Licensee, the open source library behind GitHub's license detection. My open source projects have hundreds of millions of downloads.

Most recently I owned the internal platform 4,000+ GitHubbers use to get work done: 96% durable content ownership, deploys cut from over an hour to under 10 minutes, and self-serve publishing for non-technical teams. I led a team of six and merged 700+ pull requests with Copilot. I've also been Chief of Staff for Security, Director of Engineering Operations and Culture, and the company's first Government Evangelist, driving adoption across nearly 2,000 government organizations in 75+ countries.

I'm also the author of Open and Async, the collaborative software development playbook for remote and distributed teams. It ships with a Model Context Protocol server, so agents can query its practices directly.

Before GitHub, I served as a Presidential Innovation Fellow and a member of the White House's first agile development team, helping draft parts of President Obama's Digital Strategy and Open Data Policy. The US CTO once called me one of "the baddest of the badass innovators," the single nicest thing anyone's ever put in print about me. I'm also an attorney, a member of the DC Bar, and argued in the Public Contract Law Journal that federal IT procurement should look more like modern software development.

What I care about:
• Developer platforms: APIs, open source libraries, and developer experience
• Building for agents: MCP, Markdown, and making platforms legible to AI tools as well as people
• Open source: sustaining communities, licensing, and making collaboration the default
• Remote and async work: clear writing, strong defaults, and showing your work

I hold a J.D. and M.B.A. from the George Washington University.

More at ben.balter.com.

## Career

- **Author at Open & Async** (May 2026 - Present)
  Open and Async: the collaborative software development playbook for remote and distributed teams.
  • Shipped end to end: Wrote, produced, and launched the book in print, ebook, and audiobook, with accessibility designed in from the first draft rather than retrofitted at the end.
  • Built for agents too: Shipped a Model Context Protocol server alongside the book, generated from the manuscript's own structure, so an agent can query its practices directly instead of working from a scraped copy.
  • Published and distributed: Took a 576-page, ten-part playbook from manuscript to ebook and paperback across major retailers, and documented the production process in public as the book was written.
  • Codified the practice: Turned a decade of remote-first work at GitHub into a playbook on working in the open, defaulting to async, and measuring impact over hours logged.
- **Director of Hubber (Employee) Enablement, Office of the COO at GitHub** (Jul 2024 - Jul 2026)
  Product owner for GitHub's internal employee platform: the knowledge base, onboarding, and enablement tooling 4,000+ Hubbers use to get work done. Led a team of six across product, engineering, and content.
  • Platform product ownership: Owned the roadmap for the company's internal knowledge platform, driving durable content ownership to 96%, cutting deploy times from over an hour to under 10 minutes, and shipping a WYSIWYG editor that moved non-technical teams off filing tickets and onto self-serve publishing.
  • Shipped as a builder: Merged 700+ pull requests with GitHub Copilot, adding the delivery capacity of an additional engineer and accelerating automation, accessibility, and platform work across internal tools.
  • Incident communications: Owned internal communications and stakeholder status updates during active incidents.
  • Onboarding as a product: Rebuilt company-wide onboarding to 100% semi-async coverage, and ran a continuous learning program that reaches the majority of employees every month.
- **Director of Engineering Operations and Culture at GitHub** (Feb 2023 - Jul 2024)
  • Team leadership: Built and led a team of seven business technologists supporting Engineering executives, improving department-level and org-wide operations through internal communication, data-driven decision-making, escalation-based initiative management, and workforce planning.
  • Communication: Designed and implemented organizational async communication patterns that improved information discoverability for globally distributed teams, using AI to increase signal-to-noise for developers while limiting disruption through empathetic change management.
  • Internal tooling: Cut friction across Engineering by championing automation and shipping a suite of tools for internal communications, weekly reporting, headcount tracking, rhythm of business, and cultural touchstones.
- **Chief of Staff, Security at GitHub** (Jul 2021 - Feb 2023)
  • Directly involved in the majority of Security Incident Response Team (SIRT) incidents, coordinating across teams and driving escalations.
  • Strategic advisor and counsel to the Chief Security Officer: shaped the organization's vision, OKRs, and long-term plans, and represented the CSO in cross-functional leadership forums.
- **Staff Technical Program Manager, Enterprise and Compliance at GitHub** (Jan 2021 - Jul 2021)
  • Led organization-wide business readiness for GitHub AE, GitHub's managed enterprise SaaS offering, ahead of general availability for customers in high-compliance industries.
  • As a founding member of GitHub's Technical Program Management organization, managed business functions across GitHub Enterprise Server releases and built a weekly program-reporting process, adopted org-wide, to communicate status, risks, and mitigations to executives.
- **Senior Product Manager, Trust and Safety at GitHub** (Feb 2016 - Jan 2021)
  • Led community, safety, privacy, product security, and platform health for a software development platform with 50M+ customers and 100M+ projects.
  • Wrote and shipped github.com API endpoints powering trust, safety, and platform-health workflows for tens of millions of developers.
  • Shipped 500+ staff- and user-facing features and policies across trust and safety (Community Guidelines, DMCA and abuse reporting, PhotoDNA detection), account security (phishing-resistant 2FA, role-based access controls), and privacy and compliance (third-party analytics removal, data portability, IP ownership).
  • Piloted an Associate Product Management program with a defined promotional path to Product Manager, building the pipeline that shaped GitHub's product culture.
  • Established the Open Source Customer Advisory Board, creating a standing discovery channel between the platform's largest maintainer communities and the product organization.
- **Government Evangelist at GitHub** (Mar 2013 - Feb 2016)
  • Led a bottom-up rewrite of GitHub Pages (1M+ sites, 250,000+ pages/minute) and shipped GeoJSON rendering and diffing, enabling 500,000+ public geospatial datasets.
  • Launched choosealicense.com and wrote Licensee, the open-source library behind GitHub's license-detection API.
  • Led outreach for GitHub's government program, driving open-source, open-data, and open-government adoption across nearly 2,000 government organizations in 75+ countries and 8–10x growth in government users, organizations, and revenue. Named one of the top 25 most influential people in government and technology and FedScoop's Fed50 Disruptor of the Year.
  • Secured GitHub's first government reseller (GSA IT Schedule 70) and FedRAMP-compliant availability in AWS GovCloud, and set the company's export-control (ITAR/EAR) and OFAC compliance policy.
  • Held direct operational ownership of GitHub Pages in production, serving as incident commander during overnight incidents.
- **Presidential Innovation Fellow at Executive Office of the President** (Aug 2012 - Jan 2013)
  • As a member of the inaugural class of Presidential Innovation Fellows, shipped four open-source products from conception to production in six months using then-atypical API-first architecture, including Project MyGov, a citizen-centric prototype that let people use a single profile across federal agency sites instead of a separate account for each. The single-account model it prototyped later shipped government-wide as login.gov.
  • Described by the US Chief Technology Officer as "the baddest of the badass innovators" and by the White House Director of Digital Strategy as "lightning in a bottle".
- **Fellow, Office of the US Chief Information Officer at Executive Office of the President** (Jan 2012 - Aug 2012)
  • Drafted and drove the release of the President's Digital Government Strategy, and built the first-of-its-kind mechanism for agencies to report progress against it.
- **SoftWare Automation and Technology (SWAT) Team, Office of Administration at Executive Office of the President** (Sep 2011 - Jan 2012)
  • On the White House's first-ever agile team, and in close coordination with the Office of Federal Financial Management, led development of a prototype government-wide, open-source property-sharing system, delivering over $300 million in realized savings.
- **New Media Fellow, Office of the Managing Director at Federal Communications Commission** (May 2010 - Jan 2012)
  • Helped relaunch FCC.gov, the agency's public web presence, and built 30+ in-house, open-source tools, including site auditing and mapping software, to evaluate and consolidate a legacy footprint of 1.2 million+ pages. Received the agency's Superior Achievement Award.
  • Handled the legal questions a federal agency runs into when it moves online: cookies, third-party analytics, and using social media to collect public comment. Drafted the site privacy policy, comment-moderation policy, third-party privacy notices, and API terms of service, and built the legal and technical roadmaps for compliance with OMB memoranda M-10-22 and M-10-23.

## Publications

- It's pronounced JIF. The Open and Async audiobook is out. — ben.balter.com (Sep 2026) https://ben.balter.com/2026/09/08/gif-or-jif-audiobook-both-ways/
- Accessible by default: writing a book like software — ben.balter.com (Aug 2026) https://ben.balter.com/2026/08/27/accessible-by-default/
- How I over-engineered my book — ben.balter.com (Aug 2026) https://ben.balter.com/2026/08/17/how-i-over-engineered-my-book/
- Work loudly — ben.balter.com (Jul 2026) https://ben.balter.com/2026/07/14/work-loudly/
- Reorgs happen — ben.balter.com (Jun 2026) https://ben.balter.com/2026/06/07/reorgs-happen/
- AI-first program management: amplifying judgment, not replacing it — ben.balter.com (May 2026) https://ben.balter.com/2026/05/31/ai-first-program-management/
- The brag doc — ben.balter.com (Apr 2026) https://ben.balter.com/2026/04/27/the-brag-doc/
- How to one-on-one — ben.balter.com (Apr 2026) https://ben.balter.com/2026/04/27/one-on-one-playbook/
- No agenda, no meeting — ben.balter.com (Apr 2026) https://ben.balter.com/2026/04/06/no-agenda-no-meeting/
- Agentic workflows and the future of software development — ben.balter.com (Mar 2026) https://ben.balter.com/2026/03/18/agentic-workflows/
- I've worked remotely at GitHub for thirteen years: here's what actually works. — ben.balter.com (Mar 2026) https://ben.balter.com/2026/03/04/thirteen-years-at-github/
- How to run LanguageTool on macOS — ben.balter.com (Jan 2025) https://ben.balter.com/2025/01/30/how-to-run-language-tool-open-source-grammarly-alternative-on-macos/
- The "I don't like what they're saying, so they shouldn't be allowed to say it" approach to crisis management — ben.balter.com (Jan 2024) https://ben.balter.com/2024/01/08/dissenting-voices/
- Cathedral vs Bazaar People Management — ben.balter.com (Dec 2023) https://ben.balter.com/2023/12/08/cathedral-bazaar-management/
- How to communicate like a GitHub engineer — ben.balter.com (Oct 2023) https://ben.balter.com/2023/10/04/how-to-communicate-like-a-github-engineer/
- Transparent collaboration is the andon of knowledge work — ben.balter.com (Aug 2023) https://ben.balter.com/2023/08/30/transparency-collaboration-is-the-andon-of-knowledge-production/
- Remote work requires communicating more, less frequently — ben.balter.com (Aug 2023) https://ben.balter.com/2023/08/04/remote-work-communicate-more-with-less/
- Pull requests are a form of documentation — ben.balter.com (May 2023) https://ben.balter.com/2023/05/19/pull-requests-are-a-form-of-documentations/
- Practice inclusive scheduling — ben.balter.com (May 2023) https://ben.balter.com/2023/05/19/practice-inclusive-scheduling/
- Meetings are a point of escalation, not a starting point — ben.balter.com (Apr 2023) https://ben.balter.com/2023/04/20/meetings-are-a-point-of-escalation/
- Intro to GitHub for non-technical roles — ben.balter.com (Mar 2023) https://ben.balter.com/2023/03/02/github-for-non-technical-roles/
- How to write a great extended leave document — ben.balter.com (Jan 2023) https://ben.balter.com/2023/01/13/great-extended-leave-documents/
- Manage like an engineer — ben.balter.com (Jan 2023) https://ben.balter.com/2023/01/10/manage-like-an-engineer/
- Helpful 404s for Jekyll (and GitHub Pages) — ben.balter.com (Jun 2022) https://ben.balter.com/2022/06/30/helpful-404s-for-jekyll-and-github-pages/
- Why you should work asynchronously — ben.balter.com (Mar 2022) https://ben.balter.com/2022/03/17/why-async/
- The seven things a corporate Chief of Staff does — ben.balter.com (Mar 2022) https://ben.balter.com/2022/03/09/seven-things-a-corporate-chief-of-staff-does/
- Leaders show their work — ben.balter.com (Feb 2022) https://ben.balter.com/2022/02/16/leaders-show-their-work/
- Using GitHub Actions to get notified when an API response (or web page) changes — ben.balter.com (Dec 2021) https://ben.balter.com/2021/12/15/github-actions-website-api-change-notification/
- How I re-over-engineered my home network for privacy and security — ben.balter.com (Sep 2021) https://ben.balter.com/2021/09/01/how-i-re-over-engineered-my-home-network/
- Advice for managing open source communities at scale — ben.balter.com (Jun 2021) https://ben.balter.com/2021/06/15/managing-open-source-communities-at-scale/
- Moderating open source conversations to keep them productive — ben.balter.com (Jun 2021) https://ben.balter.com/2021/06/15/how-to-moderate-open-source-conversations-to-keep-them-productive/
- Five (and a half) practical tips for governing your open source project — ben.balter.com (Jun 2021) https://ben.balter.com/2021/06/14/open-source-governance/
- Nine things a (technical) program manager does — ben.balter.com (Mar 2021) https://ben.balter.com/2021/03/26/nine-things-a-technical-program-manager-does/
- Octoversary - eight years of optimizing for developer happiness — ben.balter.com (Mar 2021) https://ben.balter.com/2021/03/04/octoversary/
- What to read before starting (or interviewing) at GitHub — ben.balter.com (Feb 2021) https://ben.balter.com/2021/02/01/what-to-read-before-starting-or-interviewing-at-github/
- Analysis of federal .gov domains, pre-Biden edition — ben.balter.com (Jan 2021) https://ben.balter.com/2021/01/11/analysis-of-federal-dotgov-domains-pre-biden-edition/
- How I over-engineered my home network for privacy and security — ben.balter.com (Dec 2020) https://ben.balter.com/2020/12/04/over-engineered-home-network-for-privacy-and-security/
- The top 10 posts of the past 10 years — ben.balter.com (Sep 2020) https://ben.balter.com/2020/09/12/10-years/
- Trust and safety is not a product edge case — ben.balter.com (Aug 2020) https://ben.balter.com/2020/08/31/trust-and-safety-is-not-a-product-edge-case/
- Budget for the hidden "internet tax" — ben.balter.com (Aug 2020) https://ben.balter.com/2020/08/31/budget-for-the-hidden-internet-tax/
- Seven trust and safety features to build into your product before someone gets hurt — ben.balter.com (Aug 2020) https://ben.balter.com/2020/08/31/trust-and-safety-features-to-build-into-your-product-before-someone-gets-hurt/
- How I manage GitHub notifications — ben.balter.com (Aug 2020) https://ben.balter.com/2020/08/25/how-i-manage-github-notifications/
- Tools of the trade: How I communicate at GitHub (and why) — ben.balter.com (Aug 2020) https://ben.balter.com/2020/08/14/tools-of-the-trade/
- Automate common open source community management tasks — ben.balter.com (Aug 2020) https://ben.balter.com/2020/08/10/automate-common-open-source-community-management-tasks/
- Seven ways to set open source contributors up for success — ben.balter.com (May 2020) https://ben.balter.com/2020/05/15/set-open-source-contributors-up-for-success/
- Eight tips for working remotely — ben.balter.com (Mar 2020) https://ben.balter.com/2020/03/18/tips-for-working-remotely/
- User blocking vs. user muting — ben.balter.com (Feb 2020) https://ben.balter.com/2020/02/06/blocking-vs-muting/
- 10 lessons learned fostering a community of communities at GitHub — ben.balter.com (Jan 2020) https://ben.balter.com/2020/01/17/ten-lessons-learned-fostering-a-community-of-communities-on-github/
- Resolutions for sustaining and growing open source communities — ben.balter.com (Jan 2020) https://ben.balter.com/2020/01/02/resolutions-for-sustaining-and-growing-open-source-communities/
- A community of communities: Empowering maintainers to grow communities around their code — ben.balter.com (Jul 2019) https://ben.balter.com/2019/07/18/a-community-of-communities-oscon-2019/
- Go near, go far, meet in the middle — ben.balter.com (Jun 2019) https://ben.balter.com/2019/06/28/joining-a-new-team/
- What lawyers can learn from open source — ben.balter.com (Feb 2019) https://ben.balter.com/2019/02/06/open-source-legal-workflows/
- Problems, not solutions — ben.balter.com (Jul 2018) https://ben.balter.com/2018/07/16/problems-not-solutions/
- Yes, No, Maybe — ben.balter.com (May 2018) https://ben.balter.com/2018/05/04/yes-no-maybe/
- Why you probably shouldn't add a CLA to your open source project — ben.balter.com (Jan 2018) https://ben.balter.com/2018/01/02/why-you-probably-shouldnt-add-a-cla-to-your-open-source-project/
- Everything an open source maintainer might need to know about open source licensing — ben.balter.com (Nov 2017) https://ben.balter.com/2017/11/28/everything-an-open-source-maintainer-might-need-to-know-about-open-source-licensing/
- Twelve tips for growing communities around your open source project — ben.balter.com (Nov 2017) https://ben.balter.com/2017/11/10/twelve-tips-for-growing-communities-around-your-open-source-project/
- How not to prioritize a feature — ben.balter.com (Jun 2017) https://ben.balter.com/2017/06/19/how-not-to-prioritize-a-feature/
- Seven ways to consistently ship great features — ben.balter.com (May 2017) https://ben.balter.com/2017/05/23/seven-ways-to-consistently-ship-great-features/
- Using protected branches to empower non-code contributors on GitHub — ben.balter.com (Apr 2017) https://ben.balter.com/2017/04/14/create-an-open-source-moderator-role-with-protected-branches-on-github/
- Your project's README is your project's constitution — ben.balter.com (Apr 2017) https://ben.balter.com/2017/04/14/your-projects-readme-is-your-project-constitution/
- Three easy ways to show employees they're appreciated — ben.balter.com (Apr 2017) https://ben.balter.com/2017/04/04/three-easy-ways-to-show-employees-you-appreciate-them/
- Bikeshed honeypots — ben.balter.com (Mar 2017) https://ben.balter.com/2017/03/01/bikeshed-honeypots/
- How I Atom (for prose) — ben.balter.com (Dec 2016) https://ben.balter.com/2016/12/23/atom-for-prose/
- Eight things I wish I knew my first week at GitHub — ben.balter.com (Oct 2016) https://ben.balter.com/2016/10/31/eight-things-i-wish-i-knew-my-first-week-at-github/
- The seven habits of highly effective GitHubbers — ben.balter.com (Sep 2016) https://ben.balter.com/2016/09/13/seven-habits-of-highly-effective-githubbers/
- How to make a product great — ben.balter.com (Aug 2016) https://ben.balter.com/2016/08/22/ten-ways-to-make-a-product-great/
- Why you shouldn't write your own open source license — ben.balter.com (Aug 2016) https://ben.balter.com/2016/08/01/why-you-shouldnt-write-your-own-open-source-license/
- Removing a feature is a feature — ben.balter.com (Jul 2016) https://ben.balter.com/2016/07/21/removing-a-feature-is-a-feature/
- Books for geeks — ben.balter.com (Jul 2016) https://ben.balter.com/2016/07/11/books-for-geeks/
- Twelve things a product manager does — ben.balter.com (Jun 2016) https://ben.balter.com/2016/06/06/twelve-things-a-product-manager-does/
- Moderating a controversial pull request — ben.balter.com (May 2016) https://ben.balter.com/2016/05/11/moderating-a-controversial-pull-request/
- The missed opportunity that is the White House Open Source Policy — ben.balter.com (Apr 2016) https://ben.balter.com/2016/04/11/white-house-open-source-missed-opportunity/
- Optimizing for power users and edge cases is the easy part — ben.balter.com (Mar 2016) https://ben.balter.com/2016/03/08/optimizing-for-power-users-and-edge-cases/
- How to derail any meeting — ben.balter.com (Jan 2016) https://ben.balter.com/2016/01/15/how-to-derail-any-meeting/
- The six types of pull requests you see on GitHub — ben.balter.com (Dec 2015) https://ben.balter.com/2015/12/08/types-of-pull-requests/
- Open source as Yelp for software — ben.balter.com (Dec 2015) https://ben.balter.com/2015/12/08/open-source-as-yelp-for-software/
- Why open source — ben.balter.com (Nov 2015) https://ben.balter.com/2015/11/23/why-open-source/
- Four characteristics of modern collaboration tools — ben.balter.com (Nov 2015) https://ben.balter.com/2015/11/18/tools-to-empower-open-collaboration/
- Why everything should have a URL — ben.balter.com (Nov 2015) https://ben.balter.com/2015/11/12/why-urls/
- The three biggest challenges in government IT — ben.balter.com (Oct 2015) https://ben.balter.com/2015/10/18/three-biggest-challenges-in-government-it/
- Bringing open source workflows to the enterprise — ben.balter.com (Sep 2015) https://ben.balter.com/2015/09/21/open-source-behind-the-firewall/
- How to add an "improve this content" button to your GitHub Pages site — ben.balter.com (Sep 2015) https://ben.balter.com/2015/09/13/github-pages-edit-button/
- How GitHub uses automated testing to empower developers to write less-corporate blog posts — ben.balter.com (Sep 2015) https://ben.balter.com/2015/09/10/blog-style-tests/
- Five principles to guide any government IT effort — ben.balter.com (Aug 2015) https://ben.balter.com/2015/08/23/reflecting-on-the-mygov-ideals/
- The Zen of GitHub — ben.balter.com (Aug 2015) https://ben.balter.com/2015/08/12/the-zen-of-github/
- Speak like a human: 12 ways tech companies can write less-corporate blog posts — ben.balter.com (Jul 2015) https://ben.balter.com/2015/07/20/write-corporate-blog-posts-as-a-human/
- Open procurement: procurement in an increasingly open source world — ben.balter.com (Jul 2015) https://ben.balter.com/2015/07/11/open-source-procurement/
- Merge by committee — ben.balter.com (Jun 2015) https://ben.balter.com/2015/06/22/merge-by-committee/
- Using GitHub Pages to showcase your organization's open source efforts — ben.balter.com (Jun 2015) https://ben.balter.com/2015/06/11/using-github-pages-to-showcase-your-orgs-open-source-efforts/
- Copyright notices for open source projects — ben.balter.com (Jun 2015) https://ben.balter.com/2015/06/03/copyright-notices-for-websites-and-open-source-projects/
- Test your content — ben.balter.com (May 2015) https://ben.balter.com/2015/05/22/test-your-prose/
- Analysis of federal .gov domains, 2015 edition — ben.balter.com (May 2015) https://ben.balter.com/2015/05/11/third-analysis-of-federal-executive-dotgovs/
- Eight lessons learned hacking on GitHub Pages for six months — ben.balter.com (Apr 2015) https://ben.balter.com/2015/04/27/eight-lessons-learned-hacking-on-github-pages-for-six-months/
- The difference between 18F and USDS — ben.balter.com (Apr 2015) https://ben.balter.com/2015/04/22/the-difference-between-18f-and-usds/
- 19 reasons why technologists don't want to work at your government agency — ben.balter.com (Apr 2015) https://ben.balter.com/2015/04/21/why-technologists-dont-want-to-work-at-your-agency/
- Five best practices in open source: external engagement — ben.balter.com (Mar 2015) https://ben.balter.com/2015/03/17/open-source-best-practices-external-engagement/
- Five best practices in open source: internal collaboration — ben.balter.com (Mar 2015) https://ben.balter.com/2015/03/08/open-source-best-practices-internal-collaboration/
- Explain like I'm five: Jekyll collections — ben.balter.com (Feb 2015) https://ben.balter.com/2015/02/20/jekyll-collections/
- Why your agency's first open source project is going to be a flop — ben.balter.com (Feb 2015) https://ben.balter.com/2015/02/11/why-your-first-open-source-project-is-going-to-be-a-dud/

## Skills

### Business
- Change management
### Interpersonal
- Executive communication
### Other
- Agentic workflows, MCP, and AI-accelerated delivery
- Chief-of-staff operating patterns
- Developer experience
- Enterprise readiness and compliance
- Internal platforms and developer tooling
- Open source libraries and ecosystems
- Open source strategy
- Organizational design
- Platform and API products
- Privacy, security, and compliance
- Product and engineering leadership
- Product strategy and roadmapping
- REST and GraphQL API integration
- Ruby and full-stack development
- Technology law, licensing, and policy
- Trust, safety, and platform health
- Zero-to-one products

## Credentials

- Member, District of Columbia Bar — District of Columbia Bar
- Certified Information Systems Security Professional (CISSP) (expired) — International Information System Security Certification Consortium (ISC)² https://www.credly.com/badges/1a8b31f1-3727-4acf-a6a8-8d67af9ecb23

## Education

- **The George Washington University Law School** — Juris Doctor (2013)
- **The George Washington University School of Business** — Master of Business Administration, Strategic Management and Public Policy (2013)
- **The George Washington University** — Bachelor of Arts, Political Science (2009)

## Links

- GitHub: https://github.com/benbalter (verified)
- linkedin: https://www.linkedin.com/in/benbalter