Made tech Software Engineer interview typically runs 3 rounds: HR, technical system design/pair programming, and a scenario-based architect conversation. The process took a little over two weeks and felt rushed and highly structured.
$41K
Avg. Base Comp
$90K
Avg. Total Comp
3
Typical Rounds
2-3 weeks
Process Length
Our candidates report that Made Tech is looking for engineers who can stay grounded when the conversation gets concrete. The strongest signal isn’t flashy architecture; it’s whether you can take a public-service style problem, turn it into a sensible design, and then keep extending that same solution in code without losing the thread. We’ve seen repeated emphasis on pragmatic tradeoffs and a collaborative, test-driven mindset, which suggests they care less about perfect answers than about how you reason in real time.
A recurring theme is how opinionated the panel can be about delivery style. One candidate described architects pushing on digital transformation and client discovery in a very practical way, with a clear preference for someone who can gather requirements from a customer and translate them into something buildable. That lines up with the coding feedback too: they seemed to value detail-oriented implementation and TDD over algorithmic cleverness. In other words, they want to see whether you can work like someone who will actually ship with a team, not just whiteboard alone.
We’ve also noticed that the process can feel checklist-driven, so concise, structured thinking matters. Candidates who did best were ready to explain why they chose a particular cloud feature, how they handled a recent project, and how they’d resolve conflict without drifting into theory. The non-obvious trap here is over-engineering: if your design sounds impressive but not practical, it can work against you. Made Tech appears to reward engineers who can be calm, specific, and useful under pressure.
Synthetized from 1 candidates 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 Made tech 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 Made tech
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Prime to N | |
| Employee Salaries | |
| Top 3 Users | |
| Rolling Bank Transactions | |
| Customer Orders | |
| String Shift | |
| Comments Histogram | |
| Size of Joins | |
| Closest SAT Scores | |
| Random SQL Sample | |
| Largest Salary by Department | |
| Find the Missing Number | |
| Upsell Transactions | |
| Monthly Customer Report | |
| First Touch Attribution | |
| Raining in Seattle | |
| Hurdles In Data Projects | |
| Manager Team Sizes | |
| P-value to a Layman | |
| Job Recommendation | |
| Minimum Change | |
| Address Schema | |
| Lowest Paid | |
| Download Facts | |
| Permutation Palindrome |
Synthesized from candidate reports. Individual experiences may vary.
An informal first conversation with HR focused on your background, motivation for the role, and a recent project. This stage also included some behavioral discussion, such as your ideal development process and how you handled conflict with a colleague.
A structured technical round that moved quickly from system design into coding on the same problem. Candidates were asked to design a public-service style system, then implement specific use cases, with an emphasis on pragmatic choices, test-driven development, and collaborative reasoning.
A practical discussion with two architects about how you would approach a digital transformation and how you would gather requirements from a client. The interview was grounded in real-world consulting scenarios and favored a hands-on, opinionated approach over theoretical answers.