Timesinternet iOS Engineer Interview: Questions, Experience & Prep (2026)

Timesinternet is the digital arm of The Times Group, running some of India's most widely used digital products: the Times of India app, Economic Times, Gaana music streaming, MagicBricks real estate, and several other high-traffic platforms. The company currently has 20 open roles posted, with iOS engineering a clear priority.

The interview process typically runs across 2-3 rounds. Candidates report a coding screen first, a deep technical discussion on iOS architecture and system design, then a final conversation with a senior engineer or hiring manager on past experience and team fit. Across the 70 iOS Engineer openings tracked in India right now, Delhi leads with 21 listings, followed by Bangalore at 6 and Mumbai at 3.

Timesinternet apps handle news feeds, live audio and video streaming, music playback, real estate search, and heavy ad loads. Interviewers focus closely on performance thinking, memory management, and how you build and maintain iOS apps at scale.

These questions reflect the technical and product challenges that Timesinternet iOS teams deal with across their portfolio.

1. How would you reduce cold launch time for a news app that fetches a live feed on startup?
2. Walk us through how you would implement background audio playback on iOS, covering AVAudioSession, interruptions, and lock screen controls. (This is directly relevant to products like Gaana.)
3. How do you handle deep linking in a large iOS app with many content types: articles, property listings, songs, and videos?
4. How would you build a smooth infinite-scroll feed that mixes text, images, ads, and video cards without dropping frames?
5. How do you manage memory when a feed loads many images and video thumbnails at the same time?
6. You need to integrate a third-party ad SDK. How do you test its impact on launch time, memory, and crash rate before shipping to production?
7. How would you implement an offline reading or caching layer for a news app?
8. How do you structure an iOS project when multiple teams are shipping features in parallel, for example one team on news and another on entertainment?
9. How would you handle silent push notifications that update content in the background so the app feels instant when the user opens it?
10. Walk us through a production crash you diagnosed and fixed. What tools did you use and what was the root cause?
11. How would you track analytics events across a multi-product iOS app without tightly coupling feature code to the analytics layer?
12. What is your approach to A/B testing a UI change in a live iOS app at scale?

Q: How would you reduce cold launch time for a news app that fetches a live feed on startup?

*Situation:* At my previous company, our news app was taking several seconds to display the first article on a cold launch, and early-session drop-off for new users was visible in our analytics.

*Task:* I was asked to investigate the launch sequence and bring time-to-first-content down meaningfully.

*Action:* I used Instruments' App Launch and Time Profiler templates and found that a synchronous network call was happening on the main thread, blocking the first frame. I moved the fetch to a background URLSession task, pre-populated the feed with the most recent headlines from a Core Data cache on launch, and loaded fresh content progressively below the fold. I also deferred SDK initializations that were not needed before the first frame.

*Result:* The app showed cached content almost instantly on relaunch, and in an A/B test the group seeing immediate content had noticeably better retention through the first session. The team adopted the pattern across other app sections.

---

Q: How do you manage memory when a feed loads many images and video thumbnails at the same time?

*Situation:* A consumer app I worked on had a vertical scroll feed similar to a news or property listing view. On older devices, the app was receiving memory warnings and occasionally crashing mid-scroll.

*Task:* I needed to reduce peak memory usage without degrading the visual experience for users on newer devices.

*Action:* I used the Memory Graph Debugger to audit the image pipeline and found we were keeping full-resolution images in memory for every recently scrolled cell. I replaced this with a two-level cache: a small NSCache capped by cost in memory, and a disk cache for decoded thumbnails. I also adopted UICollectionViewDataSourcePrefetching to start loads early and cancel them when cells scrolled out of the window. For video thumbnails, I generated them at display size rather than decoding full frames.

*Result:* Peak memory on the feed dropped measurably and we stopped seeing memory-pressure crashes on lower-RAM devices, which our crash reporting confirmed within the first week after the release.

---

Q: Walk us through a production crash you diagnosed and fixed.

*Situation:* Shortly after a feature release, our crash reporter showed a spike in crashes on a property detail screen, affecting a visible slice of users.

*Task:* I needed to reproduce and resolve it quickly because the feature had only just launched.

*Action:* The symbolicated stack trace pointed to a force-unwrap on an optional model field. The crash occurred only when the API returned a null value for a field we had assumed was always populated. I reproduced it locally by mocking the edge-case response, replaced the force-unwrap with safe optional binding and a sensible fallback, added a unit test for the nil case, and then audited the rest of the model layer for similar patterns.

*Result:* A hotfix build shipped the following day and the crash rate on that screen dropped to near zero. The broader audit found and removed several other risky force-unwraps before they could cause their own incidents.

