# Who is the HackerOne Code Community of Experts?

## What do reviews from our engineers look like?

Think of HackerOne Code as an extension of your current team. An engineer will be reviewing your code before it is merged. Their feedback is posted in your source control provider alongside your internal developers. This means you'll be able collaborate with our engineers just like one of your teammates.

![](/files/-MBf7tXIeNRe6HpAxi25)

### Can I see some examples?

Yes!

* [https://github.com/oughtinc/ergo/pull/61](<https://github.com/oughtinc/ergo/pull/61&#xA;>)
* <https://github.com/oughtinc/ergo/pull/55>
* <https://github.com/Unity-Technologies/unity-cache-server/pull/36>
* <https://github.com/commons-app/apps-android-commons/pull/3046>

You can also check out our walkthrough/demo here: <https://hackerone.navattic.com/dub0m4q?g=cmcv3tdiv000304kwh9fa9dqz&s=0>

## **What are HackerOne experts like?**

Reviewers are mostly based in the US and are senior-level software engineers with 5+ years\* experience building complex applications and systems.

<figure><img src="/files/CN9xtmgnpNiVKXXRL5eI" alt=""><figcaption></figcaption></figure>

Members come from a variety of backgrounds and include:&#x20;

* Serial technical founders
* Major language/framework maintainers
* CS PhDs
* Technical project owners at companies like Google, SpaceX, Amazon, Uber, Instagram, Square, Dropbox, Microsoft, Zynga, Coursera, NASA, Lockheed Martin, Bloomberg, Moz, Procore, and many, many more.

Here are some guest contributions our reviewers have made to our blog:

[**What To Look For When Reviewing C#**](https://www.pullrequest.com/blog/reviewing-csharp-code/) by [Artak Mkrtchyan](https://www.linkedin.com/in/mkartak/)\
[**How to Write a Good Code Comment**](https://www.pullrequest.com/blog/how-to-write-a-good-code-comment/) by [Tyler Adams](https://www.linkedin.com/in/tyler-adams-60644714/)\
[**Writing A Great Pull Request Description**](https://www.pullrequest.com/blog/writing-a-great-pull-request-description/) by [Gonzalo Bañuelos](https://www.linkedin.com/in/gbanuel/)\
[**The Top 5 Mistakes Made in Angular Projects**](https://www.pullrequest.com/blog/top-5-mistakes-in-angular-projects/) by [Alain Chautard](https://www.linkedin.com/in/achautard/)\
[**Top 3 Security Vulnerabilities I Find in iOS and Android Projects**](https://www.pullrequest.com/blog/top-3-security-vulnerabilities-in-ios-android-projects/) by [Chris Griffith](https://www.linkedin.com/in/criggles/)

![](/files/-MBfI-CStfy29XryQpo7)

&#x20;*\* With rare and extraordinary exceptions.*


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pullrequest.com/customer-documentation/frequently-asked-questions/what-to-expect/who-is-the-hackerone-code-community-of-experts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.