1

Senior Google Technical Writer Jobs (NOW HIRING)

Senior Google AI Engineer

Mclean, VA

$107K - $147K/yr

As a Senior Google AI Engineer, you will serve as a handson technical leader for AI solution delivery. You'll translate mission needs into secure, scalable AI/ML systems; guide data, platform, and ...

Senior Google Engineer

$107K - $146K/yr

The Senior Google Engineer is responsible for the delivery of complex projects focusing on Google ... Strong technical experience with Google Workspace services, including understanding their ...

Company Description Senior Technical Writer 5 months Contract To Perm Position is in Malvern, PA. 100% onsite. Technical writing experience, combined with any experience in: * Senior Technical Writer ...

The Senior Technical Writer will be responsible for developing, evaluating, and maintaining high-quality technical documentation, training materials, operational procedures, and deployment guides ...

The Senior Technical Writer will be responsible for developing, evaluating, and maintaining high-quality technical documentation, training materials, operational procedures, and deployment guides ...

next page

Showing results 1-20

Senior Google Technical Writer information

See salary details

$56.5K

$103.1K

$170K

How much do senior google technical writer jobs pay per year?

As of Jun 9, 2026, the average yearly pay for senior google technical writer in the United States is $103,091.00, according to ZipRecruiter salary data. Most workers in this role earn between $81,000.00 and $124,000.00 per year, depending on experience, location, and employer.

What does a Senior Google Technical Writer do?

A Senior Google Technical Writer creates, manages, and improves technical documentation for Google's products and platforms. This includes writing user guides, API references, and developer tutorials to help users and developers understand and use Google technologies effectively. Senior writers also collaborate with engineers, product managers, and other stakeholders to ensure accuracy and clarity. They often mentor junior writers and contribute to documentation strategy and best practices across teams.

How does a Senior Google Technical Writer typically collaborate with engineering and product teams during documentation projects?

As a Senior Google Technical Writer, collaboration with engineering and product teams is integral to producing accurate, user-friendly documentation. You’ll often attend project meetings, conduct interviews with subject matter experts, and participate in product reviews to gain deep technical understanding. Regularly, you'll provide feedback on feature designs from the documentation perspective and ensure that user guides, API docs, and release notes align with the latest product changes. This role requires strong communication skills to bridge the gap between technical teams and end-users, fostering a collaborative environment that supports both product development and customer success.

What are the key skills and qualifications needed to thrive as a Senior Google Technical Writer, and why are they important?

To thrive as a Senior Google Technical Writer, you need advanced writing and editing abilities, deep understanding of technical concepts, and experience in documentation processes, typically supported by a relevant degree and several years of technical writing experience. Proficiency with documentation tools like Markdown, XML, Git, content management systems, and familiarity with Google's internal documentation platforms are crucial. Exceptional collaboration, attention to detail, and the ability to translate complex technical information into clear, user-friendly content are standout soft skills. These competencies ensure the creation of accurate, accessible documentation that supports both users and engineering teams in a fast-paced tech environment.

What is the difference between Senior Google Technical Writer vs Technical Content Specialist?

AspectSenior Google Technical WriterTechnical Content Specialist
CredentialsBachelor's degree in technical communication, journalism, or related field; experience in technical writingSimilar educational background; often requires technical writing experience
Work EnvironmentTech companies, especially Google, creating documentation, tutorials, and API guidesVarious industries including tech, manufacturing, and healthcare, focusing on creating technical manuals and content
Employer & Industry UsagePrimarily in large tech firms like Google, focusing on software and hardware documentationUsed across multiple industries, often in corporate or technical settings

The main difference is that a Senior Google Technical Writer specializes in creating technical documentation specifically for Google products and services, often within a tech giant environment. In contrast, a Technical Content Specialist works across various industries, producing technical manuals, guides, and content for different technical products. Both roles require strong writing skills and technical knowledge, but the scope and industry focus differ.

More about Senior Google Technical Writer jobs
What cities are hiring for Senior Google Technical Writer jobs? Cities with the most Senior Google Technical Writer job openings:
What are the most commonly searched types of Google Technical Writer jobs? The most popular types of Google Technical Writer jobs are:
What states have the most Senior Google Technical Writer jobs? States with the most job openings for Senior Google Technical Writer jobs include:
Infographic showing various Senior Google Technical Writer job openings in the United States as of May 2026, with employment types broken down into 88% Full Time, and 12% Part Time. Highlights an 51% Physical, 2% Hybrid, and 47% Remote job distribution, with an average salary of $103,091 per year, or $49.6 per hour.
Sr. Google Cloud Platform Architect - Technical Lead

Sr. Google Cloud Platform Architect - Technical Lead

