Senior Cloud Backend Engineer – Big Data

We need to output HTML fragment with sections only if real content. Must include headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the job posting. Job title: Senior Backend Engineer Hybrid On-Site Dearborn MI $55-75/HR. Not to repeat as heading. We need sections: About the role (maybe from Position Description). Responsibilities (Key Responsibilities). Requirements (maybe Required Skills? Actually Required Skills is a list of skills; could be Skills section). Qualifications (Required Experience). Benefits (Everforth Apex Benefits Overview). Pay (the $55-75/HR). Schedule (Hybrid On-Site maybe? Not explicit schedule but location/hybrid). The instruction: include a section ONLY when posting has real, specific content for it. So we need to see if we have content for each. - About the role: we have Position Description paragraph: "The Senior Backend Engineer will be responsible for designing, building, and operating high-throughput backend systems..." That's substantive. So we can have About the role. - Responsibilities: Key Responsibilities list with many items. So include. - Requirements: Could be Required Skills? But they also have Required Experience. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide mapping. Probably: - Requirements: maybe the Required Skills list? Or Required Experience? Actually they have both Required Skills and Required Experience. Could treat Required Skills as Skills section, Required Experience as Qualifications (or Requirements). Let's map: - Skills: Required Skills (list of GCP, Big Data, Data Warehousing, AI/Expert Systems, API Development). That's a list. - Qualifications: Required Experience (7+ years IT, 5+ years software dev, senior-level, practical experience in at least two programming languages, etc.) Also Education Required Bachelor's Degree. - Requirements maybe could be something else? But we have both Skills and Qualifications; we could omit Requirements if not distinct. However instruction: "Prefer a few substantive sections over many thin ones." We could combine Skills and Qualifications into one? But they ask to use those headings if content exists. We have content for Skills and Qualifications. Could also have Requirements as maybe the Required Experience? But then Qualifications would be Education? Let's think. Better to follow typical job posting: Responsibilities, Requirements (skills/experience), Qualifications (education), Benefits, Pay, Schedule. But we have both Required Skills and Required Experience. Could treat Required Skills as Skills, Required Experience as Requirements, Education as Qualifications. That seems logical. Thus: - About the role (Position Description) - Responsibilities (Key Responsibilities) - Requirements (Required Skills) maybe? Actually Required Skills is a list of skills; but Requirements could be both skills and experience. However we have separate Required Experience. Might be better to put Required Skills under Skills, Required Experience under Requirements, Education under Qualifications. Let's decide:

Skills

-> list of Required Skills (GCP, Big Data, Data Warehousing, AI & Expert Systems, API Development). Each bullet maybe sub-items? We'll flatten.

Requirements

-> list of Required Experience items (7+ years IT, 5+ years software dev, senior-level engineering, practical experience in at least two programming languages, etc.) plus maybe Education? But Education is separate Qualifications.

Qualifications

-> Education Required Bachelor's Degree.

Benefits

-> Everforth Apex Benefits Overview paragraph.

Pay

-> $55-75/HR (from job header). Also maybe mention Hybrid On-Site Dearborn MI? That's location not pay.

Schedule

-> Hybrid On-Site (maybe mention Hybrid On-Site Dearborn MI). Could treat as schedule: Hybrid On-Site. We must not include boilerplate like EEO, legal, etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from sections we include. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

The Senior Backend Engineer will be responsible for designing, building, and operating high-throughput backend systems that ingest, process, and serve large volumes of telematics data from connected vehicle fleets. This role sits at the intersection of distributed systems, data engineering, and API development, delivering reliable, low-latency services that power fleet intelligence products for commercial and enterprise customers.

Responsibilities

• Design and develop scalable, high-performance backend services and APIs that process and expose telematics data, including: GPS data, Trip events, Driver behavior, Vehicle diagnostics, Sensor telemetry
• Build and maintain real-time and batch data pipelines that ingest high-volume vehicle event streams from messaging systems such as Pub/Sub and Kafka.
• Process and transform data for use within data warehouses and operational data stores.
• Design cloud-native solutions leveraging GCP services and distributed data-processing technologies.
• Develop and maintain RESTful and/or gRPC APIs that support integrations between applications and backend microservices.
• Support scalable data warehouse architectures and data models for downstream analytics.
• Develop or integrate AI/ML models and rule-based expert systems where applicable.

Skills

