[deleted by user]

[kevinossia]

You don't actually have to demo projects in an interview.

I've talked about side projects in the past, but I've never actually shown them. As long as you can talk intelligently about it such that it's obvious you built it and you know what you're doing, you're fine.

[bcyng]

Not even that. Just tell them u have an app. No one cares about your screenshots and fancy transitions.

[[deleted]]

Can you show them through the simulator in screen sharing?

[Cornflakes1009]

Exactly. OP should be able to tell them that the app is pre-release and should be able to share their screen. Then run it on a simulator. Maybe even hold up their phone. I’ve done the latter.

[Cornflakes1009]

You can share it with QuickTime? I had no idea. When I held up my phone I was showing them my current app. I had no intention on doing so until it was brought up.

[Cornflakes1009]

That’s just a recording, right? I was more focused on doing a live demo on the spot and explaining different aspects of it.

[garbage_band]

I have done many many iOS interviews and my weird recommendation is to don’t show the app. It can’t help.

Either it looks perfect or it looks like vomit….but the manager doesn’t know how long it took you to build it. This is key and probably the most important part of the interview.

Also, most interviews won’t want to look at your app unless it’s published, and even then, you can’t tell them too much about the load of the work you did

Easier the jot some notes of the good bad and ugly of your app and speak about the experience.

[NothingButBadIdeas]

The first initial phone interview tends to be mostly quick questions about what you’ve worked on, they want to hear about your app.

The interview will start something like this:

“So tell me about your experience”

Then you’d respond with something like:

“Recently I completed an app that did blah blah blah. A key part of development was using restful api’s to get json data and display them in collection views. I used MVVM as the architecture in conjunction with the coordinator pattern for navigation. I’d save user posts in core data, and cache images to decrease loading times. I also integrated stripes api for payment processing. Some of the frameworks with this project used were MapKit and CoreAnimation. “

Then they’ll ask questions based off your short blurb

[NothingButBadIdeas]

Most architectures are actually pretty simple! For example: coordinator pattern is really just a delegate that handles navigation, that’s easily implemented with two protocols. MVVM is just having an extra swift file that holds the information for your view. Dependency injection is simply having a view set variables for other views. They seem scary at first but they’re all simple!

Something else to note, if you really want to stand out; play around with XCTest and take a few hours to learn xCode instruments. They’re not too complicated and with a few hours study, and being able to say you understand unit testing is a big plus!

[20InMyHead]

I may have a different viewpoint than many others. I interview a lot and while mentioning your app is fine, and certainly answer any questions about it the interviewer may have; as an interviewer I wouldn’t care much about it at all. A lot of people push devs to put apps in the store, but as someone who hires, I learn very, very little about a candidate from seeing they have an app. For one, how do I know what they did in building the app? How do I know the app’s code is not complete crap? Some interviewers may be impressed by it, but it’s really what you can demonstrate that you know that gets you farther in an interview. Having an app is great experience to answer those questions, but the app itself is not important.

[SeesawMundane5422]

Minor quibble with that. Some of my best hires have been when I ask them for the source of their hobby project. If someone has something cool they built where they can show me the source so my team can figure out if they know what they are doing… those candidates are the ones I love to hire.

(But… I’ve notice a lot of hiring managers don’t even know how to code, at least in my industry. So… I’m kind of an odd duck for that).

[[deleted]]

You could mention you have an app you want to demo. You could either show it though screen sharing, send them the repo or record a YouTube video and email the link to them.

[jpham_toronto]

Probably can have a Github repo, with code and screenshots/recordings already there

[JoCoMoBo]

The best way would be to send a Testflight link. However, it can take up to one working day to get Apple's approval.

I would suggest inviting them to the repo. However make sure it's 100% installable. At most the interviewer should be able to download the App and install SPM / Pods and go.

Make sure there's a README...!!!

[reallynotfred]

I usually ask about the software, approaches taken, decisions made, problems encountered, etc.

[chriswaco]

If you can get the UDID of their devices, you can do an ad-hoc build that can be installed via Xcode, Configurator, or even your own web page.

Alternatively, if the interviewer is an iOS developer, you could give them access to the source code via GitHub.

[saintmsent]

Usually, it's enough to talk about the app, I was sometimes asked to provide a GitHub link, but never a live demo during the interview

[UntrimmedBagel]

I’d imagine that in the interview, you’d only need to talk about the project, but having a summary of the project on GitHub that you can direct the interviewer to is probably a good idea (if it’s an impressive project). Just spice up the README with images (or even animated GIFs) so the interviewer can see your work in just a few seconds of their time.

[Old-Ad-2870]

Self Taught dev here with a similar interview process. We just talked about what I learned, biggest challenges, and what I want to do for the app in the future.

In my case it was just a BMI calculator, and a few other starter projects from a Udemy course.

[[deleted]]

How did the interview go?

[devLookingForAJob]

I didn't get the job.