CoSourcing Partners

Chicago, IL • Hybrid

Other

Posted 11 days ago


Job description

Position: Sr. Google Cloud Platform Architect - Technical Lead
Company: Confidential Client
Location: Chicago, IL (Onsite 3-4 days/week)
Employment Type: Full-Time (Direct Hire Preferred; Contract-to-Hire Considered)
Role Overview
We are seeking a Sr. Google Cloud Platform (GCP) Architect to serve as the technical lead for a global digital transformation initiative with a Fortune 100 enterprise. This highly visible role will interface directly with senior stakeholders and lead a cross-functional team of cloud engineers and consultants. Operating onsite in Chicago 3-4 days per week, the architect will drive solution design, technical governance, and cloud strategy within a high-stakes enterprise environment. The position reports to the VP of Transformation and is expected to influence cloud decisions at the highest levels while ensuring architectural integrity and delivery excellence across multiple workstreams.
Employee Value Proposition
Purpose
This role represents an opportunity to shape the cloud modernization journey for one of the world's most recognized enterprise brands. You'll operate at the intersection of business strategy and cloud engineering, serving as a bridge between visionary goals and hands-on implementation across teams and partners.
Growth
You'll gain visibility with global leaders, own enterprise-scale design decisions, and guide the implementation of next-gen GCP solutions. The position offers a unique combination of technical leadership, client influence, and executive exposure ideal for a high-performing architect ready for enterprise impact.
Motivators
This opportunity is ideal for someone who thrives on client-facing leadership, cross-functional influence, and delivering transformative cloud results. You'll be empowered to lead architecture sessions, drive critical decisions, and collaborate directly with engineering leads and C-level stakeholders across domains.
Major Objectives
1. Lead Enterprise-Scale GCP Architecture Engagements
Within the first 90 days, take ownership of the end-to-end GCP architecture design across multiple client domains. Facilitate executive-level strategy discussions and lead technical solutioning workshops. Ensure architectural alignment across security, data, and application teams, delivering an initial reference architecture approved by all key stakeholders.
2. Guide Cross-Functional Engineering Execution
Over the first 6 months, provide technical oversight and leadership to 2-3 engineering squads supporting the GCP transformation program. Ensure technical decisions align with the agreed architectural blueprint, and serve as an escalation point for blockers. Partner with delivery leads to ensure timelines, resource plans, and quality standards are consistently met.
3. Influence Strategic Cloud Direction and Governance
Within the first 120 days, lead architecture governance reviews and formalize key cloud principles for the client organization. Shape policy and platform decisions by collaborating with enterprise architects, security, and infrastructure teams. Measure success by adoption of architectural standards and reduction in solution variance across teams.
4. Establish Executive-Level Credibility and Trust
From day one, engage directly with VP- and SVP-level stakeholders to advise on cloud transformation priorities, risks, and options. By month three, serve as the client's go-to technical advisor for GCP architecture, backed by consensus among internal and external contributors. Influence roadmap decisions through data-driven recommendations and strategic guidance.
Critical Subtasks
1. Conduct Architecture Workshops and Discovery Sessions
Within the first 30 days, facilitate deep-dive technical sessions to uncover business needs, legacy constraints, and transformation objectives. Capture outcomes in a living architecture document to guide solution planning.
2. Translate Business Requirements into GCP Solution Blueprints
Create architectural models that directly align to business KPIs, latency/security requirements, and scalability needs. Present solution blueprints for internal review and client validation within 45-60 days.
3. Lead Technical Decision-Making Across GCP Services
Take the lead on evaluating and selecting GCP services and components, ensuring alignment with both client preferences and industry best practices. Defend decisions with clarity and confidence in both technical and business terms.
4. Mentor Engineering Teams on GCP Best Practices
On an ongoing basis, provide hands-on support, code reviews, and architectural feedback to junior engineers and technical leads. Track improvements in code quality and solution resilience as a direct result of your coaching.
5. Drive Alignment with External Vendors and Consulting Partners
Coordinate technical direction with outside consulting firms, Google technical account managers, and third-party tool vendors. Ensure all parties are executing against a common architectural vision.
6. Measure and Report Architectural Success Metrics
Establish KPIs for architecture stability, cost efficiency, and delivery speed. By month six, deliver a consolidated report showing architectural ROI and ongoing risks.
7. Continuously Evaluate and Integrate AI to Improve Performance
Within the first 90-180 days, take ownership of identifying how AI and automation tools can support or enhance the core responsibilities of this role. Evaluate tasks that could be streamlined or improved, lead pilots, and embed continuous AI adoption into daily work. This task may be enhanced using AI-based planning, monitoring, and advisory tools.