Senior Linux Systems Engineer
About the role
with paragraph). Responsibilities: from What You'll Do. Requirements: from What We're Looking For (mandatory). Qualifications: maybe combine with Requirements? Usually Qualifications separate but we can put Requirements as qualifications. Skills: maybe from Nice to Have? Or we could treat Nice to Have as Skills. Benefits, Pay, Schedule: not present, so omit. We must not create empty sections. Thus sections: About the role, Responsibilities, Requirements, Skills (nice-to-have). Possibly also Company Overview as a section? Not in list of allowed headings; allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Company Overview not allowed; we could fold into About the role? But it's separate. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we can use others? Probably we should stick to those. Company Overview could be placed under About the role? Might be better to include as a paragraph within About the role? But it's separate content about company. Could we create a section "Company Overview"? Not in list but maybe allowed as it's not prohibited. The instruction says use those for section headings (e.g.) meaning those are typical but not exclusive? Safer to include only those headings. Could we put company overview under About the role as extra paragraph? That would mix role description with company overview; but it's still substantive. Might be acceptable.
Alternatively, we could treat company overview as a separate section but not using allowed heading; risk of violating instruction. Better to incorporate into About the role.
Thus:
About the role
... combine About The Role paragraph and Company Overview paragraph.
Then Responsibilities: list items from What You'll Do. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep each bullet point asfor prose; could be multiple
inside section? Probably each
separate. We'll put two
elements. Now Responsibilities: need to capture bullet points under each subheading. From What You'll Do: Platform and fleet: - Own the Linux platform end to end: kernel and base snap versions, patching cadence, image management, end-of-life planning - Run deployment and update pipelines that push OS, driver, application, and configuration changes safely across a large number of units: channels and tracks, staged rollouts, canaries, health checks, rollback - Maintain the display-server layer (Ubuntu Frame/Mir, Wayland, X11, GPU drivers, remote display) on embedded and server-class hardware Application stability and performance: - Ensure the applications running on the platform are stable under real-world load: resource limits, service supervision via snapd and systemd, restart behavior, dependency management - Profile and tune at the OS/application boundary: CPU scheduling, memory pressure, I/O, GPU utilization, network throughput - Define health and performance baselines, set up alerting on regressions, and lead root-cause analysis when things degrade Security: - Own the OS security posture: hardening baselines, access control, privilege separation, secure boot, disk encryption - Use snap confinement (AppArmor, seccomp, interfaces) as the primary isolation boundary for applications - Run vulnerability management: CVE monitoring and triage, patch prioritization, and coordinated rollout across the fleet - Reduce attack surface at the application layer: least privilege, dependency and supply-chain hygiene - Maintain audit logging and integrity checks; support incident response and any compliance requirements Leadership: - Identify where the platform should evolve and make the case with clear tradeoffs and migration paths - Keep documentation, runbooks, and fleet tooling accurate and usable by others - Manage and mentor engineers on the team; set priorities across OS, fleet, application, and cloud reliability work - Be the escalation point for anything below the application code itself We need to output as
- for any list of duties/requirements/benefits. So we can just make a single
- with all these items, preserving the text exactly. Could also group but not needed.
Now Requirements: from What We're Looking For:
- 8+ years running production Linux systems, with real depth in kernel, boot, init, storage, and networking internals
- Experience deploying and updating Linux at fleet scale, ideally on Ubuntu Core: snap packaging and confinement, channel and track management, transactional updates and rollback, and a fleet management tool (Landscape or similar)
- Track record of keeping production applications stable and fast on Linux, including profiling and performance debugging
- Strong security background: you read advisories, understand attack surface, and patch without breaking things
- Hands-on experience with display servers and GPU stacks beyond the desktop use case
- Judgment about when to change something and when to leave it alone
- Comfortable with scripting (Bash, Python) and observability tooling (Prometheus, Grafana, or similar)
- Prior experience leading or mentoring engineers
- Clear written communication
We need to preserve all.
Now Skills: from Nice to Have:
- Experience with IoT or edge device fleets: constrained hardware, intermittent connectivity, remote provisioning and recovery
- Experience building and publishing snap packages, including confinement design and interface declarations
- Experience building custom Ubuntu Core images, gadget and kernel snaps, or brand stores
- Familiarity with other immutable OS models (ostree, NixOS)
- Kernel module or driver debugging experience
- Enough cloud familiarity (AWS, GCP, or similar) to partner well with cloud-focused engineers
- Compliance exposure (SOC 2, ISO 27001, CIS benchmarks)
We should output as
- .
Now ensure we don't include any boilerplate.
Now produce HTML fragment:
About the role
We run an established Ubuntu Core-based platform and display-server estate deployed across a large fleet of devices, along with the applications that run on it. We're looking for an experienced OS internals engineer to own the platform: keep it secure, stable, and performant, evolve it where it makes sense, and make sure changes reach every unit reliably. You'll inherit systems that work and have room to improve them, but we value incremental, well-reasoned change over rewrites. You'll lead our infrastructure function and provide technical direction for the team.
Orange Barrel Media (OBM) creates and operates iconic urban media displays that advertisers ask for by name in top U.S. markets. Since our founding in 2004, OBM has pioneered a community-oriented model of outdoor media development and is nationally recognized by cities and real estate owners alike seeking to implement premier media programs that add to the character of urban places. In the advertising community, OBM is widely recognized as the owner of the highest impact and most memorable advertising locations in the cities where it operates. The OBM team is also a leader in smart city infrastructure, launching the Interactive Kiosk Experience (IKE) platform in concert with cities across the U.S. through the company IKE Smart City. IKE is a best-in-class public engagement platform that helps cities communicate with the public, enliven the pedestrian experience, and tell the story of their city. The core pillars of the IKE platform are public benefit and social equity, values that we seek to maximize in every IKE market to achieve city objectives and exceed community expectations. We are a place where people are inspired to achieve success, genuinely like each other, and have endless opportunities to grow. Learn more at www.obm.com and www.ikesmartcity.com.
Responsibilities
- Own the Linux platform end to end: kernel and base snap versions, patching cadence, image management, end-of-life planning
- Run deployment and update pipelines that push OS, driver, application, and configuration changes safely across a large number of units: channels and tracks, staged rollouts, canaries, health checks, rollback
- Maintain the display-server layer (Ubuntu Frame/Mir, Wayland, X11, GPU drivers, remote display) on embedded and server-class hardware
- Ensure the applications running on the platform are stable under real-world load: resource limits, service supervision via snapd and systemd, restart behavior, dependency management
- Profile and tune at the OS/application boundary: CPU scheduling, memory pressure, I/O, GPU utilization, network throughput
- Define health and performance baselines, set up alerting on regressions, and lead root-cause analysis when things degrade
- Own the OS security posture: hardening baselines, access control, privilege separation, secure boot, disk encryption
- Use snap confinement (AppArmor, seccomp, interfaces) as the primary isolation boundary for applications
- Run vulnerability management: CVE monitoring and triage, patch prioritization, and coordinated rollout across the fleet
- Reduce attack surface at the application layer: least privilege, dependency and supply-chain hygiene
- Maintain audit logging and integrity checks; support incident response and any compliance requirements
- Identify where the platform should evolve and
- .
Now ensure we don't include any boilerplate.
Now produce HTML fragment: