> Markdown version of [/jobs/ext/4692842-senior-software-engineer-ii](https://www.wearedevelopers.com/jobs/ext/4692842-senior-software-engineer-ii). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Senior Software Engineer II

- **Company:** LiveView Technologies
- **Location:** Seattle, WA, United States
- **Experience:** Expert
- **Salary:** $185,000 - $230,000
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, Amazon Web Services, Amazon S3, Cloud Computing, Cloud Engineering, Distributed Systems, Protocol Buffers, Python (Programming Language), Message Queuing Telemetry Transport (MQTT), Operational Data Store, Software Engineering, Data Streaming, Systems Integration, Network Routers, Backend, Kubernetes, Information Technology, Apache Flink, Avro, Apache Kafka, Api Design, Stream Processing
- **Published:** November 12, 2026
- **Apply:** https://www.careerbuilder.com/job-details/senior-software-engineer-ii-seattle-wa--81868bca-3297-4ba9-bdc5-aac8d53fea13

## About the Role

Software Engineering, Artificial Intelligence (AI), Solar Power, Safety Compliance, Leadership, High Tech Industry, Intelligence Agencies, MCP - Microsoft Certified Professional, Network Routers, Cloud Computing, * Backend / Distributed Systems Depth: 6+ years building and operating backend or distributed systems in production at scale, with strong systems and API design experience.

 * Event Streaming / Log-Based Architecture: Hands-on with Kafka or a comparable log/streaming system; topic and partition design, consumer-group semantics, delivery guarantees, replay, and schema-registry integration.
 * Reliability & Observability: A track record of hardening services for production including SLOs, metrics and alerting, dead-letter and failure handling, and the operational maturity to own on-call trade-offs.
 * Storage & Projection Patterns: Comfortable choosing and operating different stores per access pattern (document/relational hot stores; object storage / lakehouse for cold and analytical).
 * Technical Foundation: Strong in Go and/or Python; experience building APIs and large-scale backend services.
 * Cloud-Native: AWS and Kubernetes, with a bias toward open, cloud-portable components.
 * Education: Bachelor's or Master's in Computer Science, Engineering, or a related field, or equivalent practical experience., * Building agent-facing or MCP data-access layers, governed query interfaces over operational data for autonomous consumers.
 * Integrating agent or CV runtimes onto an event pipeline as pluggable consumers.
 * Stream-processing frameworks (Benthos/Bento, Flink, or similar).
 * Schema and contract tooling (protobuf/Avro, schema registry).
 * Lakehouse producer experience (Iceberg / S3, CDC); MQTT / IoT ingest at scale (EMQX or comparable).

## Description

* Harden the event pipeline: Make the cloud pipeline production-grade consumer reliability, delivery and ordering guarantees, replay, idempotency, dead-letter handling, and schema/contract enforcement at the boundary.
 * Serve the agent layer: Make the dispatch path to agent and CV workflows reliable, and expose the event projections via MCP / agent-facing query interfaces that agents read for context, so the agentic platform has a dependable substrate to run on.
 * Scale ingress and projections: Stand up and scale the materialized stores the pipeline serves from (operational hot store, cold capture into the lakehouse), keeping each projection fit to its access pattern and rebuildable from the log.
 * Observability and operability: Own the signals that make the pipeline supportable, own dashboards, alerting, and feature flags.