<commit_before>---
layout: markdown_page
title: "Developer Responsibilities and Tasks"
---

At GitLab, developers are highly independent and self-organized individual 
contributors who work together as a tight team in a [remote and agile](https://about.gitlab.com/2015/09/14/remote-agile-at-gitlab/) way.


## General Developer Responsibilities

* Develop features from request to polished end result.
* Support our [service engineers](https://about.gitlab/com/jobs/service-engineer) in getting to the bottom of user-reported issues and come up with robust solutions.
* Engage with the rest of the core team and the open source community and collaborate on improving GitLab.
* Review code contributed by the rest of the community and work with them to get it ready for production.
* Write documentation around features and configuration to save our users time.
* Take initiative in improving the software in small or large ways to address pain points in your own experience as a developer.
* Keep code easy to maintain and keep it easy for others to contribute code to GitLab.
* Qualify developers for hiring.

### Responsibilities Split Between Various Developers
* Omnibus packaging
* Chef cookbooks
* DevOps: ensuring that deployments are smooth and scalable
* Maintenance of various servers such as 
   * license.gitlab.com
   * version.gitlab.com
   * status.gitlab.com
   * doc.gitlab.com
   * dev.gitlab.org
* Feature development for GitLab CE, EE, and CI.
<commit_msg>Dev: remove "responsibilities and tasks" from title<commit_after>---
layout: markdown_page
title: "Developer"
---

At GitLab, developers are highly independent and self-organized individual 
contributors who work together as a tight team in a [remote and agile](https://about.gitlab.com/2015/09/14/remote-agile-at-gitlab/) way.


## General Developer Responsibilities

* Develop features from request to polished end result.
* Support our [service engineers](https://about.gitlab/com/jobs/service-engineer) in getting to the bottom of user-reported issues and come up with robust solutions.
* Engage with the rest of the core team and the open source community and collaborate on improving GitLab.
* Review code contributed by the rest of the community and work with them to get it ready for production.
* Write documentation around features and configuration to save our users time.
* Take initiative in improving the software in small or large ways to address pain points in your own experience as a developer.
* Keep code easy to maintain and keep it easy for others to contribute code to GitLab.
* Qualify developers for hiring.

### Responsibilities Split Between Various Developers
* Omnibus packaging
* Chef cookbooks
* DevOps: ensuring that deployments are smooth and scalable
* Maintenance of various servers such as 
   * license.gitlab.com
   * version.gitlab.com
   * status.gitlab.com
   * doc.gitlab.com
   * dev.gitlab.org
* Feature development for GitLab CE, EE, and CI.

{'fraction_non_alphanumeric': 0.062436719541005735, 'fraction_numerical': 0.005399932500843739, 'mean_word_length': 4.330935251798561, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 8, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '220387', 'n_tokens_mistral': 795, 'n_tokens_neox': 733, 'n_words': 375}