Senior Software Engineer - Core Team

{
  "content_hash": "e93b922160b29150a43b0ebef8a2c52b85eec1b9fd10de036527f1c6580f224f",
  "source_hash": "54d7e84b76e5401d119a8f603a7641190876297ce9e5bc1ea80423c8a2b0f0da",
  "last_changed_at": "2026-06-23T10:47:38.354Z",
  "active_status": "active"
}

{
  "dedupe": null,
  "language": "en",
  "location": {
    "raw": "Dublin, Dublin, D01 V3P0, Ireland",
    "city": "Dublin",
    "region": "Dublin",
    "country": null,
    "is_remote": false,
    "confidence": 0.8
  },
  "salary_max": null,
  "salary_min": null,
  "inferred_at": "2026-06-23T10:47:38.354Z",
  "launch_scope": {
    "reason": "bamboohr_production_catalog",
    "included": true,
    "location": {
      "raw": "Dublin, Dublin, D01 V3P0, Ireland",
      "city": "Dublin",
      "region": "Dublin",
      "country": null,
      "is_remote": false,
      "confidence": 0.8
    },
    "countries": []
  },
  "remote_policy": null,
  "salary_period": null,
  "workplace_type": null,
  "salary_currency": null
}

{}

{
  "list_job": {
    "id": "128",
    "isRemote": null,
    "location": {
      "city": "Dublin",
      "state": "Dublin"
    },
    "atsLocation": {
      "city": null,
      "state": null,
      "country": null,
      "province": null
    },
    "departmentId": "18573",
    "locationType": "2",
    "jobOpeningName": "Senior Software Engineer - Core Team",
    "departmentLabel": "Engineering",
    "employmentStatusLabel": "Full-Time"
  },
  "detail_errors": [],
  "detail_job_opening": {
    "location": {
      "city": "Dublin",
      "state": "Dublin",
      "postalCode": "D01 V3P0",
      "addressCountry": "Ireland"
    },
    "datePosted": "2026-06-22",
    "atsLocation": {
      "city": null,
      "state": null,
      "country": null,
      "countryId": null
    },
    "description": "<p><span style=\"color: rgb(43, 58, 85); font-size: 14pt; font-weight: bold\">About Userpilot</span></p>\n<p><span style=\"font-size: 10pt\">Userpilot is a leading product analytics and engagement platform. Hundreds of product teams use us to understand, segment, and activate their users in real time. Under the hood, that's a distributed Elixir/Phoenix backend sustaining hundreds of thousands of concurrent WebSocket connections, high-throughput Kafka event ingestion, ClickHouse analytics at scale, and always-on content delivery.</span></p>\n<p><span style=\"font-size: 10pt\">We move fast, we ship often, and we believe the best engineers care as much about how the whole system holds together as about the feature in front of them.</span><br></p>\n<p><br></p>\n<p><span style=\"color: rgb(43, 58, 85); font-size: 14pt; font-weight: bold\">The Role</span></p>\n<p><span style=\"font-size: 10pt\">This is the most senior individual-contributor engineering role at Userpilot, and it is a different kind of role. Core Team engineers are the closest thing we have to software architects. They don't own a single feature area; they own how the system fits together, how it behaves under load, and how it recovers when something breaks.</span></p>\n<p><span style=\"font-size: 10pt\">They are a rare breed: equally at home in a Terraform module, an application lifecycle, a high volume database query plan, and an architecture review. They set the technical direction the rest of engineering builds on, they are the first responders when production is on fire, and they design the guardrails that stop a class of problem from ever happening twice. Application squads move fast on features precisely because the Core Team keeps the ground underneath them solid.</span></p>\n<p><span style=\"font-size: 10pt\">And they do all of this in an AI-native way. Coding agents extend their reach across the stack, but the judgment about what is safe, what will scale, and what must never break stays with them.</span><br></p>\n<p><br></p>\n<p><span style=\"color: rgb(43, 58, 85); font-size: 14pt; font-weight: bold\">Where You'll Have Impact</span></p>\n<ul>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Technical direction and system design. </span><span style=\"font-size: 10pt\">Decide how non-trivial work should be built before a squad writes the first line. Write the ADRs, choose the patterns, and make durability, extensibility, robustness, observability, and scalability properties of the system rather than afterthoughts bolted on later.</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Scale and reliability. </span><span style=\"font-size: 10pt\">Keep a distributed, real-time system healthy as traffic grows: event pipelines from Kafka into ClickHouse, real-time delivery over hundreds of thousands of connections, caching, backpressure, and the failure modes that only appear at scale or during a deploy.</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Firefighting and incident response. </span><span style=\"font-size: 10pt\">Be the first call when production breaks. Diagnose under pressure, restore service, find the real root cause, and then turn that incident into a guardrail so the squads don't keep hitting it.</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Infrastructure and foundations. </span><span style=\"font-size: 10pt\">Own infrastructure provisioning end to end: AWS (EKS, EC2, S3, RDS) and the Terraform and Kubernetes that tie it together. This is one of the things you do, not the whole job.</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Enabling the squads. </span><span style=\"font-size: 10pt\">Raise the architectural bar across teams you don't manage. Review for architectural consistency, drive adoption of patterns that actually stick, and keep application engineers focused on shipping product.</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Agentic engineering infrastructure. </span><span style=\"font-size: 10pt\">Make the system safe for a team that ships with AI agents: CI/CD quality gates every PR must pass regardless of author, AGENTS.md and runbooks that teach agents the topology and operational constraints, and Infrastructure as Code clean enough that an agent's change proposal is safe to reason about.</span><br></li>\n</ul>\n<p><br></p>\n<p><span style=\"color: rgb(43, 58, 85); font-size: 14pt; font-weight: bold\">What You'll Do</span></p>\n<ul>\n<li><span style=\"font-size: 10pt\">Lead system design for cross-cutting and high-risk work, and write and shepherd ADRs the org actually follows.</span></li>\n<li><span style=\"font-size: 10pt\">Partner with application squads to turn product requirements into designs that hold up under load and over time, then get out of their way.</span></li>\n<li><span style=\"font-size: 10pt\">Own production reliability: monitoring, alerting, and on-call practices that surface real problems without drowning the team in noise (Grafana, Prometheus, CloudWatch).</span></li>\n<li><span style=\"font-size: 10pt\">Be first-in on incidents: run the diagnosis, coordinate the fix, write the postmortem, and ship the change that prevents a recurrence.</span></li>\n<li><span style=\"font-size: 10pt\">Design, provision, and operate infrastructure on AWS with Terraform and Kubernetes, with high availability and cost both in mind.</span></li>\n<li><span style=\"font-size: 10pt\">Build and improve CI/CD pipelines and validation gates that make every change trustworthy, whether a human or an agent wrote it.</span></li>\n<li><span style=\"font-size: 10pt\">Write the technical context (ADRs, runbooks, AGENTS.md) that makes the system understandable to new engineers and safe for AI tools.</span></li>\n<li><span style=\"font-size: 10pt\">Keep an eye on infrastructure cost and find the optimizations that actually matter.</span></li>\n<li><span style=\"font-size: 10pt\">Provide technical direction and mentorship across the engineering org.</span></li>\n</ul>\n<p><br></p>\n<p><span style=\"color: rgb(43, 58, 85); font-size: 14pt; font-weight: bold\">What We're Looking For</span></p>\n<p><span style=\"color: rgb(26, 26, 26); font-size: 12pt; font-weight: bold\">Required</span></p>\n<ul>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Senior experience designing and operating distributed systems in production</span><span style=\"font-size: 10pt\">, with a track record of being the person who owns how the whole system fits together.</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Strong software-engineering and CS fundamentals</span><span style=\"font-size: 10pt\"> (data structures, algorithms, system design). You can go deep in application and backend code, not just infrastructure.</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Architectural judgment</span><span style=\"font-size: 10pt\">: you reason explicitly about durability, extensibility, robustness, observability, and scalability and the tradeoffs between them, and can write an ADR others can follow.</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Distributed-systems instincts</span><span style=\"font-size: 10pt\">: you can break down a complex system to find its failure modes, bottlenecks, and the one change that actually moves the needle.</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Calm, methodical incident response</span><span style=\"font-size: 10pt\">: you root-cause under pressure and instinctively turn an incident into prevention.</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Hands-on infrastructure</span><span style=\"font-size: 10pt\">: AWS (EKS, EC2, S3, RDS) and the networking that connects them, production Kubernetes and Docker (operating clusters, not just deploying to them), and solid Terraform / Infrastructure as Code.</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Observability in practice</span><span style=\"font-size: 10pt\">: Grafana, Prometheus, CloudWatch, and alerting that signals real problems.</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Strong communication and influence</span><span style=\"font-size: 10pt\">: this role touches every team, and you drive adoption of patterns across people who don't report to you.</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">An AI-native workflow</span><span style=\"font-size: 10pt\">: you use AI coding agents (Claude Code, Cursor) as a real part of how you work, and you have a point of view on how to review and trust their output.</span></li>\n</ul>\n<p><br><br></p>\n<p><span style=\"color: rgb(26, 26, 26); font-size: 12pt; font-weight: bold\">Bonus Points</span></p>\n<ul>\n<li><span style=\"font-size: 10pt\">Elixir, Erlang, or BEAM systems (our backend runs on them) and OTP patterns: supervision trees, GenServers, distribution.</span></li>\n<li><span style=\"font-size: 10pt\">Scaling highly available distributed systems in a fast-moving product environment.</span></li>\n<li><span style=\"font-size: 10pt\">Kafka, RabbitMQ, ClickHouse, Broadway, or similar high-throughput data tooling (we use both brokers).</span></li>\n<li><span style=\"font-size: 10pt\">Building and operating CI/CD that supports high-frequency deployments.</span></li>\n<li><span style=\"font-size: 10pt\">Cloud cost optimization through caching, right-sizing, or more efficient data processing.</span></li>\n<li><span style=\"font-size: 10pt\">Experience as a tech lead, staff engineer, or architect setting direction for an engineering org.</span></li>\n<li><span style=\"font-size: 10pt\">A point of view on the trust model for automated and agent-generated change: automated PRs, agent-triggered deploys, and the gates that make them safe.</span></li>\n<li><span style=\"font-size: 10pt\">Interest in AI-powered observability: anomaly detection, automated runbook execution, or self-healing infrastructure.</span></li>\n<li><span style=\"font-size: 10pt\">Writing technical context documentation (runbooks, ADRs, AGENTS.md-style files) that makes systems understandable to the people and agents joining them.</span></li>\n</ul>\n<p><br><br></p>\n<p><span style=\"color: rgb(43, 58, 85); font-size: 14pt; font-weight: bold\">Our Stack</span></p>\n<ul>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Cloud: </span><span style=\"font-size: 10pt\">AWS (EKS, EC2, S3, RDS, CloudFront)</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Orchestration: </span><span style=\"font-size: 10pt\">Kubernetes, Docker, Terraform</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Backend: </span><span style=\"font-size: 10pt\">Elixir / Phoenix, OTP</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Data: </span><span style=\"font-size: 10pt\">ClickHouse (analytics), MySQL (primary)</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Messaging: </span><span style=\"font-size: 10pt\">Kafka, RabbitMQ, Broadway</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Observability: </span><span style=\"font-size: 10pt\">Grafana, Prometheus, CloudWatch</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">CI/CD: </span><span style=\"font-size: 10pt\">GitHub Actions</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">AI: </span><span style=\"font-size: 10pt\">Claude Code / Cursor for agentic development; AGENTS.md, CLAUDE.md, and Infrastructure as Code as shared context for humans and agents alike</span></li>\n</ul>\n<p><br><br></p>\n<p><span style=\"color: rgb(43, 58, 85); font-size: 14pt; font-weight: bold\">What “Agentic Engineering” Means Here</span></p>\n<p><span style=\"font-size: 10pt\">We are shifting toward spec-driven, AI-assisted development, and the Core Team is what makes that safe.</span></p>\n<ul>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Every PR, human or agent, passes the same quality gates. </span><span style=\"font-size: 10pt\">Our CI/CD has to be reliable, fast, and unambiguous in its feedback, regardless of who (or what) wrote the change.</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Agents need to understand where they're operating. </span><span style=\"font-size: 10pt\">We maintain AGENTS.md and operational context so an agent doesn't make a dangerous assumption about topology, service contracts, or operational constraints.</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Infrastructure as Code is the single source of truth</span><span style=\"font-size: 10pt\">, for humans and for agents proposing changes. The cleaner and more expressive it is, the safer agent-assisted work becomes.</span></li>\n<li><span style=\"font-size: 10pt; font-weight: bold\">Agents do a lot of the typing; the Core Team owns the architecture, the judgment, and the boundaries </span><span style=\"font-size: 10pt\">that keep fast-moving, non-deterministic development from compounding into risk.</span></li>\n</ul>\n<p><span style=\"font-size: 10pt\">You don't need to have built agentic infrastructure before. But you should find the challenge genuinely interesting.</span></p>\n<p><br><br></p>\n<p><span style=\"font-size: 14pt; font-weight: bold\">Right to Work</span></p>\n<p><span style=\"font-size: 10pt\">Candidates must have the right to work in Ireland. We are not in a position to offer visa sponsorship for this role.</span></p>\n<p><br></p>\n<p><span style=\"font-size: 14pt; font-weight: bold\">Equal Opportunities Statement</span></p>\n<p><span style=\"font-size: 10pt\">Userpilot is an equal opportunity employer. We are committed to creating an inclusive environment for all employees and applicants. We do not discriminate on the basis of gender, civil status, family status, age, disability, race, religion, sexual orientation, or membership of the Traveller community, in accordance with the Employment Equality Acts 1998–2015.</span></p>\n<p><br></p>\n<p><span style=\"font-size: 14pt; font-weight: bold\">Data Privacy Notice</span></p>\n<p><span style=\"font-size: 10pt\">By applying for this role, your personal data will be processed by Userpilot for the purposes of recruitment and candidate evaluation. We will retain your information for no longer than is necessary for this purpose.</span></p>",
    "compensation": null,
    "departmentId": "18573",
    "locationType": "2",
    "seekPromoted": false,
    "jobCategoryId": null,
    "jobOpeningName": "Senior Software Engineer - Core Team",
    "departmentLabel": "Engineering",
    "jobOpeningStatus": "Open",
    "minimumExperience": "Experienced",
    "jobOpeningShareUrl": "https://userpilot.bamboohr.com/careers/128",
    "employmentStatusLabel": "Full-Time"
  }
}