[vilvadot]

Completely see your point in the privacy aspect, but it is really difficult to offer a good user experience with a project like this without storing data. I don't even consider selling data as part of a business model for my projects but I understand that is opaque to the user and not everyone is like this.

On the second argument, I assume recruiters are seeing tons of resumes presented in the same package daily. I don't think this will affect negatively to the applicants. Hopefully this starts becoming a problem and I get to work and design 100 more templates for variety :)

[avaika]

Moreover, as a person who participated in hiring a lot, a unique design for every CV isn't something I'd be happy with. The more it unified, the easier to scan the paper for the things I'm looking for.

[udayrddy]

(because you being a recruiter/recruited a lot) Out-of-context, shamelessly plugging https://nextRound.ml to consider your feedback. To keep the thread precise to the OP, drop an email at [e-mail] (just in case you want to feedback) .

[jahlove]

Which is a point against these fancy templates. Even if its super popular, it's still not as popular as a boring word document.

The only case for these fancy resumes is for graphic designers in my view, who should be designing the resume themselves, obviously.

[ghego1]

One the second point, you could add the option to change the color scheme/font of each template to arbitrary colors set by the user. In this way the chances that two CV look the same are slightly smaller if the user customizes the template. The next step being a template builder, but I understand that that is probably a much bigger endeavor

[grenoire]

You could always do it the Europass way and embed the metadata in the PDF. Their system can read back its own exports into the interface and allow you to edit the contents. Would still work with your subscription model too.