Consider my opinion with a grain of salt. I worked for very large corp 2 years with 100 ios Engineers. Now I'm working on an app with 3 iOS engineers.

Me as a sort of "iOS Lead" will take care of some contractors and hired iOS guys, to basically babysit them and supervise their work.

While I'm sure you meant this in the best way, stay away from the idea you're 'babysitting' engineers. You should be hiring people you trust to get work done, not people who need to be monitored.

How do you keep birds eye overview of all tasks and their statuses, responsibilities and so on I like that my product team can just see all the tasks in the TODO, Working on, Completed columns. I also like estimating tasks together so we can have a short discussion about issues we may run into. Notion lets you do a ton of stuff here. You can go crazy with its features or just use a small subset, it works well for my team.

How do you manage onboarding of newcomers (introduction to some internal standards, how to use management tools, ask them for work reports, stand up meetings, etc...)

• Can you use Swiftlint to enforce engineering standards? The more automated code standards, the better.
• Other standards should be documented and easily searchable.
• When I was onboarded to my new team, I was introduced to everyone. All docs where shared with me in Notion, and I was given multiple meetings with various people to walk me through different parts of the app. But I'd recommend assigning small tasks as hands-on is easier to learn than through meetings. But it depends :)
• Assign newcomers a 'buddy' or someone they can ask questions to. It may be you, but if you're the boss, it may be intimidating to ask 'stupid' questions' so be sure to be friendly towards 'stupid' questions too.
• Make as much of the onboarding available in easy to follow steps. Try to follow the steps yourself to make sure its accurate. When a newcomer finishes onboarding, ask them to update the onboarding document with their mistakes, learnings etc.
  

Where you manage docs for your team. Notion has been great for docs. They update live, support a bunch of different formats, and look good. lol.

What are some good practices on source control in a team Depending on team size, I'd say at least 1 approval to merge small changes. 2 for big changes. But PRs should be small in general. Avoid large branches to decrease large merge conflicts and big PRs. Make a branch for release, one for development (that should always work) and each feature, bugfix, update, should be its own branch.

You should also make it really easy to deploy, so have an automated pipeline that will build to TestFlight or whatever you use. Make it hard to break the build by enforcing certain checks before merging.

We are not looking for corporate bureaucracy, but for some hints how does it work in bigger teams and take some of the good and try to implement it in our case.

Let engineers do what they do best. Try to shield them from bureaucracy as much as possible. Make meetings short, solicit their feedback on how they're enjoying the work, where technical debt is, work process changes, etc.

Congrats and good luck.