For technical 'how would you' questions: Start with the constraint you are solving for (performance, scale, offline support), name the iOS API or pattern you would reach for, then explain the trade-off you made consciously. Timesinternet runs products at high traffic, so always connect your answer to what happens at scale, not just in a small demo.

For architecture questions: Describe the problem the architecture solves before naming the pattern. Whether you prefer MVVM, MVC with coordinators, or a clean architecture approach matters less than showing you understand why you chose it and where it breaks down under pressure.

For behavioral questions: Use the STAR format: Situation, Task, Action, Result. Keep Situation and Task brief. Spend most of your answer on the specific Actions you took personally, not 'we did this', and quantify the Result wherever you honestly can.

For debugging and crash questions: Show your diagnostic process: reproduce, isolate, instrument, fix, verify. Name your tools by name (Instruments, Memory Graph Debugger, Xcode Organizer, Firebase Crashlytics) because specificity signals real production experience rather than textbook knowledge.

For SDK and third-party integration questions: Always raise the risk angle: impact on binary size, launch time, crash attribution, and user data privacy. Timesinternet ships ad-supported products, so awareness of SDK overhead is directly relevant to their day-to-day engineering decisions.

Product context awareness. Timesinternet builds apps used by a very large number of people across news, music, and real estate daily. Interviewers respond well to candidates who connect technical answers to real user impact: faster launch means more engaged readers, smoother playback means fewer song skips.

Performance as a default habit, not an afterthought. Memory management, background task handling, and UI thread hygiene should feel like second nature. Come ready to discuss Instruments and profiling tools by name, with real examples from your own work, not from a tutorial.

Hands-on debugging depth. Candidates who can walk through a production incident from first symptom to root cause fix, naming the tools and decisions along the way, stand out clearly from those who give only textbook answers.

Collaboration and code quality signals. With 20 open roles, Timesinternet is building teams. Showing that you write testable code, communicate trade-offs to teammates, and take code review seriously matters in the conversation as much as raw technical depth.

Genuine product curiosity. Interviewers notice when a candidate has actually used the apps. Download and explore the Times of India, Economic Times, or Gaana app before your interview. Your answers will be sharper and more specific when you can refer to the actual product.

One week out

Revisit the core iOS concepts most likely to come up: ARC and memory management, URLSession and Swift concurrency (async/await and actors), UICollectionView with diffable data sources, Core Data and caching strategies, and AVFoundation basics for audio and video. Install the Times of India and Gaana apps and spend time thinking about how the feed, media playback, and deep linking might be built under the hood.

Three to four days out

Prepare 2-3 STAR stories from your own work: a performance fix you drove, a production crash you resolved, and a complex feature you shipped end to end. Write down results in concrete terms where you have them, and hedge honestly where you do not. Review how Xcode Instruments works, especially Time Profiler and Memory Graph Debugger, so you can reference them fluently.

One to two days out

Do a focused coding session in Swift: build a simple paginated feed with image caching from scratch, without third-party networking or image libraries. Timesinternet typically expects clean Swift that shows you understand what frameworks do underneath, not just that you can call them.

Day of

Have a concise 'tell me about yourself' ready that leads with iOS-specific depth and highlights any experience with media, feeds, or high-traffic consumer apps. Prepare a question for the interviewer about the team's current technical challenges, as it signals genuine interest in the work.

If you are actively applying to iOS roles, knok checks 150+ job sites every night, applies to roles that match your resume, and messages HR for you, so you can spend your time on interview preparation rather than tracking down listings.

Skipping the 'why'. Many candidates describe what they built but not why they chose that approach. Timesinternet interviewers look for engineers who make conscious trade-offs, not engineers who follow the first result from a web search.

Treating performance as optional. Saying 'I would add lazy loading if needed' is weaker than showing lazy loading is your default. Frame memory management and async work as standard habits you already practise.

Using Objective-C examples exclusively. If your background is mostly Objective-C, prepare Swift-specific examples too. Timesinternet's newer codebases are predominantly Swift, and interviewers will notice if you cannot speak to async/await or value semantics.

Being vague about debugging. 'I used the debugger' is not sufficient. Name the tool, describe the symptom, explain the root cause. Specificity builds credibility in a technical interview far more than confident-sounding generalities.

Not knowing the product. Interviewing for a Gaana-adjacent team without having used the app, or applying to the TOI team without having scrolled the feed, is a missed opportunity to connect your answers to real product problems the team cares about.

Over-relying on third-party libraries. If your entire architecture answer is 'I used Combine' or 'I used Alamofire', follow up immediately with what you understand about what those libraries do underneath. Interviewers want to know you could build without them if needed.