ZipRecruiter

Log In

1

Google Technical Solutions Engineer Jobs (NOW HIRING)

Associated Builders and Contractors (ABC)

... custody solutions--all fully licensed and compliant. We're big enough to lead the charge in ... that get a developer from nothing to a working integration * Answer technical questions from ...

Smartsheet

Enterprise Technical Solutions Engineer

Smartsheet is looking for an Enterprise Technical Solutions Engineer who will provide technical guidance throughout the sales process. We are a fast-growing, high revenue-growth Software as a Service ...

Smartsheet

Enterprise Technical Solutions Engineer

$117K - $142K/yr

Smartsheet is looking for an Enterprise Technical Solutions Engineer who will provide technical guidance throughout the sales process. We are a fast-growing, high revenue-growth Software as a Service ...

Asana

Technical Solutions Engineer, Command

New York, NY · On-site +1

... technical validation, and solution design while partnering seamlessly with Asana's existing Account Executives, Customer Success Managers, and core Solutions Engineers to support both net-new and ...

Ksb

Technical Solutions Engineer I

Mulberry, FL · On-site

Technical Solutions Engineer I Job Title: Technical Solution Engineer I Department: Sales Reports to: Regional Sales Manager Location: Mulberry, Florida Shift: 1st Purpose / Summary: Develop and ...

previous page

Showing results 41-60

All JobsTechnology JobsSoftware JobsSoftware Developer JobsGoogle Technical Solutions Engineer Jobs

Google Technical Solutions Engineer information

See salary details

$64.5K

$115.6K

$152.5K

How much do google technical solutions engineer jobs pay per year?

As of Sep 12, 2026, the average yearly pay for google technical solutions engineer in the United States is $115,565.00, according to ZipRecruiter salary data. Most workers in this role earn between $95,500.00 and $142,500.00 per year, depending on experience, location, and employer.

What does a Google Technical Solutions Engineer do?

A Google Technical Solutions Engineer acts as a bridge between Google's technical products and its customers, helping to resolve complex technical issues and implement solutions for clients. They work closely with engineering and product teams to troubleshoot problems, provide technical guidance, and ensure customer satisfaction. Their responsibilities often include debugging code, creating technical documentation, and collaborating with cross-functional teams to improve product performance and reliability.

What are the key skills and qualifications needed to thrive as a Google Technical Solutions Engineer?

To thrive as a Google Technical Solutions Engineer, you need a strong background in computer science, problem-solving, and analytical skills, often backed by a relevant degree or equivalent experience. Familiarity with programming languages (such as Python, Java, or C++), cloud platforms, and troubleshooting tools is essential, and certifications like Google Cloud Professional can be advantageous. Excellent communication, teamwork, and customer-centric attitude are crucial soft skills for collaborating with clients and internal teams. These competencies ensure effective resolution of complex technical issues and contribute to customer satisfaction and product improvement.

How does a Google Technical Solutions Engineer typically collaborate with product and engineering teams to resolve customer issues?

As a Google Technical Solutions Engineer, you’ll regularly work cross-functionally with product managers, software engineers, and support teams to diagnose and resolve complex customer issues. This often involves reproducing technical problems, analyzing logs, and escalating bugs or feature requests to the relevant development teams. You’ll also provide feedback to help improve product documentation and usability, ensuring that customer insights are incorporated into future releases. Collaboration is highly dynamic, and effective communication skills are essential for keeping all stakeholders aligned and informed throughout the resolution process.

What is the difference between Google Technical Solutions Engineer vs Google Cloud Support Engineer?

AspectGoogle Technical Solutions EngineerGoogle Cloud Support Engineer
Required CredentialsBachelor's in CS or related field, technical certificationsTechnical background, certifications often preferred
Work EnvironmentCustomer-facing, technical consulting, pre-sales and post-sales supportTechnical support, troubleshooting, issue resolution
Employer & Industry UsageGoogle, cloud services, enterprise clientsGoogle Cloud, enterprise clients, support teams
Common Search/ComparisonTechnical problem-solving, solutions consultingSupport tickets, troubleshooting, technical assistance

The Google Technical Solutions Engineer focuses on providing technical consulting and solutions to clients, often involved in pre-sales and post-sales support. In contrast, the Google Cloud Support Engineer primarily handles troubleshooting and resolving technical issues within existing cloud services. Both roles require technical expertise and certifications but differ in their focus on consulting versus support.

