Product Engineer (Backend) at Instabug

Job description

What this role is You own a slice of Luciq end to end: the problem, the design calls, the code, the rollout, and customer value. Engineers bring a lot of value to driving product decisions and we innovate on the implementation layer to create differentiating solutions. The stack is Ruby on Rails and Golang hosted on Kubernetes clusters on AWS, with ClickHouse, Kafka, and Flink behind ingestion and query. You will hand-write less of it than engineers did two years ago. We expect you to work with coding agents the way a strong engineer works with a capable junior: delegate hard, review harder, stay accountable for what ships. Half the job is judgment about what to build. Luciq is repositioning around agentic mobile observability and experience. We are a broad mobile platform with large enterprise customers who get a lot of value from the different capabilities and signals we capture and innovate on. What you'll do Ship a product area end to end: scope it, build it, launch it, then watch the usage numbers and make sure customers get a lot of value. Build the agentic parts of the product. Use agents on your own work. Codegen, migrations, test coverage, spec-to-PR. Bring what works back to the rest of engineering. Talk to customers directly. Join escalations, read session replays, sit on calls. As you gain knowledge of the product and customer space, participate actively in driving scope and work in iterations to deliver. Instrument what you ship. You should know your feature's adoption, p95 and infrastructure cost. We invest in helping our Product Engineers get to this level of detail and want them engaged in evolving it, creating efficiencies and making decisions to drive further improvements. Operate what you build. On-call responsibility is part of the role and more importantly, share the learnings, implement the preventative measures and continue to iterate. Make the rest of the company faster. We all share in the success of our customers, we win together. Raise the floor on quality and security in the code you touch, and leave the codebase easier to work in than you found it. What we're looking for We do not screen on years or degrees. Tell us what you built, who used it, and what changed because of it. Required A track record of shipping products that real users depended on, with your fingerprints on the product decisions, not only the implementation. Minimum of 5 years of experience shipping production software, ideally in a fast-moving product engineering environment. Deep production experience in Golang, or enough depth in another server language. AWS at production scale: compute, storage, networking, CI/CD, and a working sense of what things cost. Shipped something built on LLMs. You can talk about retrieval, tool calling, evals, latency and failure modes from experience, not from reading. A daily agent-assisted workflow, and an opinion about where it breaks down. Taking full ownership of the work generated, the quality and the approach to the implementation. We love simple solutions to complex problems and we value engineers and the high leverage they bring. AI is a tool in the toolbox. Solid API design, and comfort with MySQL, Redis and a messaging system such as Kafka. You test where tests pay and skip where they don't, and you apply a pragmatic approach to building guardrails. You write clearly. Design notes, incident writeups, release notes. Helps Mobile experience: iOS or Android, SDK work, or debugging someone else's app in production. Columnar and streaming infrastructure: ClickHouse, Flink, or similar at volume. Developer tools or observability as a product domain. Open source work. How we work Pods own customer outcomes, not services. Your scope follows the problem across the SDK, the pipeline, the API, and the dashboard. Decisions happen in the open, in writing, and fast. If you need three meetings to change a schema, this will frustrate you. You will be in the room when pricing, packaging, and positioning touch your area, and your objections count. We deploy continuously, and we watch what we deploy. There is no queue of pre-chewed tickets waiting for you. There is a roadmap, a lot of customer signals, and room to drive high-impact work.

Requirements

Must-haves

What this role is
Ship a product area end to end: scope it, build it, launch it, then watch the usage numbers and make sure customers get a lot of value.
Build the agentic parts of the product.
Use agents on your own work. Codegen, migrations, test coverage, spec-to-PR. Bring what works back to the rest of engineering.
Talk to customers directly. Join escalations, read session replays, sit on calls.
As you gain knowledge of the product and customer space, participate actively in driving scope and work in iterations to deliver.
Operate what you build. On-call responsibility is part of the role and more importantly, share the learnings, implement the preventative measures and continue to iterate.
Make the rest of the company faster. We all share in the success of our customers, we win together.
Raise the floor on quality and security in the code you touch, and leave the codebase easier to work in than you found it.
We do not screen on years or degrees. Tell us what you built, who used it, and what changed because of it.
A track record of shipping products that real users depended on, with your fingerprints on the product decisions, not only the implementation.
Minimum of 5 years of experience shipping production software, ideally in a fast-moving product engineering environment.
Deep production experience in Golang, or enough depth in another server language.
AWS at production scale: compute, storage, networking, CI/CD, and a working sense of what things cost.
Shipped something built on LLMs. You can talk about retrieval, tool calling, evals, latency and failure modes from experience, not from reading.
Solid API design, and comfort with MySQL, Redis and a messaging system such as Kafka.
You test where tests pay and skip where they don't, and you apply a pragmatic approach to building guardrails.
You write clearly. Design notes, incident writeups, release notes.
Mobile experience: iOS or Android, SDK work, or debugging someone else's app in production.
Columnar and streaming infrastructure: ClickHouse, Flink, or similar at volume.
Developer tools or observability as a product domain.
Open source work.
Pods own customer outcomes, not services. Your scope follows the problem across the SDK, the pipeline, the API, and the dashboard.
Decisions happen in the open, in writing, and fast. If you need three meetings to change a schema, this will frustrate you.

Nice-to-haves

None flagged.

Application prep

Use the role’s language and application details while tailoring your materials.

Keywords to mirror

golangkubernetesawsrestci/cdaiapi

Platform: bamboohr
Effort: medium