• Google Cloud Platform (GCP) Experience deploying and managing services on Google Cloud Platform, including: Compute Engine, Cloud Storage, IAM, Cloud Functions
• Experience designing and implementing cloud-native application architectures using technologies such as: Google Kubernetes Engine (GKE), Cloud SQL, Pub/Sub
• Big Data Experience working with large-scale data-processing frameworks and technologies, including: Apache Spark, Dataflow, BigQuery
• Experience building ETL pipelines capable of processing large volumes of event data and transforming it for downstream analytics.
• Data Warehousing Experience designing and maintaining data warehouse solutions such as: BigQuery, Snowflake, Redshift
• Experience with data modeling and warehouse architecture, including solutions such as star schemas used for analytics and reporting.
• Artificial Intelligence & Expert Systems Experience developing or integrating AI/ML models and rule-based expert systems.
• Experience with technologies such as Vertex AI for model development and implementation.
• Experience implementing automated decision-making or rule-engine solutions.
• API Development Experience designing, building, and consuming RESTful and/or gRPC APIs.
• Experience with API authentication and security, including OAuth 2.0.
• Experience designing versioned APIs that integrate applications with backend microservices.

Requirements

• 7+ years of IT experience
• 5+ years of software development experience
• Senior-level engineering experience
• Practical experience in at least two programming languages, or advanced expertise in one programming language
• Experience providing technical guidance and contributing to engineering best practices

Qualifications

Education Required: Bachelor's Degree

Benefits

Everforth Apex offers a range of supplemental benefits, including medical, dental, vision, life, disability, and other insurance plans that offer an optional layer of financial protection. We offer an ESPP (employee stock purchase program) and a 401K program which allows you to contribute typically within 30 days of starting, with a company match after 12 months of tenure. Everforth Apex also offers a HSA (Health Savings Account on the HDHP plan), a SupportLinc Employee Assistance Program (EAP) with up to 8 free counseling sessions, a corporate discount savings program and other discounts. In terms of professional development, Everforth Apex hosts an on-demand training program, provides access to certification prep and a library of technical and leadership courses/books/seminars once you have 6+ months of tenure, and certification discounts and other perks to associations that include CompTIA and IIBA. Everforth Apex has a dedicated customer service team for our Consultants that can address questions around benefits and other resources, as well as a certified Career Coach. You can access a full list of our benefits, programs, support teams and resources within our ‘Welcome Packet’ as well, which an Everforth Apex team member can provide.

Pay

$55-75/HR

Schedule

Hybrid On-Site (Dearborn, MI)

We must ensure we didn't include any boilerplate like EEO, legal, etc. We removed those. Check that we didn't repeat job title as heading. Good. Check that we didn't include Job ID or requisition numbers. We omitted. Check that we didn't include navigation, cookie, etc. Check that we didn't include any filler like "commensurate with experience". Not present. Check that we preserved all substantive information: we included Position Description, Responsibilities list, Skills list (including sub-items), Requirements list, Qualifications (Education), Benefits paragraph, Pay, Schedule. We might have missed some details like "Preferred Technical Experience" (Languages KotlinJavaPython..., Frameworks & APIs..., Data Technologies..., Cloud & Infrastructure..., Engineering Practices..., Preferred GCP Experience...). Those are "Preferred" not required. The instruction: include sections only when posting has real, specific content for it. Preferred experience is still substantive content. Should we include a section for Preferred? Not in the list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Preferred experience could go under Skills or Requirements? But it's "Preferred Technical Experience". Could be considered part of Skills (preferred skills). However we already have Skills section for Required Skills. We could add a subsection under Skills for preferred? But we must not invent headings. Could we add a

under Skills describing preferred? The instruction: Use

• for any list of duties/requirements/benefits, and

  for prose. So we could add a

  under Skills describing preferred experience. But we must preserve all substantive information; we cannot omit preferred experience. So we need to include it somewhere. We could add a

  Preferred Skills

  but not allowed heading. However we could incorporate under Skills as a

  paragraph after the list, describing preferred experience. That would be acceptable: still under Skills heading. Similarly, we have "Preferred GCP Experience" etc. That's also preferred. Thus we need to include all preferred details. Let's extract preferred sections: From the posting: "Preferred Technical Experience Languages KotlinJavaPythonEquivalent JVM/backend programming languages Frameworks & APIs Spring BootgRPCREST API design Data Technologies BigQueryPostgreSQLRedisBigtableKafkaPub/Sub Cloud & Infrastructure Google Cloud Platform or equivalent cloud platformDockerKubernetesCI/CD pipelines Engineering Practices Test-Driven Development (TDD)MLOps-adjacent data pipeline patternsDatabase performance tuningAPI versioning Preferred GCP Experience Familiarity with advanced Google Cloud Platform services beyond core compute and storage, including: Vertex AIDataflowCloud Composer / Apache AirflowBigQuery ML Experience using technologies such as Cloud Composer to orchestrate scheduled data pipelines feeding into a BigQuery data warehouse is preferred." Also earlier: "Preferred Technical Experience Languages KotlinJavaPythonEquivalent JVM/backend programming languages Frameworks & APIs Spring BootgRPCREST API design Data Technologies BigQueryPostgreSQLRedisBigtableKafkaPub/Sub Cloud & Infrastructure Google Cloud Platform or equivalent cloud platformDockerKubernetesCI/CD pipelines Engineering Practices Test-Driven Development (TDD)MLOps-ad