Three reports describe Flex software interviews as conversational and practical, with resume projects, SQL joins, and object-oriented programming each coming up in two of the accounts.
$103K
Avg. Base Comp
$120K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Flex software interviews, as candidates describe them, tend to be conversational, and two of the three reports center on the projects on your resume. In those accounts, interviewers asked what candidates built and why they chose their technologies. One candidate was also given situational problems. Expect to go deeper than a surface-level project summary.
One Software Engineer candidate had a calm first interview of about 25 minutes built around resume projects, situational questions, and Java concepts from that work. That candidate did not advance and later felt they should have spelled out their design trade-offs more clearly. Another Software Engineer candidate went through two technical rounds, a manager round, and a final discussion spread over at least two to four days. The technical questions covered object-oriented programming, system lifecycle methodology, and SQL joins, and the manager round explained the team's growth projects and the role. The outcome arrived by email a few days later.
A separate Associate Software Engineer report opened with a medium-difficulty aptitude round on data interpretation, logical reasoning, and quantitative questions. The technical round covered HAVING versus WHERE, join types, writing queries for scenarios, and OOP explained in depth. A short HR round followed, and an offer came about three weeks later.
To prepare, rehearse each project out loud, including the alternatives you rejected. Practice writing joins and aggregate queries by hand, and back up OOP answers with examples from your own code.
Synthesized from 4 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 Flex process.
I went in for a Software Engineer role at Flex, and the whole process was surprisingly laid-back. The initial interview lasted about 25 minutes, and the interviewer was calm and welcoming from the start—that kind of ease actually helped me settle in and do my best thinking. Most of the conversation centered around my resume and the projects I'd built. They walked through what I'd done, asked me to explain my thinking, and then threw situational problems at me to see how I'd approach them. The questions weren't purely algorithmic; they wanted to understand how I'd actually solve real problems, and a lot of it came back to Java concepts I'd used in my projects. The interviewer seemed genuinely interested in my background rather than just running through a checklist, which I appreciated. That said, I didn't move forward after this round. Looking back, I think I could have dived deeper into the reasoning behind some of my design decisions and been more explicit about the trade-offs I'd considered. The experience felt professional and collaborative, but apparently it wasn't the right fit for what they were looking for at that stage.
Prep tip from this candidate
Be ready to walk through your resume projects in detail, explaining not just what you built but why you made specific technical choices—especially around Java and OOP concepts. Practice articulating trade-offs in your design decisions when asked situational questions.
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 Flex
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| Find the Missing Number | |
| Scrambled Tickets | |
| Maximum Profit | |
| Hurdles In Data Projects | |
| Find the First Non-Repeating Character in a String | |
| One Element Removed | |
| The Brackets Problem | |
| Level Of Rain Water In 2D Terrain | |
| Get Top N Frequent Words | |
| Precision and Recall | |
| Random Weighted Driver | |
| Cyclic Detection | |
| Three Zebras | |
| One-Hot Encoder | |
| Radix Addition | |
| Valid Anagram | |
| Finding The Mode | |
| Dijkstra implementation | |
| Real-Time Hashtag Partitioning | |
| Success Measurement | |
| Find the Missing Element | |
| Search Linked List | |
| Digitizing Student Test Scores | |
| Matrix Rotation | |
| Target Value Search | |
| Oversized Document Retrieval | |
| Categorize Sales | |
| Worker Distribution Dilemma | |
| Seller Type Modeling |
Synthesized from candidate reports. Individual experiences may vary.
One Associate Software Engineer candidate began with an aptitude round covering data interpretation, logical reasoning, and quantitative aptitude. They rated it medium difficulty and said practicing quant problems and logic puzzles beforehand helped. The Software Engineer reports did not mention this step.
A Software Engineer candidate described a calm interview of about 25 minutes centered on resume projects. The interviewer asked them to explain their thinking and posed situational problems, many tied back to Java concepts from those projects. Be ready to explain why you made each design choice and what trade-offs you weighed.
A Software Engineer candidate reported two technical rounds covering OOP, system lifecycle methodology, and SQL joins, and described the questions as practical rather than abstract algorithm puzzles. The Associate Software Engineer candidate was asked about HAVING versus WHERE, types of JOINs, and writing queries for specific scenarios, and said the focus was on understanding rather than trick questions.
The Software Engineer candidate with the multi-round loop described a manager round about the team's growth projects and the role, then a final discussion, with an email outcome a few days later. The Associate Software Engineer candidate described a short HR round on company policies and logistics, and an offer about three weeks later.
