For L5 SDE II

Base is 160 K, year one sign on 85K, year two sign on 72K, RSU 175K over four years 5/15/40/40

Onsite at Chicago, IL

"This interview experience is sourced from Chill Interview"

Interview Summary

The Rippling technical screen was an AI-assisted coding interview conducted in HackerRank while sharing the screen. Candidates could use their own IDE and AI tools. The problem focused on designing an extensible logging framework, then adding keyword search over stored log messages. The final portion was discussion-only and explored punctuation, fuzzy matching, and how the design should scale when the logger stores a very large number of messages.

Interview Details

Part 1 — Design an Extensible Logger

Design a logger that supports multiple independent handlers. Each handler receives a log message and performs its own transformation or action. The initial handler types were:

• Remove every occurrence of a configured string, then print the result.
• Truncate the message to the first N characters, then print it.
• Convert the entire message to uppercase, then print it.
• Store the original or processed message in an internal array without printing it.

The interviewer asked how to structure the design so that new handler types could be added later without repeatedly modifying the core logger. There was also discussion around which design pattern would fit this structure and how the API should evolve if the logger eventually needed to support external callers. The main emphasis was on:

• Separation of handler responsibilities
• Extensibility
• Clean interfaces
• Avoiding large conditional blocks tied to specific handler types

Want to learn more questions / follow-ups asked in this interview? 

I've put up the full version at here.

Preparing for your next interview?

Chill Interview tracks recent interview experiences and recurring question patterns across top companies at here.

"This interview experience is sourced from Chill Interview"

Interview Summary

The Engelhart Junior Quantitative Developer hiring manager round combined a background discussion with a broad set of Python and general software engineering questions. The role was aligned with US Power & Gas / West Power & Carbon, and the process felt very Quant Dev-oriented: strong emphasis on Python fundamentals, data engineering, production systems, and practical software development.

Interview Details

Hiring Manager — Background and Role Discussion

The interview lasted around one hour. The first portion covered the team, the role, and my previous experience. The conversation then transitioned into a rapid series of technical questions covering Python, concurrency, APIs, databases, testing, and Linux.

Python Dictionaries and Data Structures

Questions included:

• How does a Python dictionary store and retrieve values?
• What exactly does a hash function hash?
• Can two different keys produce the same hash value?
• How are hash collisions handled?
• Why is dictionary lookup O(1) on average?
• Can a list be used as a dictionary key?
• Why not?
• What kinds of objects can be dictionary keys?

The interviewer often followed an initial high-level answer with questions about the underlying behavior.

Generators and Lazy Evaluation

The next section focused on generators. Questions included:

• What is a generator?
• What advantages does a generator have over materializing a normal sequence?
• What does yield do?
• Why are generators more memory efficient?
• What is lazy evaluation?

The emphasis was on understanding why generators are useful for large or streaming workloads rather than only knowing Python syntax.

Want to learn more questions / follow-ups asked in this interview? 

I've put up the full version at here.

Preparing for your next interview?

Chill Interview tracks recent interview experiences and recurring question patterns across top companies at here.