Home 
How Blumble Works 
Search Algorithm 
Your Privacy 
About 
Facebook
Twitter
Blog
Most recent job postings at GitHub
via ZipRecruiter
posted_at: 2 days agoschedule_type: Contractor
Azure DevOps ( GitHub Automation) -Dallas TX -ONSITE
(Main focus on text marked in bold) ALSO MUST COMPLETE THE CHART BELOW ON SKILLS
1Must have working knowledge of Azure
2MUST HAVE GitHub Actions(Shared Lib, interfacing with SonarQube, Veracode, multiple java versions)
3Kubernetes architecture4Must have done or designed HA and resiliency of various tools5Good at scripting (Bash, Python, Perl etc)This position will be responsible for the build,
Azure DevOps ( GitHub Automation) -Dallas TX -ONSITE
(Main focus on text marked in bold) ALSO MUST COMPLETE THE CHART BELOW ON SKILLS
1Must have working knowledge of Azure
2MUST HAVE GitHub Actions(Shared Lib, interfacing with SonarQube, Veracode, multiple java versions)
3Kubernetes architecture4Must have done or designed HA and resiliency of various tools5Good at scripting (Bash, Python, Perl etc)This position will be responsible for the build, management and automation of multiple components and different environments, focusing initially on Azure PAAS components (eg Azure App Gateway and APIM) Drive the design of solutions implemented in public cloud (Azure) and work with application developers and system administrators for automation and management of system architecture and preparation for new technical implementations (hardware, platform, product, and service deployments) Collaborate with other engineers to continue finding new areas that can be improved by bringing a DevOps... mindset to all the areas the company manages
Below filter criteria.
• 5+ years of DevOps skills
• Azure DevOps skills or Expertise with Github Action to enable CI/CD flows
• Hands on experience with YAML scripting , experience in Powershell / Bash Scripting/Groovy
• Hands experience with Docker / Kubernetes deployments for applications ( preferably AKS on Azure)
Requirements
Please ask candidate to share below skill matrix
Skills
Rating (10)
No. of years exp
Last Use
Azure
GitHub actions
interfacing with SonarQube
Shared Lib
Veracode
java
PCF Deployment and AKS Deployment from
YAML experience - Artifactory
Docker/ Kubernetes
Jenkins
Benefits
Candidate\u2019s name:
Phone number:
Email address:
Skype ID
Visa status (With validity):
Current location:
Willing to relocate:
Availability for interview:
Expected salary/rate:
Notice period:
Highest education (Including date)
Reason for change:
Communication:
LinkedIn Profile:
If Ex-TechM Employee required ID NO:
Reporting Manager:
Project name:
Exit reason:
Last 3 Months rating Show more details...
(Main focus on text marked in bold) ALSO MUST COMPLETE THE CHART BELOW ON SKILLS
1Must have working knowledge of Azure
2MUST HAVE GitHub Actions(Shared Lib, interfacing with SonarQube, Veracode, multiple java versions)
3Kubernetes architecture4Must have done or designed HA and resiliency of various tools5Good at scripting (Bash, Python, Perl etc)This position will be responsible for the build, management and automation of multiple components and different environments, focusing initially on Azure PAAS components (eg Azure App Gateway and APIM) Drive the design of solutions implemented in public cloud (Azure) and work with application developers and system administrators for automation and management of system architecture and preparation for new technical implementations (hardware, platform, product, and service deployments) Collaborate with other engineers to continue finding new areas that can be improved by bringing a DevOps... mindset to all the areas the company manages
Below filter criteria.
• 5+ years of DevOps skills
• Azure DevOps skills or Expertise with Github Action to enable CI/CD flows
• Hands on experience with YAML scripting , experience in Powershell / Bash Scripting/Groovy
• Hands experience with Docker / Kubernetes deployments for applications ( preferably AKS on Azure)
Requirements
Please ask candidate to share below skill matrix
Skills
Rating (10)
No. of years exp
Last Use
Azure
GitHub actions
interfacing with SonarQube
Shared Lib
Veracode
java
PCF Deployment and AKS Deployment from
YAML experience - Artifactory
Docker/ Kubernetes
Jenkins
Benefits
Candidate\u2019s name:
Phone number:
Email address:
Skype ID
Visa status (With validity):
Current location:
Willing to relocate:
Availability for interview:
Expected salary/rate:
Notice period:
Highest education (Including date)
Reason for change:
Communication:
LinkedIn Profile:
If Ex-TechM Employee required ID NO:
Reporting Manager:
Project name:
Exit reason:
Last 3 Months rating Show more details...
via Upwork
schedule_type: Contractorsalary: 15–30 an hourwork_from_home: 1
BACKGROUND
Hi, we're looking to move our existing website (40+ pages) from GitHub Pages to WordPress. Our blog is already hosted on WordPress and we use WPEngine as a hosting provider...
ABOUT THE PROJECT
We want to make sure all of our static pages are imported to WordPress (HTML/CSS done). We want to make sure SEO is unaffected and we keep the same URL structure, do relevant redirects etc.
It would also be great to set up our staging entirely
BACKGROUND
Hi, we're looking to move our existing website (40+ pages) from GitHub Pages to WordPress. Our blog is already hosted on WordPress and we use WPEngine as a hosting provider...
ABOUT THE PROJECT
We want to make sure all of our static pages are imported to WordPress (HTML/CSS done). We want to make sure SEO is unaffected and we keep the same URL structure, do relevant redirects etc.
It would also be great to set up our staging entirely on WordPress/WP Engine and set up several page templates for easy content production.
BENEFITS
- We will likely have ongoing requirements for this so it could turn into a permanent role for the right person or agency.
- You will work with a supportive and dynamic team. Any questions and access to tools etc. will be provided swiftly.
- We are also happy to pay well above average for this project as it is a key priority right now.
REQUIREMENTS
- You need to have extensive experience with WordPress migrations.
- Expert-level WordPress dev skills
- Very good communication
- Understanding of technical SEO so you can de-risk the migration (organic traffic is our top channel)
HOW TO APPLY
- Please provide 2-3 examples of websites you have fully migrated from a custom setup or alternative CMS to WordPress (ideally from GitHub Pages but not essential).
- Start your cover letter with the word "WordPress"
- Please share the main risks you see in this project and how you will tackle them.
- Add any questions you have about this project (URL will be provided after you are shortlisted)
Thanks for reading and good luck Show more details...
Hi, we're looking to move our existing website (40+ pages) from GitHub Pages to WordPress. Our blog is already hosted on WordPress and we use WPEngine as a hosting provider...
ABOUT THE PROJECT
We want to make sure all of our static pages are imported to WordPress (HTML/CSS done). We want to make sure SEO is unaffected and we keep the same URL structure, do relevant redirects etc.
It would also be great to set up our staging entirely on WordPress/WP Engine and set up several page templates for easy content production.
BENEFITS
- We will likely have ongoing requirements for this so it could turn into a permanent role for the right person or agency.
- You will work with a supportive and dynamic team. Any questions and access to tools etc. will be provided swiftly.
- We are also happy to pay well above average for this project as it is a key priority right now.
REQUIREMENTS
- You need to have extensive experience with WordPress migrations.
- Expert-level WordPress dev skills
- Very good communication
- Understanding of technical SEO so you can de-risk the migration (organic traffic is our top channel)
HOW TO APPLY
- Please provide 2-3 examples of websites you have fully migrated from a custom setup or alternative CMS to WordPress (ideally from GitHub Pages but not essential).
- Start your cover letter with the word "WordPress"
- Please share the main risks you see in this project and how you will tackle them.
- Add any questions you have about this project (URL will be provided after you are shortlisted)
Thanks for reading and good luck Show more details...
via Upwork
posted_at: 22 days agoschedule_type: Contractorwork_from_home: 1
We are looking for a skilled React App Consultant who can help us get our React App to work on Github Pages. The ideal candidate should have a strong understanding of React and experience working with Github Pages. They should be able to work independently and provide guidance and support to our development team in resolving any issues that may arise during the deployment... process.
Responsibilities:
Evaluate our current React App and provide recommendations
We are looking for a skilled React App Consultant who can help us get our React App to work on Github Pages. The ideal candidate should have a strong understanding of React and experience working with Github Pages. They should be able to work independently and provide guidance and support to our development team in resolving any issues that may arise during the deployment... process.
Responsibilities:
Evaluate our current React App and provide recommendations on how to optimize it for deployment on Github Pages.
Provide guidance on how to set up and configure the Github Pages environment for our React App.
Work with the development team to identify and resolve any issues related to deploying the React App on Github Pages.
Ensure that the React App is fully functional and runs smoothly on Github Pages.
Provide ongoing support and maintenance for the React App on Github Pages.
Requirements:
Strong understanding of React and its ecosystem.
Experience with Github Pages and deploying React Apps to Github Pages.
Familiarity with Git and version control.
Ability to troubleshoot and resolve issues related to React App deployment on Github Pages.
Excellent communication skills and ability to work collaboratively with a team.
Attention to detail and ability to ensure that the React App is fully functional and meets all requirements Show more details...
Responsibilities:
Evaluate our current React App and provide recommendations on how to optimize it for deployment on Github Pages.
Provide guidance on how to set up and configure the Github Pages environment for our React App.
Work with the development team to identify and resolve any issues related to deploying the React App on Github Pages.
Ensure that the React App is fully functional and runs smoothly on Github Pages.
Provide ongoing support and maintenance for the React App on Github Pages.
Requirements:
Strong understanding of React and its ecosystem.
Experience with Github Pages and deploying React Apps to Github Pages.
Familiarity with Git and version control.
Ability to troubleshoot and resolve issues related to React App deployment on Github Pages.
Excellent communication skills and ability to work collaboratively with a team.
Attention to detail and ability to ensure that the React App is fully functional and meets all requirements Show more details...
via Upwork
schedule_type: Contractorwork_from_home: 1
We are looking for a 1500-2000 word piece that dives into the ins and outs of Github’s authorization model.
Ideally, we're looking for a developer that enjoys writing. This is only the first project. Once we find the right person we will work with on a series of posts for our developer audience...
This is a thought leadership post about the authorization model Github uses to manage access and permissions to organizations and repos. Github provides
We are looking for a 1500-2000 word piece that dives into the ins and outs of Github’s authorization model.
Ideally, we're looking for a developer that enjoys writing. This is only the first project. Once we find the right person we will work with on a series of posts for our developer audience...
This is a thought leadership post about the authorization model Github uses to manage access and permissions to organizations and repos. Github provides a combination of general scopes like admin:repo_hook, roles that may restrict the set of permissions on a resource, and even resource-specific permissions.
Ideally, you can read and write code, have used github before, and can transform your research and experience into a story for an audience developers that aren't subject matter experts. Our audience includes both IC developers as well as tech leadership. These individuals are familiar with the overall field of authorization, but not necessarily well-versed in the details (like you will be when you read about why you shouldn’t use OAuth scopes as permissions).
Here are a couple of resources:
Access permissions on Github : https://docs.github.com/en/enterprise-cloud@latest/get-started/learning-about-github/access-permissions-on-github
Repository roles for an organization: https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization
Scopes for OAuth Apps: https://docs.github.com/en/enterprise-cloud@latest/developers/apps/building-oauth-apps/scopes-for-oauth-apps
And here’s a suggested outline:
- Intro: Github is where the world goes to code. Github authorizes access to your code and repos for other users based on granular roles associated with users or groups (teams). They also use general scopes in an attempt to mimic permissions.
- Role-based access control (RBAC) describes the practice of aggregating discrete application permissions into a small set of roles that are assigned to users or groups.
- Examples from the docs- this section (https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization) shows you a breakdown of permissions per role use it to create a few examples (for example, Ian a jr. engineer is part of the “intern” team that has “read” permissions for the “ACME corp” repo. As a result, he can access the code and create pull requests, but he cannot approve pull requests, for that you need “write” permissions or higher.)
- Why should I care? Because Github’s authorization model can get messy quickly. Scopes are associated with users, but users can have various roles assigned to them in the organization, as part of a team, or even per repo. So, Github’s model isn’t purely RBAC, it is a combination of general OAuth scopes like admin:repo_hook, roles that may restrict the set of permissions on a resource, and even resource-specific permissions.
- What’s wrong with using scopes for access decisions: here's a great resource: https://www.aserto.com/blog/oauth2-scopes-are-not-permissions
- Conclusion
Please share a couple of relevant writing samples you have written for technical audiences with your proposal.
Thanks so much Show more details...
Ideally, we're looking for a developer that enjoys writing. This is only the first project. Once we find the right person we will work with on a series of posts for our developer audience...
This is a thought leadership post about the authorization model Github uses to manage access and permissions to organizations and repos. Github provides a combination of general scopes like admin:repo_hook, roles that may restrict the set of permissions on a resource, and even resource-specific permissions.
Ideally, you can read and write code, have used github before, and can transform your research and experience into a story for an audience developers that aren't subject matter experts. Our audience includes both IC developers as well as tech leadership. These individuals are familiar with the overall field of authorization, but not necessarily well-versed in the details (like you will be when you read about why you shouldn’t use OAuth scopes as permissions).
Here are a couple of resources:
Access permissions on Github : https://docs.github.com/en/enterprise-cloud@latest/get-started/learning-about-github/access-permissions-on-github
Repository roles for an organization: https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization
Scopes for OAuth Apps: https://docs.github.com/en/enterprise-cloud@latest/developers/apps/building-oauth-apps/scopes-for-oauth-apps
And here’s a suggested outline:
- Intro: Github is where the world goes to code. Github authorizes access to your code and repos for other users based on granular roles associated with users or groups (teams). They also use general scopes in an attempt to mimic permissions.
- Role-based access control (RBAC) describes the practice of aggregating discrete application permissions into a small set of roles that are assigned to users or groups.
- Examples from the docs- this section (https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization) shows you a breakdown of permissions per role use it to create a few examples (for example, Ian a jr. engineer is part of the “intern” team that has “read” permissions for the “ACME corp” repo. As a result, he can access the code and create pull requests, but he cannot approve pull requests, for that you need “write” permissions or higher.)
- Why should I care? Because Github’s authorization model can get messy quickly. Scopes are associated with users, but users can have various roles assigned to them in the organization, as part of a team, or even per repo. So, Github’s model isn’t purely RBAC, it is a combination of general OAuth scopes like admin:repo_hook, roles that may restrict the set of permissions on a resource, and even resource-specific permissions.
- What’s wrong with using scopes for access decisions: here's a great resource: https://www.aserto.com/blog/oauth2-scopes-are-not-permissions
- Conclusion
Please share a couple of relevant writing samples you have written for technical audiences with your proposal.
Thanks so much Show more details...
Norton safe Web