I've seen ones that put datatype validation so you have to enter numeric values. I've been tempted to put "1337" but I doubt whomever sees the form would understand it these days.
They're listing competitive salary, I want competitive salary, makes sense, right?
This Business and Moment...
- Thread starter randomshenans
- Start date
Most are, this one doesn't even have mandatory fields on the form. I could have literally left it blank, the only thing that prevented me from submitting was the T&C's, had to agree to proceed.
Tbh, this is not a great look, when you can't even create a simple application form on your portal. Big red flag IMHO.
Last edited:
I find one of the more irrational design decisions is from workday - it just happens that the common safari credentials experience uses the same credentials for all the workday-operated sites (irrespective of which workday customer) so applicants have to keep resetting their passwords to access to apply for roles.
Anyways - application done.
It did ask if I'd ever been dismissed .. so naturally everyone that's been terminated under 2 years tenure, is going to be Yes at that point! Should prove interesting to understand any feedback
Anyways - application done.
It did ask if I'd ever been dismissed .. so naturally everyone that's been terminated under 2 years tenure, is going to be Yes at that point! Should prove interesting to understand any feedback
Isn't that so they can just host their SaaS stuff under a single domain though? I mean to me it makes sense that they have ABC.workday.com XYZ.workday.com etc for different clients as it must make management of stuff a lot simpler and I don't see much alternative, the issue is more if your browser is caching credentials against a higher level than the full domain name or whatever so you can't easily manage them independently.
Yes = that's precisely what is happening and the obvious architectural decision. However how many people use safari on Mac and iOS devices? That is is the number of affected people.. they started with a technical but not an end user.
I don't think it's their problem to solve though - IMO if Apple can't sort their **** out to properly manage credentials in this sort of scenario where you have multiple logins under a single second level domain, people should be complaining about them, not Workday and doubtless numerous other SaaS providers for which the same presumably applies.
What's the alternative, create thousands of new domains on a per-client basis? That feels like it introduces other problems that could also impact the end user.
What's the alternative, create thousands of new domains on a per-client basis? That feels like it introduces other problems that could also impact the end user.
Last edited:
My point is not who is at fault - my point is the end user experience.
It’s a standard model but the end user doesn’t care and nor should they.
I did, but I stopped.