-
-
Notifications
You must be signed in to change notification settings - Fork 20
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
BIZDEV-19 | Adding carrers, contribute and faqs sections
- Loading branch information
1 parent
c840553
commit 65949da
Showing
5 changed files
with
130 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,98 @@ | ||
# Carrers | ||
|
||
|
||
## How we work | ||
|
||
!!! info "Binbash work culture" | ||
|
||
:star: **Fully Remote** | ||
Binbash was founded as a remote-first company. That means you can always work from home, | ||
a co-working place, a nice cafe, or wherever else you feel comfortable, and you'll have almost complete control over | ||
your working hours. | ||
_Why "almost"?_ Because depending on the current projects we'll require few hours of overlap between all Leverage | ||
collaborators for some specific meetings or shared sessions (pair-programming). | ||
|
||
:star: **Distributed Team** | ||
Despite the fact that our collaborators are currently located in 🇦🇷 Argentina, | ||
🇧🇷 Brazil and 🇺🇾 Uruguay, consider we are currently hiring from most countries in the time zones | ||
between :earth_americas: GMT-7 (e.g. California, USA) to :earth_africa: GMT+2 (e.g., Berlin, Germany). | ||
|
||
:star: **We promote life-work balance** | ||
Job burnout is an epidemic 🙆, and we tech workers are especially at risk. So we'll do our best to de-stress | ||
our workforce at Binbash. In order to achieve this we offer: | ||
|
||
- Remote work that lets you control your hours and physical location. | ||
- Normal working hours (prime-time 9am-5pm GTM-3), in average no more than ~30-40hs per week, and we don't | ||
work during weekends or your country of residence national holidays. | ||
- Project management and planning that will take into consideration the time zone of all our team members. | ||
- A flexible vacation policy where you could take 3 weeks per year away from the keyboard. If more time is needed | ||
we could always try to arrange it for you. | ||
- No ON-CALL rotation. We only offer support contracts with SLAs of responses on prime time business days hours | ||
exlusively. | ||
- You will take on big challenges, but the hours are reasonable. | ||
- Everyone is treated fairly and with respect, but where disagreement and feedback is always welcome. | ||
- That is welcoming, safe, and inclusive for people of all cultures, genders, and races. | ||
|
||
|
||
## Leverage Software / DevOps Engineer Profile | ||
|
||
!!! info "What You'll Work On (our tech stack) :man_technologist: :woman_technologist: :rocket:" | ||
- [x] [**DevOps Automation Code Library**](how-it-works/index.md) | ||
|
||
Create a collection of reusable, tested, production-ready E2E AWS oriented infrastructure modules | ||
(e.g., VPC, IAM, Kubernetes, Prometheus, Grafana, EFK, Consul, Vault, Jenkins, etc.) using several tool and | ||
languages: *Terraform, Ansible, Helm + Helmsman, Dockerfiles, Python, Bash and Makefiles*. | ||
|
||
- [x] [**Reference Architecture**](how-it-works/code-library/code-library.md) | ||
|
||
Improve, maintain, extend and update our reference architecture, which has been desingned under optimal configs | ||
for the most popular modern web and mobile applications needs. Its design is fully based on the | ||
[**AWS Well Architected Framework**](https://leverage.binbash.com.ar/support/#aws-well-architected-review). | ||
|
||
- [x] **Open Source & Leverage DevOps Tools** | ||
|
||
Contribute to our open source projects to continue building a fundamentally better DevOps experience, including | ||
our [open source modules](how-it-works/code-library/modules-library-per-tech.md), | ||
[leverage python CLI](https://github.com/binbashar/leverage), | ||
[Makefiles Lib](https://github.com/binbashar/le-dev-makefiles) among others. | ||
|
||
- [x] **Document team knowledge** | ||
|
||
Get siloed and not yet documented knowledge and extend the [Leverage documentation](https://leverage.binbash.com.ar), such as | ||
creating knowledgebase articles, runbooks, and other documentation for the internal team as well as Binbash | ||
Leverage customers. | ||
|
||
- [x] **Customer engineering support** | ||
While participating in business-hours only support rotations, collaborate with customer requests, teach | ||
Binbash Leverage and DevOps best-practices, help resolve problems, escalate to internal SMEs, and automate and | ||
document the solutions so that problems are mitigated for future scenarios and users. | ||
|
||
- [x] **Role scope and extra points!** | ||
|
||
- Responsible for the development, maintenance, support and delivery of Binbash Leverage Products. | ||
- Client side Leverage Reference Architecture solutions implementation, maintenance and support. | ||
- Client side cloud solutions & tech management (service delivery and project task management). | ||
- Bring Leverage recs for re-engineering, bug fixes (issues) report and improvements based on real scenario implementations. | ||
- Mentoring, KT, PRs and team tech follow up both internally and customer facing. | ||
Binbash is a small, distributed startup, so things are changing all the time, and from time to time we all wear | ||
many hats. You should expect to write lot of code, but, depending on your interests, there will also be lot of | ||
opportunities to write blog posts, give talks, contribute to open source, go to conferences, talk with customers, | ||
do sales calls, think through financial questions, interview candidates, mentor new hires, design products, | ||
come up with marketing ideas, discuss strategy, consider legal questions, and all the other tasks that are part | ||
of working at a small company. | ||
|
||
!!! important "Nice to have background" | ||
- You hate doing the same thing twice and would rather spend the time to automate a problem away than do the same work again. | ||
- You have strong communication skills and are comfortable engaging with external customers. | ||
- You know how to write code across the stack (“Dev”). | ||
- You have experience running production software ("Ops"). | ||
- You have a strong background in software engineering (or are working hard on it!). | ||
- You have a passion for learning new technologies and languages | ||
- Bonus points for a sense of humor, empathy, and curiosity. | ||
- Note that we're less concerned with prior experience than we are with curiosity about all areas of the stack and demonstrated ability to learn quickly and go deep when necessary. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
# Frequently Asked Questions (FAQs) | ||
|
||
!!! question "Who is Leverage's target audience?" | ||
- [x] Leverage Reference Architecture is mainly oriented to :earth_americas: Latam, North America and :earth_africa: | ||
European **startup's CTOs, VPEs and/or engineering team leads (Software Architects / DevOps Engineers / Cloud Engineers)** | ||
looking to rapidly set and host their modern web and mobile applications and systems in | ||
[**Amazon Web Services**](https://aws.amazon.com/) (✅ typically in just few months!). | ||
|
||
- [x] Oriented to Development leads or teams looking to solve their current AWS infrastructure and software delivery | ||
business needs in a securely and reliably maner, under the most modern best practices. | ||
|
||
- [x] Your Entire AWS Cloud solutions based on DevOps practices journey will be achieved: | ||
- :star: Containerization | ||
- :star: Infrastructure as Code | ||
- :star: Container Orchestration (K8s) & Application Services | ||
- :star: CI / CD | ||
- :star: Security, Compliance & Reliability | ||
- :star: Cost Optimization & Performance Effiency | ||
- :star: Observability & Monitoring | ||
|
||
- [x] Moreover, if you are looking to have the complete control of the source code, and of course be able to run it | ||
without us, such as building new Development environments and supporting your Production Cloud environments, | ||
you're a great fit for the [**Leverage AWS Cloud Solutions Reference Architecture**](how-it-works/index.md) model. | ||
|
||
**_And remember you could implement yourself or we could implement it for you!_** 💪 | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters