US
for US
- Location
- Charlotte, NC 28273
- Phone
- 2168487236
- Address
- Charlotte, 28273, United States
- Document
- Sahil Resume 2026 PM.pdf
One per right to work. The default is what a posting falls back to when its country matches none of them.
for US
for IN
The resume editor is off on this deployment. To turn it on, set JOBBY_OWNER_PASSWORD (at least 12 characters) and JOBBY_SESSION_SECRET (at least 32 random characters) in the Vercel project's environment variables and redeploy.
Every question answered once, kept for the next form. 200 stored
POLICY: acknowledging a posted salary range
YES, whatever the range. Standing instruction from the user on 2026-08-20. He would rather stay in the process and discuss compensation later than be filtered out at the form. This is ONLY for acknowledge-and-agree questions about a range the posting states. It is NOT the answer to 'what are your compensation expectations' or 'desired salary', which take the stored figures: $120,000 expected for a US role, Rs 30,00,000 for an India role, and $90,000 current fixed base. Never put 'Yes' in a field that wants a number.
POLICY: background check, willingness versus authorisation
WILLINGNESS: Yes, always. Standing instruction from the user on 2026-08-19. Covers 'are you willing to submit to / undergo / complete a background check', including when it is bundled with a drug screen or reference check. Saying he is willing is a statement of intent and it is his to give. AUTHORISATION: still the user's, always park it. 'I authorise the company to obtain a consumer report', an FCRA disclosure and acknowledgement, a signature or initials on a background-check consent form, anything granting a third party the right to pull records. Agreeing to be checked later is not the same act as signing the consent that lets it happen, and only the second one is a binding authorisation.
POLICY: what compensation figure goes in the field when the posting states a band?
THE MIDDLE OF THE BAND. Standing instruction from the user on 2026-08-20. $70,000-$90,000 gives $80,000. $140,000-$180,000 gives $160,000. Do not compute it by eye: python3 scripts/salary.py --band "<the range verbatim>" It handles K suffixes, en dashes, 'to', lakh grouping, LPA and one-sided bands, and returns the figure already formatted the way the band was written. This applies whenever the posting states a band, above or below his own number. Naming a figure above a published band invites a filter; naming one below it leaves money on the table before a conversation has started. NO BAND STATED: use the stored expectation instead, $120,000 for a US role and Rs 30,00,000 for an India role. This is the answer to 'what is your expected compensation'. It is separate from the acknowledge-the-range checkbox, which is always Yes.
POLICY: what current location goes on an application?
Match the posting's region, always. A US posting gets Charlotte, NC. An India posting gets Navi Mumbai, MH. Standing instruction from the user on 2026-08-19. City and state only for a 'current location' or 'where are you based' field. The full street address goes in only when the form asks for a street address, and it is the one on the region-matched resume identity block. Never put a street address on a resume header. A posting outside the US and India still takes the region of the resume being sent, which is the US one by default.
POLICY: exclusion, debarment and ineligibility questions
NO, always. Standing instruction from the user on 2026-08-20. Healthcare employers and government contractors must ask this. Covers exclusion from federal healthcare programs (42 USC 1320a-7b(f)), the OIG exclusion list, debarment or suspension from federal contracting, SAM.gov excluded parties, and state equivalents. Answer No and do not park. This does not extend to criminal history, professional licence discipline, or immigration status. Those still go to the user.
POLICY: how should free-text screening questions be answered?
SIX SENTENCES AT MOST, every answer, no exceptions. Even a question that invites depth ('go five levels deep', 'describe the architecture') gets six sentences; compress rather than run long. Three or four is fine for a simple why-us. Write in Sahil's own voice: read ~/.job-application/voice/answers_sample.txt first, which holds 25 answers he actually submitted and is the ground truth for register. His patterns: open by connecting their problem to his own experience rather than praising them; use 'Honestly,' to pivot to the real reason; name a gap before they find it; close on standing rather than enthusiasm ('I'm not coming in to learn X from scratch'); attach a number to every claim. Never: opening praise, 'passionate', 'thrilled', 'excited to', em-dashes, rhetorical-question openers, manufactured symmetry. Every claim must still trace to the resume, the answer store or the story bank; brevity is not licence to invent.
POLICY: how is an accuracy certification answered, in any field shape?
AGREE, and match whatever the field is. Standing instruction from the user, given for the attestation on 2026-08-19 and extended to name and yes/no shapes on 2026-08-20. CHECKBOX: tick it. YES/NO or radio: Yes. TEXT expecting a name: 'Sahil Sapra'. A date field alongside it: today's date in the format the form shows. THE CONDITION, unchanged: only agree when every answer on the form came from the profile, the answer store or the story bank. Certifying is a statement that everything else on the page is true, so if any field holds something inferred, guessed or composed beyond those sources, park instead of certifying a guess as his fact. Read what the certification actually covers. If it also authorises a background check or consumer report, or contains a non-compete, IP assignment or at-will agreement, park it with the clause quoted. Arbitration alone does not block it.
POLICY: how is 'how did you hear about us' answered?
Company website. Standing instruction from the user on 2026-08-19.\nFREE TEXT: write 'Company website'.\nDROPDOWN: pick the closest equivalent, in this order: Company Website, Careers Page, Company Careers Site, Our Website, Direct. If none of those exist, take the most neutral remaining option: Job Board, Search Engine, Online Search, Other.\nNEVER pick Referral, Employee Referral, or a named employee. Those claim a person vouched for him, which is a different thing entirely and is checkable. Never name a recruiter or a job fair he did not attend.
POLICY: how are interview recording consents answered?
YES, always. Standing instruction from the user, first given on 2026-08-19 and restated for named tools. Covers any interview recording, transcription or AI notetaker consent, whatever the vendor: BrightHire, Metaview, Zoom, Gong, Read, Otter, or an unnamed 'our AI assistant'. Answer yes and do not park. This is consent to being recorded in an interview and nothing wider. It does not extend to a background-check authorisation, a data-processing agreement, or any consent granting rights over his records.
POLICY: how are political contribution questions answered?
NO, always. Standing instruction from the user on 2026-08-19. Financial and investment-advisory firms ask this to satisfy pay-to-play rules, so it appears on most finance applications, worded around any lookback window: two years, five years, 'ever'. Covers contributions to officials, candidates, parties, PACs and political organisations, and covers 'have you or a member of your household'. Answer No and do not park.
POLICY: how are post-employment restriction questions answered?
NO, always. Standing instruction from the user on 2026-08-19. Covers any wording asking whether a previous or current employer restricts him from taking this job: non-compete, non-solicitation, non-dealing, garden leave, notice restrictions, 'are you subject to any agreement that would limit your ability to perform this role', 'do you have any restrictive covenants'. The user has confirmed he is under none. Answer No and do not park.
POLICY: how are relationship and conflict-of-interest questions answered?
NO, always. Standing instruction from the user on 2026-08-19. Covers any wording asking whether he is related to or closely associated with someone who could influence the employer's business: a client's director, officer or senior employee; a government or public official; a regulator; an existing employee of the hiring company; a competitor. Includes 'by birth, adoption or marriage', 'close personal relationship', 'immediate family member'. Answer No and do not park. This does NOT extend to questions about criminal history, immigration status, or anything not in these three categories. Those still go to the user.
POLICY: how should any active-immigration-case question be answered?
No. Standing instruction from the user on 2026-08-19, for this and all future applications. This covers wordings like 'do you have an active immigration case', 'is a petition pending on your behalf', 'any pending USCIS matter'. It does NOT change the sponsorship answers, which remain No for the US and No for India, nor the citizenship answer, which is Indian citizen.
POLICY: how should a US work-authorization question be answered?
Student visa, and sponsorship WILL be required in the future. Standing correction from the user on 2026-08-25, replacing the 2026-08-19 wording that said sponsorship would never be required. DROPDOWN: choose the option describing a student visa or F-1/OPT status. If the list has no student option, choose the one that means authorised to work now with future sponsorship required, and never the one that means no sponsorship will ever be needed. YES/NO 'are you authorised to work now': Yes. YES/NO 'will you require sponsorship': Yes.
POLICY: may an accuracy or truthfulness attestation checkbox be ticked?
YES, when nothing on the form was inferred. Standing instruction from the user on 2026-08-19. This covers wordings like 'I certify the information provided is true and accurate to the best of my knowledge' and 'I confirm I have read the above' when it attaches to an accuracy statement. It does NOT cover binding legal agreements: arbitration agreements, class-action waivers, background-check authorizations and non-competes still go to Needs you.
POLICY: may an acknowledgement checkbox be ticked, or a name typed to acknowledge?
YES, tick it or type 'Sahil Sapra' and today's date. Standing instruction from the user on 2026-08-25, given for Axon's questionnaire acknowledgements and extended to every application. COVERS confirming that something has been read, understood or received: a questionnaire acknowledgement, an at-will employment acknowledgement, a policy or handbook receipt, a privacy notice, an equal-opportunity statement. DOES NOT COVER anything that grants a right or gives something away, which stays with the user: a background-check or consumer-report authorisation, an FCRA disclosure, a drug-test authorisation, an IP or invention assignment, an NDA, a non-compete or non-solicitation, an indemnity, or a waiver of a legal right. Park those, whatever word the form puts in front of them.
POLICY: may an arbitration agreement acknowledgement be ticked?
YES, always. Standing instruction from the user on 2026-08-19. Covers any wording of an arbitration agreement acknowledgement, including 'Applicant Arbitration Agreement Acknowledgement', 'I agree to resolve disputes through binding arbitration', and mutual-arbitration checkboxes attached to the submit step. The user knows this waives court and class-action rights and has decided it is acceptable. Do NOT re-park an application for this reason.
POLICY: may a binding legal agreement (arbitration, class-action waiver, background check) be agreed to?
ARBITRATION: yes, always. Standing instruction from the user on 2026-08-19; see the dedicated arbitration policy entry. EVERYTHING ELSE: no. Background-check authorizations, non-competes, IP assignment and anything else granting rights over the user still go to Needs you with the clause quoted, because the user authorized arbitration specifically and nothing wider.
When may a tailored resume or cover letter be rebuilt after it is created?
ONE BUILD. The first resume and cover letter produced for an application is the one that gets shown and sent, provided it passes the stated guidelines. Do not rebuild a passing document for polish, taste, consistency with other applications, or a second opinion. Rebuild ONLY when an objective gate fails: resume_pdf.py verify reports a difference, ats_match.py reports a non-empty unsourcedTerms list, a frozen field (employment title, date, number, employer, education, certification) does not match the base, the wrong regional base or identity block was used, or the rendered document is corrupted. Iterating inside a single build (render, verify, fix, re-render until the gates pass) is part of building, not a rebuild. If a gate fails, say which gate and why rather than silently redoing the work.
POLICY: how should any relocation question be answered?
ALWAYS YES. Standing instruction from the user on 2026-08-19: answer yes to every relocation question on every application, present and future, regardless of the city or country named. This includes willing-to-relocate, open-to-relocation, able-to-relocate-to-X, and willing-to-work-onsite-at-this-location. Do not surface these as questions for the user and do not qualify the answer.
POLICY: how many applications may be worked on at once, and when is each submitted?
STRICTLY ONE AT A TIME, FILL THEN SUBMIT. Take a single application from start to submitted before beginning the next. Never run two application fills concurrently. The sequence per application is: open it, fill every field from the store, verify by reading values back from the page, log a write-ahead 'submitting' event, click submit once, verify the confirmation, log 'completed' with the resume and cover letter filenames, then and only then start the next one. Supersedes the earlier always-stop-before-submit setting: the user authorised submission on 2026-08-19. If an application cannot be completed (a required answer is missing, an account or OTP or CAPTCHA is needed), park it, log why, and move to the next one rather than stopping the run.
POLICY: typing a name as an electronic signature
Type 'Sahil Sapra', and today's date where the field asks for one, in whatever format the form shows. Standing instruction from the user on 2026-08-20. READ WHAT IS ABOVE IT FIRST. Typing the name IS signing, and the signature covers whatever the certification block says. Sign when that block is an accuracy or truthfulness certification: the information given is true and complete, omissions are grounds for dismissal, the employer may verify what was stated. That is the same thing as the accuracy attestation the user already authorised, and it carries the same condition: only sign when every answer on the form came from the profile, the answer store or the story bank. If anything was inferred, park instead. DO NOT sign when the block also grants rights over him: a background check or consumer report authorisation, an FCRA disclosure, a non-compete, IP assignment, or an at-will employment agreement. Park it with the clause quoted. Arbitration alone is authorised and does not block signing.
POLICY: how are US visa sponsorship questions answered?
SPONSORSHIP WILL BE REQUIRED in the United States. Standing correction from the user on 2026-08-25, replacing the 2026-08-19 instruction that said it never would be. Three different questions, three different answers, and conflating them puts a false statement on a form he signs: 'Are you legally authorised to work in the US?' -> YES. He is authorised now. 'Do you now or will you in the future require sponsorship?' -> YES. 'Are you authorised to work in the US without sponsorship?' -> NO. INDIA is the exception: citizen, authorised, no sponsorship, all three flip. ANYWHERE ELSE he holds no authorisation, so sponsorship would be required. Answer for the country the posting is in. Never carry the US answer onto an India form or the other way round.
Answers are stored on Your Device and mirrored to the board behind this password so you can read them here, including compensation and demographics: this is your board and your data. That changes when a second account exists, and the per-user encryption in the multi-tenant plan is what changes it.