Technical Editing Jobs

53 were found based on your criteria {{ paging.total|number:0 }} were found based on your criteria

show all
  • Hourly ({{ jobTypeController.getFacetCount("0")|number:0}})
  • Fixed Price ({{ jobTypeController.getFacetCount("1")|number:0}})
Fixed-Price - Intermediate ($$) - Est. Budget: $100 - Posted
I need assistance in pulling together my current manual which has multiple sections, in separate Microsoft Word documents. Need pulled together into one Word Doc with a linked Table of Contents to the sections. After I will need the document reviewed for any references to different/past businesses I assisted. Will need consistent formatting throughout the document. Would like formatting to be like this attached document. So that when i pdf it will look like this.
Skills: Technical Editing Microsoft Word
Hourly - Intermediate ($$) - Est. Time: Less than 1 month, 10-30 hrs/week - Posted
We are going to be selling pet brushes online, mostly marketed towards dog owners. As an extra in our package we want to include an ebook explaining and instructing proper methods for grooming your pet/dog. We would like it to include common sense grooming tips, as well as basic instructions on things to avoid, and general guidelines for best practices. We care deeply about our customers and their pets, and want to provide them with high quality advice to improve the lives and wellbeing of their pets and them as pet owners. We also want to provide them with the peace of mind of knowing that they are following the best grooming practices that they can for their pets. We want this to be 10-20 pages of solid content. We will provide a general guideline and format, as well as certain specific topics we would like covered. We are looking for somebody that will be diligent in their research, skilled in describing details, and will provide top quality work.
Skills: Technical Editing Content Writing Microsoft Word Technical writing
Fixed-Price - Intermediate ($$) - Est. Budget: $1,500 - Posted
We need to get some full feature level documentation of our web and mobile-based product. You will be responsible for following a process to produce useful internal documentation we can share with our development and sales teams. We have a lot of documentation presently, but it needs to be organized and the gaps filled. You will work with the product architect, project coordinator, and various technical resources to pull this together. Our development team is in India. Your English writing and communication skills should be perfect and you should have years of experience preparing technical documentation. Demonstrable expertise is required. We will provide additional requirements to qualified candidates. Please provide your resume and a history of products you have created technical specs for. We are looking for people who have done this. If you live and work in Delhi NCR and can visit our office directly to work with staff, that is a plus, but not required. Thanks.
Skills: Technical Editing Software Documentation Technical writing
Hourly - Expert ($$$) - Est. Time: Less than 1 week, 10-30 hrs/week - Posted
We have 9 landing pages that have been written by a non-English speaker, each landing page about 5 small paragraphs, we need a native & professional English writer who can COMPLETELY re-write the paragraphs with SEO & Marketing Consideration, he must be able to write original content that captures the attention of readers in an informative yet engaging way.
Skills: Technical Editing Blog Writing Content Writing Editorial Writing
Hourly - Intermediate ($$) - Est. Time: 3 to 6 months, 30+ hrs/week - Posted
Hi, We are looking for a technical content writer, who can write content for our technology training website. We provide training for multiple courses on topics like Java, JS, Python, Asp.net. & mobile development etc, so we need a content writer who can write attractive contents on these topics for the website. Most of our site visitors are students looking to learn these technologies. It's an urgent hiring, so please feel free to contact us for the same.
Skills: Technical Editing Content Writing Technical writing Content Management
Hourly - Expert ($$$) - Est. Time: 1 to 3 months, Less than 10 hrs/week - Posted
Looking for someone who can do technical writing on an hourly basis. No need to have specific experience with the actual task, which is drafting corporate IT policy documents. Requirements are: Smart, efficient, and excellent in English. Looking for someone in the US, and can start as soon as the week of 8/22/2016. Please send samples of your work should you be interested and qualified.
Skills: Technical Editing Business Writing Technical writing Writing
Hourly - Intermediate ($$) - Est. Time: Less than 1 week, 10-30 hrs/week - Posted
I need a blog post to be written on why judging developers or technical people based on their Github Profiles is hard. The following outlines the points I want to cover. Of course they will require more research, screenshots and the points to be assembled well. ---- Outline ---- People usually ask for a github profile as a part of the resume. Let me share with you, why I think you should not judge someone on their github profile. The commit graph I have been developing for 10yrs. I have been using github for about 5 yrs. If you are looking at my personal projects, you will find a lot of commits, but spaced out at very long intervals of time. The no of commits don't really give an idea of the quality of my code. Sometimes the amount of Code I have deleted is more important than my the number of lines I have written. Personal Projects If a company uses Github, the majority of a person's work is going to be in private repository. Again, the commit graph is only a small indicator of his technical abilities. Bugs Bugs on Open Source projects. Let me just start by saying that the barrier here is really high. People who do PRs against bugs are at the mercy of the authors time and opinion. An author could be very opinionated and can refuse to merge even if the solution works. Resolving a bug, also happens when the developers run into a problem themselves. When developers run into a problem, they mostly find a replacement library. Resolving the bugs doesn't really give them an incentive unless they have made a heavy investment in the library previously. Forks Forking a Repo is really just copying it and modifying a few pieces. You can't end up with the credit of customization. It shows a lot of Code, but figuring out a single persons contribution is really hard. Gists and Documentation Gists and documentation are really the two small pieces that will really give you an idea. In fact, gists can be really well documented too. Small independent pieces of Code that you can run anywhere.
Skills: Technical Editing Blog Development Blog Writing Internet research
Hourly - Expert ($$$) - Est. Time: More than 6 months, 10-30 hrs/week - Posted
Hi, We are looking for a technical writer for our blog. Good command of the language. Ability to do deep research and generate interesting engaging posts. The topics might include software development, data mining, ecommerce development etc. Please send your sample blog posts for review.
Skills: Technical Editing Article Writing Blog Writing Content Writing
Fixed-Price - Intermediate ($$) - Est. Budget: $30 - Posted
I would like a technical blog post written on "Using vi when learning a new framework or language". There is an outline of the blog post below. Of course there needs to be some research on each on the points. You should be able to do technical screenshots and small code examples for each point. The tone of the blog post is to support that using vi while learning something new is a good way to go. ---- Outline ---- Project structure - Opening files one at a time without any helpers forces you to memorize project structure for faster access. Frameworks are mostly about project structure and convention. Lack of auto complete -Forces you to learn and remember functions for a new language. Lack of compilation tools - Set up environment vars and command line args that are setup by default on modern editors Forces you to learn and read errors Forces you to learn better debugging skills
Skills: Technical Editing Blog Development Blog Writing Technical writing
Fixed-Price - Intermediate ($$) - Est. Budget: $30 - Posted
I need a blog post to be written on why judging developers or technical people based on their Github Profiles is hard. The following outlines the points I want to cover. Of course they will require more research, screenshots and the points to be assembled well. ---- Outline ---- People usually ask for a github profile as a part of the resume. Let me share with you, why I think you should not judge someone on their github profile. The commit graph I have been developing for 10yrs. I have been using github for about 5 yrs. If you are looking at my personal projects, you will find a lot of commits, but spaced out at very long intervals of time. The no of commits don't really give an idea of the quality of my code. Sometimes the amount of Code I have deleted is more important than my the number of lines I have written. Personal Projects If a company uses Github, the majority of a person's work is going to be in private repository. Again, the commit graph is only a small indicator of his technical abilities. Bugs Bugs on Open Source projects. Let me just start by saying that the barrier here is really high. People who do PRs against bugs are at the mercy of the authors time and opinion. An author could be very opinionated and can refuse to merge even if the solution works. Resolving a bug, also happens when the developers run into a problem themselves. When developers run into a problem, they mostly find a replacement library. Resolving the bugs doesn't really give them an incentive unless they have made a heavy investment in the library previously. Forks Forking a Repo is really just copying it and modifying a few pieces. You can't end up with the credit of customization. It shows a lot of Code, but figuring out a single persons contribution is really hard. Gists and Documentation Gists and documentation are really the two small pieces that will really give you an idea. In fact, gists can be really well documented too. Small independent pieces of Code that you can run anywhere.
Skills: Technical Editing Blog Development Blog Writing Internet research