Three candidates describe short, fairly relaxed technical screens at the Church for software roles: OOP concepts, an easy coding problem, or a small HTML/CSS/JavaScript task, with a mix of offer and no-offer outcomes.
$100K
Avg. Base Comp
$115K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The three candidates here interviewed for software-adjacent roles, two as web developer interns and one as a software QA tester. All three describe short, practical technical conversations. They are not marathon loops, so treat the details below as a guide to what these candidates saw, not a fixed format for every software engineer opening.
One intern reports three phases of about ten minutes each. They covered object-oriented fundamentals such as inheritance and polymorphism, then a Leetcode easy-level algorithm problem, then follow-up questions about their thought process. That candidate received an offer and describes the tone as collaborative, with interviewers supportive when they got stuck.
The QA tester describes a roughly hour-long conversation. It began with about five minutes of background, then ten to fifteen minutes on software engineering concepts such as modularization, then a 20-25 minute coding challenge. That candidate stressed edge cases and test-case thinking, and did not receive an offer.
The other intern, who found the interview through Handshake and did not get an offer, had a roughly 30-minute Teams call. It included a sandbox task in HTML, CSS, and JavaScript: create an input field, change some colors, and validate whether a number is divisible by 3. Searching the internet was allowed.
In practice, prepare to explain core concepts clearly, solve an easy problem aloud, and handle small front-end tasks. Be ready to talk about past work, since one interviewer asked about a portfolio. Clear communication is the recurring theme in these accounts.
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 The church of jesus christ of latter-day saints 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 The church of jesus christ of latter-day saints
In which case would you use a bagging algorithm versus a boosting algorithm
| Question | |
|---|---|
| Delivery Estimate Model | |
| Hurdles In Data Projects | |
| P-value to a Layman | |
| Success Measurement | |
| Skyscanner Partner ETL | |
| Spam Classifier | |
| Model Deployment Pipeline | |
| Why Do You Want to Work With Us | |
| Stakeholder Communication | |
| Ranking Metrics | |
| Your Strengths and Weaknesses | |
| Simple Explanations | |
| Statistically Significant Test | |
| Branch Sales Pivot | |
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Random SQL Sample |
Synthesized from candidate reports. Individual experiences may vary.
One intern candidate reports finding the interview through Handshake. They uploaded a resume and then picked an available slot, noting that slots were first come, first served. Other candidates do not describe how they were scheduled, so this may apply mainly to campus recruiting.
The QA tester candidate reports starting with roughly five minutes about their background and experience. The intern on the Teams call also reports an overview of their application and questions about prior experience and a portfolio. Expect a brief, casual opening before technical content.
One intern candidate reports conceptual questions on inheritance and polymorphism in the first of three roughly ten-minute phases. The QA candidate reports ten to fifteen minutes on software engineering concepts such as modularization. Candidates may want a simple example ready for each concept.
Candidates report coding tasks of modest difficulty. One had a Leetcode easy-level problem, one had a 20-25 minute coding challenge involving edge cases and test cases, and one had a sandbox task in HTML, CSS, and JavaScript with a divisibility-by-3 check. Explaining your approach while working appears to matter.
The intern with the offer reports a final phase of follow-up questions on their thought process and general programming knowledge. The other two candidates report no offer. Their accounts do not say what led to those outcomes, so avoid drawing conclusions about what decided them.
