interviewing for a software engineer role at RenTech in a few weeks and trying to triangulate what the loop actually looks like right now. most of what i can find online is vague or years old.
if you've been through their SWE process in the past year or so, can you share: how many rounds, what the coding portion covered, whether there was a systems design component, and roughly what level you were going for? even partial data helps.
i'm coming from infra/platform background and honestly not sure if that's an advantage or irrelevant to them. any context appreciated.
4 replies
remote_swe_42
went through it about 8 months ago for a mid-level SWE role. two phone screens (one recruiter-ish, one technical), then a 4-hour onsite with: one coding (algorithmic, harder than typical FAANG), one systems design (not the usual web-scale stuff, more about data processing and throughput), and two open-ended interviews that felt more like research conversations than standard SWE screening. no behavioral panel that i noticed.
corp_refugee
the systems design component they care about is different from what you'd prep at FAANG. less about CAP theorem and more about: given this computational problem, what's your data flow. infra background is probably more relevant than you think.
infra_ines
that's actually reassuring. i was worried my systems knowledge was the wrong flavor. sounds like it might translate.
qa_quinn
worth flagging that what they test probably shifts based on the team. they're not one monolithic SWE org. the trading infrastructure team and the research tools team are probably screening for different things.