Back-end Software Development Engineering Senior Engineer
Fast Switch · MI
—
Jul 14, 2026
MI
Jul 20, 2026
What this job asks for AI summary
A senior back-end engineering role centred on building and maintaining cloud-native APIs and microservices on Google Cloud Platform, primarily using Python, Java, and C++. Day-to-day work spans designing REST and gRPC APIs, managing GCP services such as Cloud Run and GKE, implementing CI/CD pipelines, and instrumenting services for observability. The role suits an engineer with at least two years of backend cloud development experience who is comfortable working across data storage, event-driven architecture, and security practices.
Mid level · 2+ years · National · Bachelor's required · Contract
Advertised as Senior, but the requirements read as Mid.
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (9)
The posting is from FastTek Global, an IT staffing/consulting firm — this is almost certainly a contract placement, not a direct full-time hire, though the employment type is not explicitly stated in the job description itself.
The title says 'Senior Engineer' but the only experience gate is 2+ years of backend engineering, which aligns with a Mid-level role on a standard career ladder.
Kafka is described as 'a strong plus given TOP's observability stack' — it appears in the required experience section but is explicitly framed as a plus/bonus, so it is treated as preferred.
OpenTelemetry is listed as required ('Experience instrumenting services with OpenTelemetry or equivalent observability frameworks'); 'or equivalent' means the specific tool is interchangeable but the capability is a hard gate.
LLM inference API integration and OpenAPI/API gateway familiarity appear under the explicit 'NICE TO HAVE' section.
Telematics and AI/Expert Systems appear under 'Skills Preferred' in the structured skills block and are captured via the LLM APIs preferred skill; the telematics/automotive data formats note also appears under Nice to Have.
Google Cloud Professional Cloud Developer certification is listed as a Nice to Have; certifications are not emitted as skills per extraction rules.
Bachelor's Degree is listed under 'Education Required' and is treated as a hard degree gate.
Posting is for a contract engagement — the market benchmarks below price full-time roles, so read the comp comparison with that in mind.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.