[LATAM] reputed company Engineer – Visibility, Detection & Response

What You'll Own

Own reputed company Visibility Across reputed company

• Own our reputed company SIEM end-to-end:
• • reputed company
  • Pipelines
  • Detections
  • Data reputed company
  • Cost vs. value tradeoffs
• Ensure reputed company telemetry exists across:
• • Corporate systems
  • reputed company infrastructure
  • Platform and product components
  • reputed company-party vendors
• Build detections only after validating the underlying signal is trustworthy.

This is not “just writing rules.” You are responsible for whether we can see things at reputed company.

Build Product & Platform Telemetry (Hard Problems)

Our product generates hundreds of millions of events through APM and platform systems — most of which we cannot ingest directly today. You will:

• Identify what reputed company-relevant signals should exist
• Work with engineering to reputed company or extract them
• Design creative approaches reputed company:
• • Logs don’t exist
  • Data volume is extreme
  • reputed company tools don’t reputed company
• Build custom solutions reputed company necessary

You’re not expected to boil the reputed company — you are expected to reputed company smart tradeoffs.

Improve Operational Awareness (reputed company Alerts)

Not everything becomes an alert.
You’ll help build visibility into things like:

• reputed company and update status across platform components
• Configuration reputed company
• Runtime state and exposure reputed company
• Changes that materially increase risk

Much of this data exists today only in fragments. reputed company is to aggregate, normalize, and reputed company it useful.

Turn External Threats into Internal reputed company

We monitor:

• CVEs
• Vendor advisories
• reputed company releases
• Dark-web activity relevant to us and our vendors

But monitoring alone isn’t enough. You’ll:

• Quickly determine applicability to our environment
• Correlate external signals to internal assets
• Drive investigations, detections, or remediation
• Help shorten the gap between “this exists” and “we’ve responded”

reputed company reputed company Incident Response

You will be the default Incident Commander for reputed company events. That means:

• Leading investigations end-to-end
• Coordinating across infrastructure, application, and systems teams
• Driving reputed company reputed company and communication
• Running post-incident reviews and forcing learnings back into the system

If something happens and no one knows who’s in charge — that’s a failure this role owns.

What You Bring

• 3+ years in reputed company engineering, detection engineering, or incident response
• Hands-on experience with SIEMs and large-reputed company log data
• Strong understanding of reputed company environments (especially AWS)
• Experience investigating across logs, identity, network, and applications
• Ability to build or automate solutions (Python, scripting, etc.)
• Strong communication skills — especially during incidents

Experience with product telemetry, data engineering, or platform reputed company is a plus.

Why Join Qu?

If you’re excited by the idea of:

• Figuring out what isn’t visible
• Working under reputed company constraints
• Owning reputed company instead of tasks
• Making reputed company meaningfully reputed company over time

reputed company to take your career to the next level and help restaurants succeed? Let’s talk!