Skip to main content

LG Ad Solutions

Backend Software Engineer (C++, Go)

New York, NY$154k–$220kfulltimemidAdded 1 month ago

About this role

LG Ad Solutions seeks an experienced backend engineer to build and maintain scalable, low-latency systems for their Automatic Content Recognition platform that processes billions of data points daily. You'll work with Go and C++ to develop high-throughput infrastructure, data pipelines, and contribute to system architecture improvements.

What you'll do

  • Design and develop scalable backend systems in Golang and C++ with emphasis on low latency and high throughput
  • Collaborate on systems architecture updates and improvements
  • Build and maintain high-volume data pipelines using Kafka
  • Drive best practices for QA, testing, and monitoring across the platform

What they're looking for

  • 6+ years backend engineering experience
  • Golang and/or C++ proficiency
  • High-throughput, low-latency system design
  • Kafka data pipeline development
  • Concurrent and performant code writing
  • Debugging tools (GDB, Delve)
  • AWS and Infrastructure as Code
  • Technical documentation
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

LG Ad Solutions

LG Ad Solutions builds advertising and content recognition infrastructure for connected TV, processing massive-scale data pipelines and serving billions of data points daily. The company is hiring software engineers, platform engineers, and backend developers to design distributed systems, manage cloud and on-premises infrastructure, and develop high-throughput data processing platforms.

View all jobs at LG Ad Solutions

Likely interview questions

  • Can you walk us through a low-latency, high-throughput system you've designed in Go or C++? What were the key performance bottlenecks and how did you optimize for them?
  • Describe your experience building and maintaining data pipelines with Kafka. How have you handled backpressure, data ordering, or failure scenarios at scale?