More about Google Technical Solutions Engineer jobs

What are popular job titles related to Google Technical Solutions Engineer jobs?

For Google Technical Solutions Engineer jobs, the most frequently searched job titles are:

Google Technical Solutions Engineer jobs near you
Infographic showing various Google Technical Solutions Engineer job openings in the United States as of September 2026, with employment types broken down into 100% Full Time. Highlights an 67% In-person, and 33% Remote job distribution, with an average salary of $115,565 per year, or $55.6 per hour.

Technical Solutions Engineer

On-site

Associated Builders and Contractors (ABC)
Education • 11 - 50 employees
Learn more about Associated Builders and Contractors (ABC)external

Other

Posted 12 days ago

Key responsibilities

  • Own and maintain the API and integration documentation, ensuring it is accurate, complete, and up-to-date.

  • Build quickstart guides, sample code, and reference architectures to facilitate developer integrations.

  • Answer technical questions from partners during sales and development, and resolve issues independently.

Job description

At Coinme, we’re redefining access to financial services in a digital world. By combining the cutting-edge power of blockchain technology with everyday simplicity, we make digital currencies accessible and usable for all.

As the world’s largest network of cryptocurrency kiosks with over 40,000 locations nationwide, we’re breaking down barriers to crypto adoption through our seamless mobile app, secure digital wallet, and DeFi integrations. Beyond our consumer offerings, we’re also the infrastructure powering the crypto revolution for businesses.

Through our enterprise Crypto-as-a-Service (CaaS) platform, we enable businesses to launch crypto capabilities in weeks, not months. Our modular, API-first infrastructure provides everything from KYC and payment processing to liquidity and custody solutions—all fully licensed and compliant.

We’re big enough to lead the charge in decentralized finance but small enough that your ideas will make waves. Every role at Coinme contributes to building a financial future where everyone has the tools to thrive. At Coinme, your growth fuels our mission. Together, we RISE.

About The Role

Coinme is part of Polygon Labs, and together we’re putting out a stablecoin payments stack: our fiat on and off ramps, Sequence wallets, and settlement on Polygon. Fintechs and financial institutions are integrating it now, and the documentation hasn’t caught up. Partners are asking questions that should have been answered in a doc six months ago, and those questions land on engineers who need to be building.

What You’ll Do
  • Own the API and integration docs. Rewrite what’s wrong, fill what’s missing, keep it current as the stack changes
  • Build the quickstarts, sample code, and reference architectures that get a developer from nothing to a working integration
  • Answer technical questions from partners during sales conversations and during builds, and resolve them yourself rather than passing them to engineering
  • Take signed partners live: requirements intake, provisioning once KYB and KYC clear, sandbox testing, webhooks, go-live checks
  • Work with the integration program manager on timelines so partners know what’s coming and when
  • Learn the stack deeply: CaaS ramps, Sequence wallets, Trails, OMSX, bank rails, custodial and non-custodial flows, virtual accounts, deposit addresses, webhooks
  • Build demos and sample apps that BD can use to show what the products do
  • Push what you learn back into Product and Engineering. You’ll see every rough edge in the API before anyone else does
  • Automate the repetitive parts of onboarding and provisioning, and use AI tools to move faster on docs and support
Who You Are

We’re open to two different backgrounds here, and you only need one:

You’ve run API integrations for customers at a payments or fintech company, taking them from kickoff to production. Or you’ve owned docs, SDKs, or developer support at an API-first company and want to go deeper into payments.

Either way, you should have:

  • Real hands‑on API skills. You can read logs, debug a broken webhook, reason about auth, and work in Postman or Bruno and Datadog. You don’t need to be a software engineer, but you do need to solve problems instead of routing them
  • Strong technical writing. You can take a messy system and document it so a stranger can follow it
  • Patience for ambiguity. The stack changes weekly, the docs are thin, and nobody is going to hand you a plan
  • Comfort using AI tools in your daily work, and an eye for how to make our docs work well for developers who are using them too

Payments fundamentals (fund flows, settlement, reconciliation) will help, but we can teach that to the right person.

Nice to have:
  • crypto or web3 background, especially stablecoins and wallets.
  • Enough coding to build a demo app.
  • Experience with a docs platform like Mintlify.
  • Exposure to KYB and KYC tooling.

Check out our AI Usage Guidelines to understand how we approach AI tools during the hiring process.

#J-18808-Ljbffr

Apply