What candidates report about Softrams engineering interviews: a resume-driven panel, a live-coding SDET session, and a DevOps process with slow recruiter communication, plus an estimated US pay range.
$155K
Avg. Base Comp
$165K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The three Softrams candidates here interviewed for different engineering roles, so treat their reports as separate data points. All three were rejected, and each describes a different kind of conversation.
The Full Stack Developer candidate had a recruiter screen followed by an hour-long panel with eight people. Every question traced back to the resume: Selenium, TestNG, JavaScript, project frameworks and Git workflows. This candidate was also asked how JWTs are encoded and decoded, framed as a check on hands-on experience rather than a definition quiz. They described the panel as collaborative.
The SDET candidate had a single recorded Zoom hour with screen sharing and live coding. It started with writing a method to reverse a string. Follow-ups covered which language they would choose to build a new framework and why, what a Gauge feature file is, and the difference between == and === in JavaScript. They were also asked how many tests they write each day. They felt there was little time to think between questions.
The Senior DevOps candidate said the engineers were knowledgeable and the questions leaned on Kubernetes, Terraform and AWS. Their complaints were about recruiting: slow email replies, an assessment that did not match the role they applied for, and salary coming up only at the end.
In practice, be ready to explain every tool on your resume with concrete project examples. Practice small coding exercises while sharing your screen. Confirm the role's scope and pay range with the recruiter early. With only three reports, the format may differ by team and role.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Softrams process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Softrams
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| Prime to N | |
| Over-Budget Projects | |
| Find the Missing Number | |
| One Element Removed | |
| Level Of Rain Water In 2D Terrain | |
| Hurdles In Data Projects | |
| Find Duplicate Numbers in a List | |
| Words in Encrypted String | |
| Target Indices | |
| Swiping App Design | |
| Spam Classifier | |
| 85% vs 82% | |
| RAG Strict Source Control | |
| Subway Machine Learning Model | |
| Inherited Model Evaluation | |
| Seller Type Modeling | |
| Three Indexes Adding Zero | |
| Green Dot | |
| Impossibly Iterative Fibonacci | |
| Why Do You Want to Work With Us | |
| Shortest Path Algorithms | |
| Fixed-Length Arrays: Deletion | |
| Decision Tree Evaluation | |
| Customer Review and Rating System | |
| Your Strengths and Weaknesses | |
| Alternative Vendor Tradeoff | |
| Electricity Supply | |
| Stakeholder Communication | |
| Friends vs Posts |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a recruiter conversation or text exchange before the technical stage, and one said remote and onsite options were both discussed. Another reported being sent an assessment that did not match the role they applied for. It is sensible to confirm the exact role, scope and pay range at this stage.
One candidate described an hour-long panel of eight engineers who probed resume items such as Selenium, TestNG, JavaScript, Git and JWT. Another reported a recorded Zoom session with live string-reversal coding, plus Gauge and JavaScript equality questions. Format likely varies by role and team.
The Senior DevOps candidate said technical questions centered on Kubernetes, Terraform and AWS and that the engineers were easy to talk to. They described a long process with slow email replies. Applicants to infrastructure roles may want to prepare to discuss how they design and operate systems with these tools.
Candidates report mixed communication. The SDET candidate was told to expect news within two days, heard nothing, and received a rejection only after emailing four business days later. The DevOps candidate said feedback requests went unanswered. Sending a polite follow-up is reasonable if timelines pass.
